Skills / Reconciliation and close

Vendor Statement Reconciliation

A vendor statement and an AP subledger will almost never agree line for line by coincidence. Timing differences, unapplied credits, and genuinely missing invoices are normal; the actual job is classifying every difference explicitly instead of letting a vendor's claimed balance and the subledger's balance sit unreconciled with no record of why. At volume, across dozens or hundreds of vendors, that classification work is exactly the kind of high-frequency, low-complexity comparison that quietly eats a week of an AP team's month without ever showing up as a single hard problem to solve.

What it does

For each vendor, this skill classifies every statement line and every open subledger line into one of four outcomes: matched (the reference ties on both sides with the amount agreeing), disputed (the reference is found on both sides but the amounts disagree), missing-from-subledger (the statement shows an invoice or credit with no matching reference in our subledger), or in-subledger-not-on-statement (an open subledger invoice whose number never appears on the statement). The reconciled balance is built from the subledger's open total plus each classified item's dollar effect, then compared to the statement's own implied ending balance; agreement within a cent is a tie, and anything else is reported as a named difference, never plugged.

The one rule it can't skip

It never concludes that a discrepancy is resolved. Every classified item carries a proposed next step, request an invoice copy, apply a credit, confirm with the vendor, explicitly labeled SUGGESTED (not a determination), and the skill stops there. Settling a disputed amount needs the underlying invoice, contract, or purchase order, and that call stays with whoever is working the vendor relationship, not the reconciliation itself.

How the classification actually runs

Each statement line is matched against the subledger first by reference number, the strongest available key; a match with agreeing amounts closes the line, and a match with disagreeing amounts is classified disputed rather than accepted as close enough. A statement line with no subledger match at all is classified missing-from-subledger, a possible unrecorded liability if it's an invoice or an uncaptured credit if it's a credit memo. Separately, every open subledger invoice is checked against the statement, and one that never appears there is classified in-subledger-not-on-statement rather than folded into the same bucket as a missing invoice, since the two point to opposite root causes. The reconciled total is then built from the subledger's open balance plus every classified item's effect and compared to the statement's own ending balance.

What it won't do

It won't draft or send anything to the vendor; the proposed action tells AP what to do next, not what to say, and it's always labeled a suggestion rather than a determination. It won't merge missing-from-subledger and in-subledger-not-on-statement into one undifferentiated gap, since the first usually means our records are incomplete and the second usually means the vendor's statement or our payable is stale. And it won't force a reconciled balance to zero; a real difference is reported in dollars and named, never absorbed into a residual line.

Inputs and output

InputsA vendor statement extract across all vendors (reference, date, amount, line type: invoice, credit, or payment), and the AP subledger export covering the same period
OutputA per-vendor reconciliation with every line classified matched, disputed, missing-from-subledger, or in-subledger-not-on-statement, a tied or named-difference total, and a suggested action per discrepancy
Who it's forAP teams running statement reconciliations across a vendor base, and whoever follows up on the proposed actions

Adopt's agents run this reconciliation across your full vendor base on the cadence you choose, classify every line into its own explicit bucket, and route anything genuinely disputed for AP to work directly with the vendor. Start free with Fino, or book a pilot to run it against your messiest vendor statement.