An expense can serve a legitimate business purpose and still breach a documented rule. Preserve the original finding, establish which policy applies and record who is authorized to decide the exception.
Identify the rule that produced the finding
Begin with the policy version in force when the expense occurred. Record the relevant category, employee grade, amount, currency and effective dates. A limit from a newer policy or another business unit can produce a precise calculation for the wrong rule.
Keep spending limits separate from approval authority. The ordinary limit for a category may be $150 while a manager has authority to approve up to $500. The larger authority does not automatically remove the original policy exception. The company's exception process determines whether that manager may authorize a departure and what evidence is required.
Also distinguish a confirmed failure from missing information. A receipt marked absent and a receipt-status field omitted from the export are different conditions. In the second case, the first action may be to obtain the missing record rather than ask the employee to defend a breach.
Work a fictional operational exception
In this fictional example, a field technician buys a replacement diagnostic tool for $186.40 to complete a scheduled customer equipment repair. The applicable equipment-expense limit is $150. The employee reports that the receipt is missing, and company policy requires one for this amount. The approving manager's authority is $500.
The excess over the category limit is $36.40. The amount under review remains $186.40. Neither figure alone establishes an accounting misstatement or an amount that should be rejected. The reviewer needs evidence of the purchase, its business purpose and the basis for any permitted exception.
| Question | Evidence to request | What remains separate |
|---|---|---|
| Was the tool needed for the repair? | Work order, technician's explanation and relevant service record. | Business need does not establish the price or payment. |
| What was bought and paid? | Merchant receipt or replacement invoice, with payment support. | A card entry alone may not identify the purchased item. |
| Why was the limit exceeded? | Availability, urgency and the policy's exception conditions. | An explanation needs evaluation against the applicable rule. |
| Who may approve the exception? | Current authority record and independent approval. | Approval authority and spending-policy compliance are distinct. |
| Was it already reimbursed? | Claim history and payment record. | A new receipt should not create a second reimbursement. |
A replacement receipt might resolve the documentation issue while leaving the spending-limit exception intact. Conversely, an authorized policy exception does not prove that the employee paid the stated amount. Record each conclusion rather than applying one “approved” label to every question.
Write an exception rationale that explains the decision
A useful rationale identifies the rule, the circumstances, the supporting documents and the reason the exception is permitted. “Business expense” is too broad to explain why a specific limit or documentation requirement was waived. Include the decision-maker's authority and the date the decision occurred.
Keep uncertain facts visible. If the merchant has not supplied a replacement receipt, say what alternative evidence was reviewed and what the policy allows. Do not mark the receipt present merely because someone approved reimbursement. The evidence condition and the business decision should remain distinguishable.
Where an approval happens after reimbursement, retain that sequence. A later review may resolve the outstanding question, but it does not establish that the original prepayment control operated. The review record should explain both the transaction's disposition and any process follow-up.
Preserve the original claim through correction and review
Retain the submitted claim, the policy references used, the finding and subsequent evidence. If a category was entered incorrectly, record why it changed and who made the correction. Rerun relevant checks against the corrected input, then connect the new result to the earlier one.
For work under PCAOB standards, audit documentation connects procedures, evidence and conclusions and identifies the people who performed and reviewed the work. That principle is useful when designing a review record, although an operational expense log is not itself a complete audit workpaper. See PCAOB AS 1215: Audit Documentation.
Look for repeated causes once individual items are resolved. Recurring missing receipts may indicate an upload problem; repeated urgent purchases may indicate a procurement gap. Define the population before drawing that conclusion. A few selected exceptions cannot establish how often the issue occurs across the business.
Use OpenAuditor's expense and approval checks separately
The financial-audit pack supports expense checks for supplied limits, receipt status, employment dates, period and population-based duplicate or split criteria. Its receipt check uses a supplied status field; it does not authenticate an uploaded receipt. The default receipt threshold is a product setting, not a statement of tax law or your company's policy.
An expense-approval decision has separate checks for authority, independence, approval timing and support from the underlying claim. When a failed claim is approved with a recorded exception and rationale, evaluating that rationale may require a qualified judgment question. Recording an exception does not automatically turn the claim into a pass, and an unresolved claim remains unresolved.
Keep human disposition and the original verification result together. The results reference explains decided and unresolved findings; the guide to materiality and control exceptions helps distinguish the rule breach from its significance. Use the batch review workflow when the same process needs to cover a population of claims.