AP Accrual Handoff at Close

Define what the accrual handoff covers

The handoff covers payables that relate to the closing period but are not yet invoice-ready. That usually means goods received without an invoice, services performed without a bill, and approved commitments with a known amount. It does not include disputed invoices or items the business has not accepted.

Write the definition in the close calendar and name the cut-off. A handoff that includes everything open will double count items already recorded. A handoff that includes only invoices on hand will miss obligations that arrived by email or receipt after the last extraction.

Agree the definition with the controller before the first close, and keep it with the close calendar. A definition that changes mid-cycle makes the accrual and the reversal hard to compare.

Freeze the open-item population

Pull the receipt, service, and open-invoice records as of the close cutoff. Record the report names, run times, filters, and row counts. Include the PO line, receipt date, supplier, amount or estimate, currency, and current invoice status.

Reconcile the extract to the control totals and investigate missing rows before estimating. If a receipt system was unavailable, record the gap and the manual workaround. A population with an unexplained hole cannot support a reliable accrual.

If the receipt system cannot provide a cutoff view, take two extracts and compare them. The difference shows what arrived during the freeze and should be logged as a known limitation.

Distinguish received-not-invoiced from disputed

Received-not-invoiced is an obligation with accepted goods or services and no invoice. A disputed invoice is a recorded liability with an open question. Mixing them can overstate the accrual or hide a payable that should already be in the ledger.

Use separate queues and separate owners. The receiving or business owner confirms acceptance for the first; the dispute owner resolves the second. The accrual handoff should show both, but it should not merge their amounts or their next actions.

For each disputed item, record the amount already recorded and the amount in question separately. That prevents the dispute from being accrued twice or ignored because it is uncomfortable.

Give accounting a reproducible estimate

For each item, show the source of the amount: the PO price, the receipt quantity, the contract rate, or a prior invoice. State whether the amount includes tax, freight, or discounts. If the amount is an estimate, label it and name the person who supplied the basis.

Do not smooth the total to a round number without a record. Accounting may adjust the estimate, but the adjustment should be visible. A reviewer should be able to rebuild the proposed accrual from the line-level inputs and the stated method.

Where a contract rate is used, cite the clause and the effective date. Where a prior invoice is used, attach it and note why it is representative. The reviewer should not have to guess which basis was chosen.

Document the method and the inputs

Write a short method note: population definition, cutoff, estimation basis, treatment of tax and freight, currency conversion, and the owner who approved the estimate. Attach it to the close package so the next period can apply the same logic.

Keep the source files and the working file together. If the method changes from the prior period, show the change and the reason. A method change without explanation makes the period-over-period comparison unreliable.

Keep the method note short enough to be read at the close review. A one-page note with the population, cutoff, basis, and owner is more useful than a long appendix nobody opens.

Handle late invoices after the freeze

An invoice can arrive after the accrual is posted but before the ledger closes. Decide in advance whether it replaces an accrual line, creates a new payable, or waits for the next period. Record the decision and the owner.

If the invoice amount differs from the accrual, keep the accrual line and the invoice linked so the reversal and the actual can be compared. Do not delete the accrual to make the variance disappear. The difference is useful evidence about estimate quality.

Record the invoice receipt time, not only the invoice date, when deciding which period it belongs to. A supplier can date an invoice earlier than the service or the receipt.

Reconcile the accrual to the next period

At the next close, compare each accrual line to the invoice or payment that followed. Record matched, partially matched, still open, and reversed without invoice. Report the residual by supplier and owner.

Investigate recurring large residuals. They may indicate a cut-off problem, a receipt timing issue, or a supplier that consistently bills late. The pattern is more useful than a single period's total.

A reversal that clears an accrual without an invoice should be explained. It may be a valid estimate that was never billed, or it may be an obligation that was missed.

Review the handoff with the controller

Walk through the population, the largest items, the estimate basis, and the unresolved exceptions. Ask the controller to confirm the accounting treatment and the reversal plan. Record the review date and any changes requested.

Do not present a single total without the supporting lines. The controller needs to see what is included, what is excluded, and what could change before the ledger is final. A short review now prevents a long cleanup later.

Close with the reversal plan

The handoff is complete when the accrual is posted, each line has a source and owner, the reversal method is documented, and the next-period comparison is scheduled. Keep the package with the close evidence.

If an item cannot be estimated reliably, say so and route it to the owner rather than inserting a placeholder. An explicit open item is easier to manage than a number that looks precise and has no basis.

If the controller changes an estimate, record the change, the reason, and the revised amount in the handoff rather than only in the ledger. That note is what makes the next comparison explainable.