Capture, validation, duplicate checks, coding and ledger sync — each stage is a separate module you can enable independently. Most teams start with capture and expand from there.
Every module writes to the same document record, so context from capture stays available when coding and syncing.
Email forwarding, mobile camera, drag-and-drop upload, watched folder or S3 bucket. The document lands in one queue regardless of where it started.
Vendor, date, tax ID, line items, subtotal, tax breakdown, total and currency — each returned as a typed field with its own confidence score.
EU VAT numbers are checked against VIES, UK numbers against HMRC, and US exemption certificates against expiry date before any record posts.
Vendor, amount, date and document hash are compared against 24 months of history. Near-matches surface for review instead of auto-filing.
Map vendors, categories and cost centres to GL accounts with conditions. Rules evaluate top-down and the winning rule is stored on the record.
Two-way posting to Xero, QuickBooks, NetSuite and Sage Intacct. Approved documents push automatically; edits made in the ledger flow back.
Each stage is idempotent, so a failed run can be replayed without creating duplicate records.
File is checksummed, virus-scanned and routed to the extraction stage. Original is stored under your retention policy.
Layout analysis identifies the document type, then field extraction runs against the matching template.
Tax IDs, arithmetic totals and currency are checked. Discrepancies lower confidence on the affected fields only.
Coding rules assign GL account and cost centre, then the record posts to your ledger if approval thresholds are met.
Every module is available through the REST API, so tvmmm can sit inside an existing approval flow rather than replacing it.
Signed callbacks for parsed, validated, approved, posted and failed states, with automatic retry on non-2xx.
Replay-safe writes. A retried request with the same key returns the original result instead of duplicating it.
A separate environment with synthetic vendors and tax IDs, so you can test rules without touching production data.
Every field change records who made it, what the prior value was, and which rule applied.
AES-256 at rest, TLS 1.3 in transit, customer-managed keys available on Enterprise.
Pin processing and storage to EU or US regions. Data does not leave the region you select.
SOC 2 Type II audited annually, with a DPA and sub-processor list available on request.
Upload a sample batch before connecting anything. Most teams know within one pass whether the field coverage holds for their vendors.