Supplier paperwork read and matched before anyone retypes it.
Invoices, delivery notes and customs papers matched to the order, with freight and duty carried into the cost of every item.
A trader loses the hours in matching: a supplier invoice against a purchase order, a delivery note against what arrived, a payment against three invoices, a customs document against a shipment. Document capture and matching take back the retyping, reading the paperwork into fields and posting what agrees. People keep the exceptions, the prices and the suppliers.
The hours go into typing the same figure twice.
Watch a trading back office for a morning and count the double entries. The supplier's invoice total goes into the ERP. The delivery note quantity goes into a spreadsheet. A payment covering three invoices is split by hand. The customs paperwork goes into a folder, and the landed cost stays in somebody's head.
Each of those is a matching job. Document capture reads the paperwork into fields, and validation checks that totals add up, dates are possible and references exist. Reads below the confidence threshold wait for a person, and everything that agrees posts itself.
Where a figure cannot be verified, the system refuses and queues. A wrong landed cost posted silently turns up at the end of the quarter, in the margin.
Six pieces, all reading from one record.
- Supplier document capture. Invoices, delivery notes, packing lists and customs paperwork read into fields, with a confidence on every read. Computer vision & OCR.
- Three-way matching. Order, receipt and invoice matched automatically, with exceptions queued and the difference highlighted.
- Landed cost. Freight, duty, insurance and clearing charges added to the item's valuation through ERPNext's Landed Cost Voucher, so margin is measured on what the goods cost once they land.
- Stock that reflects reality. Warehouses, batches with expiry dates, stock reserved against sales orders, and the adjustments that keep it accurate, on ERPNext.
- Quote to order. Price lists, customer-specific pricing, and margins visible only to the roles allowed to see them.
- A customer portal. Order status, documents and statements, so the phone stops being the tracking system.
In the UAE, a trader's master data takes the first hit from e-invoicing.
Invoices between businesses fall under the UAE mandate, with a short list of exclusions. Your system has to issue structured PINT AE invoices, exchanged through an Accredited Service Provider, and a PDF, a scan or an email does not qualify.
The first deadline falls on the largest traders: businesses with AED 50 million or more in revenue have until 30 October 2026 to appoint an ASP. The rest have until 31 March 2027, and go live on 1 July 2027.
A trader feels it first in master data: thousands of customer and supplier records, TRNs blank or formatted four different ways, item codes that never carried a tax category. Cleaning that is most of the readiness work, and it pays off even if the dates move again. Credit notes, discounts and multi-line tax are where invoice templates break, so they are tested on your own history, not on a sample file.
The ASP you appoint carries the invoices, and your tax adviser answers the tax questions. Our part is making your system produce what the ASP needs, and proving it on your own invoices.
From a document survey to the first month live.
- Document survey. A sample of every document type you handle, including the bad scans and the handwritten annotations.
- Baseline accuracy. Each field of each document type scored on your own samples, so the first number you see is a measured one.
- Core setup. Items, price lists, customers, suppliers, opening stock and balances, dry-run and reconciled.
- Matching rules. What may post automatically, what must be checked, and what must never post.
- Parallel cycle. One month in both systems, differences investigated until they are zero.
- Live, then tune. Thresholds raised as the correction queue shows they can be.
For more on how that first number is measured, see straight-through rate. Traders who also move the goods should read the logistics page.
Frequently asked questions
Where does document matching take back a trader's hours?
A trader loses the hours in matching: a supplier invoice against a purchase order, a delivery note against what arrived, a payment against three invoices, a customs document against a shipment. Document capture and matching take back the retyping, reading the paperwork into fields and posting what agrees. People keep the exceptions, the prices and the suppliers.
What is three-way matching?
Checking a supplier invoice against the purchase order and the goods received before it is paid: the same item, quantity and price on all three. The system does the comparison, posts what agrees and queues any difference for a person, with the lines that disagree highlighted.
Our documents mix languages, and half are photographs. Will it cope?
That is the normal case. Accuracy is measured on your own documents before anything posts, and reported per field, including where it is not good enough to post automatically. Those fields go to the queue instead of being pretended away.
Can it keep our existing item codes and customer price lists?
Yes, including customer-specific pricing and the historical price a customer will insist they were given. Migration runs into a staging copy first and is reconciled against your trial balance before anyone relies on it.
Will this replace our current ERP?
Not by default. Where your current system has an API, capture and matching feed it. Replacing a working system has to be argued with numbers, and sometimes the numbers do argue for it: when it cannot hold batches, landed cost or the fields PINT AE needs.
Can a model post a supplier invoice on its own?
Only above a confidence threshold you set, after the totals, the tax-number format and the purchase order all check out, and after a duplicate check that fails closed. Anything doubtful queues for a person. Nothing is posted on a guess.
How long does a trading implementation take?
The signed proposal dates each milestone once the scope is written, and the amount of history you bring across moves those dates more than anything else.