AP reconciliation is not just a month-end accounting task. It is the control that proves what the business actually owes.
The accounts payable reconciliation process compares what your company records as payable with the evidence behind those obligations: vendor statements, invoices, purchase orders, receiving records, payment activity, the AP sub-ledger, and the general ledger. The goal is to prove that every payable balance is real, complete, accurate, approved, and ready for close.
Sage describes accounts payable reconciliation as comparing AP ledger balances with vendor statement balances so the business knows what it owes suppliers. In practice, finance teams need more than a balance check. They need a repeatable workflow for collecting evidence, matching transactions, resolving exceptions, approving adjustments, and preserving an audit trail.
What’s in this article?
- What accounts payable reconciliation includes
- When finance teams should reconcile AP
- A step-by-step AP reconciliation process
- A practical workflow table for owners and evidence
- Common mistakes that create close risk
Why accounts payable reconciliation matters
Accounts payable is where operational reality becomes a financial obligation. A vendor ships goods, a contractor submits an invoice, a project owner approves work, a payment run is prepared, and accounting records the liability. If those steps are disconnected, the AP balance can look right while the underlying evidence is weak.
Good reconciliation helps prevent duplicate payments, missed invoices, misstated liabilities, vendor disputes, weak accruals, and delays. It also gives finance leaders confidence that the AP aging report, vendor balances, payment records, and general ledger tell the same story.
Atlar’s AP reconciliation guidance emphasizes collecting vendor documentation and comparing the AP sub-ledger with the general ledger. That is the core control. The team must be able to trace the balance from ledger number to supporting documents and back again.
Accounts payable reconciliation process
Use this process as a month-end workflow, then tighten the cadence for high-volume vendors, contractor programs, marketplaces, global payment operations, or any account with elevated risk.
- Confirm the opening balance. Start with the prior period’s approved reconciliation. If the ending balance from the prior period does not match the current opening balance, stop and resolve the break before reviewing new activity.
- Collect source documents. Gather vendor statements, invoices, purchase orders, receiving records, contracts, payment confirmations, credit memos, debit memos, and AP aging reports.
- Match vendor statements to AP records. Compare vendor statement balances with your AP sub-ledger by vendor. Identify invoices the vendor shows but your system does not, and invoices your system shows but the vendor does not.
- Match invoices to approvals and receipts. For PO-backed spend, confirm the invoice matches the purchase order and proof of receipt or service completion. For non-PO spend, confirm the correct business owner approved the obligation.
- Compare the AP sub-ledger to the general ledger. The detailed vendor balances should tie to the AP control account. Any difference needs an owner, cause, and adjustment path.
- Review payments and open items. Confirm paid invoices cleared correctly, outstanding invoices remain valid, credits are applied, and voids or failed payments are reflected in the right period.
- Resolve exceptions. Route missing invoices, duplicate records, disputed quantities, tax differences, currency differences, and approval gaps to the right owner instead of leaving them as comments in a spreadsheet.
- Record adjustments with evidence. Post correcting entries only after the reviewer can see the reason, source document, approver, and period impact.
- Approve and lock the reconciliation. Separate preparation, review, and approval where possible. Store the reconciliation package with enough evidence for audit, close review, and future vendor questions.
AP reconciliation workflow table
The table below gives finance teams a simple operating model for turning reconciliation into a controlled workflow.
| Step | Primary owner | Evidence needed | Common exception |
|---|---|---|---|
| Opening balance check | Staff accountant | Prior approved reconciliation and current AP ledger | Beginning balance does not tie |
| Vendor statement match | AP specialist | Vendor statement, AP aging, invoice list | Vendor shows missing invoice or unapplied credit |
| Invoice support review | AP specialist and business owner | Invoice, PO, receipt, contract, approval record | Invoice lacks receipt or business approval |
| Sub-ledger to GL tie-out | Accounting team | AP sub-ledger, general ledger, journal entries | Control account does not match vendor detail |
| Exception resolution | Assigned exception owner | Dispute notes, corrected document, approval trail | Duplicate, wrong period, tax, FX, or payment issue |
| Review and approval | Controller or finance manager | Completed reconciliation package | Unresolved item lacks owner or deadline |
How often should AP be reconciled?
Most companies reconcile AP during month-end close. Higher-risk areas may need weekly or daily checks. Numeric notes that reconciliation frequency should depend on transaction volume, risk, and account type. That principle matters for AP because one company may have a few predictable vendors while another manages thousands of contractor payments, marketplace payouts, or project-based supplier invoices.
A practical rule: reconcile high-volume vendors, strategic suppliers, and payment-critical accounts more often than low-risk vendors. If a vendor dispute could stop delivery, delay a project, or create compliance exposure, do not wait until close to find the break.
Common AP reconciliation mistakes
The first mistake is treating reconciliation as a spreadsheet exercise instead of a control workflow. A spreadsheet can compare numbers, but it will not prove ownership, approvals, source documents, or exception status.
The second mistake is reconciling only at the vendor balance level. Vendor totals can match while individual invoices, credits, payment timing, taxes, or currency conversions are wrong. Finance teams should investigate material open items, aging anomalies, and unusual changes in vendor balances.
The third mistake is unclear segregation of duties. Tipalti’s reconciliation guidance describes preparation, review, and approval as distinct responsibilities. Smaller teams may not have perfect separation, but they still need a real reviewer.
The fourth mistake is letting exceptions live in email. Missing approvals, disputed invoices, duplicate records, and vendor credits should have owners, due dates, and resolution evidence. Otherwise, the same exceptions reappear every month.
Where Workhint fits
Workhint helps finance and operations teams turn AP reconciliation from a manual checklist into a live work system. A team can route missing invoice support to the right owner, track vendor exceptions, require approval evidence, connect payment status to project or contractor records, and keep blockers visible until resolved.
For teams managing contractors, vendors, agencies, marketplaces, or global payments, the reconciliation problem is often bigger than accounting software. The work crosses finance, operations, procurement, legal, project owners, and external partners. Workhint fits where those roles, approvals, documents, payment steps, and reporting need to operate together.
FAQ
What is accounts payable reconciliation?
Accounts payable reconciliation is the process of comparing AP records with vendor statements, invoices, payment activity, the AP sub-ledger, and the general ledger to verify what the business owes.
What documents are needed for AP reconciliation?
Common documents include vendor statements, invoices, purchase orders, receiving records, contracts, payment confirmations, credit memos, debit memos, AP aging reports, and general ledger detail.
Who owns accounts payable reconciliation?
AP specialists or staff accountants usually prepare the reconciliation. A controller, accounting manager, or finance leader should review and approve it, especially for material balances or high-risk vendors.
How is AP reconciliation different from invoice approval?
Invoice approval confirms that a specific invoice should be paid. AP reconciliation verifies that all payable balances, invoices, credits, payments, and ledger entries are complete and accurate for the period.
What should happen when AP reconciliation does not match?
The team should identify the source of the difference, assign an owner, collect supporting evidence, correct the invoice or ledger record if needed, and document the resolution before approval.
Conclusion
An effective accounts payable reconciliation process gives finance teams confidence that vendor obligations are complete, accurate, approved, and supported. Start with source documents, match vendor statements to AP records, tie the sub-ledger to the general ledger, resolve exceptions with owners, and preserve evidence for close and audit review. The result is a stronger control for every vendor, contractor, project, and payment workflow.
Leave a Reply