SettleFlow
{# Audience named, fear answered, licence stated. The previous sub-head described the mechanism ("reconcile a settlement file against a bank statement") which is the builder's framing, not the buyer's problem. #}For merchants and accountants reconciling Razorpay payouts against bank credits. Upload your settlement file and your bank CSV — get matched transactions, an exception list, and Tally / GST / TDS code-1035 workpapers.
Razorpay, PayU, Cashfree, PhonePe and Juspay exports; HDFC, SBI, ICICI, Axis, Kotak, PNB and DBS statements. Open source (MIT). Your files are used for this one reconciliation only; the run record is deleted after 30 days. No account, no card.
How the matching works
- It does not match on the UTR. Your bank statement carries the
correspondent bank's UTR, which is a different number from the gateway's
settlement_utr. The match key is the settlement id, with a (date + net amount) fallback. - Amounts are Decimal, in rupees. Gateway exports quote paise; the conversion happens once, at parse time.
- Every match is inspectable. You get the matched ledger and the exception list, not a score.
Your data
Nothing is kept beyond the run itself: the uploaded files are written to a private temporary file, used, and deleted immediately. The run record (matched ledger, exceptions, generated CSVs) is deleted after 30 days, automatically. Privacy has the detail.
Currently supported: settlement exports from Razorpay (API JSON and CSV), PayU, Cashfree, PhonePe and Juspay, and bank statements from HDFC, SBI, ICICI, Axis, Kotak, PNB and DBS (plus SBI PDFs). A format with no verified public sample is refused, never guessed — the open ones are listed on About.