OfficeFlow — billing, compliance & cash-flow platform

How we built it

Delivered in deliberate phases.

1. 01

   Isolation for a compliance product

   Every firm's data lives in its own PostgreSQL database rather than a shared table with a tenant column, so one firm's books are structurally separated from another's. The customer-facing app connects with a least-privilege role, and a separate admin console supports firms without ever mixing data.

2. 02

   Getting money right first

   Every amount is stored as integer paise, never a floating-point number; the Indian April–March financial year is treated as a first-class concept across numbering, reports and returns; and invoice numbers are serialised in the database so they never collide, gap or duplicate.

3. 03

   GST and TDS modelled at entry

   Each invoice line computes CGST/SGST or IGST from the place of supply, and TDS is modelled in both directions — deducted by clients on receipts and by the firm on vendor payments — each tagged to its section and quarter, with an invoice settled by cash plus TDS plus any advance applied.

4. 04

   Collections and reconciliation

   Ageing, scheduled email and WhatsApp reminders and no-login pay links accelerate collection, while a flexible CSV bank-reconciliation importer matches statement lines against receipts, advances, expenses and vendor payments by amount and nearest date.

5. 05

   Audit-grade by default

   An append-only trail records every create, edit and deletion across every module, and statutory outputs — GSTR-1, GSTR-3B, TDS registers, a day-book and a Tally export — fall out of data captured at the point of entry rather than being reconstructed at quarter-end.