BillMart
Avail Trade Finance through Working Capital Loans, Channel Finance, Supply Chain Finance, Revenue Discounting, Import Export Finance, and everything around Bill, and we built a precise yet expressive solution in close collaboration.
YEAR
2021 to 2025
CLIENT
BillMart
SCOPE
PLATFORM
Web

The Challenge
Lending against an invoice is only partly a software problem. Before any financing can happen, the platform has to answer a harder question: is this business real, and is it good for the money?
In India that answer is assembled from statutory identity — GST, PAN, CIN, LLPIN, MSME registration — from filed financials, and from the directors behind the company. None of it arrives in one place, and much of it cannot be self-reported and believed. A borrower typing their own profit figure into a form is not underwriting.
It is also not a two-sided system. There are five kinds of participant: the buyer or seller raising the invoice, the financier funding it, the chartered accountant who attests the numbers, the facilitator who brings deals in, and the administrator approving all of them. Each sees a different product, and each has to be approved before they can act at all.
Objectives
- Establish a business's statutory identity and keep it approvable, auditable and revocable.
- Capture financials in a form a lender can act on, with the accountant who entered them recorded on the record.
- Serve five participant types from one platform without five platforms' worth of code.
- Keep every approval auditable — who approved what, when, and what was said to whom.
- Scale with deal flow rather than with servers.
Our Approach
Make the accountant a user, not a document
The chartered accountant is a first-class participant, mapped to the businesses they act for. Balance sheets, financial details and filing status each record the accountant who entered them. The consequence is that a lender is not reading numbers a borrower typed about themselves; they are reading numbers with an attributable professional behind them.
One role field, five products
Participant type is a single bitmask — admin, buyer/seller, financier, accountant, facilitator. One user record, one permission check, five experiences. It is an old technique and it is the reason the platform did not fork into five applications.
Approval is a workflow, not a boolean
Onboarding carries a status through not-submitted, pending, in progress, approved and rejected, at multiple levels, with two separate remark fields — one shown to the applicant, one for internal operations. Regulated onboarding needs both, and conflating them is how internal notes end up in front of customers.
A service per capability, on Lambda
Each business capability is its own function behind API Gateway, guarded by a custom authorizer, inside a VPC, onto Aurora, with SQS, SNS and SES carrying the asynchronous work. Trade-finance load is spiky by nature — quiet, then a deal closes — which is the shape serverless is actually good at.
Order the protocol, not just the payloads
Every request carries a message code, a session identifier issued at login, and a sequence number that increments within that session. It means the server can reason about the order requests arrived in and reject replays, on a platform where the requests move money.
The Solution
Statutory onboarding
Business identity captured as GST, PAN, CIN, LLPIN and MSME registration with incorporation date and industry classification, alongside addresses, verified email, and bank accounts resolved against a bank and branch master with IFSC codes. Each element approvable and each carrying its approver, remarks and timestamp.
An attested credit picture
Balance sheet positions by financial year, revenue, interest expense and profit after tax, GST return and annual report dates, registrar status and listing status — with supporting documents stored against the user and typed by what they are. Directors are recorded with their identification number, other directorships, and any prosecution history.
Operations tooling
An administrative surface for the team running approvals: reviewing submitted businesses, moving them through the levels, recording decisions and remarks, and managing the participants on the platform.
The clients
An Angular application served from S3 through CloudFront, plus an administrative application for the operations team running approvals.
Under the Hood
Frontend
Angular, on S3 behind CloudFront, with a separate admin application.
API
Route 53 into API Gateway with a Lambda custom authorizer.
Services
Lambda per business capability, inside a VPC.
Data
Amazon Aurora.
Async
SQS, SNS and SES.
BillMart has since publicly reported disbursing over ₹2,500 crore across more than 24,000 transactions, with over 40% going to SMEs and MSMEs, through a network of 40+ lenders and 70+ corporate partners. Those are the client's own published figures for their business, not a measurement of our work. This case study describes the platform as we built it; it has been running and evolving since.
Commercial mechanics are deliberately not described here.
The Decisions
The accountant's user ID goes on the financial record
It would have been simpler to store the numbers. Storing who entered them is what turns a form submission into something a lender can price risk against, and it is the difference between a marketplace and a listings site.
Two remark fields, not one
An approval workflow that cannot separate “what we told the applicant” from “what we said internally” will eventually show one to the other. Two columns from the start is a cheap way never to have that incident.
Serverless because the load is lumpy
Deal flow arrives in bursts. Paying for idle capacity between them, on a platform whose early volumes are unknown, is the wrong shape of cost — and API Gateway with a custom authorizer gives one place to enforce which of the five participant types may call what.
Outcomes
The platform went live and has been operating since, and BillMart has grown into one of India's active digital trade-finance providers on the numbers it publishes above.
We have not attached our own metrics to this page. The engagement ran from 2021, and the growth BillMart reports is theirs — built on the platform, not produced by it.

Other Case Studies

Speed Machine
A direct-to-customer insurance platform that integrates leading insurer APIs so people can...

Advantage
A multi-tenant insurance benefits portal PrishaPolicy offers to its corporate clients,...

Vantage
An internal insurance operations platform built for PrishaPolicy, unifying sales, policy...

Prisha Policy
Empowering a prominent insurance broker to safeguard client assets and liabilities through...

Centuro Global
Revolutionizing global mobility services to deliver swift, cost-effective solutions for...

Akoya
Streamlining itinerary planning and enhancing the travel experience through intelligent...

TellGo
TellGo provides seamless global connectivity through eSIM technology combined with a...

H&S Store
Kuwait's Premier Electronics Retailer - Transforming retail operations with real-time...

Empathable
EmpathablePX — an AI patient-simulation platform where clinicians rehearse high-stakes...

