What Merchaint does
Invoices, purchase orders, supplier statements — read into data, checked against each other, and sent on. Everything else in this Help Centre is a detail of that.
- What Merchaint actually takes off your desk
- The three things that happen, in order
- What is left for a person to do
- The four questions people ask first
01 · Why
Why do we have this?
Most finance teams already know what to do with an invoice. What takes the time is everything before that: opening the PDF, typing the numbers somewhere, finding the purchase order it belongs to, comparing them line by line, and chasing whoever has to approve it.
Merchaint does that part. What is left for a person is the small number of documents where something genuinely does not add up.
02 · What it means for you
Three things happen, in order
- Documents come in — by upload, by email, or from a spreadsheet.
- Merchaint reads them into fields and line items, and puts them in a table.
- Merchaint checks them against the records you already have, and only stops for you when something disagrees.
After that you can send the result to Xero or QuickBooks Online, and set up rules so most of it happens without anyone watching.
Everything else in this Help Centre is a detail of one of those three steps — How it all fits together draws the whole chain in one picture.
03 · FAQ
Common questions
No. Forward them to an address Merchaint gives you, or drag them in — see Forward documents by email.
Invoices, bills, purchase orders, goods receipts and supplier statements are the common ones. What it reads is set by a schema, which you can change.
Only if you build a workflow that does that. Out of the box, nothing leaves Merchaint on its own.
Good enough that the exceptions are the interesting part — which is why the product is built around showing you what did not match rather than what did.