Raising one
If CRM is enabled, the picker reads its companies. If not, you type the details, and they are stored on the invoice.
Description, quantity, unit price, tax. Lines post to the income accounts and dimensions you choose.
Due date, payment terms, and a reference if the customer needs a purchase order number on it.
Emailed with your branding, with a link the customer can pay through.
Reminders go out on the schedule you set. The most reliable improvement to cash collection is reminders that happen without anyone remembering.
When an invoice is raised, the customer details are copied onto it. Renaming the company in CRM afterwards does not rewrite invoices already issued — which is correct: a document sent to a counterparty should not change retrospectively.
Invoices
£46,980 outstanding · £12,400 overdue
| Invoice | Customer | Due | Amount | Status |
|---|---|---|---|---|
| INV-1044 | Acme Inc | 28 Mar | £3,600.00 | Sent |
| INV-1042 | Harbour Logistics | 9 Mar | £8,400.00 | Paid |
| INV-1039 | Meridian Group | 1 Mar | £5,200.00 | 11 days late |
| INV-1037 | Coastline Ltd | 24 Feb | £7,200.00 | 17 days late |
| INV-1045 | Northwind Retail | — | £1,150.00 | Draft |
Getting paid
An invoice carries a payment link. The payment itself is taken by the Client Portal, which holds the processor relationship, and the settlement comes back to Accounting as a payment against the invoice. That split is the same one the platform uses for its own billing: one system decides what is owed, one collects it.
When the money lands in the bank, the bank line reconciles against the invoice. For a single payment against a single invoice this is automatic. For a processor payout covering many invoices at once, the payout is settlement rather than income and is handled through Commerce.
Ageing and chasing
The ageing report buckets receivables by how overdue they are, and the invoice list filters the same way. Reminders are configured per customer or globally, and the audit trail records what was sent and when — which matters when a customer says they never received it.
| Bucket | Typical action |
|---|---|
| Not yet due | Nothing. |
| 1–30 days | Automated reminder. |
| 31–60 days | A person makes contact. |
| 61–90 days | Stop supplying, decide about escalation. |
| 90+ days | A commercial decision, not an accounting one. |
What this does not do
There is no quote object that converts to an invoice.
Subscriptions are billed through the Client Portal, not raised on a schedule here.
An invoice recognises when it posts. There is no deferred-revenue schedule engine.
Reminders send; there is no dunning ladder with approval steps.
Logo, colour and footer. There is no layout editor.
Questions
Can we invoice in another currency?
Yes, and it is translated to the base currency at posting.
Can a customer see all their invoices in one place?
Yes, through the Client Portal if they have access to it.
What happens if we void an invoice?
It is reversed, not deleted, and the audit trail keeps both.