A double-entry ledger with multi-currency settlement built in
Our own financial system: invoices, journals, multi-currency settlement and dimensional allocation.
Key facts
A real journal-based ledger, derived deterministically from operational data
Functional currency INR, with realised FX gain and loss computed on settlement
Allocation by project, service, developer and cost centre
We bill clients in several currencies and needed a ledger that can, in time, tell us which projects made money. Off-the-shelf accounting software answers the statutory question and not the operational one.
Accounts Hub separates three layers: an operational layer of invoices, line items, allocations and payments; an accounting layer where journal entries and lines are derived from operational data by deterministic posting services rather than entered by hand; and an analytics layer of query objects, designed to move to materialised views.
The interesting constraint is what it deliberately does not do: no period locking, no strict ledger immutability, no statutory filing. It isn’t trying to replace an accountant. It’s built toward answering “which of these engagements is actually profitable, in the currency we spend.”
Tax treatment is modelled through profiles and categories rather than hard-coded, so a service’s tax behaviour is data. Dimensional allocation means a single invoice line can be split across projects and cost centres.
Building something
like this?
Thirty minutes with one of the engineers.
Book a call