It’s the 4th. The statements are here.
Three accounts, a card, and a hundred-and-some lines each. Someone has to read every one, decide what it was, and key it into QuickBooks. That someone is you, or someone you pay.
Act 1 — The month you know
And it’s not the typing that gets you.
It’s the deposit that’s already in there from an invoice, waiting to get booked twice. The check with no name on it. The month that’s off by $61.40 and won’t say why. A single double-booked deposit can take days to find and unwind. Hand-coding is slow; undoing hand-coding is worse.
Act 2 — The ride: one statement, start to finish
01
The statement goes in. That’s your whole job.
Upload the PDF from your phone or desk — the same file the bank gave you. No bank logins, no feed connections. The file is checked and fingerprinted so the same statement can’t sneak in twice.
Upload a statementReview queue
EntityRidgeline Excavating
📄 june-2026-checking.pdfPDF, ≤ 4 MB
Upload
✓ Done — 87 items ready to review.
02
First it has to tie. To the penny. Or nothing happens.
Beginning balance plus deposits minus withdrawals has to equal the ending balance the statement itself printed — and every line has to sum to the statement’s own totals. If it doesn’t tie, Bookhand refuses the whole statement rather than ingest half of one.
03
Then every line gets a proposal — in plain English.
“Fuel stop, looks like the truck card — Fuel & Auto, 94% confident.” Bookhand reads against your live QuickBooks chart of accounts, so if your accountant renames an account, the next run already knows. Every proposal shows its reasoning; nothing hides in a black box.
Diesel at the pump — the truck card’s usual fuel stop.−$84.12
→ Ridgeline Excavating · Fuel$84.12
ApproveChange accountHoldReject
04
When it isn’t sure, it doesn’t guess. It asks.
A deposit with no name, a check with no payee, a line that could be two things — those hold, with a short card that asks the one question a human can answer: “Who was this check written to?” The judgment calls — owner draws, money moving between your companies — get routed to your accountant with the question already written.
Check #2151−$650.00
The statement shows this check’s number and amount but not who it was written to. Look it up and enter the payee — the engine categorizes it from there.
Who was this check written to?Identify & categorizeI’m not sure → CPAReject
05
Nothing posts until a human says so.
This isn’t a caveat — it’s the feature. You (or your bookkeeper) tap through the queue on your phone: approve, fix, or hold. Every tap is written to a permanent audit log with your name on it. AI proposes; people decide.
Transactions to review
14 left · 2 checks need a payee
You can decide these
Parts counter run — job supplies for the week.−$212.47
ApproveHold
Mulch and fittings — could be job supplies or a kept tool.−$96.30
ApproveHold
Checks — who was this written to?
Check #2151−$650.00
Who was this check written to?
06
Approved entries land in QuickBooks as native records.
Real Purchases and Deposits in your actual books — not a side ledger, not a pending feed. Every record carries a durable tag, and every posting run first checks QuickBooks for what’s already there, so the same entry structurally cannot post twice.
07
Then Bookhand reads them back.
After posting, every record is re-fetched from QuickBooks and compared field by field — amount, date, account. And if a posted entry ever needs changing, it’s corrected or voided to $0 with a note, never deleted. Your books keep their whole history.
08
The money you already entered gets matched — never booked twice.
If you invoice in QuickBooks, your customer payments are already there — so Bookhand matches the bank deposit to your record instead of creating a new one. Same for payroll run through QuickBooks. Double-booked income isn’t a thing it avoids carefully; it’s a thing the guards make impossible.
09
The month ends with a signed statement of where every line went.
Posted, matched, or held with a named reason — every single line, with the totals tied to the statement’s own printed numbers, both directions. That’s the month certificate, and a named human countersigns it. If anything in the month changes later, the certificate flags itself stale — and a daily watch keeps scanning your books for anything unexpected.
Month certificate — June 2026
Ridgeline Excavating · operating checking ····4417
complete, with named holds
Posted — 63 lines$48,112.40
Matched to your records — 19 lines$36,210.55
Held, with a named reason — 2 lines$1,412.10
Undecided — 0 lines$0.00
✓ Ties to the statement’s own totals — both directions
held: waiting on the loan statement’s principal / interest — 2 lines · $1,412.10
Act 3 — The month after Bookhand
Open QuickBooks. It’s just… done right.
Clean native records with the check numbers on them, deposits matched to the payments you recorded, an audit trail behind every entry — and nothing deleted, ever. Your accountant gets a book they can trust, with the judgment calls queued up and the questions pre-written.
And here’s the part of your month you get back:
Keying transactions line by lineabout 2 minutes each — 3–4 hours a monthTick-and-tie against the statement totals30–60 minutes per statementHunting duplicate deposits1–3 hours per account, per monthClosing out the month by hand2–4 hours per account, per monthFiguring out who each check was written to1–3 minutes per checkRe-deciding the same vendor every month— approve it once, Bookhand remembers
And here’s what Bookhand will never take from you.
Every entry still gets your yes. Business-vs-personal, owner draws, tax questions — those are yours and your accountant’s, always; Bookhand just tees them up. It never touches invoicing, never runs payroll, never posts income you already record, and never guesses.
You decide
- Every entry that posts — approved by a human, always
- Business vs. personal, owner draws, tax questions (with your accountant)
- Who each unnamed check was written to
- Whether a proposed match is confirmed
Bookhand does
- Reads and ties every statement to its own totals
- Proposes every entry with a reason and a confidence
- Posts approved entries as native QuickBooks records — then reads them back
- Matches what you already recorded so nothing books twice
Who it’s for
Owners of service & trades businesses
You send statements and answer plain questions. No software to learn — the queue reads like English and works from your phone.
Owners with messy, real books
Multiple companies, mixed-use cards, backlog, personal spend tangled in — that’s the normal case here, not the exception.
Bookkeepers & firms
The keying and matching grind automated, final judgment kept human. Access is granted per company, so a bookkeeper sees only what they should.
White-glove start. We do the setup with you.
- Connect QuickBooks. The standard Intuit sign-in, once per company — accounting scope only. We never ask for payments or payroll access.
- A short intake — where Bookhand becomes yours. Who records income, how payroll runs, your companies, your vendors. Every client’s rules are built around exactly that — set up with us, not picked from a template — which is why it holds up on messy, real books.
- The bank-feed decision. We walk you through it so the QuickBooks feed can’t re-import copies of what Bookhand posts.
- Logins. For you, and your bookkeeper if you have one — each limited to the companies they should see.
- Send the first statements. Expect the first month to hold a lot — that’s Bookhand being honest before it has learned your vendors. It gets sharper every month.
Straight answers
Does the AI post to my books on its own?
No. Every entry is approved by a human first. There is no invisible-write mode.
Do you need my bank login?
No. Bookhand reads the statement PDFs — no bank credentials, no Plaid.
I already enter my customer payments. Won’t this double them?
That’s the exact problem the matching layer exists for — your records get matched, never re-created.
What if a statement is wrong or short a page?
Then nothing happens: if it doesn’t tie to its own printed totals, Bookhand refuses the whole file.
Can it delete or change things behind my back?
It deletes nothing, ever. Voids are $0 records with a note; corrections are audit-logged with a name attached.
Does it do payroll or taxes?
No. Payroll run through QuickBooks gets matched, not re-created. Tax and judgment questions go to you and your accountant — with the question pre-written.
What access does it have?
QuickBooks accounting scope only, via Intuit’s standard connection. No formal security certification yet — and here’s what does exist: your data is isolated row-by-row from every other client, QuickBooks tokens are stored encrypted, write permissions are separated, and every action lands on a full audit trail.
What does it cost, and how do I start?
Onboarding is white-glove and operator-led — we set it up with you. Use the form below and we’ll take it from there.
Send us one month. See the ride with your own statement.
No commitment — tell us a little about the business and we’ll reply within one business day.
Got it. ✓
Thanks — we’ll reply within one business day. If the month-end pile is on your desk right now, leave it there. That’s kind of the point.