Send one month
Forward the bank CSV, the POS daily summary and the payroll journal to the private address we give each location. Nothing installed at the restaurant.
Your restaurant clients' books fill up with problems QuickBooks can't see — cash that never reached the bank, tips that don't match payroll, hundreds of uncategorized charges. LedgerInbox finds every one, stacks them in a single list, and clears each with one keystroke.
A $30/day drawer shortage is $11,000 a year your client can't prove.
no card · cancel anytime · works alongside Shogo & Bookkeep — keep them, we prove the cash
Every step of closing a restaurant's books lives in one place. You send the files; the list comes back.
Forward the bank CSV, the POS daily summary and the payroll journal to the private address we give each location. Nothing installed at the restaurant.
A format we do not recognise is rejected by name, with the offending lines quoted. We never guess at a column and we never half-import a file.
Files are fingerprinted by content. Re-sending the same bytes returns 'already have it' and adds nothing — so a forwarded email chain cannot double-count a month.
Card batches from the POS are matched against the deposits that actually landed in the bank. What never arrived becomes a finding.
Counted cash against banked cash, per location, per day. A $30/day shortage is $11,000 a year that nobody can currently prove either way.
Tips accrued at the register against tips paid through payroll, checked against the tip-liability balance sitting in QuickBooks.
Everything lands in a single inbox with its evidence and the arithmetic shown. J and K move, A resolves, S dismisses.
Accepted fixes post to QuickBooks — idempotent, logged, reversible, and refused outright if the period is already closed.
A per-client, per-period certificate showing what was reconciled, what was found, and what is still open. Signable, and provable later.
Shipped means shipped — each line tracks a roadmap mark that is only set once it is true in production. 30 of 33 are live today; what is not built yet says so.

