Invoicing system for service and project businesses

Approved work in. Clear invoice out.

Create the invoice from the work already agreed, issue it once and keep due, disputed and paid states current. A focused invoicing workflow is usually £1,500 - £4,000.

For an existing accounting product, website or private system. Provider fees, accountant advice and HMRC-compatible software remain separate unless named in the proposal.

Invoice statesynthetic example
INV-DEMO-104£480.00

North Street Kitchen

Emergency website repair and recovery
Work approvedIssuedDuePaid

Customer, work, document and balance share one reference.

One triggerapproved work creates the draft
One numberassigned when the invoice is issued
One statedue, disputed, part-paid or paid
One traildelivery, correction and payment

No email, payment or accounting entry

Start with approved work. Follow the invoice state.

Choose a synthetic work record, create its draft, issue the pretend invoice, then inspect the reminder and payment routes. Nothing is sent, charged, submitted or stored.

Interactive example
01
Operational recordApproved work
Completed job

Website repair marked complete

Customer
North Street Kitchen
Charge for
Emergency website repair and recovery
Supply date
1 September 2026
Approved total
£480.00

Customer and address present

Description and supply date present

Amount approved by the named owner

02
Invoice recordCurrent document and balance
waiting

No draft yet

The invoice begins with the approved work record, not a blank document and somebody’s memory.

What a polished PDF can still hide

The invoice looks finished. The record is not.

An invoice made from memory can use the wrong customer, description, amount or due date. A sent PDF then drifts away from the job, payment and accounts. Staff chase a settled balance, overwrite an issued document or cannot explain which version the customer received.

Copying

Wrong details survive the template

Customer, scope, amount and dates should come from an approved source.

Version

The sent invoice is overwritten

A correction needs its own controlled route and trace, not a quiet PDF replacement.

Payment

Money has no dependable match

The amount and reference must resolve to the current invoice and balance.

Chasing

A settled customer gets reminded

Automation must stop for paid, disputed, void or review states.

One document through every state

Draft, issue, deliver, settle.

An agreed business event creates a draft from the customer and work record. Required details and totals are checked before one unique invoice is issued and delivered. Due, disputed, part-paid, paid, void and credited states remain visible, while reminders and accounting exports follow that current state.

A draft may change. An issued invoice keeps its identity and history. Payment changes the balance, while a receipt acknowledges what was paid.

  1. 01
    Draft

    Build from approved work

    Customer, description, dates, tax treatment and amount are checked.

  2. 02
    Issue

    Assign the unique number

    The issued document and delivery event become part of the record.

  3. 03
    Manage

    Follow due, dispute and correction states

    A reminder is prepared only while the current state permits it.

  4. 04
    Settle

    Match payment and export the result

    Part-payment, full payment, refund or credit updates the balance and downstream record.

Choose where the accounting truth lives

Generate, connect or build around the work.

Best for a service or project business that repeatedly copies approved work into invoices, loses time matching payments or needs invoice status inside its operational workflow. Ernest can improve an existing accounting connection, add a contained invoice route or build bespoke billing logic when milestones, recurring work or several systems make the standard route unreliable.

01The process is contained and manual

Focused invoice route

Create, issue, deliver and track a small volume with clear ownership and export.

Useful when a complete accounting platform would be excessive.
02Accounts already use a suitable product

Connected accounting workflow

Send approved operational data into the chosen product and return the current invoice status.

Usually best when the accountant already has a source of truth.
03Billing follows unusual operational rules

Bespoke billing system

Handle milestones, retainers, allocations, several payers or custom approval and reporting.

Worthwhile only when the workflow earns the complexity.

The trigger changes, the control does not

Invoice the right event. Keep the right reference.

Deposits, balances and part-payments

Every payment carries the invoice reference and updates the remaining balance.

See payment integrations

Connections checked before the quote

The job creates the invoice. The result returns.

Ernest checks the accounting product, plan, API or import, numbering owner, customer match, tax configuration, payment provider and failure route before promising automation.

Customer, job or project recordApproved amount and supply detailsCurrent invoice stateAccounting software and exportPayment match, receipt and follow-up

Test and live invoice series stay separate

Duplicate creation and delivery are handled safely

A failed connection enters review with its source intact

Required details before clever automation

Make the document valid. Make the state useful.

UK invoices normally need a unique number, supplier and customer details, a clear description, supply and invoice dates, amounts, VAT where applicable and the total owed. Business type and VAT treatment can add requirements.

01
IdentitySupplier, customer and unique number
02
SupplyDescription, dates, quantity or extent
03
MoneyNet, tax where applicable, total and terms
04
ControlIssue, delivery, correction and payment trail

Your accountant confirms the invoice wording, tax point, VAT treatment, retention and accounting source for your exact business. The system applies those agreed rules consistently.

