Issued and applied are different events
Issuing a credit note documents an adjustment. Applying it records how that adjustment is used against an obligation or otherwise settled in the agreed accounting workflow. The source export must make the settlement meaning clear. A current balance can be expected, for example when the next payment has not yet occurred.
Calculate the residual, not the face value
Consider a fictional EUR 1,000 credit note. Your agreed application export contains EUR 300 and EUR 250 against it. The remaining balance is EUR 450. Counting the entire EUR 1,000 as outstanding would overstate the issue. Counting the two application rows as separate credits would also be wrong. Keep the document link and original currency intact.
Include the context around the cutoff
Use the same as-of date across notes and applications. Do not accidentally compare a complete credit-note list with an application export that ends earlier. Bring in older issued notes where newer applications refer to them. A ledger row without its matching note makes the snapshot incomplete; the current intake blocks that condition instead of showing a misleading total.
Investigate overapplication separately
If applications sum to more than the note, first check duplicate rows, reversal semantics and source mapping. VendorCredits flags overapplication for review and excludes it from monetary exposure. The current template accepts positive application amounts only. Negative reversals or complex netting need an agreed normalization approach; simply removing the minus sign would change the meaning.
Use aging as a review priority
The current default application window is 14 days. It helps surface older residuals; it does not establish that the supplier breached an agreement. Compare the apparent delay with the payment cycle and finance team’s procedure. Prioritize explainable, material differences and keep different currencies separate.
Close with settlement evidence
The reviewer should document whether the note was applied later, refunded, disputed or incorrectly mapped. Record the supporting reference and date. The application does not move money, edit the ERP or email the supplier. Its purpose is to keep the evidence and next action together so the responsible finance colleague can complete the process.
Keep “found” separate from “recovered”
A residual discovered in an export is a potential discrepancy, not a confirmed benefit. Measure confirmed outcomes only after finance verifies them. Preserve a record of dismissed findings as well; repeated false positives often point to a source-data problem that is more valuable to fix than another dashboard metric.
VendorCredits product guide · Updated 11 September 2026. Worked examples are fictional. Findings require verification against source records.