Skip to main content

Settlement audit + purpose codes

Three related audits on the LRS remittance table. Pure reads over data already stored — no new ingest, no broker calls.

What it audits​

  1. Settlement lag — time from remittance-paid to funds-credited-to- beneficiary per remittance. Mean / median / p95 / max.
  2. Missing UTR — credited remittances where the settlement UTR (the bank reference number) isn't captured. An audit / follow-up item.
  3. Purpose codes — per-purpose breakdown (with the uncoded count) for RBI reporting.

What tends to surface​

  • Credited remittances with a missing UTR — usually a settlement-fetch gap where the "credited to beneficiary" flag flipped without a matching settlement record landing. Follow-up: audit the settlement-id → UTR fetch path.
  • Uncoded purpose codes — the field isn't reliably populated on the order. Follow-up: confirm with the upstream where the code actually lands.
  • Lag stats are None until a book has enough credited remittances with both timestamps to compute averages.

Where to see it​

  • Frontend: the Settlement card at the top of /ops-audit (India book).
  • API: GET /v1/india/settlement-audit?fy=.