Invoice Register
Late is measured from the final date for payment, not the invoice date.
Every invoice out, with the final date for payment it belongs to, what came back against it, and how many days it is over. Accounts systems age invoices from the invoice date, but construction contracts pay from the final date for payment, so a ledger can show nothing overdue while a job funds itself from your bank account.
What you get
How it works
The contract's date, not the ledger's
Each invoice carries its cycle due date and its final date for payment, and days over runs from the contract's date. An invoice that is genuinely late looks late, and one that is not does not get chased pointlessly.
The position, at a glance
Invoiced, received, outstanding, overdue and the longest delay, totalled across the register, so the state of the money is one look rather than a reconciliation.
One register, every job
Contract and application references sit on every row, so one file carries every live account and the pattern across them, including the payer who is always exactly this late.
An Excel template with no macros. Only the yellow cells can be edited, the Guide tab explains every step, and it prints on A4. Your contract's terms override the statutory defaults.
Related paid help
For invoices issued, tracked and chased against the contract's dates for you, see the Payment Application Assembly & Issuance service.