How to reconcile a vendor credit memo.

Define which credit you are checking

Here, vendor credit means a supplier credit note or credit memo, not a loan or trade-credit facility. A supplier may issue a note for a return, price adjustment or another agreed reason. Keep those populations separate unless the review explicitly covers all of them. Record the legal supplier entity, the account used in AP, the business reference, the document date and the currency. Those details let a colleague reconstruct the relationship instead of relying on a filename or an email subject.

Start from the approved event, not the invoice total

A return authorisation can permit a shipment without approving the final credit value. Confirm the amount actually agreed and any documented change, such as a restocking deduction. The original invoice provides context; it is not automatically the expected credit. Microsoft’s Business Central documentation illustrates that a purchase credit memo can be linked to an invoice and that return and correction workflows differ. That is a system example, not evidence of a VendorCredits integration.

Choose the source grain before adding amounts

Determine whether each export row represents a whole credit memo, a memo line or an allocation. Three lines bearing the same document number may be legitimate detail; three copies of a header total are not three credits. Retain row identifiers and a document reference separately. For one memo spanning several approved returns, document the allocation and verify that allocations sum to the original memo. Do not copy its entire value into every case.

Compare issued amounts with one consistent basis

Use the same supplier, approved event, currency, tax basis and cut-off. Add all distinct related notes, after addressing cancellations or reversals. Subtract issued credits from the approved value. Preserve negative results: a EUR 1,000 approval with EUR 1,200 issued leaves −EUR 200, not zero. It may reflect a duplicate, an amended approval or an allocation error. The result asks for evidence; it does not tell you to book an adjustment.

Then reconcile the applications

For each accepted credit memo, identify the applications, offsets or separately documented refund treatment in the AP system. Use the relevant posted records and dates, not a workflow label saying “done”. A memo can be fully issued but only partly used. An application linked to another memo must not be brought across just because the supplier total looks right. Keep a credit-value question with the supplier owner and an application question with finance.

Read the fictional split-credit example

In the table, a EUR 1,200 approved return has two notes totalling EUR 1,000. The missing issued value is EUR 200. Applications of EUR 500 and EUR 100 leave EUR 400 across the issued notes. These are two control stages, not a claim of EUR 600 recovered. If a final EUR 200 note arrives after the cut-off, record that timing and repeat the comparison with the appropriate later snapshot. Do not rewrite the earlier snapshot silently.

Prepare a reviewable handoff

Retain the approval, related credit references, confirmed applications, signed differences, currency and source dates. Name the owner and next action. Where a reference is uncertain, label it unresolved rather than making up a match. The free workbook handles reviewed case totals; the demo shows an exception workflow. Neither automatically interprets arbitrary PDFs or exports from every ERP. Agree any data mapping before a real-data review.

Fictional example: one approved EUR 1,200 return

Your action checklist

1. Confirm the approved amount rather than assuming the invoice total.
2. Identify document headers, lines and allocations before aggregation.
3. Keep approval, issued value and applications in the same scope.
4. Preserve negative differences, incomplete evidence and reviewer decisions.

Practical questions