Digital records without a false promise

An invoice app is not automatically tax software.

Making Tax Digital for Income Tax now applies to some sole traders and landlords, and qualifying records must be created and kept using compatible software. Where several products are used, required records need a permitted digital link rather than manual copying.

The UK has also announced structured VAT e-invoicing from April 2029, while technical guidance is still developing. A current build should keep invoice data structured and connections replaceable, not bury the only record inside a decorative PDF.

Boundary checked in the proposal

Operational invoicing

Creates and follows the document inside the business workflow.

can connect to

Compatible accounting software

Keeps and submits records for the obligations it is recognised to support.

Chasing follows state, not a calendar alone

Polite when due. Silent when it should stop.

Payment terms are agreed before issue. Reminders can be prepared before or after the due date, but a dispute, payment, credit, void or unclear match pauses the automatic route for human review.

  1. Before dueUseful reminder with invoice and payment route
  2. Due todayClear amount, reference and agreed terms
  3. OverdueEscalation follows your approved process
  4. StopPaid, disputed, credited, void or needs review

Real operational proof

The invoice starts inside the project.

Ernest built a private Projects CRM in React and Node that orders work by priority and creates invoices from the project record. It is a private operational system, so there is no public login presented as a live invoicing demo.

Read the Projects CRM record
Projects CRM20+active projects managed in one tailored system

Priority, project detail and invoice creation share one private workflow.

React · Node · invoicing built in

Acceptance is the awkward invoice handled well

Test the corrections and the failures.

01Duplicate issueA repeated event does not create another live invoice.
02Missing required detailThe document stays draft until the issue is resolved.
03Correction or creditThe issued record is not silently overwritten.
04Part-paymentThe received amount and remaining balance are both visible.
05DisputeAutomatic reminders pause for a named owner.
06Provider unavailableThe source remains recoverable and enters review.

Invoicing system price

A range with visible reasons.

The written proposal confirms the invoice trigger, required data, state model, roles, numbering owner, connections, migration, tests and handover. The timeline follows that audit.

See all website and system prices
Typical one-off build£1,500 - £4,000timeline quoted after invoice and workflow audit
  • Invoice data, trigger and state model
  • Issue, delivery, payment and correction routes
  • Agreed accounting or operational connections
  • Migration test, acceptance tests and handover

Price rises with several businesses or series, complex VAT or currencies, milestones, recurring billing, part-payments, large migration, many roles, detailed reports or external APIs.

Standalone support£35 - £45/moorRun Growthincluded in £199/mo

Support is optional. Accounting, payment, email, hosting or other providers may charge their own fees directly.

Before automating invoicing

Invoice workflow questions.

Can invoicing connect to Xero, QuickBooks, FreeAgent or another accounting product?

Often, yes. I first check your product, plan, API or approved import route, invoice numbering ownership, tax configuration and error behaviour. The accounting product should remain the source of truth where your accountant needs it to be. Provider fees and access are shown separately in the proposal.

Will this invoicing system submit VAT or tax information to HMRC?

Not unless the agreed route uses software and connections recognised for that specific HMRC obligation. An invoice generator is not automatically Making Tax Digital compatible accounting software. Your accountant confirms the record, VAT and reporting treatment, and I can connect the operational workflow to suitable software without claiming the website itself is your tax adviser.

Can invoices be raised from completed jobs, milestones or recurring services?

Yes. We define the exact event that makes a draft appropriate, who approves it, how the amount is calculated and when the supply and due dates apply. A recurring schedule still needs exceptions for pauses, price changes, failed delivery and cancelled work.

Can customers pay an invoice online?

Yes. A hosted or embedded payment route can carry the invoice reference and amount, while a verified provider result updates the current balance. Card details stay with the payment provider. Partial payments, fees, refunds and bank-transfer matching are scoped separately where needed.

Can payment reminders stop automatically when an invoice is paid or disputed?

Yes, if the system has a dependable paid or disputed state. Reminder timing, wording, recipients and escalation are agreed first. A failed payment connection or an unresolved match goes to a human review route instead of allowing another automatic chase to be sent blindly.

Can existing customers and invoice history be migrated?

Yes, when the source can be exported and the records are reliable enough to map. I test a recoverable sample first, preserve original references, agree how open balances and credits are treated, and avoid importing unnecessary personal data. The volume, format and condition of the history affect the quote.

Bring three invoices and their source records

Raise the invoice without rebuilding the facts.

Show Ernest what starts an invoice, who approves it, where accounts live and how payment is matched today. You will know whether to tidy the existing route, connect accounting software or build focused billing logic.

Discuss your invoice workflowExplore every system and add-on Email or telephone only. No obligation and no accounting-software reseller pitch.