API connectors: expenses come in, supporting documents go back.
The platform replaces none of your tools. It plugs in where your expenses already live — payment solution, bank, expense reports, accounting — and returns, attached to each one, the document the merchant should have given you.
Where expenses come from
Cards and payment solutions
The richest feed: every payment arrives with its merchant, amount and date. This is what triggers collection — no invoice received, and the request goes out after four days.
Bank accounts
Transactions on professional accounts confirm expenses and reveal the ones nobody has justified. When the bank label does not say who should invoice, enrichment finds the merchant and their contact address.
Expense reports
Expenses filed by your employees arrive with or without a supporting document. The missing ones enter collection; the invoices obtained go back and file themselves into the report, ready for reimbursement. Details on the expense reports page.
Accounting and ERP
This time on the way out: the attached invoice, corrected lines, secured VAT. Accounting receives instead of chasing — that is the role of the accounting export.
One direction of travel
- The expense comes in. By API, webhook or export. No re-entry: a piece of information that already exists somewhere is not typed again elsewhere.
- The platform works. Merchant identification, solicitation under mandate, follow-ups, reception, control — the chain described brick by brick on the features page.
- The supporting document goes back. Pushed through your tool’s interface or dropped into the monthly export, always attached to its original expense with its matching score.
What travels — and what never does
What a connector carries
The expense identifier, its date, its amount, the merchant identification, the last four digits of the card. Enough to solicit the right merchant in the name of the right company, nothing more.
What never crosses
The full number of a bank card, as a matter of principle: four digits are enough to tell two expenses apart. And every connector stays within the scope of the mandate signed by the company concerned.
For software vendors
You publish a payment solution, an expense-report tool or accounting software? Your users have the same expenses without invoices. Plug document recovery into your product — direct or white-label — without building it in-house. That is what our partners offer covers.
Frequently asked questions
Do we have to replace our tools to use the platform?
No. The connector plugs into what you already run: payment solution, bank, expense reports, accounting. The platform is one link in the chain, not a replacement — nothing needs to be migrated.
Our software has no open API — can we still connect our expenses?
Yes: the file export is a fully-fledged way in and out. Tell us which tool you use, the architecture was designed for it — and where an interface does exist, the supporting document and its corrected lines can be written directly into your tool.
Can the connector write into our books?
That is the return path: the attached invoice, its corrected lines and the VAT can be pushed into your solution through its interface, on top of the monthly export. Every entry stays linked to its original expense, with its matching score.