Why Construction Accounts Need a Single Exception Register

A shared inbox is where construction invoice problems go to hide.

One person asks a question in email. Another chases the supplier in WhatsApp. Someone in accounts parks the invoice. The project manager thinks it is being handled. By the time month end arrives, nobody has a clean view of what is still open, who owns it, or what should happen next.

A single exception register fixes that by turning scattered queries into one visible workflow.

Why a shared inbox is not a control

Construction businesses often treat an inbox as if it were a tracker. It is not.

An inbox can receive a message, but it cannot reliably answer the questions that matter for accounts:

• What is the issue?
• Who owns it?
• What is blocking it?
• When does it need to be resolved?
• Has the supplier, site team, or commercial lead already replied?

Without those answers, an invoice query is just a loose thread.

That is how costs drift. The invoice sits unresolved for days, then gets posted because everyone is tired of chasing it. The commercial record loses clarity, and the next person to touch the job has to start over.

What belongs in the exception register

The register should only hold items that are genuinely unresolved.

Typical entries include:

• missing PO number
• wrong job or site reference
• invoice value above the approved amount
• partial invoice or staged claim
• disputed scope or rate
• missing delivery evidence
• unapproved variation
• duplicate invoice risk
• retention query
• VAT or document issue

The point is not to create a second inbox with a better name. It is to capture the exception in a standard format so the business can manage it properly.

Give every exception an owner

If nobody owns the next step, the issue will sit there until someone gets annoyed enough to chase it again.

Every exception should record:

• the supplier or subcontractor
• the job or project reference
• the reason it is blocked
• the person responsible for actioning it
• the next action
• the date it needs a reply by
• the current status

That one extra line of ownership changes the workflow completely. Accounts is no longer asking, "Has anyone looked at this?" They can see who has it and what happens next.

This matters most when the same issue needs input from more than one person. For example, accounts may need the project manager to confirm the job, while the site team needs to check delivery, while the commercial lead decides whether the value should be queried or approved.

Sort by urgency, not inbox order

An exception register is only useful if it helps the team prioritise.

The most urgent items are not always the oldest messages. They are the ones that affect payment runs, margin, or supplier relationships.

A good weekly review usually asks:

1. What is due before the next payment run?
2. Which items are blocking month-end posting?
3. Which suppliers are waiting for an answer?
4. Which issues have been open too long?
5. Which entries can now be closed, posted, or escalated?

That is a much better rhythm than letting the inbox decide the order of work.

Keep routine invoices out of the register

The register should not become a dumping ground for everything.

Routine invoices that already match the PO, job reference, and approval trail should move through the normal process. The register is for exceptions only.

That distinction matters because a messy register creates the same problem as a messy inbox: too much noise, too little signal.

If the team starts logging every invoice, the register becomes another list nobody trusts. If it only holds genuine blockers, it stays readable and useful.

Use the register to improve the process, not just the chase

The best exception registers do more than help accounts chase faster.

They also show patterns. For example:

• one supplier repeatedly sends invoices without PO numbers
• one site keeps missing delivery evidence
• one project manager often approves work informally first and records it later
• one type of invoice keeps getting queried for the same reason

Those patterns matter because they point to a workflow problem, not just a one-off delay.

If the same issue keeps appearing, the business should fix the standard process rather than just chasing harder.

What a useful weekly review looks like

A weekly exception review does not need to be heavy.

It only needs enough discipline to keep the list moving:

• review open items by ageing and due date
• confirm the owner for each entry
• close anything that has been resolved
• escalate anything that is still blocking payment or posting
• note recurring issues for process improvement

That rhythm gives accounts and commercial teams a shared view before month end turns the list into a fire drill.

How BuilderDash helps

BuilderDash helps construction teams keep purchase orders, invoice checks, approvals, and exceptions in one workflow instead of scattering them across email, chat, and memory.

That means the business can see what is blocked, who owns it, and what still needs a decision before the cost is posted. It also makes it easier to spot recurring problems, because the same issue is visible across jobs rather than hidden inside separate inboxes.

Suggested internal links

• What to Do When an Invoice Arrives Without a PO Number
• How to Stop Invoice Queries Going Missing Between Site and Accounts
• What Every Construction Invoice Pack Should Contain Before Accounts Touch It
• How to Reduce End-of-Month Invoice Chasing in Construction

Call to action

If exceptions are still living in inboxes, phone calls, and half-finished notes, move them into one register before they disappear again. BuilderDash keeps the exception, the owner, and the next action together so the team can clear blockers without rebuilding the story every time.