Corva One · Products coming soon For repair and trade businesses · Corva One home
Corva One
Coming soon
A field service technician at work
Corva One · For repair professionals

Finish the job.The books are already done.

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.

Jobs and timeInvoices and paymentsReal double-entry books
Who this is for / 01

Built for the trades that fix things.

If the work happens at a customer's site, the financial record should begin there too—not on your kitchen table at 11pm.

01

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.

02

Handymen & appliance repair

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

03

Plumbing & electrical

Time lands on the job as you log it, approval recognises the revenue, and the ledger entry is written in the same step.

One continuous flow / 02

Work → Approve → Invoice → Paid.

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.

01

Work

Enter time against the job, priced from your service catalogue's rates.

02

Approve

Approval recognises the revenue for time-and-materials work, with a balanced posting in the same step.

03

Invoice

Issue it from its own screen — the receivable is raised and the tax line written as it posts.

04

Paid

Record the payment against the invoice, apply it, or reverse it if something was wrong.

The problem / 03

The work is the easy part.

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.

Fragmentation

Five apps to manage one job.

A calendar, a spreadsheet, an invoicing tool, a payments app and whatever your accountant uses. None of them agree, and you are the integration.

Revenue leakage

You did the work. Did it get billed?

Time gets logged, the crew moves to the next call, and afterwards nobody is certain it ever reached an invoice.

Re-keying

The paperwork happens twice.

Once on site while the job is happening, then again when someone re-keys it into whatever holds the numbers.

Reconstruction

Month end is archaeology.

Rebuilding what happened from memory, job sheets and a bank feed—weeks after the detail was fresh.

Late visibility

You find out what the job earned afterwards.

The job is closed, the invoice is out, and only then does anyone add up what it actually brought in.

Accountant hand-off

Your accountant asks for something you cannot produce.

The request is reasonable. Assembling it means going back through months of records held in four places.

Choose your package / 04

One record. Two ways to run it.

Nothing changes underneath—the same jobs, the same invoices, the same books. What changes is how much coordination the product asks of you.

For individualsComing soon

Corva Solo

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.

Customers and jobs
Time and charges
Invoices, payments and books
Explore Corva Solo
For crews and teamsComing soon

Corva One Teams

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.

Shared customers and jobs
Time approval and ownership
Connected invoicing and books
Explore Corva One Teams
The books / 05

Not records for your accountant. Actual books.

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.

Real double-entry books

A general ledger, a chart of accounts and fiscal periods you can close.

Written as you work

Every approved financial action posts a balanced entry in the same step — never assembled afterwards.

Ready for your accountant

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.

Built around trust / 06

Clear by design.

Software that runs the money needs honest boundaries and dependable records, whatever size you are.

01 · Ownership

Know who is responsible.

An owner and a status stay with the work, so the next action is visible.

02 · Evidence

Keep the why nearby.

Notes, costs and approvals stay attached to the job they explain.

03 · Boundaries

Say what the product is.

Corva One runs client work and the books it produces—and this site says plainly where that stops.

Read about security principles
Straight answers / 07

A connected product—without inflated claims.

Corva One is coming soon. Everything below describes what the product does today, and says plainly where it stops.

Do I need to know accounting to use Corva One?

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.

Is Corva One available now?

Not yet. Corva One is coming soon, and final availability and product details will be published here before access opens.

Can I import from QuickBooks or a spreadsheet?

Not yet. Importing customers, items and opening balances is planned, not built—the supported migration path will be published before access opens.

Does anything post to the books without me?

No. Nothing that touches money posts until a person approves it, and every entry carries the name of whoever approved it.

What about estimates, scheduling and dispatch?

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.

What will it cost?

Pricing has not been published. It will be here before access opens, along with what each package includes.

Corva One · Coming soon

Run the job.
Keep the books.

Choose your package Read the FAQ