LedgerFlow
Everyday bookkeeping for small businesses — ledgers, cash book, invoices and reminders in one place.
- Type
- Web application · SaaS
- Platform
- Responsive web, mobile-first entry
- Scope
- Product design, architecture, full-stack
- Status
- Concept Project
Merchant dashboard. Cash position, receivables and payables, cash-flow trend and recent transactions.
Overview
LedgerFlow is a concept for a financial management platform aimed at small businesses — retailers, wholesalers, workshops and service providers who extend credit to customers, buy on account from suppliers, and still track much of it on paper or in spreadsheets.
The aim was a system simple enough for an owner to use at the counter, yet rigorous enough underneath — a proper ledger model, an auditable history and clean reporting — that an accountant could trust the numbers.
Problem & solution
The business problem
Small businesses often run on informal credit. What customers owe and what is owed to suppliers lives in notebooks, chat messages and memory, so the real cash position on any given day is hard to know.
- Customer balances are tracked by hand, so disagreements about what is owed are common and hard to settle.
- Cash in and cash out are rarely reconciled daily, so errors surface weeks later.
- Invoices are created in word processors with no link to the payments received against them.
- Following up on overdue payments is manual, awkward and inconsistent.
- Owners have no quick view of receivables, payables or monthly profitability.
Proposed solution
A single workspace where every sale, purchase, payment and expense is recorded once and flows automatically into the right ledgers, the cash book and the reports.
- Party ledgers for every customer and supplier, with running balances and a full transaction history.
- A daily cash book that separates cash, bank and mobile-wallet movements and supports a day-end close.
- Invoices generated from the same records, so issuing an invoice and receiving payment stay connected.
- Scheduled payment reminders with a clear, polite message and a summary of what is outstanding.
- A merchant dashboard for day-to-day decisions and an administrative console for platform operations.
Key features
- 01
Customer & supplier ledgers
Separate receivable and payable ledgers per party, with opening balances, running balances and statement export.
- 02
Digital bookkeeping
Every entry is recorded as balanced debit and credit lines — an auditable trail rather than editable totals.
- 03
Cash book management
Daily cash, bank and wallet movements with opening and closing balances and a day-end close.
- 04
Income & expense tracking
Categorised income and expenses with receipt attachments and notes.
- 05
Invoice generation
Branded invoices with line items, taxes and due dates, linked directly to the customer's ledger.
- 06
Payment reminders
Scheduled reminders for overdue balances by email or SMS, with a reminder history per customer.
- 07
Transaction history
Searchable, filterable history across all accounts, with references back to source documents.
- 08
Financial reports
Profit & loss, receivables ageing, cash-flow summary and party statements for any date range.
- 09
Merchant dashboard
Cash position, receivables, payables and recent activity at a glance.
- 10
Administrative dashboard
Merchant onboarding, plan management, usage monitoring and support tooling for the platform team.
Interface design
User roles & workflows
Runs the business and needs a reliable view of what is owed, due and on hand.
- 1
Record a credit sale against a customer
- 2
Issue an invoice from the sale
- 3
Schedule a reminder for the due date
- 4
Mark payment received; balance updates
Architecture
- Merchant web app
- Mobile-first entry screens
- Admin console
- REST API
- Auth & role-based access
- Validation & idempotency
- Ledger posting engine
- Invoicing
- Reminder scheduler
- Reporting
- PostgreSQL — double-entry ledger
- Redis — queues & cache
- Object storage — receipts & PDFs
- Email & SMS provider
- PDF rendering
- Payment links (concept)
Double-entry at the core
Every business event is posted as a balanced set of debit and credit lines inside a single database transaction. Balances are derived from entries, not stored as editable totals, which keeps the books auditable.
Money as integers
Amounts are stored in minor units with an explicit currency code, avoiding floating-point rounding errors in totals and reports.
Idempotent writes
Entry creation accepts an idempotency key, so a request retried on a weak mobile connection can never post the same payment twice.
Work off the request path
Reminders, PDF generation and report exports run on a job queue, keeping the interface responsive and making retries safe.
Technology stack
- Frontend
- Next.js
- React
- TypeScript
- Tailwind CSS
- Backend
- Node.js
- NestJS
- REST API
- BullMQ
- Data
- PostgreSQL
- Prisma ORM
- Redis
- Infrastructure
- Docker
- S3-compatible storage
- CI/CD pipeline
Proposed stack for the concept; choices would be validated against a real client's constraints.
Engineering considerations
- 01
Simple on top, rigorous underneath
Owners think in terms of “this customer owes me 2,000”, not debits and credits. The interface speaks the owner's language while the posting engine translates every action into balanced ledger entries.
- 02
Correcting mistakes without rewriting history
Entries are never edited or deleted. Corrections are posted as reversing entries with a reason, preserving a complete audit trail.
- 03
Reminders that respect reality
Scheduling must respect time zones, quiet hours and partial payments — and must never message a customer who paid an hour ago. Each reminder job re-checks the balance just before sending.
- 04
Fast reports at scale
Reports are served from periodic balance snapshots plus recent entries, keeping them fast without trading away accuracy.
- 05
Tenant isolation
Every query is scoped to the merchant's organisation at the data-access layer, with tests that guard against cross-tenant leakage.
Project status
LedgerFlow is a self-initiated concept project, created to explore product design and engineering for small-business finance. It has not been delivered to or deployed for a client. The interface designs and architecture are presented as a case study, and all names, businesses and figures shown in the mockups are illustrative.