Wrong details survive the template
Customer, scope, amount and dates should come from an approved source.
Invoicing system for service and project businesses
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.
North Street Kitchen
Emergency website repair and recoveryCustomer, work, document and balance share one reference.
No email, payment or accounting entry
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.
Customer and address present
Description and supply date present
Amount approved by the named owner
The invoice begins with the approved work record, not a blank document and somebody’s memory.
Draft ready for approval.
What a polished PDF can still hide
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.
Customer, scope, amount and dates should come from an approved source.
A correction needs its own controlled route and trace, not a quiet PDF replacement.
The amount and reference must resolve to the current invoice and balance.
Automation must stop for paid, disputed, void or review states.
One document through every state
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.
Customer, description, dates, tax treatment and amount are checked.
The issued document and delivery event become part of the record.
A reminder is prepared only while the current state permits it.
Part-payment, full payment, refund or credit updates the balance and downstream record.
Choose where the accounting truth lives
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.
Create, issue, deliver and track a small volume with clear ownership and export.
Useful when a complete accounting platform would be excessive.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.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
Approved completion provides the customer, work description, amount and owner.
See customer records and CRM →A named approval or deliverable releases the agreed stage amount for review.
See the acceptance tests →Schedules account for pauses, cancellations, price changes and failed delivery.
Choose the billing route →Every payment carries the invoice reference and updates the remaining balance.
See payment integrations →Connections checked before the quote
Ernest checks the accounting product, plan, API or import, numbering owner, customer match, tax configuration, payment provider and failure route before promising automation.
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
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.
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
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.
Creates and follows the document inside the business workflow.
can connect toKeeps and submits records for the obligations it is recognised to support.
Chasing follows state, not a calendar alone
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.
Real operational proof
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 recordPriority, project detail and invoice creation share one private workflow.
React · Node · invoicing built inAcceptance is the awkward invoice handled well
Invoicing system price
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 pricesPrice rises with several businesses or series, complex VAT or currencies, milestones, recurring billing, part-payments, large migration, many roles, detailed reports or external APIs.
Support is optional. Accounting, payment, email, hosting or other providers may charge their own fees directly.
Before automating invoicing
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.
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.
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.
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.
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.
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
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.