A construction payment exception register should track the question, evidence, contractual basis, amount, owner, decision and financial disposition. Use statuses that distinguish a candidate from a confirmed issue and a posted correction from recovered cash. Preserve rejected findings so review quality can be measured.
What to take away
- Give every exception a precise decision and responsible owner.
- Keep candidate exposure out of confirmed-benefit totals.
- Link related findings to prevent duplicate counting.
Design the row around the decision
Use a stable exception ID and link it to the project, contract, change, application and transaction where relevant. State the question in plain language. “Was invoice 418 included in both CO-12 and the base line?” is more actionable than “possible financial issue.”
Attach the source clause, conflicting records, calculation and proposed treatment. Identify the person who can supply evidence and the person authorized to decide the commercial outcome. They may be different. Record the last verified date and the next action so the register does not become an aging list with no route to resolution.
Keep evidence, decision and settlement stages distinct
A useful sequence starts with candidate, evidence requested and under review. The decision may be cleared, confirmed or unresolved. A confirmed issue can then move through approved adjustment, executed change or posted credit, and settlement where applicable.
Avoid one “closed” label that mixes false positives, administrative closure and recovered cash. Keep a reason and source for each closure. An issue can be contractually disputed but fully documented; another can be arithmetically clear but not yet agreed. Those differences matter to the portfolio owner.
| Status | What it means | Required source |
|---|---|---|
| Candidate | Rule or reviewer raised a question | Trigger and competing records |
| Evidence gap | Decision cannot yet be made | Specific missing record |
| Cleared | Treatment accepted | Reviewer explanation |
| Confirmed issue | Error or agreed problem established | Authorized decision |
| Adjustment posted | Correction entered | Ledger or executed reference |
| Settled | Financial disposition verified | Cash or valid offset evidence |
Worked example: three flags represent one issue
A fictional duplicate payment generates a near-match invoice flag, a repeated supporting-document flag and an apparent excess-cash flag. All relate to one $12,000 obligation settled twice. Link the three candidates to one parent issue before reporting exposure.
After confirmation, the potential excess is $12,000. If the supplier issues a $12,000 credit and it is applied to a later payment, record the credit and application as stages of the same outcome. The total benefit does not become $24,000. Preserve the component flags for methodology review while using the parent issue for financial reporting.
Age by next decision and payment cutoff
Track when the evidence request was sent, when a response is due and when the relevant payment decision occurs. Use actual project commitments rather than invented universal deadlines. An item awaiting a contract interpretation needs a different escalation from a supplier who has not provided a credit memo.
Review reopened findings and overwritten amounts. If new evidence changes a $20,000 candidate to a $3,000 confirmed issue, retain both the original and final basis. That history helps assess screening quality and prevents an inflated original flag from continuing to appear in a benefit dashboard.
Make the register useful to the control owner
At each review, show new issues, decisions needed, changes since the last version and confirmed outcomes. Keep sensitive source records behind approved access rather than copying them into every summary. Export the register so the owner can inspect the decision history independently.
Buildalytic can be evaluated on the collection and follow-up around one exception queue. Ask the team to scope additional reconciliation and writeback explicitly. Include a cleared finding, a disputed interpretation and a settled adjustment in the demonstration. The register should help the authorized owner decide, without allowing an automated flag to approve a payment or declare a recovery.
Common questions
Should cleared findings be deleted?
Preserve their disposition and reason. They show what the review covered and support measurement of false positives.
Can a posted credit be counted again when applied?
No. Record the application as evidence of the same issue's disposition and use a consistent benefit-recognition rule.
Sources and editorial notes
Prepared with AI assistance. Reference date: 2026-11-05. Worked examples are illustrative and are not customer results. Product details can change; confirm the current scope and terms before rollout.
How we prepare and update field notesScope one evidence-backed review workflow.
Bring a redacted contract, payment packet and one unresolved question. Discuss the supported collection and follow-up steps, any additional scope and the human review needed to validate the result.
Start with the call, text or record your team already handles. Review the expected outcome and the human handoff before choosing a rollout.
Discuss your review workflow Explore the relevant capability
