Practitioner-led articles on trade finance, AML, payments, UAT, and banking implementation — Domain intelligence for banking implementations.
Most LC discrepancies are avoidable. Here is why presentations go back — the MT752 waiver flow, the 5 banking day rule, partial utilisation tracking.
Read Article →Calibration, structuring detection, and the tipping-off prohibition — three AML system gaps that most UAT plans never test.
Read Article →Four rails. Four different settlement finalities. Four different return mechanisms. Testing one and assuming the others are equivalent is the gap that produces production incidents.
Read Article →Most production incidents trace back to scenarios not in the UAT plan — because the team writing test cases did not know the regulation well enough to construct the boundary.
Read Article →DSCR computation is only the start. The covenant breach workflow, DSRA drawdown lifecycle, and TRA waterfall sequencing are where project finance implementations fail.
Read Article →FTP method selection, EVE vs NII distinction, and India-specific LCR SLR treatment — three ALM gaps that appear in production because they were never in the UAT plan.
Read Article →Drawing power vs sanctioned limit, MPBF computation, and the SMA/NPA cascade — three working capital scenarios that break CBS implementations because they were never properly tested.
Read Article →MT700 field interdependency, MT103/MT202COV correlation, and the ISO 20022 migration — the SWIFT scenarios that pass field-level UAT and still break in production.
Read Article →Onboarding a generalist BA onto a banking implementation without domain grounding costs weeks in rework, not days in training. What that actually means for project budgets.
Read Article →Re-KYC risk-tiering, video KYC liveness edge cases, and Central KYC Registry deduplication — KYC scenarios that get bundled into AML UAT and tested incorrectly, or not at all.
Read Article →Forfaiting, factoring, Islamic trade finance, and supply chain finance get tested as if they're variations of the same product. They aren't — and the UAT gaps prove it.
Read Article →A failed UPI transaction and a disputed card transaction follow completely different rules, timelines, and liability — testing them as the same scenario produces a system that mishandles both.
Read Article →New to Banking Domain?
If these articles raised more questions than answers, our self-paced video course builds the domain foundation from the ground up — at your own pace.
Explore Training →