Work
Enter time against the job, priced from your service catalogue's rates.
Enter and approve time, issue invoices and record payments—and every financial action writes a balanced entry into real double-entry books as it happens.
Built for a single business in a single currency. You record payments against invoices—Corva One is not a payment processor.
The work itself varies enormously. What you sell, how you price it, whether it happens at a customer's site or at your own desk, whether you do it alone or hand it between people — none of that changes what has to be true underneath.
Something was agreed. Work happened. It was worth money. Somebody has to bill it, collect it, and be able to explain it later. Corva One keeps those five facts on one record instead of five systems.
The work and the books are the same record, not two systems that have to be reconciled.
Four beats on one record. The connection between them is not a handoff you configure — it is the balanced posting each financial action writes as it happens.
Enter time against the job, priced from your service catalogue's rates.
Approval recognises the revenue for time-and-materials work, with a balanced posting in the same step.
Issue it from its own screen — the receivable is raised and the tax line written as it posts.
Record the payment against the invoice, apply it, or reverse it if something was wrong.
Whatever you sell and however you price it, the same failures turn up the moment the work lives in one system and the money lives in another. None of them are dramatic—which is why they survive for years. They cost hours every week, and some of them cost revenue you never notice missing.
A calendar, a spreadsheet, an invoicing tool, a payments app and whatever your accountant uses. None of them agree, and you are the integration.
Time gets logged, the work moves on, and afterwards nobody is certain it ever reached an invoice.
Once while the work is happening, then again when someone re-keys it into whatever holds the numbers.
Rebuilding what happened from memory, notebooks and a bank feed—weeks after the detail was fresh.
The work is finished, the invoice is out, and only then does anyone add up what it actually brought in.
The request is reasonable. Assembling it means going back through months of records held in four places.
Corva One closes the gap they all come from: the work and the books are one connected record, not two. If you want it in the language of your own trade or practice, these go deeper — repair & trade, independent professionals, professional practices.
Nothing changes underneath—the same jobs, the same invoices, the same books. What changes is how much coordination the product asks of you.
Everything the business needs when the business is you. Clients, jobs, time, invoices and real books—with none of the coordination machinery you would only be administering for yourself.
The same record, shared. Who did the work, who approved the time and what that approval posted stay explicit—so the story survives people handing work to each other, and keeps working as the team grows.
One action, one posting. The invoice you issue writes the entry itself—so the books are a by-product of the work rather than something assembled from it weeks later.
A general ledger, a chart of accounts and fiscal periods you can close.
Every approved financial action posts a balanced entry in the same step — never assembled afterwards.
GAAP-structured statements, reconciliation and an audit package for whoever reviews the books.
For a single business in a single currency. No inventory ledger—that is Corva ERP.
Software that runs the money needs honest boundaries and dependable records, whatever size you are.
An owner and a status stay with the work, so the next action is visible.
Notes, costs and approvals stay attached to the job they explain.
Corva One runs client work and the books it produces—and this site says plainly where that stops.
Corva One is for anyone who does client work and has to bill for it—a site visit, a shoot, an audit, a repair. It is coming soon, and everything below describes what the product does today, and says plainly where it stops.
Anyone who does client work and has to bill for it. The work can be a site visit, a shoot, an audit or a repair—what matters is that something was agreed, work happened, and somebody has to invoice it and explain it later. If you want it in the language of your own trade or practice, the repair & trade, independent professional and professional practice pages go deeper.
Not yet. Corva One is coming soon, and final availability and product details will be published here before access opens.
Work → Approve → Invoice → Paid. Time is entered against a job, approval recognises the revenue with a balanced posting, the invoice raises the receivable and writes the tax line, and the payment is recorded against it. Each of those is a screen you open—the connection between them is the posting, not a sync you configure.
A general ledger with a chart of accounts and fiscal periods, manual journal entries with an approval trail, period close, financial statements presented on the ASC 210/220/230 structure, account reconciliation, and an audit package for whoever reviews your books. Corva One calculates and posts sales tax; it does not file returns.
No. You run clients, jobs, time and invoices. The double-entry happens behind the work you approve—your accountant sees proper books, you see the operation.
Pricing has not been published. It will be here before access opens, along with what each package includes.
Notes on why the gap between the work and the books opens in the first place—and what it costs while it stays open.
Field notes on keeping the work and the money in one place.