Accounts by role, MFA everywhere
A named account for every staff member, multi-factor on all of them, admin rights held by the fewest people possible. No shared “info@” password living in a sticky note.
TrueFigures — AI operations for Ontario bookkeeping firms
It starts with a Google Workspace your firm actually runs on — accounts, shared drives, and payroll data behind a real wall. Then TrueFigures watches one Drive inbox, reads each receipt with a vision model running on your own hardware, applies the Ontario rules you already know, and appends a validated row to your Master Invoice Ledger. Anything it can’t read cleanly, it flags with a written reason.
The automation does the reading, the math, and the filing. The professional judgement — what’s a personal expense, what needs chasing, what gets signed — stays with the bookkeeper.
Start here
A bookkeeping firm holds the most dangerous combination in a small business: client bank details, CRA credentials, payroll files, and one shared inbox where anyone can ask for any of it. Before a single receipt is automated, the workspace gets a real perimeter — a named account per person, payroll and partner data behind a wall, permissions that follow the person and end when they leave. AI hasn’t changed what’s at risk. It has made the convincing email cheaper to write.
One foundation, then the money work, then the upkeep. No layer is useful without the one beneath it — which is why every engagement starts with the workspace.
A named account for every staff member, multi-factor on all of them, admin rights held by the fewest people possible. No shared “info@” password living in a sticky note.
Organizational units and sharing rules put payroll, partner draws, and client tax IDs behind a wall — so a phished session, a junior staffer, or a staff AI tool can’t reach them by accident.
Access follows the person, not the folder someone forwarded. When staff turns over — and it will — you can revoke one account and know exactly what they could see.
External-sender banners, private-by-default sharing, and device and session rules — the unglamorous settings that make a fake supplier email look fake before anyone clicks it.
the threat surface moved
None of this needs a sophisticated attacker any more. The things small firms actually see:
Payment diversion
A supplier “changes their bank details” in an email that reads perfectly.
Business email compromise
A real inbox, a real thread, one quiet rule that forwards everything out.
Synthetic documents
Receipts and invoices generated wholesale — clean scans, no paper behind them.
Gemini is optional and comes later, if you want it — inside the same perimeter. Nothing on this page depends on it, and nothing about it is switched on by default.
Nothing here changes what your staff knows or how your clients send things. It changes where the hours go.
Today
With TrueFigures
Today
the month-end crunch
Hours per client spent keying receipts by hand — deriving HST on tax-inclusive slips one at a time, separating tips, fixing what junior staff entered against the wrong rule.
With TrueFigures
the month-end crunch
Staff drop a file in a folder. The pipeline types the row — vendor, date, totals — and files the receipt itself.
Today
the rulebook
Invoices over $150 need a valid HST registration number. Meals are a 50% ITC, not 100%. Tips aren’t taxable at all. Miss any of it and the CRA notices before you do.
With TrueFigures
the rulebook
The rules live in code and are checked to the cent on every document — never reinterpreted, never tired at 11pm. What’s ambiguous still waits for a human.
Today
the chase
The receipts that never showed up, the folders that say “final_v2”, the client who swears they sent it. Entry is only half the cost — so is knowing what’s missing.
With TrueFigures
the chase
Named folders, renamed files, and a review queue that says exactly what’s missing — the gap becomes visible instead of discovered at filing time.
Layer 01 built the folder and the perimeter. This is what happens once a file lands in it — four steps, in the order they actually run.
01
A scan, photo, or PDF lands in the client’s Google Drive inbox — either dragged in or scanned straight to it. No new app for your staff, no retraining.
02
A vision model reads vendor, date, totals, tips, and tax lines — including scanned pages with no text layer. The model runs locally; the document never leaves your hardware.
03
The Ontario rules, in code: 13% HST, the 13/113 derivation on tax-inclusive receipts, the 50% meals ITC, tips excluded from the taxable base, and an HST registration-number check on anything over $150.
04
One validated row lands in your Master Invoice Ledger; the file is renamed and archived. If anything is unclear, the document becomes a flagged review row with a written reason — never a silent guess.
Every document the pipeline touches ends in exactly one of two states: a clean ledger row, or a review flag with a written reason. There is no third state.
HST split, derived tax-inclusive amounts, and ITC logic are computed in code and validated to the cent — not re-interpreted per document.
Every row is clean or carries a written reason. Cut-off scans, unreadable totals, and rule violations surface — they don’t pass silently.
The same receipt cannot land twice. Deduplication runs against the real ledger before any commit.
Each processed document is renamed to a standard form and moved to the archive. The inbox stays empty; the audit trail stays complete.
TrueFigures removes the typing, not the review. Ambiguous documents wait for a human — that’s the design, not a limitation.
Most capture tools send your clients’ documents to their cloud before you see a single field. TrueFigures takes receipts seriously because you take them seriously — and it starts with a workspace whose perimeter you control.
The Layer 01 workspace puts payroll and partner data behind organizational units before any automation exists. The pipeline is then granted access only to the inbox and archive folders it actually needs — nothing else in the tenant.
The vision model that reads receipts can run locally — on premises or on infrastructure you control. The document bytes stay inside your perimeter.
The inbox, the archive, and the ledger are your Google Drive and your Google Sheet. If we part ways, you keep every byte.
Cloud model inference is available if a firm wants the leanest possible setup. The local option exists for firms that won’t send client documents anywhere. You pick; we’ll say which you chose.
Three layers, priced so a firm can start with the foundation and add the next when it pays for itself: the Workspace your team runs on, the pipeline that fills the ledger, and the retainer that keeps both alive.
01
The foundation — where every engagement starts.
$1,000CAD
one-time · one week
02
Layer 02 — automate the money work.
$1,500CAD
one-time build & deploy
03
Layer 03 — so it never breaks.
$550CAD
per month · recurring
Every engagement starts with the Sprint — the workspace comes first. Prices in CAD; Ontario HST applies.
Talk it through on a callTrueFigures is built and run by Zylan Labs in Oshawa, Ontario. The pipeline you’ll see on the demo call is the same one running in our test firm’s sandbox — live Workspace, live folders, live ledger, real Ontario receipts. We’ll show you yours before you buy anything.
About Janaka and Zylan Labs →Book a 15-minute call. We’ll show the sandbox running end to end, answer the technical questions, and tell you honestly if the pipeline wouldn’t pay for itself at your volume.