Find missing credit notes and refund entries by comparing three pieces of evidence for each return: the confirmed repayment at the payment provider, the WooCommerce refund record and the linked AFAS credit or financial entry. None replaces another. Give each missing link its own reason and follow-up action.
The word “refund” hides three actions
Returning money, recording a refund in the online store and processing the financial correction in ERP can happen at different times and in different systems. Some payment methods do not support automatic API refunds and require manual action. A credit note may also become available after the money moves. A generic green return status therefore says little about financial completeness.
Retain immutable amounts and identities from the approved refund point. This prevents a later order change from recalculating the historical correction. Link each piece of evidence exactly to workspace, order and return. Amount and customer name alone are insufficient when several partial refunds exist.
Month-end closing check per return
| Payment provider | WooCommerce | AFAS | Interpretation |
|---|---|---|---|
| Confirmed | Recorded | Credit linked | Technically complete under the policy |
| Confirmed | Recorded | Missing | Investigate the financial next step |
| Confirmed | Missing | Credit linked | Restore the online store record without sending money again |
| Manual action required | Prepared | Prepared | Task stays open until external evidence exists |
| Uncertain | Do not execute | Do not execute | Verify the provider outcome first |
This framework is a process check, not financial or legal advice. Have the applicable documents, timing and deadlines established for your situation. A workflow in Connect can bring technical evidence and statuses together.
Fictional example: money returned, online store record missing
Fictional example: a customer of sports shop Stapvast receives a partial refund of 65 euros. Mollie confirms the refund and AFAS contains the linked credit. Recording it in WooCommerce stalled during an outage. A naive “retry refund” could send another 65 euros.
The check sees that the movement of money is already confirmed and creates only a task for the missing online store record. The recovery step explicitly updates WooCommerce without affecting payment or stock again. In a second fictional case, the payment method does not support API refunds; the task remains “manual refund required” until an authorised employee records external evidence. Each missing link leads to a different, bounded action.
Evidence and ownership
- Use a separate identity for each partial refund.
- Record which system actually moves money and which only records it.
- Make an uncertain provider outcome visible before any retry.
- Compare the refund amount with the recorded snapshot, not a subsequently changed order.
- Assign separate owners to a missing credit, online store record and manual payment.
- Have a closing action verify that all evidence required by policy exists.
In Desk the return can show the correct financial follow-up task without customer service having to compare dashboards. More about technical order and AFAS identity is available in the WooCommerce–AFAS integration.
Plan checks around delays, but do not use delay as an excuse. Define for each link how quickly evidence normally becomes available and when attention is required. A credit note missing after ten minutes may be normal; the same state beyond an approved threshold needs an owner. Have finance and process management establish the threshold and display it alongside the signal. A generic nightly batch must not hide a customer-facing manual refund.
Test corrections without moving money too. Create a fictional refund already confirmed by the provider and demonstrate that repairing the WooCommerce record makes no second payment call. Then test an AFAS credit whose first write request timed out: recovery must search by stable identity first. Finally, add two partial refunds for the same amount. Their own refund IDs must keep them separate. These scenarios reveal whether the implementation relies on identities and statuses or merely on amounts that happen to match.
Include a second-person check for manual money movements at each closing. The person adding evidence need not be the person who closes the exception definitively. Your own financial policy determines the appropriate separation of duties.
Retain both decision points separately in the audit trail.
Want to find missing refund links without moving money twice? Design an evidence-based check with Yindle.