Finance Index

How to prepare a late-invoice list for month-end

Build a month-end late-invoice list that distinguishes overdue payments, late-arriving documents, and unposted obligations with owners and cutoff evidence.

A month-end late-invoice list should distinguish invoices received after cutoff, invoices received but not posted, and posted invoices past their payment due date. Those populations answer different questions. Record the relevant dates, accounting period, amount, status, owner, and next action so the controller can assess cutoff and AP can resolve operational delays without double counting obligations.

At a Glance

Aspect Short Answer Why It Matters
Definition Separate late receipt, late posting, and overdue payment Prevents a misleading single backlog
Population Reconcile intake, open workflows, ERP, and subsequent receipts Captures work missing from one system
Cutoff Record goods or service period and accounting assessment Due date alone does not establish recognition
Resolution Assign owner, action, and final posting reference Prevents unresolved items rolling forward

Which records should be included?

Start with open intake queues, unapproved invoices, posting failures, ERP open items, and invoices received after the reporting cutoff. Where relevant, review receipt records, supplier statements, and business-owner confirmations for obligations not yet supported by an invoice. Keep those uninvoiced items distinguishable from received invoices.

Use an explicit as-of timestamp and document source filters. An aging report of posted invoices alone will miss documents still waiting in intake or approval. Follow the month-end AP close and accrual process to reconcile populations.

What columns should the list contain?

Include vendor, entity, invoice or source reference, amount, currency, invoice date, receipt date, goods or service period, due date, current workflow status, expected accounting period, owner, blocker, next action, and target resolution date. Add PO or receipt references, existing accrual reference, ERP posting ID, and subsequent payment status where relevant.

Mark unknown dates explicitly instead of substituting the invoice date. Distinguish confirmed amounts from estimates. Use stable identifiers to avoid counting one invoice from an inbox export and an ERP report twice.

How should finance assess cutoff?

Assess the underlying goods or services and applicable accounting policy. A late invoice date, late receipt, or overdue payment does not by itself decide the accounting period. Ask the business owner for evidence where the service or delivery period is unclear.

If the obligation is already represented by an accrual, link that record before posting the invoice and follow the approved clearing or reversal process. Escalate uncertain recognition, tax, allocation, or materiality decisions to the controller rather than applying a blanket treatment to every late item.

How should the list be reviewed and closed?

Review high-value, old, disputed, and unowned items separately. Assign an action such as obtain evidence, resolve approval, correct coding, recover ERP posting, or evaluate an accrual. Keep a dated explanation for exclusions and items carried forward.

Use AP-to-GL reconciliation to check the accounting result. Retain the original cutoff view alongside later updates, so reviewers can distinguish what was known at close from what arrived afterward.

Stampli perspective

Stampli connects invoice status, documents, discussions, and ERP context. Confirm available reporting fields, filters, exports, and posting-status visibility. The controller retains responsibility for cutoff judgments and accounting treatment.