What belongs in a cloud expense exception register

An exception register should help AP, FP&A, and the budget owner finish an action—not archive unexplained noise. Each row needs enough detail that someone who was not in the audit room can still resolve it.

Minimum fields: exception ID, vendor, invoice or usage reference, amount, nature of the issue, suspected cause, owner, target date, and status. Optional but useful: related purchase order, cost centre, and whether the item affects cash or only the accrual.

Avoid dumping every tiny rounding difference into the register. Set a threshold aligned with your materiality for cloud spend. Below that threshold, summarise in a single line so attention stays on items that move the close.

Close exceptions with evidence: a credit note number, a corrected journal, or a signed acceptance that the charge stands. Open items older than one close cycle deserve a status review with the controller, not another silent carry-forward.

Back to Field Notes