Refunds and chargebacks across month-end

The refund timing problem

A sale settles in March. The customer is refunded in April. The April payout is reduced by an amount relating to March revenue. Both periods are individually correct and the clearing account holds the difference, which is legitimate and completely opaque to anyone reading a balance.

This compounds. Several months of cross-period refunds produce a balance that is the net of many correct entries, which is why investigating it transaction by transaction so rarely converges.

The chargeback problem is worse

A chargeback is initiated by the processor, not by the merchant. The disputed amount leaves the balance, usually with a dispute fee attached, and nothing in the order system triggers an entry. The ledger still shows the original sale in full.

The result is a silent divergence between cash and books. Nobody is notified, and the amount is often small enough individually to escape attention while accumulating across a period.

A five-minute check

Export dispute activity from each processor for the last closed period and confirm every item appears in the ledger. In practice this is where a meaningful share of an unexplained clearing balance is found, and it takes very little time.

Worth including in the same check: disputes resolved in the merchant's favour, which create a reversal that also has to be recorded.

Dispute fee treatment

Dispute fees are handled inconsistently across teams, sometimes as a processing fee and sometimes netted into the disputed amount. Either can be defensible. What causes reconciliation problems is doing it differently in different months, because the comparison basis shifts. Pick a treatment, document it, and apply it consistently.

When standard software is enough

Low dispute volume and few cross-period refunds mean this is a short manual check rather than a recurring project.

When custom automation may be justified

High refund or dispute volume, several processors, and a monthly check that always follows the same procedure. Attributing each adjustment to the payout that carried it is mechanical, and holding a rollup when a component has no ledger side is a rule, not a judgment.