Ledger
General ledger and chart of accounts
Fiscal periods, account structure, and every posting the work produces.
Accounting
Not records for your accountant.Actual books.
Corva One keeps real double-entry books — a general ledger, periods you can close, and GAAP-structured statements — generated by your day-to-day work rather than re-keyed from it.
It calculates and posts sales tax; it does not file returns. For a single business in a single currency.
One action, one posting / 01
The invoice writes the entry itself.
Revenue is recognised when the work is approved, not when the invoice goes out—so issuing the invoice settles the receivable and adds the tax line rather than counting the revenue twice. That is what ASC 606 asks for, and it is what the engine does.
What is in the books / 02
The ledger, and everything around it.
All of it built and reachable today. Where something is planned rather than shipped, this page says so.
Where it stops / 03
What this is not.
A boundary stated once is worth more than a feature list stated twice.
It is not a tax system. Corva One calculates and posts sales tax on invoices. It does not file returns, produce 1099s, or determine nexus.
It does not take payments. You record a payment against an invoice, apply it, or reverse it. There is no card processing, no ACH, and no payment provider behind it.
It is single-entity and single-currency. Multi-currency and multi-entity are deliberate future work, not omissions.
There is no inventory ledger. Stock, receiving and vendor-bill matching belong to Corva ERP, a different product.
Direct job costing is planned. Approved time reaches the job today, so job views show what the work earned. Attributing a directly-paid expense to a job is committed work that is not built yet.