A supplier credit often starts as a conversation about a short delivery, a damaged case or a price that did not match. Weeks later the team may hold an email promising a credit, a document from the supplier, an entry in the finance system and part of that value used against an invoice. Each is a different event. Treating any one as proof of the others is how a credit quietly disappears or gets counted twice.
This guide follows one requested credit from the original discrepancy to a documented resolution. It does not reconcile invoice lines against deliveries, and it gives no tax, legal or posting rules. The worksheet is fully manual and calculates nothing. The example, CT-025, is original fiction.
Scope one credit before tracking anything
Open one case per requested credit. Record the supplier reference, the buying entity, the outlet, the currency and the value basis the request uses, such as net goods value before tax and charges. Name the original invoice and the specific line, and link the evidence behind the request: a discrepancy record, a return note or a receiving photo reference. Hold these as protected references to your own records, not copies of documents, account details or personal contacts.
The original invoice stays as issued. A request does not change it, and nothing here nets a hoped-for credit against that invoice. If the value basis is unclear, settle it with finance first; comparing a net figure with one that includes tax creates a difference that is not real.
A request is not approval and creates no right to a credit. Whether a credit is due, how it is classified and how any tax is treated belong to the supplier agreement and your existing authorised finance process. This record shows only what each party has actually done.
Keep the events apart
Several events tend to collapse into one word: credited. The supplier agrees in principle. The supplier issues a document, such as a credit note. Finance validates that document and records it in the finance system. Finance allocates some or all of it against an invoice, or a refund arrives. Each has its own date, reference and owner, and none is implied by another.
An email promising a future credit is not evidence that the supplier has issued the credit note. A supplier document is not validated until the responsible finance role confirms it against the request, supplier, entity, currency and basis. A validated document is not yet applied to anything. Record a bank refund as verified only after the responsible finance process checks receipt against the bank record; a message saying it was sent is insufficient.
Quantities need the same care. An amount-only credit does not by itself change recorded goods received or restore quantity available to invoice in a receipt pool. A quantity-related credit needs a separately validated allocation with the relevant finance, receiving and stock evidence; this record assumes none.
Register each document once, however often it arrives
Log every supplier document with its reference, type, date, stated value and basis, how it arrived and who logged it. Before adding a row, check reference, supplier, entity, date and basis against existing rows. The same document attached to a second email is the same document: link it as a duplicate and never count its value again.
Revisions and replacements are different. If a supplier corrects or reissues a document, link the new version to the old one and record which is current after finance review. If a credit is cancelled, keep the original row and add the cancellation with its reference. Never delete a row or assume a reissue simply replaces earlier value.
This tracking form does not authorise anyone to issue a supplier document. A pending credit gives this record no basis to deduct from or withhold any payment.
Worked example: CT-025 as of 8 November 2026, 17:00 IST
In this fictional case, Outlet North raised discrepancy DISC-025 against line L1 of invoice INV-025 from supplier SUP-025, billed to entity ENT-N in INR. Request REQ-025 asked for INR 300 on a net goods-only basis; tax and other charges are referred to finance and not calculated here. Nothing about the request was approved or recoverable automatically.
Supplier document CN-025 arrived for INR 200, and finance validation VAL-025 confirms only that 200 is within scope. Allocation APP-025, verified against INV-025, applied 150. The same CN-025 later arrived again as attachment DOC-025-B and is linked as a duplicate, not a second 200. No cash refund has been received or verified.
| Fact (fictional) | INR, net goods basis | Evidence | Status at 17:00 |
|---|---|---|---|
| Requested credit REQ-025 | 300 | DISC-025 on INV-025 line L1 | Request only; not approval |
| Validated document CN-025 | 200 | VAL-025; DOC-025-B linked as duplicate | Within scope; counted once |
| Applied allocation APP-025 | 150 | Verified against INV-025 | Applied; invoice balance not assumed |
| Validated, not yet allocated or refunded | 50 | Manual check in finance | Finance owner to reconcile |
| Requested, not covered by any document | 100 | Supplier review pending | Purchasing owner to follow up |
| Cash refund | None | No bank confirmation | Not received |
Reading CT-025 without collapsing the numbers
Three facts stand side by side: 300 requested, 200 documented and validated, 150 applied. Two remaining positions follow, and they differ in kind. The 50 is validated credit not yet allocated or refunded, as manually checked in finance. The 100 is the part of the request that no document covers and that the supplier is still reviewing.
Adding them into a single 150 to collect would be wrong. The 100 is not a supplier debt or a refund entitlement; it may never be granted. The 50 is not cash either, and its use is for finance to decide through the authorised process.
Invoice INV-025 is unchanged. Do not assume the allocation reduced its unpaid balance unless finance independently verifies the invoice's actual state. The manually entered case status is Open, with two actions: the finance owner reconciles the 50 through the authorised process, and the purchasing owner follows up the 100 with the supplier.
Later evidence, payment details and closure
When later evidence arrives, such as a revised document, a further allocation or a bank-confirmed refund, record it as a dated review. Keep the 17:00 snapshot exactly as it was and add the new position beside it. A correction gets its own history row with the reason, reviewer and time; the original entry stays.
Never act on payment details from this trail. If a message asks to change where a refund or payment goes, refer it to your existing independent verification process and do not use those details here. Confirm the supplier's identity and any allocation through established records, not a reply in the same thread.
Closure is a manual decision. Close the case only when the document trail is complete and every remaining action is resolved or has an authorised disposition recorded. A subtotal reaching zero is not closure.
Where the distinction comes from
Xero's help article on adding a supplier credit note treats the credit note as its own document carrying a reference and reason, separates saving a draft, submitting for approval and approving, and handles allocating a credit and recording a refund as distinct steps. Only those distinctions inform this record. Its US interface, user roles, default amounts, automatic allocation and any financial policy are not adopted, and no Keystonne feature is implied. CT-025 and its workflow are original fiction.
Put it into practice
Your action checklist
Your progress saves in this browser. No sign-up needed.
0 of 10 complete
From reading to doing
Supplier Credit Tracking
Open Supplier Credit Tracking for one requested credit within one supplier, entity, outlet, currency and explicit value basis, linked to the original invoice and line and the discrepancy or return evidence. The sheet is fully manual: it calculates no amounts, applies no tax treatment, posts nothing, makes no payment decision and never closes a case automatically. Sections cover scope; request and evidence; a supplier response and document register of 8 rows; duplicate and replacement links; a finance validation register of 6 rows with status, role, time and evidence; an application and refund register of 8 rows with a separate event type, actual amount, basis, system reference, independent verification and owner; manual as-of reconciliation blocks keeping requested, validated, applied, validated-but-unallocated and unresolved-request positions apart; 6 action rows for unresolved requests and unallocated credit; 4 correction history rows; and a final review. Use protected references only, with no account details, payment instructions, credentials or personal contacts.
Open the Supplier Credit Tracking tab in the launch workbook. Keep a copy for your own business.
Download the free workbook See what’s inside the toolkit →Sources & further reading
- Add a supplier credit note (Xero Central) ↗
Retrieved 8 November 2026. Used only for the general distinctions that a supplier credit note is its own document with a reference and reason, that draft, submission for approval and approval are separate states, and that allocating a credit and recording a refund are separate steps. Its US interface, user roles, default amounts, automatic allocation and any financial policy are not adopted. CT-025, its references, figures and workflow are original fiction.
Published by Keystonne Grow. Product links connect to the Keystonne ecosystem; check the linked product or service for its current scope.