Move one. Sysco lands uncategorized in seven restaurant books the same week. QuickBooks Online is built around a single company file, so Intuit's AI categorizes one; Double's firm workflow doesn't batch across books either. Press B. Confirm the books. Post — all seven. Total wall-clock time: ~3 seconds.
Move two. The drawer came up $312 short across March. Shogo posted the daily sales entries perfectly and still can't see it — it lives between the POS cash line, the paid-outs, and the deposit slip. LedgerInbox computes it daily, queues it, and one keystroke either posts the adjusting entry or asks the manager to explain it.
This is the demo that sells. Not “watch me press J” — “I ran your client's March files and found $7,400 of cash nobody can account for.”
Every finding arrives with the evidence and the line-by-line derivation — because no bookkeeper signs a number she can't see derived. Nothing posts to QuickBooks without a human keystroke.
Illustrations from demo data — the same derivation every finding carries in the product.
| drawer count | $486.00 |
|---|---|
| bank deposit | $533.00 |
| over/(short) | −$47.00 |
Name the locations and set the cash tolerance you'll tolerate. Everything here is saved and carries straight into onboarding — nothing to re-enter.
Unlimited seats — we don't charge you for having colleagues. A $30/day drawer shortage is $11,000 a year your client can't prove; one caught leak pays for the year. And the price you sign at is the price you renew at.
Per-location pricing means your bill is your book of business. Here it is, exactly — next to what one unreconciled drawer costs.
Unlimited seats at any count — the whole firm on every book, no per-user math.
| Core · 12 × $40 | $480/mo |
|---|---|
| Plus · 12 × $70 | $840/mo |
| A full year of Core · $480 × 12 | $5,760/yr |
| One location's $30-a-day drawer leak | $10,950/yr |
A year of Core for all 12 locations costs less than one location's unproven drawer leak.
A restaurant bookkeeper considering LedgerInbox is also weighing QBO Accountant, Double, Uncat, and Shogo or Bookkeep. Here's the matrix you're building in your head, written down. We win on the close — tips, cash, batch, keyboard. They win on the parts we deliberately don't build, and Shogo/Bookkeep isn't even a rival: they post the daily sales entry; we reconcile what they post.
| You're here LILedgerInbox Core10 locations · unlimited seats | QBOQuickBooks Online AccountantIntuit | DDoubleAI bookkeeping workflow | UUncatUncategorized Q&A | SShogo / BookkeepDaily sales entries | |
|---|---|---|---|---|---|
Annual cost 10 locations · published list prices | $4,800/yr$40/location/mo | $1,788/yrAccelerate · $149/mo | ~$2,400/yr$10–25/client/mo published | $1,080/yr$9/client/mo | ~$4,200/yr$30–40/location/mo typical |
§ 01 The close· the reconciliation nobody else runs | |||||
| Tip-liability reconciliation | |||||
| Cash over/short, daily | |||||
| Manager Q&A links (no-login) | |||||
| Email report ingestion (Toast → inbox) | |||||
§ 02 Speed & ergonomics | |||||
| Keyboard-first inbox | |||||
| Batch across every client's books | |||||
| Sub-100ms keystroke latency | |||||
| Per-firm policy memory (visible, editable) | |||||
§ 03 Where they win· honestly | |||||
| Daily sales journal entries | native | ||||
| Practice management & workflow | |||||
| $9 price point | |||||
| 1099 filing | |||||
§ 04 Plumbing | |||||
| QBO write-back (2-way) | native | ||||
| Xero support | |||||
| SOC 2 Type II | |||||
Best for | Pick us when…Restaurant bookkeeping firms that want tips, cash, and exceptions proven every close. | Pick them when…Firms already deep in the Intuit stack. | Pick them when…Firms whose bottleneck is practice workflow, not reconciliation. | Pick them when…Solos who only need client Q&A on uncategorized transactions. | Pick them when…Posting the daily sales journal entry — pair us with them. |
The things restaurant bookkeepers email us about, in the order they ask. No support ticket required.
QBO Accountant is a horizontal practice tool that bundles categorization AI, 1099 management, client communication, and a dozen other things — all forced into a single-company architecture. It has no idea what a drawer count is, and it never will.
LedgerInbox does one thing: turn every exception in a restaurant firm's books — uncategorized vendors, cash over/short, tip-liability drift — into a sub-100ms keyboard loop across every book at once. QBO stays the ledger. We're the queue inside your close.
No. QBO stays your canonical ledger. We sit on top — reports and bank data flow in, we run the inbox, accepted lines post back to QBO as journal entries or matched bills.
Your clients still see QBO. You stop having to live inside it.
Two reasons. First, vendor overlap: a restaurant-only client base shares Sysco, US Foods, Restaurant Depot, the liquor distributor, Toast fees, DoorDash fees — which makes the batch keystroke hit harder here than in any other vertical.
Second, tips and cash are the vertical's unsolved reconciliation problem — money that never touches a bank feed. A tool for everyone is a tool for no one's close.
Double is a strong AI workflow for generalist firms — it doesn't reconcile tips or cash. Uncat asks your client about uncategorized transactions at $9/client — useful, narrower than a close. Booke is an RPA categorizer. All of them start at the bank feed.
Shogo and Bookkeep aren't competitors at all: they post the daily sales entry, and they do it well. Keep them. We reconcile what they post.
No. They post daily sales; we reconcile tips, cash, and exceptions they structurally can't see — the drawer shortage lives between the POS cash line, the paid-outs, and the deposit slip, and no sales-entry tool looks there.
Most of our design partners run both.
Three things: Toast's scheduled email report pointed at the location's LedgerInbox address, the payroll journal, and a bank export.
No API approvals, no logins from the restaurant, nothing installed on the POS. If the manager can forward an email, you're live.
We haven't published measured accuracy numbers yet — we're pre-launch and any percentage we put here would be a guess. Once design partners have been running for a quarter we'll publish a methodology page with the real curves.
The pitch isn't raw accuracy — Intuit claims 95–98% and we're not promising to beat that. The pitch is what happens with the part that's wrong: speed of correction, batch correction across clients, no context switch to fix it.
Not yet SOC 2 certified — we plan to engage an auditor at Team-plan scale and this page will update with the real audit window when work begins. Today: data is encrypted at rest in Postgres with per-firm row-level security. Bank feeds via Plaid are optional plumbing, not a requirement — and Plaid handles bank credentials; we never touch them.
The AI categorization model sees only the bank-line description, the amount, the date, and your firm's policy memory — never balances, never client PII beyond the transaction line. Read the security page →
Open your books and see the shortages, the tip drift and the vendors — before you decide anything.
no card · cancel anytime · export your data whenever you want