The multi-entity problem
Most accounting software assumes you run one company.
Separate where it counts
Each company keeps its own ledger, its own periods and its own month-end close. Nothing is quietly pooled to make the software's life easier.
Together when you need it
See the whole group at once — cash, revenue, margin — without exporting anything into a spreadsheet on the last day of the month.
Intercompany cancels itself
Move $25,000 between two of your companies and the group view nets it to zero. No elimination entries to remember, no spreadsheet gymnastics.
Provable, not promised
The controls are the product.
Each claim below is held up by the database itself — not by a policy document, and not by everyone remembering to be careful.
-
The ledger never edits history
Every posting is double-entry and permanent. There is no update or delete path to a posted entry: mistakes are corrected by reversal, in the open, and both entries stay.
Database triggers reject any attempt to change or remove a posted entry, and a test proves it on every code change.
-
The close proves itself
Closing a month produces a package containing a fingerprint — a SHA-256 hash — of that month's trial balance. Re-compute it any time to see whether the numbers you signed still hold.
Close packages are insert-only rows; reopening a closed period takes a second person's approval, recorded permanently.
-
Two people, not one
Amount thresholds and ordered approval chains gate bills. Manual journal entries follow the same rule from the other side: whoever drafts one is never the person who posts it.
The separation is enforced at the point of approval and, for period-end journals, by a database constraint — not by an office convention.
-
Each company's books are sealed off
Your workspace's data is isolated inside the database, not filtered by an application that has to remember. A query arriving without your workspace's context returns nothing at all.
PostgreSQL row-level security, enforcing in production, with invoker-mode views. A continuous check fails our build if a new table ships without an isolation policy.
The close
Four steps, in this order, every month.
-
See what's true, and what's left
Every tie-out recalculates against your actual books when you open the page — subledgers against the ledger, intercompany to zero, nothing cached. What's still in the way is listed plainly, and the close button stays disabled until it's dealt with.
-
Resolve, on the record
Match a bank line to the entry it belongs to. Exclude one — and write the reason, because the system won't take it without one. Approve the last bill, through the gate.
-
Sign off
One click closes the month and writes a package that can't be edited: the checklist as it stood, the full trial balance, and the hash that fingerprints it.
-
Seal
Lock the period and the books are shut — no further entries, not even adjusting ones. It lands in a history that can be added to but never rewritten.
Getting here
Bring your history with you — and prove it arrived intact.
The honest fear about changing accounting systems is that the numbers shift in transit and you find out months later. So the move is a reconciliation, not an import.
Start from your trial balance
Export the closing trial balance from QuickBooks, Zoho or whatever you run now. Zelims maps it to your new chart by account code — exactly, never by guesswork.
Tie out to the penny
Every account is compared line by line against what you brought. Nothing is committed while a balance is unmatched or the two sides disagree.
Keep the certificate
When it ties, Zelims issues a migration certificate recording that your opening balances match the books you left. It's permanent, and your accountant can read it.
What the AI is allowed to do
The AI can suggest. It cannot post.
Email a bill to your books
Forward a vendor invoice to your workspace's address. It comes back read and classified, with the fields it lifted shown beside the document they came from.
Ask in plain English
"How much did we spend on freight last quarter?" The answer arrives with the entries it was computed from, so you can check the work rather than trust it.
Routines you write in a sentence
"Chase overdue invoices every Monday." Zelims restates what it will do before you switch it on — and only does the things it says.
Nothing the AI produces reaches your ledger until a person accepts it. It has no posting ability to misuse, and every session it runs is recorded.
In the box
What a multi-company operator actually needs.
- Per-company & consolidated dashboards
- Cash, receivables and profit — one company or all of them.
- Automatic intercompany elimination
- Transfers between your companies cancel in the group view.
- Close Command Center
- Every company's month-end state on one screen.
- Sealed close packages
- Hashed, permanent, exportable for your accountant.
- Invoicing & customer portals
- Branded portals where your customers see what they owe.
- Bills, approvals & payments
- Ordered approval chains, each step by a different person.
- Bank connections, read-only
- Transactions matched against your ledger. Rolling out now.
- Smart document inbox
- Email documents in; the AI reads and proposes, a person accepts.
- Reconciliations & tie-outs
- Subledgers proven against the ledger, continuously.
- Reports that tie out
- P&L, balance sheet, cash flow, margin and aging — per company or consolidated.
- Your data, exportable
- Trial balance and general ledger as CSV, close packages as JSON. It's your ledger.
- Unlimited users, no seat charges
- Your bookkeeper and your accountant included, on every plan.
Questions people ask
Straight answers.
What is Zelims?
Double-entry accounting software for people who own more than one company. Each company keeps its own books; you also get one consolidated view of the whole group, and a month-end close that produces a sealed, hashed record of what you signed.
Who is it for?
Owner-operators running several companies — holding structures, related operating businesses, a nonprofit alongside a business — and the bookkeepers and accountants who work in their books. It is not a fit if you run a single company and QuickBooks is working fine.
How is it different from QuickBooks, Xero or Zoho Books?
Those are built around one company per file. Consolidating several means exports and spreadsheets, and intercompany transfers get eliminated by hand every month. Zelims treats multiple companies as the normal case: intercompany nets to zero in the group view on its own, and the close is governed — approvals, tie-outs and a hashed package — rather than a checklist someone keeps in their head.
Can I bring my history from my current system?
Yes. You import the closing trial balance from your current system; Zelims matches it to your chart account by account, refuses to commit while anything is unmatched or out of balance, and issues a certificate recording that your opening balances tie to the books you left.
What does it cost?
Pricing isn't published yet. Zelims is invite-gated while we onboard a small number of operators at a time, and we talk about price directly during that conversation. Every plan includes unlimited users — we don't charge per seat, and your accountant doesn't cost extra.
Is my data separated from other customers?
Yes, and in the database rather than only in application code. Workspace-owned tables carry a PostgreSQL row-level security policy beneath the application's own scoping, so a query that arrives without your workspace's context returns nothing at all — and a continuous check fails our build if a new workspace-scoped table ships without one. A short, documented set of exceptions is scoped in the application instead: the tables read to identify your workspace before that context can exist, the file-attachment registry, and the customer-portal link registry.
What is the AI allowed to do?
Read documents, classify bank transactions, answer questions with citations, and draft routine work. It cannot post to your ledger — there is no posting capability in its toolset to misuse. Everything it produces is a proposal a person accepts or rejects before it reaches your books.
Put every company on one set of books.
Zelims is invite-gated while we onboard a small number of multi-company operators at a time — which means you get set up by the people who built it, and your history is tied out before you rely on anything. Tell us what you run.