Why invoicing breaks down past a couple of clients

Freelancers don't lose time on any single invoice. They lose it re-running the same reconciliation by hand across every client: which invoice is paid, which method it came in on, which one is quietly overdue, and whether anyone actually followed up. None of that's visible until you're doing it for five clients across three different billing tools at once, and cash flow visibility stays reactive instead of something you can plan around.

What I built

Ledger centralizes that lifecycle, invoicing, payment tracking, forecasting, and reminders, so none of it depends on someone remembering to check a spreadsheet.

• Multi-workspace billing. Each client gets its own workspace, invoice history, payment terms, and compliance state, rolled into one view instead of one browser tab per client.
• Forecasting. Payment history per client feeds a cash flow forecast and flags a client trending toward overdue before the invoice is actually late.
• Reminders that don't need a human. A due-date nudge, then escalating follow-ups, then a final notice, all triggered off real payment status.
• Compliance per region. Tax rules and invoice validity get checked before an invoice goes out, not after it bounces back.

The part that's actually hard

None of the above is the hard part. The hard part is Razorpay: reconciling payment status across UPI, cards, net banking, and international methods, each with its own webhook shape and its own way of arriving late, out of order, or twice, without ever marking an invoice paid when it isn't, or the reverse.

Stack

Next.js · TypeScript · PostgreSQL · Prisma · Razorpay · tRPC · Vercel

What changed

Overdue invoices dropped once the follow-up sequence stopped depending on someone remembering to send it. More importantly, revenue across every client now lives in one place instead of split across spreadsheets, email threads, and whatever the payment dashboard happens to show that day.