The platform
How Root works underneath. Point of sale, accounting, customers, and AI read and write one database, with no integration layer between them, so a single charge writes one record that posts to the books, updates the customer, and moves analytics at once. This is the foundation the whole business runs on.
The connected flow
A charge anywhere, at the bar, the spa, retail, or a room, becomes one order record. From that single record, four things happen at once.
Nothing to wire together. No nightly sync. Every event is idempotent, so a retry never double-counts.
The order becomes a balanced journal entry. Debits equal credits, validated to the cent, the instant the charge clears.
The profile records the visit and the spend. Any house-account or AR balance moves with it, in the same record.
Revenue, covers, and margin update as the charge lands. There is no overnight roll-up and no export to wait on.
Root AI reads the same live record and flags anything that looks wrong, the moment it happens rather than at month-end.
The folio
For multi-outlet operations, a charge across food and beverage, spa, retail, activities, or a room posts to one guest or member folio. Drill it by name, by room, or by member number. In real time, never an overnight batch.
The differentiator
Root keeps a true double-entry general ledger. Every transaction posts a balanced journal entry, with debits equal to credits, validated to the cent. Trial balance and period close happen inside the system, not in a tool you export to.
Accounts payable and accounts receivable run as subledgers. Bank reconciliation lives here too. Gift cards are held as a liability until redeemed, then recognized as revenue. A tax engine applies effective-dated rates, so a rate change never leaves a double-count or a gap.
No QuickBooks. No Restaurant365. No month-end spreadsheet.
| Account | Debit | Credit |
|---|---|---|
| Sales revenue | — | 1,284,902 |
| Cost of goods | 436,120 | — |
| Gift card liability | — | 52,840 |
| Accounts receivable | 18,305 | — |
Foundations
The platform holds money, so it is built the way a financial system has to be: tenant-isolated rows, idempotent events, an append-only audit trail, and amounts stored as integer cents. These are not features. They are the floor.
Every record is scoped to its tenant by row-level security. One business cannot read or touch another's data.
A retried or duplicated event is a no-op. The books never double-count, no matter what the network does.
Every change is recorded append-only and immutable: who changed what, and when. Nothing is overwritten or erased.
Money is handled as exact integer cents, never floating point. A fraction of a cent cannot appear or disappear.
Payment card numbers are tokenized at the point of capture. They never touch Root's servers, so there is nothing to leak.
Stored credentials are encrypted with AES-256, at rest, so a copy of the data is not a copy of the keys.
Always-on integrity
Root runs more than thirty background reconcilers and detectors, continuously. The platform is always proving its own numbers are right, so a problem surfaces the day it starts rather than the day you find it.
Security and compliance
A day on Root
No switching tools, no end-of-day stitching. The first order at open and the bank match at close write to the same ledger.
The first orders ring in. The books open themselves, with nothing to reconcile from yesterday, because last night already closed.
Two stations work one check without colliding. The kitchen display routes each course, and every tender posts to the ledger as it lands.
Root notices a regular has gone quiet and drafts a win-back message. You read it, tap approve, and move on.
Tips are reconciled, the deposit is matched, and the day is squared away without a spreadsheet.
There is no scramble. The books have been closing themselves all month, so the period is already done.