How are reconciling exceptions documented for audit?

Short answer

Each exception is logged with its amount, age, cause, support, owner, and resolution, and signed review shows the open items explain the full difference.

Auditors test reconciliations by selecting reconciling items and asking for evidence. The documentation needs to show what each exception is, that someone investigated it, and that it was resolved or carried forward on purpose.

What auditors look for

Completeness: Open exceptions sum to the difference between the ledger and the source, with no unexplained plug.
Support: Each item ties to evidence outside the reconciliation, such as a statement line, invoice, deposit slip, or journal entry.
Aging: Old items are visible and explained. A reconciling item that rolls forward for several periods is a common audit finding.
Review evidence: The reconciliation shows who prepared it, who reviewed it, and when.
Corrections: Adjusting entries are approved and posted in the right period.

Fields recorded for each exception

Field	What it records
Item	Date, description, reference number, and which side it appears on
Amount	Unmatched amount, plus the original amount for a partial match
Age	Days outstanding from the original transaction date, not the date first flagged
Cause	Timing difference, missing entry, duplicate, amount error, misclassification, or unknown
Support	Link or reference to the document that backs up the explanation
Owner	Person responsible for resolving it
Resolution	Correcting entry, follow-up, or expected clearing date
Status	Open, in progress, or resolved, with the resolution date

Sign-off and carried-forward items

Sign-off: Preparer and reviewer names and dates, plus reviewer notes on any item they questioned.
Carried-forward items: Prior period exceptions show as resolved or carried forward with their original date, never silently dropped.
Aging buckets: Exceptions grouped by age, such as under 30, 30 to 90, and over 90 days, so stale items stand out.
Retention: The reconciliation, support, and review evidence are kept together for each period so they can be pulled on request.

Building the audit trail with Ramp Stack

Each exception a Ramp Stack agent flags sits in an editable workpaper, so the team can add owner, support, and status columns and keep the evidence next to the item. The Session Audit Log records each step the agent took in plain English, which shows how every exception was identified. Correcting entries are posted only once the accountant has approved them.