Estimates and quotes
A priced document a customer accepts before the work starts. Not in the product today.
Time is entered against a job, approval recognises the revenue, the invoice raises the receivable, and the payment is recorded against it. Each is a screen you open — the connection between them is the posting.
Built for a single business in a single currency.
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.
The work is recorded once, where it happens — not re-keyed later from a notebook.
Approve the time. For time-and-materials work, approval is the moment revenue is recognised, with a balanced posting written in the same step.
This is the beat that makes the books trustworthy: nothing reaches the ledger until a person approves it.
Issue the invoice from its own screen. The receivable is raised and the tax line written as it posts.
Corva One does not pretend the job turns itself into an invoice — a person issues it.
Record the payment against the invoice, apply it, or reverse it if something was wrong.
You record the payment. Corva One is not a payment processor.
Naming them is the point. These are committed work, not shipped behaviour, and this site will not imply otherwise.
A priced document a customer accepts before the work starts. Not in the product today.
Work orders, assigned visits and recurring agreements. Not in the product today.
Approved time reaches the job now; putting a charge or a directly-paid expense on a job is planned.
The invoice screens are built and the books behind them are real. The step that raises a job's invoice from the job itself is not in the product yet.