Integrations
Connect what you already run
Sources and systems of record are pluggable connectors, not a fixed list. If it exposes an API, a mailbox or a file drop, it can be connected.
What connects today
Everything below is built and shipping. Anything not on the list is a connector we can add — the interfaces are deliberately small.
Sources
Bring invoices in from wherever they land.
- Microsoft 365 / Exchange Online — connect the mailbox in a click
- Google Workspace / Gmail — connect the mailbox in a click
- Any other mailbox over IMAP
- SharePoint and OneDrive folders
- Google Drive folders
- Samba / Windows shared drives
- SFTP and FTP watched folders
- Salesforce record attachments
- Direct upload and drag-and-drop
- PDF, PNG, JPEG and TIFF — including faxed .tif and phone photos
Systems of record
Post approved invoices where your finance team already works.
- Microsoft Dynamics 365 Finance & Operations
- QuickBooks Online — approved invoices become Bills, posted over the Intuit API
- Tally (TallyPrime) — purchase vouchers, posted to a Tally gateway you expose to us or written as import-ready XML to a folder you already watch
- SAP Ariba, over cXML
- An SFTP drop, as JSON or CSV
- A Samba / Windows shared drive, as JSON or CSV
- Any other ERP, AP or workflow system reachable over an API — tell us what you run
Master data
Match against your own records, not a guess.
- Vendor master and PO master, per organization
- Import by CSV, or pull on a schedule from your ERP
- Vendors matched on tax ID first, then fuzzy name
- An invoice quoting an unknown PO is held for review
How connectors work
Two small interfaces, not a rewrite.
- A source only has to hand us a file and an identifier
- A destination only has to accept a vendor invoice and be idempotent
- Field schema, thresholds and routing are per-organization configuration
- New connectors ship without touching extraction or review
Need a different ERP or source? The connectors are pluggable interfaces — tell us what you run.
Tell us your stackWhat a connector actually has to do
Very little, which is why new ones are quick. A source hands us a file and a stable identifier — that is enough for us to de-duplicate, render and extract it. A system of record accepts a finished vendor invoice and honours an idempotency key so a retry cannot create a duplicate.
Everything else — your field schema, your confidence thresholds, your approval rules, your vendor matching — is configuration on your organization, not code.
Tell us what you run
Send us your sources and your system of record and we will confirm the fit before you commit to anything.