On this page Jump to section
Find the recurring cause
Compare the exception with the task’s normal trigger, input, and handoff. A missing receipt, a changed bank description, and a failed approval are different causes even when the task status is simply late. Escalate changes to recurring transactions or rules instead of fixing them in the log.
Record the expected task before the failure
Start with the recurring task's name, scheduled run, responsible person, and expected input. Include the normal completion evidence: a saved report, a reviewed queue, or a document reference. Without that baseline, “late” can mean several different problems and the next owner will have to investigate from scratch.
Preserve the original due date when a task moves. Add a revised review date separately so the history still shows when the exception began. If the task was completed elsewhere, link the completion evidence rather than creating a duplicate work item.
Use a cause that points to an action
- Required document absent
- What the preparer recordsThe missing document reference and request history
- Useful next stepAssign the person who can supply it
- Source data changed
- What the preparer recordsThe old expectation and the new observed value
- Useful next stepAsk the workflow owner to review the difference
- Access unavailable
- What the preparer recordsThe affected task and access request reference
- Useful next stepRoute through the approved access process
- Approval outstanding
- What the preparer recordsThe named reviewer, request date and decision needed
- Useful next stepFollow up with that reviewer
- Output does not match the expected result
- What the preparer recordsThe output reference and specific discrepancy
- Useful next stepHold the task for a reviewer to investigate
Describe what was observed without guessing a cause. A changed bank description, for example, is evidence of a changed description; it does not prove that a matching rule should be changed. Keep proposed fixes separate from approved changes.
Keep recurring occurrences connected
If the same issue returns next week, create a dated occurrence linked to the earlier exception. This lets the workflow owner see frequency and recurrence without erasing the previous resolution. Record whether the earlier fix was temporary or intended to prevent the issue from returning.
A useful weekly review asks which exceptions are newly opened, which remain blocked, which have reopened, and which were closed with evidence. Review repeated causes separately from isolated missing documents. A long-running access issue needs a different owner and response from a single delayed receipt.
Write a handoff another person can act on
An illustrative exception note could say: “The scheduled report was prepared, but the reviewer could not reconcile one source reference. Report and supporting document links are attached. Review owner: the designated account reviewer. Next step: confirm the source reference before accepting the report.” This identifies the completed work, the unresolved question and the decision boundary.
Avoid notes such as “waiting” or “please fix.” Name the dependency, the responsible person, and the next review date. Do not include passwords or sensitive financial records in the exception description; use approved restricted references.
Close only against the expected result
Before closing an exception, check the original completion criteria and attach the result or reviewer confirmation. Record who accepted the result and whether any follow-up remains. If the resolution changes a recurring template, access permission or bookkeeping rule, link the separately authorized change instead of using the exception log as authorization.
Keep unresolved work visible at handoff. The purpose of the log is to make recurring work dependable and traceable, not to make every status look complete. Bookkeeping support can help organize the collection queue, document follow-ups and reviewer handoffs around the process you already approve.
Related resources
Compare the service fit on the QuickBooks VA services page, then use the free consultation form to map the first handoff. For platform context, review QuickBooks Online.



