How to reconcile a D0 settlement file

Start with the final states

A payment is only reconcilable when it has reached a final state. Titan Pay notifies all four terminal outcomes, so the settlement file should never contain a line that is still moving. If an order is pending at cut-off, it belongs in the next batch, not in today’s payout.

The fields that make a line match

At minimum, each settlement line should carry the order ID, UTR, gross amount, fee, net amount, final status, batch ID and settlement date. The order ID ties back to your system; the UTR ties to the bank; the batch ID ties the file to the payout. If one of these is missing, the line is not reconciled—it is only a number.

Five checks before you close the day

1. Count. Successful orders in the period equal the lines in the batch.
2. Reference. Every successful line has a UTR, and no UTR appears twice.
3. Amount. Gross minus fee equals net, with no rounding drift.
4. Status. Failed, expired and refunded orders are excluded or reversed correctly.
5. Cut-off. The batch window and value date match the schedule you signed.

Treat a missing UTR as an incident

A missing reference is not a formatting issue. It becomes a support ticket, a delayed payout and an audit question. Attach the reference from the console on the same day, and keep the correction in the file history. If the same merchant or channel produces missing UTRs repeatedly, fix the integration before you scale traffic.

Why this matters more at D0

Same-day settlement compresses the time between payment and payout. That is good for cash flow, but it also compresses the time to catch a mismatch. A T+1 cycle gives you a day to fix references; D0 gives you hours. Automate the five checks and make the file immutable once it is closed.