What is obligation mapping?
Obligation mapping, the term Fiscus uses for a practice every strong credit team runs in some form, reconciles a borrower bureau tradelines against the repayment debits actually visible in their bank statements, in both directions, so that leverage cannot hide in either dataset.
Updated 18 August 2026
Key takeaways
- Direction one: recurring debits with no matching tradeline expose undisclosed obligations, app loans, BNPL, informal borrowing and disbursals not yet reported.
- Direction two: tradelines with no matching outflow expose closed, restructured, disputed or bounced obligations still on the record.
- The output is a statement derived obligation load and FOIR that can be compared against the declared one.
- The gap between declared and observed obligations is itself an underwriting signal.
How does the reconciliation work?
Recurring repayment debits are identified in the categorised banking: EMIs, NACH mandates, card payments, BNPL settlements, with counterparty, amount, frequency, first seen and last seen dates. Each is matched against bureau tradelines by lender, amount and cadence. What matches is confirmed conduct; what fails to match, in either direction, is a question with a page reference attached.
Misses and delays then become a monthly conduct record per obligation: which EMIs slipped, by how many days, whether bounce charges followed, and whether the pattern is tightening or recovering.
What does each direction of mismatch mean?
Debit without a tradeline. An obligation the bureau does not know: a fintech app loan, BNPL line, informal borrowing, or a disbursal too fresh to have reported. Declared FOIR understates reality by exactly these amounts.
Tradeline without a debit. An account that looks live on the bureau but shows no servicing in the banking: closed but unreported, restructured, disputed, or a mandate bouncing elsewhere. Either way, the record and the behaviour disagree.
There is no standardised industry definition of this practice, which is why we name and define it explicitly. The underlying reconciliation, banking against bureau in both directions, is simply what a thorough analyst would do with unlimited time.
Where this shows up in Fiscus
Fiscus auto tags recurring EMI outflows across all accounts, cross checks them against bureau data and flags misses and delays month by month. See bank statement analysis.
Frequently asked questions
Related terms
Read these signals off your own book.
Every term in this glossary is a field in a Fiscus report. Run a parallel evaluation on cases your team has already decided.