Treasury Portal: multi-bank ledger with a signed audit trail
Krishna Bhupathi
Client project in fintech. The client's name is withheld under NDA. My role: backend and integrations engineer.
The problem
A business running several legal entities needed one place to see and move money across multiple banks. Every bank's API returned data in its own shape, reconciliation was manual, and the finance team needed an audit trail they could hand to an auditor.
What I built
Bank integrations across multiple banking APIs, with a normalizer that maps every bank's data into one unified schema.
A double-entry ledger core in PostgreSQL, so every movement of money balances and can be traced.
Signed audit trail: entries are cryptographically signed with AWS KMS, so records can't be changed silently.
Access control: role-based access with SSO, scoped per entity.
Automated reconciliation across banks, replacing the manual matching.
Outputs: a portal UI in React, SOC 2-style compliance exports and Stripe payouts.
What it shows
Compliance-heavy backend work where correctness matters more than speed: a ledger that always balances, an audit trail you can prove, and integrations that keep working when a bank changes its format.
Stack: Node.js, PostgreSQL, React, Stripe, AWS KMS, Docker. Code is private under NDA; architecture walkthrough on request.
Like this project
Posted Oct 10, 2026
Multi-entity treasury portal: multi-bank API integrations, a double-entry ledger, KMS-signed audit trail and automated reconciliation for a fintech team.
Likes
0
Views
1
