Refund / cancellation reversal
Sweep cancelled / failed / expired GlomoPay orders that still have an FX- spread accrual on the books and post reversing entries.
The problem it solves
If a GlomoPay order fires paid and Valura posts the FX-spread accrual,
then the order later flips to cancelled / failed / expired, the
accrual is UNEARNED. It needs to be reversed so:
4030 FX Spread Revenuedoesn't carry phantom margin.1300 GlomoPay FX Receivabledoesn't show money we're not actually owed.- If the settle already fired to
1010, that also needs unwinding.
How the sweep works
Run either as a dry-run (preview) or live:
- Find every LRS remittance in
cancelled,failed, orexpiredwith an original FX-spread transaction still posted. - Find any related settlement transaction.
- Post a reversing entry for each — mirrors the original's journal lines.
- Idempotent — re-runs post nothing new.
In practice
Most books at any given moment have zero candidates — the sweep runs cleanly and reports nothing to do. The value shows up when a cancelled order lands after the accrual posted; the sweep catches it on the next run without any manual work.
Where to see it
- Frontend: Refund / reversal card at the bottom of
/ops-audit(India book). Dry-run + Post-reversals buttons. - API:
POST /v1/jobs/refund-reversal-india.