Internal system

Invoice Generator

Invoices raised from the confirmed order rather than retyped into a template — and payment reminders that go out on schedule without anyone maintaining a list.

Order to invoice

  1. Order confirmed

    Accepted quotation becomes the source of truth

  2. Invoice raised

    Line items, tax treatment and terms carried over

  3. Sent and logged

    Delivered to the customer and recorded against the account

  4. Due-date tracking

    Every invoice has a status, not just a date

Why we built it

The order was already agreed — so why retype it?

An accepted quotation already contains everything an invoice needs: the customer, the scope, the amounts and the terms. Copying that into a separate document is duplicate work, and duplicate work is where mismatches appear.

Chasing was the second problem. Follow-up happened when someone had time, which meant older invoices quietly slipped down the list.

What it does

Issue, track, remind

The invoice is generated from the confirmed order, so the numbers match by construction. Once it is sent, the system holds a status against it — sent, due, overdue, part-paid, settled.

Reminders are scheduled from that status. Accounts only gets involved where a reminder has not worked and a conversation is actually required.

The flow

From confirmed order to collected payment

  1. Order confirmed

    Accepted quotation becomes the source of truth

  2. Invoice raised

    Line items, tax treatment and terms carried over

  3. Sent and logged

    Delivered to the customer and recorded against the account

  4. Due-date tracking

    Every invoice has a status, not just a date

  5. Reminders

    Scheduled before and after the due date

  6. Escalation list

    Accounts sees only what needs a human call

What changed

The difference in day-to-day work

No re-entry

The invoice inherits the order, so the amounts on the two documents cannot drift apart.

Ageing is visible

Outstanding invoices are a live list rather than something assembled at month end.

Reminders are routine

Polite, scheduled reminders go out whether or not anyone is thinking about collections that week.

Escalation is deliberate

A call happens because the system flagged it, not because a customer happened to come to mind.

Cleaner conversations

When a customer is called, the full history of the invoice and its reminders is in front of the caller.

Feeds the dashboard

Collections status flows into the same daily view as enquiries, quotations and orders.

Collections should not depend on who remembered to call.

If invoicing and follow-up are still manual, that is usually the quickest place to return time and cash.