Every reconciliation process generates exceptions -- transactions that could not be automatically matched, amounts that don't agree, timing differences that fall outside the normal window. How you triage and resolve those exceptions determines whether the close takes 3 days or 12 days. The matching work on clean transactions is the same either way; the exception handling is where the time goes.
This article walks through a practical exception handling workflow for accounts payable reconciliation: how to categorize exceptions by root cause, how to structure the triage process, and how to build a resolution workflow that clears the exception queue in hours rather than days.
The Exception Categories That Matter Most in AP Reconciliation
Not all exceptions are created equal. Before building a triage workflow, it helps to understand the distribution of exception types in a typical AP reconciliation. Most exceptions fall into a small number of repeating categories:
Timing exceptions: The bank feed shows a payment that has not yet been recorded in the accounts payable ledger, or a payment has been recorded in AP but not yet settled at the bank. These are not errors -- they represent the normal lag between AP entry and bank settlement. They resolve themselves within a few business days and require no action other than documentation and re-check at the next close.
Amount differences: The bank shows a different amount than the AP ledger for what appears to be the same vendor and similar date. Common causes: bank applied a wire fee that was not accrued in AP; vendor applied an early-payment discount that was not reflected in the original invoice entry; the payment was split differently between AP and the bank due to partial credit memo application. These require controller review and a correcting entry.
Unmatched bank entries: Items in the bank feed that have no corresponding AP ledger entry. Common causes: direct charges to the bank account that bypassed AP entirely (bank fees, automatic subscriptions, card charges), payments made from an account not connected to the AP module, or new vendors not yet set up in the AP system.
Duplicate candidates: Two entries that appear to represent the same payment -- same vendor, same or similar amount, close dates. These require careful review before confirmation because confirming a true duplicate as two separate payments creates an overpayment that may be difficult to recover.
Unmatched AP entries: Payments recorded in AP but not appearing in the bank feed within the expected settlement window. These represent potential errors in the AP entry (wrong payment date, wrong bank account), voided checks that were not properly closed in AP, or payments that were initiated but failed to process.
Building the Triage Workflow
Effective exception triage requires two things: a categorized exception queue and a clear ownership assignment for each category. Without categorization, the controller is reviewing every exception from scratch each time, re-establishing context and deciding how to handle it on the fly. Without ownership assignment, exceptions sit in the queue while the controller waits for someone else to provide information.
Step 1: Age-sort the queue. Exceptions that have been open the longest are the most likely to be genuinely problematic rather than simple timing differences. New exceptions from the last 3 days are probably timing issues that will self-resolve. Exceptions older than 5 business days that have not resolved require active investigation.
Step 2: Auto-resolve timing exceptions. Any exception where the bank entry and AP entry are within the expected settlement window for the payment type -- 1-2 days for ACH, 3-5 days for check -- should be marked as pending timing resolution and removed from the active triage queue. Re-check these at the next close cycle.
Step 3: Route amount differences to AP. Amount difference exceptions require the AP team to review the original invoice, any credit memos applied, and any fees charged. Give them the bank entry and AP entry side by side with the amount difference clearly labeled. Set a resolution deadline of one business day.
Step 4: Research unmatched bank entries. For bank entries with no AP counterpart, the first question is: was this a payment that should have gone through AP but didn't? Check the bank description against known vendor names and recent direct charges. If it is a bank fee or a known subscription that regularly charges the account directly, create the AP entry and mark it resolved. If it is unrecognized, escalate to the CFO.
Step 5: Hold duplicate candidates pending verification. Do not confirm either side of a potential duplicate until you have verified that both entries do not represent separate legitimate payments. Review the original invoices. Check whether the vendor has applied two separate invoice numbers. If confirmed duplicate, void one side and recover the payment if already disbursed.
The Documentation Standard for Resolved Exceptions
Every resolved exception should carry a brief documented explanation before it is closed. This is not bureaucracy -- it is the audit workpaper. An auditor reviewing the reconciliation workpaper will see the exceptions and ask about them. "Timing difference - settled 3 days post-period, confirmed bank statement Dec 5" is a complete answer. "Resolved" with no context is not.
The documentation standard for each resolved exception should include: the category (timing / amount difference / unmatched / duplicate candidate), the root cause in one sentence, the resolution action taken, and the date resolved. For amount differences, include the correcting entry reference. For unmatched items, include the AP entry created. For timing exceptions, include the bank date of eventual settlement.
In a manual spreadsheet workflow, this documentation lives in cell comments or a separate notes column. In an automated reconciliation system, it is captured as a structured field in the exception record. Either way, the content requirement is the same.
Setting Resolution SLAs
Exception queues that are not time-bounded drift. The controller reviews the exceptions, finds they require input from AP or the CFO, routes the request, and the exception sits for three days while the requester is in meetings. The close deadline arrives with five exceptions still open. The controller either holds the close or closes it with open items, both of which are worse than having set a resolution SLA in the first place.
A practical SLA structure for AP reconciliation exceptions:
- Timing exceptions: auto-resolved pending settlement, no SLA needed
- Amount differences: AP team response within 1 business day; correcting entry by end of close period
- Unmatched bank entries: controller research within 1 business day; escalation to CFO same day if unrecognized
- Duplicate candidates: hold from confirmation for 2 business days; controller verification; recovery initiated if confirmed
- Unmatched AP entries: AP team research within 1 business day; void or correction initiated within 2 days
These SLAs assume a close cycle that starts on day 1 and needs to complete by day 7. If the reconciliation process starts later, the SLAs compress accordingly. The point is not the specific day counts but the discipline of setting expected resolution times and following up when they are missed.
Preventing Recurring Exceptions
Some exceptions recur every month because of a structural mismatch that has not been addressed: a vendor that always settles one day outside the matching window, a bank account not connected to the AP module, a regular subscription that charges the bank directly without going through AP. These are not new exceptions to investigate every month -- they are known patterns that could be resolved at the source.
Keep a recurring exceptions log alongside the monthly exception queue. When the same item appears in the recurring log for three consecutive months, treat it as a process improvement item. Either adjust the matching window for that vendor, connect the missing bank account, or create a standing AP entry for the direct charge. Reducing the recurring exception rate is the most efficient long-term improvement to AP reconciliation close time.
The Practical Result
A well-structured AP exception handling workflow -- categorized queue, clear ownership, documented resolutions, time-bounded SLAs -- transforms exception management from an open-ended investigation into a predictable checklist. Instead of the close stalling at "reconciliation not complete" while exceptions sit unresolved, the controller works through a categorized queue with clear next steps for each item.
For most growing companies, the shift from open-ended exception investigation to structured triage reduces exception resolution time by 60 to 70 percent. Combined with automated matching on clean transactions, it is the specific combination that moves the close from 12 days to 3 or 4.
