Operating exceptions that appear too late in the books

Why exceptions surface after the month has closed

Operating exceptions appear too late in the books because operations records them as work problems, and finance only sees them when an invoice, credit note or write-off finally arrives. The cure is a shared rule about which exceptions carry a cost, who must log them, and a review rhythm that brings them to finance before the month closes. Without that rule, the books describe last month's surprises rather than this month's position.

Picture a delivery that fails inspection. The operations team arranges a redelivery, absorbs extra transport and pays overtime to meet the new date. Each step is handled competently on the ground. Finance learns about them piecemeal: an unexpected transport bill, a payroll variance, perhaps a customer deduction much later. By the time the pieces are connected, the job's margin has already been reported wrong.

Exceptions that always carry a financial consequence

Operations deals with plenty of exceptions that cost nothing. The governance task is for the operations head and the finance head to agree which categories must always be reported to finance, whatever their size.

• Rework or redelivery caused by quality failures, whether the cost falls on you or a supplier
• Damaged, lost or expired stock that will need writing down
• Overtime or extra shifts authorised outside the plan
• Customer complaints likely to end in a credit note, deduction or contractual penalty
• Supplier failures that may support a claim or price adjustment
• Work done outside the contract scope that should be billed as a variation
• Equipment breakdowns needing unplanned repair or hire

One exception register, two sets of owners

Variations and unplanned hire swing in opposite directions. An unbilled variation is revenue the company earned but may never invoice, while unplanned hire erodes a job's margin quietly until the bill arrives. Both need to reach finance early.

Keep exceptions in one register both teams can read, rather than in operations logs finance never opens. Operations owns the entry: what happened, which job, what was done about it and a rough cost estimate if one is known. Finance owns the financial treatment: whether to accrue, issue a credit, raise a supplier claim or bill a variation. Each team edits only its own fields.

Two status sets help. The operational status tracks whether the problem is resolved on the ground. The financial status tracks whether the cost or revenue has been recognised. An exception closes only when both are closed, which stops the familiar situation where the site considers a matter finished and finance has not yet heard of it.

Encourage operations to log an exception the day it happens, with a rough estimate, even when the cost is uncertain. Finance would rather adjust an estimate later than meet a cost for the first time on a supplier invoice. A blank cost field is acceptable; a missing entry is not. Give each entry a simple reference so it can be quoted on supplier claims, credit notes and journal entries, linking the operational record to the accounting one.

Aligning the review rhythm with the month-end close

Exceptions should reach finance on a rhythm, not when someone remembers. A short weekly look at the register between an operations manager and the finance person responsible for the close catches most items while there is still time to accrue them. A firmer cut-off before month-end, set by finance and published in the shared calendar, tells operations when late entries stop counting for the current period.

Use the review to spot patterns as well as individual items. If the same supplier keeps appearing, or the same site keeps logging overtime, the conversation shifts from bookkeeping to fixing the cause. Finance brings the cost view, operations brings the explanation, and both leave with an owner for the fix. The review also feeds customer conversations. Where an exception creates a claim against the customer, such as a variation or a delay the customer caused, the account manager needs to know before the next invoice goes out, so the claim is raised while the facts are fresh.

Write the rules down. A one-page exception policy, agreed by both department heads and revisited when the business changes, avoids arguments later about whether something should have been reported.

Recording exceptions where both teams can see them

Fasttrade's BukuOP covers work tracking, status and exceptions, and BukuCloud covers bills, payments and the P&L and balance sheet reports finance closes each month. If you want exceptions logged on the ground to reach the books in time, we can help you define the register and scope how information should pass between operations and finance in a conversation with both heads.

Frequently asked questions