Built for bookkeepers & accountants with many clients

Thirty clients, thirty ways of sending receipts — one intake fixes it

One client texts photos of every receipt. Another forwards a monthly email. A third drops off a shoebox of paper in March. tvmmm gives every client one place to send documents and one set of supplier rules — then publishes each client's records to that client's own ledger, with no retyping. When intake is consistent, month-end stops being a hunt for missing paper.

Start free trial Try the live demo ↓

No card details are requested for a trial request. The demo below runs on plain text — image OCR is not part of it, and the demo never posts to a real ledger. See the bookkeeper setup →

Illustration: a paper receipt turning into a checked ledger record

🧾 Sample receipt — scanning…

Grand Harbour Hotel · 24 Oct 2026 · EUR 1,284.00 · NL003456789B01

Vendor — Grand Harbour Hotel

Date — 2026-10-24

Total — EUR 1,284.00

✓ Totals match · Tax ID recognised · Ready to post

↓

Ledger entry (preview)
Travel & lodging · EUR 1,284.00 · Tax ID NL003456789B01 · ✓ checks passed

📥 Capture🔍 Extract👀 Review if unsure📒 Sync to ledger

Animated sample document, not a customer record. Run the same pipeline yourself in the live demo — every field carries its own confidence score, and anything below your threshold goes to review instead of posting silently.

The real problem is not one lost receipt

For a single business, losing a receipt is annoying. For a bookkeeper with many clients, the expensive problem is different: there is no single intake process at all. Documents arrive by text, email, shared drive and paper, and each one is handled differently depending on who picks it up.

No single intake

Thirty clients mean thirty habits. Some get entered twice, some never get attached to a transaction, and nobody can say, at a glance, what is still missing for a given client.

Inconsistent coding

The same supplier gets coded one way in January and another way in March, because the rule lived in someone's head instead of in the system. Month-to-month comparisons then stop meaning anything.

The year-end backlog

A busy period arrives, receipts pile up, and catching up feels large enough to keep postponing — until a shoebox arrives in March and the whole quarter has to be reconstructed.

How tvmmm is set up for multi-client work →

From any client's inbox to that client's ledger, in four steps

No templates to build, no field mapping to maintain. Give each client one intake route, set that client's supplier rules once, and the same pipeline runs for every client — publishing only to that client's ledger, never to another client's books.

One intake per client

A dedicated address, a mobile upload, or a shared folder — one route per client, and clients are told to stop sending documents anywhere else.

Extraction runs

Documents are parsed into vendor, date, tax ID, line items and totals. Each field carries a confidence score.

Your team reviews

Low-confidence fields are routed to a review queue. Confident documents flow through on your approval rules.

Publish to that client's ledger

Clean entries post to the client's own ledger, with tax codes and cost centres already mapped, and the original document kept alongside the record.

See the full feature list →

How tvmmm compares — by who it is for, not by feature count

The tools below are real, well-known products, described here in general terms so you can judge fit. tvmmm's own row is honest about status: its ledger connections are set up during trial onboarding and are not live from this demo.

tvmmm

Primary user: Bookkeepers and accountants with many clients
Capture: Dedicated intake per client; public demo parses plain text, signed-in accounts can test image OCR, email capture is an onboarding feature
Multi-client: Yes — one intake and one supplier-rule set per client
Pricing model: Per document, not per seat ($39 / 500, $129 / 5,000, Enterprise custom)

Dext-style capture tools

Primary user: Accountants and their clients
Capture: Mobile, email, web upload, some supplier-portal fetching
Multi-client: Yes, built for practices
Pricing model: Per client / volume-based

Hubdoc-style capture

Primary user: Accountants, especially Xero-aligned practices
Capture: Mobile, web upload, strong auto-fetch from bank and utility portals
Multi-client: Yes, built for practices
Pricing model: Bundled with a ledger subscription, or standalone

Expensify-style expense tools

Primary user: Business owners and finance teams
Capture: Mobile SmartScan, email, card auto-import
Multi-client: No — single-organisation focus
Pricing model: Per user / usage-based

The point of the table is fit, not a winner: a firm handling client bookkeeping usually needs capture and per-client publishing; a company whose own employees spend usually needs expense approval as well. tvmmm is positioned for the first job. See the honest status of every integration on the integrations page.

What to look for in a receipt tool — a checklist

Use this list to judge tvmmm, or any competitor, before you commit. Weakness in any one row creates manual work later, however good the demo looks.

Extraction accuracy

Why it matters: Wrong merchant, date or amount creates more manual work than it saves

What tvmmm does about it: Per-field confidence scores; low-confidence fields go to review, never post silently — test it in the live demo

Accounting integration

Why it matters: Direct publishing removes re-entry

What tvmmm does about it: Sandbox test push for signed-in accounts; production connection during trial onboarding, per ledger, via that ledger's own approval screen

Supplier rules

Why it matters: Recurring vendors should always be coded the same way

What tvmmm does about it: One rule set per client, set before the backlog arrives; see the setup section below

Mobile capture quality

Why it matters: Most receipts are captured at the point of payment, not at a desk

What tvmmm does about it: Mobile capture is an onboarding feature; the demo today parses text only

Multi-currency

Why it matters: Travel and international suppliers do not all bill in one currency

What tvmmm does about it: Currency is read from the total line in the demo; other formats route to review

Audit trail

Why it matters: For a tax review, the original document, its date and its ledger match must all be retrievable

What tvmmm does about it: Originals are kept with the record until you delete them; see Security

Bulk upload

Why it matters: Clearing a backlog one document at a time never gets done

What tvmmm does about it: Batch upload and review by supplier or month are part of the backlog workflow below

Set up a capture process that survives a busy week

