One ledger
Every document posts balanced journal lines the moment it happens. There is no separate books system to keep in step, because there is no separate books system.
About
We build point of sale, inventory, and accounting as one system with one ledger, because the nightly ritual of making three systems agree should never have existed.
The argument
Three systems, three copies of the truth, one person paid to make them agree. We removed the copies instead.
Walk into the back office of almost any shop and you will find the same ritual. The point of sale says one number, the inventory sheet says another, and the accountant is holding a third. Someone spends the quiet hours making them agree.
That work has a polite name, reconciliation, and it is treated as a fact of life. It is not. It is the direct cost of running three systems that each keep their own copy of the truth and only exchange summaries. Every export, every sync job, every month-end adjustment exists because the sale, the stock movement, and the journal entry were recorded in three different places at three different times.
The fix is not a better integration. Integrations move the disagreement around; they do not remove it. The fix is structural: record the event once, in one database, and let the register view, the stock view, and the ledger view all be projections of that single record. When a cashier closes a sale, the cost layer is consumed and the journal lines are written in the same transaction. There is nothing left over to reconcile, because there was never a second copy.
Building it this way is harder. The posting engine has to be correct under concurrent registers, survive a dead internet connection, and hold up to an auditor reading the journal line by line. We think that difficulty belongs in the software, done once, rather than in the back office of every shop, done every night.
So that is the company: a small team building one ledger that the whole counter runs on, for businesses that would rather sell than agree with themselves.
Principles
Every document posts balanced journal lines the moment it happens. There is no separate books system to keep in step, because there is no separate books system.
A counter that stops when the internet stops is broken. Sales queue locally and replay in order, and cashiers sign in with PINs that verify offline.
FIFO cost layers, sequential document numbers, and a journal behind every figure. Any number on any report can be walked back to the lines that produced it.
We build for the shop with three people wearing eight hats. Fewer screens, faster lists, and defaults that do the accounting so nobody on the floor has to.
Timeline
Each addition posts into the same ledger the first register used. Nothing has been bolted on beside it.
First register goes live in a single shop, posting straight to a Postgres ledger.
Inventory joins the ledger: FIFO cost layers, batches, and serial tracking on one posting engine.
Offline replay and PIN cashiers ship, and the first multi-store chains come aboard.
Full reporting suite: financial statements, aging that ties out, and printable templates for every document.