Skip to main content
NSWS
Case study · NBFC · Field Operations

T+1 cash-collection reconciliation across QR, bank ledger, and merchant aggregations.

QR-code-based cash collection reconciliation against bank ledger for an NBFC field-ops team, handling batched settlements, T+1 posting, multi-merchant aggregation, and dispute flagging with full audit trail.

QR Cash Collection ReconciliationClient
Challenge

The starting state.

QR settlements arrived T+1, batched, often across multiple merchants per day, manual reconciliation against the bank ledger took 4+ days per cycle.
Disputes from collection agents required spreadsheet stitching across merchant statements, bank narration, and field MIS.
Same transaction would appear in two merchant settlements occasionally, inflating reconciled totals if not deduplicated.
Our approach

How we engineered it.

01

Multi-merchant ingestion

Aggregator settlement files normalized into a common schema, with merchant attribution preserved per transaction.

02

T+1 batch handling

Date and batch-window-aware matching engine, bank posting on day T+1 reconciled against merchant settlement on day T.

03

Dispute workflow

Field-agent dispute creation routes to the reconciliation engine with audit trail and resolution log.

What we built

Architecture and the systems it talks to.

Settlement file normalization across QR aggregators
Bank narration parsing with UTR extraction and merchant identification
T+1 / T+N tolerance per matching rule (configurable per merchant)
Multi-merchant aggregation with anti-dedup safeguards
Dispute creation, routing, resolution log with audit trail
Daily and monthly summary exports
Outcomes

Quantified impact.

T+1
Settlement reconciliation

Daily, end-of-day, with exceptions queued for next morning.

Multi-merchant
Aggregation

Across QR aggregator partners with merchant attribution preserved.

0
Double-counted UTRs

Anti-dedup ensures the same UTR isn't counted across two merchant settlements.

Audit-ready
Dispute trail

Every dispute logged with resolution, replayable for inspection.

Audit trail per dispute
Source-row lineage
Configurable tolerances
Let's talk

Ready to start your project?

30-minute call with our team. Bring your project context and we'll map a clear path forward — no decks, no demos.