Every receipt system fails the same way: it works for a month, then a busy period arrives, receipts pile up, and catching up feels too large to start. The design goal is therefore not completeness, but a habit that costs almost nothing on a bad day.

One route per client

Pick a dedicated address, a mobile upload, or a shared folder for each client. Tell clients exactly where documents go — and stop accepting them anywhere else.

Supplier rules first

Before the backlog comes in, set rules for recurring vendors: category, tax treatment, payment method. Most documents should then publish without review.

Match, don't just create

Decide, per client, whether a document creates a new transaction or matches an existing bank-feed entry — and apply that rule every time. Mixing the two is where most duplicates come from.

Capture at payment

The receipt is in hand and the business purpose is still in memory at the point of payment. Anything that requires sorting a pile later will eventually not happen.

What a receipt has to show to support a deduction

A card slip on its own rarely proves enough. What supports a business cost is evidence of what was bought, from whom, when, for how much, and why it was a business cost — plus a record that matches the ledger.

Itemised, not just a total

Keep the itemised receipt, not only the card slip — the itemisation is what shows what was actually bought.

Business purpose, noted at capture

Record the purpose while it is still remembered, not at year-end. For meals, travel and anything with a plausible personal use, purpose and attendees are part of the record, not an optional extra.

Matched to the ledger

An unattached receipt proves very little. The document, its transaction and its ledger entry should be retrievable together, for as long as the relevant return can be examined.

Retention periods differ by document type — ordinary supporting records, property records and payroll records do not all expire together. Check the current guidance for the categories that apply to you, and set retention by tax year. This page is general information, not tax advice.

Clearing a backlog without drowning in it

Bulk-upload the backlog, let supplier rules code what they can, and review the rest in batches — by supplier, then by month. Match documents to existing bank-feed entries instead of creating new ones, so nothing is recorded twice. Once the backlog is clear, switch the client to a single ongoing intake route and keep it there.

Try the demo on a sample backlog item Read the full bookkeeper setup

Try it on a sample receipt — or your own

This demo runs the real extraction pipeline: rule-based parsing, per-field confidence, and validation checks. Pick a sample, or paste / upload a plain-text receipt of your own. The café sample is deliberately imperfect — its totals do not add up and it has no tax ID — so you can see review-queue routing, not just the happy path.

Sample document (text)

Extracted record

Press “Run extraction” to see the parsed fields.

Try your own receipt text

Paste the text of a receipt (for example, OCR output or a plain-text invoice), or upload a .txt file. The same parser runs on it. Image OCR is not part of this demo; use the text version of your document here.

Receipt text Or upload a .txt receipt

What this demo does not do: it does not read images, it does not connect to your email or ledger, and its “simulate posting” button does not post anything to a real accounting system. Those connections are part of trial onboarding — see the demo guide.

Works with the stack you already run

tvmmm sits between document capture and your general ledger. Nothing has to be replaced, and existing approval chains keep working. Integration status is stated honestly on the integrations page — the demo itself does not connect to any of these systems.

Ledgers
Xero, QuickBooks Online, NetSuite, Sage Intacct

Expense apps
Ramp, Brex, Expensify, Airwallex

Storage & chat
SharePoint, Google Drive, Dropbox, S3 buckets, Slack and Teams approvals

Security and data handling, in plain terms

Financial documents deserve a short, checkable answer — not a vague promise. Full detail is on the security page.

Encrypted in transit and at rest

Data is encrypted in transit with TLS. Trial requests store only the contact details you submit.

Review before posting

Nothing posts to your ledger silently: low-confidence fields go to a human review queue, and approval rules decide what flows through.

Retention

Source files are kept with your account until you delete them, and can be purged on request. Structured records persist in your accounting system independently.

Per document, not per seat

Per document, not per seat: a bookkeeper's whole client list can be reviewed without paying per reviewer. Volume plans roll over unused documents for the first quarter. These are the plans offered — not a list of existing customers.

Starter

For small teams automating their first inbox.

$39/month

500 documents per month
Email forwarding + mobile capture
Field-level confidence scoring
QuickBooks and Xero sync (planned — trial onboarding)
Email support

Start free trial

Growth

For controllers running multi-entity close.

$129/month

5,000 documents per month
Everything in Starter
Review rules and approval routing
NetSuite and Sage Intacct sync
Expense app connectors
Priority support

Start free trial

Enterprise

For groups with custom compliance needs.

Custom

Unlimited documents
Everything in Growth
SSO, SCIM and audit logs
Regional data residency
Custom retention policies
Dedicated solutions engineer

Talk to sales

Compare plans in detail →

Common questions

How accurate is the extraction?

Every field carries its own confidence score, so anything below your threshold lands in the review queue instead of posting silently. Run the live demo — it shows the exact scores and checks for each document type, including a deliberately imperfect café receipt.

Does the demo read photos or PDFs?

No. The public demo parses plain text only. If your document is an image or PDF, use its text/OCR output for the demo; signed-in accounts can upload receipt images for OCR as a test.

Which languages and currencies does the demo handle?

The demo parser handles English month names, ISO dates (2026-10-24), and day-first numeric dates (24/10/2026), plus three-letter currency codes on the total line (EUR, USD, HKD and similar). Other formats are not silently guessed — missing or unrecognised fields are routed to the review queue. See the documentation.

Where is our financial data stored?

Demo text is processed in memory for the extraction result only and is not stored as a trial record. Trial requests store only the contact details you submit. Full detail: Privacy Policy and Security.

Can I try it with my own receipt?

Yes — in the demo above, paste or upload a plain-text receipt and run the same extraction and checks. Connecting your own inbox, mobile capture and ledger sync is part of the free trial.

Read all FAQs →