Sales invoice RE-2026-0288

One outstanding item with everything attached: line items, payment terms, reminder history.

RE-2026-0288 · Fairbrook Farm Machinery LLC

in default — reminder level 2

Customer account 10064 · Rockford · sales invoice of 22 April 2026

Invoice

Invoice total: $14,821.75 gross
Net amount: $12,455.25
Sales tax: $2,366.50
Period of supply: March 2026
Order reference: AB-2026-0177 · injection-moulded parts, series 4

Payment terms

Payment terms: 30 days net, due 22 May 2026
Early-payment discount: 2 % if paid by 6 May 2026 — period elapsed
Payment method: bank transfer, no direct debit mandate on file
Outstanding: $14,821.75 — no part payment received

Default and reminders

In default since: 23 May 2026 — stored rule: the day after the due date
Reminder level: 2, created on 10 July 2026
Next level no earlier than: 24 July 2026 — stored waiting period of 14 days
Default interest: 9 percentage points above the base rate — stored rate for business customers
Flat charge: $40.00 — stored for business customers, not yet applied

Invoice lines

Line	Description	Quantity	Unit price	Amount
10	DescriptionMoulded part type 4A, series production	Quantity4,200	Unit price$1.85	Amount$7,770.00
20	DescriptionMoulded part type 4B, series production	Quantity1,500	Unit price$2.40	Amount$3,600.00
30	DescriptionTool correction after first-article inspection	Quantity1	Unit price$640.00	Amount$640.00
40	DescriptionSorting and inspection labor	Quantity12	Unit price$34.00	Amount$408.00
50	DescriptionPackaging and freight	Quantity1	Unit price$37.25	Amount$37.25

Net total $12,455.25 · Sales tax $2,366.50 · invoice total $14,821.75

From order to outstanding item

Order confirmation AB-2026-0177
14 Feb 2026
Delivery and delivery note LS-2026-0611
27 Mar 2026
Sales invoice issued
22 Apr 2026
Due date
22 May 2026 · 30 days net
Reminder levels 1 and 2
5 June and 10 July
Level 3 or hand-over
in the reminder proposal of 31 July

History of the item

Added to the reminder proposal
31 Jul, 7:05 AM
The waiting period since level 2 has elapsed. Level 3 is proposed and awaits approval.
Reminder run
Call from the customer logged
18 Jul, 2:22 PM
A complaint about series 4 was announced. There is no invoice reduction and no credit note, so the item stays outstanding in full.
A. Kendrick
Reminder level 2 created
10 Jul, 6:40 AM
Reminder with a deadline of 24 July. Default interest shown, the flat charge was not applied.
Reminder run
Reminder level 1 created
5 Jun, 6:40 AM
Payment reminder without charges, as set out in the reminder level rule.
Reminder run
Due date reached
22 May, 11:59 PM
No payment received. The item moves into the "1 to 14 days" age band.
System
Sales invoice posted
22 Apr, 9:12 AM
Created from delivery note LS-2026-0611 and attached as a PDF to the customer file.
A. Kendrick

The project frame

How Awelior would approach this project

Colworth Plastics is invented — the way it is built is not. None of this is work delivered for a client. It is the shape we would give such a project — with the same depth, but without a client who would have to answer for it.

Where it starts

At Colworth Plastics the outstanding items sit in a spreadsheet, the reminder run in a handwritten calendar, and when sales want to know whether a customer has paid, they phone accounts. The question is not whether reminders go out but whether they go out in time — and whether anyone knows first that a customer is in the middle of a negotiation.

Decisions

The reminder run is a process with an approval
A list is proposed and sent after approval. Chasing automatically is technically easy and commercially risky: one reminder to the wrong customer costs more than the entire time saved.
Invoice records, not invoice rows
Every invoice has a view of its own with lines, steps and history. Only there does it say why an item is open — and that is the answer sales need on the phone.
Reporting on its own screen, not as the entry page
The entry screen shows what has to happen today. Reporting sits alongside because it answers a different question — key figures as a start screen are the fastest route to a system that looks good and helps nobody.

Deliberately left outNo bookkeeping. This is the receivables view and not a finance ledger: chart of accounts, VAT and year-end stay where they belong, and this system feeds them.

What is in it

Screens: 5
Content blocks: 18
Languages: 4

Five screens, in all four languages, with sidebar, header and stated role. Navigation works; tables, board, calendar, charts, step chains and forms are rendered and inert. Invoice numbers, customers and amounts are invented.

How it would go on

Payment matching
Importing bank statements and allocating payments — automatically where it is unambiguous, and with a worklist for the rest.
Connection to the ledger
Invoices, payments and reminder stages have to flow both ways, or a second version of the payment status appears.
Escalation
What happens after the third reminder: delivery stop, debt collection, court proceedings — with clear responsibilities.

Talk through your project

Sample data

An application like this for your business?

Ledger Book is invented — the way it is cut is not. Applications like this come out of the processes a business already runs.

Talk about a solution Back to the software solutions The service page: Business software

Sample application by Awelior. Invented business, invented data, nothing stored.