HVAC & equipment repair
Log the labour while the call is still fresh. Approve it and the revenue is recognised—with the books written in the same step.

HVAC, plumbing, electrical, appliance and equipment repair. Log the labour on site. Approve the time and the revenue is recognised; issue the invoice and the receivable and the tax line are written with it. Nothing left to rebuild at eleven at night.
Built for a single business in a single currency. You record payments against invoices—Corva One is not a payment processor.
If the work happens at a customer's site, the financial record should begin there too—not on your kitchen table at 11pm.

Log the labour while the call is still fresh. Approve it and the revenue is recognised—with the books written in the same step.

Small jobs stop leaking money—every hour and every part lands on the invoice, not in a notebook.

Time lands on the job as you log it, approval recognises the revenue, and the ledger entry is written in the same step.
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 fix 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.
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 crew moves to the next call, and afterwards nobody is certain it ever reached an invoice.
Once on site while the job is happening, then again when someone re-keys it into whatever holds the numbers.
Rebuilding what happened from memory, job sheets and a bank feed—weeks after the detail was fresh.
The job is closed, 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.
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. Customers, 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 jobs passing between people, and keeps working as the crew 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 job sheets 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. Corva One calculates and posts sales tax; it does not file returns. 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 coming soon. Everything below describes what the product does today, and says plainly where it stops.
No. You run jobs, time, parts and invoices—the double-entry happens behind the work you approve. Your accountant sees proper books; you see your jobs.
Not yet. Corva One is coming soon, and final availability and product details will be published here before access opens.
Not yet. Importing customers, items and opening balances is planned, not built—the supported migration path will be published before access opens.
No. Nothing that touches money posts until a person approves it, and every entry carries the name of whoever approved it.
Planned, not built. Estimates, work orders, assigned visits and recurring agreements are committed work that is not in the product yet—this page will not pretend otherwise.
Pricing has not been published. It will be here before access opens, along with what each package includes.