vendor statements show invoices the AP subledger has no record of: the month-end accrual keeps missing the same supplier

TL;DR

When the vendor's statement lists invoices your AP ledger has never seen, and it is the same supplier every month, the invoices are dying at a specific intake point: sent to a personal inbox, rejected by the capture tool for a recurring reason, sent to the wrong entity or site, or blocked because the supplier's master record is duplicated and the invoices sit on the twin. Take the vendor statement as the population and check each missing invoice against every intake surface: email inboxes and capture queues, the other entities' AP, and duplicate vendor records. Accrue the genuine missing invoices at close from the statement so the liability is complete this month, then repair the intake route - one monitored address, capture rules fixed, vendor record merged - and confirm next month's statement arrives clean.

vendor statements show invoices the AP subledger has no record of: the month-end accrual keeps missing the same supplier

Use this when

• A supplier's statement shows invoices absent from the AP subledger, repeatedly the same supplier.
• The month-end accrual process relies on AP data and therefore misses these invoices too.
• The supplier sends invoices by a channel different from your standard intake, such as site email or paper to a branch.

Not for this skill when

• The vendor statement is wrong and bills another customer. Confirm identity with the vendor before accruing anything.
• The invoices exist in AP but under a different supplier name variant. Merge or alias the vendor records rather than rebuilding intake.

Steps

1. Obtain the vendor's current statement and mark every invoice not found in the AP subledger after searching by number, amount and date. Verify: the missing invoice list is proven against the whole subledger, not one vendor record
2. Search the alternative homes: duplicate vendor records, other group entities, capture-tool rejection queues and site inboxes. Verify: each missing invoice is located somewhere, or confirmed as never received
3. Accrue the genuinely missing, valid invoices at close with the statement as support, coded to the right expense or PO references. Verify: the month-end liability includes the supplier's full position
4. Fix the intake route for this supplier: confirm the correct submission address and format with them in writing, repair capture rules and merge duplicate vendor records. Verify: the supplier confirms the new route and the system changes are saved
5. At the next statement, reconcile it fully to AP before close and confirm no new invoices are missing. Verify: the following month reconciles clean, proving the route is repaired

Variant phrasings

vendor statement invoices missing from AP subledger accrual misses supplier

The completeness symptom as stated.

supplier invoices lost intake email capture queue duplicate vendor record

The intake archaeology phrasing.

AP accrual from vendor statement missing invoices month end fix

The close-accrual procedure search.

Compatibility: AP automation and capture tools (OCR and email intake) feeding SAP, Oracle, Coupa, NetSuite or Dynamics payables ledgers.

Why it happens

AP completeness depends on intake, and intake is a chain of inboxes, capture rules and master data that each supplier experiences differently. One supplier's habit - emailing a person instead of the AP address, sending PDFs the OCR rejects for a scanned signature block, trading with a site whose staff file paper - breaks the chain at the same link every month. The subledger cannot report what it never received, so accruals built purely from AP data inherit the blind spot exactly.

Edge cases / pitfalls

• Statements include invoices already paid or credited in their own presentation quirks; reconcile the statement format before declaring invoices missing.
• A supplier in dispute may inflate statements; validate missing invoices against goods or service receipt before accruing.
• Add a quarterly vendor statement reconciliation for the top suppliers by spend; it is the cheapest completeness control in AP.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ANL-RUG3PvVV9j53nVaweQ