You return an item, cancel an order or query a supplier charge. The supplier confirms that a refund or credit is coming, and you move on to the next task. Weeks later, it is difficult to remember whether the money arrived or the credit was used.
A short tracking process can keep these items visible until they are resolved. It also gives your bookkeeper the context behind an unfamiliar deposit or a supplier balance that does not look right. The aim is to connect the original purchase, the supplier's confirmation and the eventual outcome.
Separate the request from the confirmation
Start a record when you request a refund or credit, but make its status clear. A request sent to a supplier is not the same as an approved refund. Save the original invoice or receipt, the reason for the request and any return or case reference.
When the supplier responds, record exactly what was agreed. Note the amount, currency, date and any stated processing time. If the response is unclear, ask for clarification rather than assuming that the full purchase price will be returned.
Confirm whether it is money back or account credit
A refund to your card or bank account is different from a credit to use against a future supplier bill. Ask which outcome to expect and where it should appear. Keep the credit note or other supporting document alongside the original purchase record.
For a supplier-account credit, note whether it has already been applied to an invoice or remains available. Do not assume that a credit shown on a supplier statement has also been recorded in your own bookkeeping system. Give your bookkeeper the documents needed to check both sides.
Use a small, shared follow-up list
For each open item, record the supplier, original invoice number, expected amount, expected destination, status and next review date. Assign a person to follow up. A useful status might be requested, approved, received, applied or needs clarification.
Keep sensitive details out of the list. A label such as “business card ending 1234” is usually more useful for this purpose than a full card number. Store supporting records through your normal secure document-sharing process, with access limited to the people doing the work.
Match the outcome to the original record
When a refund appears, compare its amount, reference and destination with the supplier's confirmation. The transaction description may differ from the supplier name you recognise. If the amount is different, look for an explanation in the supporting correspondence before treating the matter as complete.
Avoid recording the same refund twice because it appears in both a bank feed and a manually entered transaction. Similarly, a supplier credit and a cash refund may relate to the same adjustment rather than two separate benefits. Ask your bookkeeper to confirm the correct treatment, including any related tax adjustment, instead of guessing from the bank description alone.
Follow up on the exception, not the whole history
If the expected processing time has passed, send a focused message with the original reference, confirmation date and amount still unresolved. Ask for the status and the information needed to identify the refund or credit. Do not include unrelated bank transactions or unnecessary account details.
Update the tracking note with the response and next action. If a supplier says the refund has been issued but you cannot locate it, keep that difference visible. “Supplier says sent” and “received and matched” are different stages.
Close the item with evidence
Once the refund is matched or the credit is correctly applied, mark the item complete and retain the supporting trail. A brief review of open items alongside your regular bookkeeping can stop small adjustments from becoming forgotten questions at month-end.
InnovativePro Solutions offers bookkeeping support including invoice and receipt management, basic accounts payable tracking, and bank and credit-card reconciliations. If following records across emails, supplier accounts and statements is taking up your time, explore ongoing bookkeeping support: