Reconcile across entities. Explain every difference. Hand the auditor a pack, not a folder.
TieOut Pilot reads the balance exports, invoices, bank statements and email threads your entities actually send each other — PDF, scanned, Excel, pasted text — matches what matches, explains what doesn't, and drafts the confirmation letters and PBC schedules your auditor asks for. No ERP integration required.
- Works on exports and documents, not on live ERP connections
- Every difference comes with a cited explanation and a draft adjusting entry for a human to approve
- Audit evidence packs with cross-references, ready for the PBC list
| Pair · ref | A books / B books | Status | Explanation |
|---|---|---|---|
HK Trading Ltd → SG Holdings Pte INV-20931 | 42,180.00 42,180.00 | matched | |
SG Holdings Pte → HK Trading Ltd CN-00412 | −3,600.00 −3,600.00 | matched | |
HK Trading Ltd → DE GmbH INV-20944 | 18,250.00 18,200.00 | explained | Bank fee EUR 50 netted by DE — statement p.3 line 14 |
DE GmbH → HK Trading Ltd INV-7781 | 9,900.00 — | open | No invoice received; DE statement p.1 — request copy |
SG Holdings Pte → DE GmbH INV-0552 | 27,000.00 27,310.50 | explained | FX at booking date vs settlement date; diff 310.50 — draft JE #3 |
The work it takes off your desk
Who it is for: Outsourced accounting firms and mid-market group finance teams that reconcile across entities without a shared ERP.
Two screens, one accountant
Entity A sends a PDF invoice, entity B sends an Excel balance; someone eyeballs both and writes an email. Repeat for every pair, every month.
Audit season repeats itself
The same evidence gets pulled, renamed and re-sent for every PBC request because nothing was indexed when the close happened.
Explanations live in inboxes
The reason a difference was accepted last quarter is in someone's Sent folder, not in the workpapers.
From the case library
28 situations documented so far — each with the documents involved, what the agent does and what you get back.
Posted to the wrong counterparty entity
A's invoice to SG Holdings was posted by the group AP team against HK Trading; SG shows nothing, HK shows a payable it d…
Same invoice posted twice by the buyer
B's AP posted INV-20931 on receipt of the PDF and again when the paper copy arrived. B shows double the payable.…
Trade balance booked to a loan account
A payment for services was posted by B to the intercompany loan account instead of trade payables; the trade balance loo…
How it works
Deterministic where it should be deterministic; a language model only where documents have to be read and explained. Every output cites its source.
You give it
Trial balances or intercompany ledgers per entity (Excel/CSV), the invoices and credit notes behind them (PDF or scans), bank statements, and the email thread where the two sides argued about the 50-dollar gap.
The agent
Normalises every document into transactions with provenance, runs deterministic matching (amount, counterparty, period, reference — tolerance rules you set), then reads the unmatched items against invoices and emails to propose a reason: FX rounding, bank fee netted, timing, duplicate, missing document.
You get back
A reconciliation workbook with matched / explained / open items, cited explanations linked to the source page, draft adjusting entries, confirmation-letter drafts per counterparty, and a PBC evidence pack with an index.
Token usage scales with documents, not with seats: each close reads every invoice page, statement and email thread for every entity pair. A 12-entity group with 400 intercompany invoices a month is roughly 20–60 million tokens per close. Matching itself is deterministic code and costs nothing; the model is spent only on reading and explaining.
Pricing
One RU = one document page read and classified, or one unmatched item explained. Matching runs are free. Model tokens are a separate meter billed at the provider's list price. Bring your own key (BYOK) and the model meter is zero; use our channel and tokens appear on the same Google Cloud invoice.
Pay as you go
- No minimum
- All features
- Model tokens at list price or BYOK
- Email support
Practice
- Overage $0.10/RU
- Client workspaces
- PBC pack templates
- Priority support
Group
- Overage $0.08/RU
- SSO (Google, Microsoft)
- Retention and legal hold controls
- Named support
Enterprise
- Private offer on Marketplace
- Data residency options
- Custom tolerance and policy packs
- Dedicated onboarding
| Read one invoice page or statement page | 1 RU |
| Explain one unmatched item (with citations and draft entry) | 3 RU |
| Draft one confirmation letter | 5 RU |
| Assemble one PBC evidence pack (per entity, per period) | 20 RU |
reconciliation_units (per RU)model_access_usd (provider list price, cents)- Annual plans bill once; included monthly units are netted before any overage is reported. Usage reports go to Google hourly; your invoice shows them as separate line items.
Security and data
One company, one set of policies, across every product we ship.
Your documents stay yours
Tenant-isolated storage on Google Cloud; retention you set; deletion on demand; never used to train models.
One legal framework
Privacy policy, terms, DPA (GDPR / UK GDPR / PDPO) and the sub-processor list are published once at carnegieintel.com and apply to every product.
Transparent metering
Every metered unit is itemised with request ids in your workspace before it reaches your invoice. Model tokens are billed at the provider's list price, never marked up silently.
Questions
Does it post entries to our ERP?
No. It drafts adjusting entries for a human to approve and post. TieOut Pilot never writes to your books.
What formats does it read?
Excel/CSV exports, PDF (text and scanned, OCR included), images of receipts, and email text or .eml exports. Bank statements in PDF or CSV.
Is the matching done by the AI?
No — matching is deterministic code with tolerance rules you control, so it is repeatable and auditable. The language model is used only to read documents and explain unmatched items, and every explanation cites the source page.
Where is our data?
Google Cloud, asia-east1 by default (EU/US on request). Documents are retained for the period you choose (default 90 days) and can be deleted on demand. See the privacy policy and sub-processor list.
Which models?
Google Vertex AI models by default via our channel, or bring your own key for Anthropic, OpenAI or Google. Model tokens are a separate meter at list price.
How do we buy?
Through Google Cloud Marketplace — the charge lands on your existing Google Cloud invoice and counts toward your commitment — or directly from us by invoice.
Insights
Field notes written for the people who do this job every day.
The fifty-dollar difference that costs four hours
Why the smallest intercompany differences are the most expensive to clear, and what changes when the explanation arrives…
Why reconciliation tools assume an ERP you don't have
Close-management platforms are built for groups with one finance system. Outsourced firms and most mid-market groups hav…
What auditors actually want in a PBC pack
Not more PDFs. An index that goes from their request line to the balance to the invoice page without asking you, and an …
TieOut Pilot is in early access.
We are onboarding a small number of design partners with real documents and real deadlines. Tell us what you reconcile, dispute, diagnose or bid on, and we will set up a workspace with your material.