Lido extracts structured data from purchase orders and invoices, then automatically matches them by vendor, PO number, and line-item amounts. Discrepancies are flagged with context before anything enters your ERP or approval queue, so your AP team reviews exceptions, not every document.
.png)
.png)
The classic three-way match problem: a vendor invoice arrives, and someone has to verify it against an approved purchase order and a goods receipt. Lido automates every step of that process from document intake through exception routing.
Vendor invoices and PO copies arrive as PDFs through email, a shared drive, or a fax-to-email service. Lido picks them up from a watched folder or inbox and queues them for processing automatically. No one has to manually download attachments or name files.
For each invoice, Lido pulls vendor name, invoice number, invoice date, payment terms, line items (description, quantity, unit price, extended amount), and invoice total. For each PO, Lido extracts PO number, vendor, authorized amounts, line items, and approval date. Both scanned and native PDFs are handled in the same batch.
Lido compares extracted invoice data against your open PO register using fuzzy matching. Vendor names are normalized before comparison — "Grainger Industrial Supply" matches "W.W. Grainger, Inc." PO numbers are matched with format tolerance. Amounts are compared at both the line and total level.
If an invoice from Staples Business Advantage for $4,720 references PO-2026-0881 but the PO was approved for $4,500, the discrepancy is flagged with the source documents, the matched PO line, and the variance amount. Your AP team sees exactly what is wrong, not just that something failed.
Invoices that match within your configured tolerance (e.g., within 2% or $50) are auto-approved and pushed to your payment queue or ERP. Discrepant invoices are held in a review queue with the full match context visible. Reviewers approve, reject, or escalate, and their decisions are logged for audit.
Upload a batch and get structured output in minutes.
Any vendor invoice layout, itemized or summary, with or without line items, scanned or native PDF. Lido reads header fields and line-item tables from any format.
Internal POs and vendor-facing PO copies. Extract authorized vendor, line items, quantities, unit prices, and PO total from any PO layout.
Warehouse receiving slips, delivery confirmations, and goods receipt notes. Used for true three-way match: invoice vs. PO vs. what was actually received.
Monthly vendor account statements listing open invoices and payment history. Reconcile statement line items against your AP ledger and matched POs.
Standing purchase orders with periodic call-off invoices. Lido tracks cumulative amounts drawn against the blanket PO authorization.
Vendor credit notes that reduce the net amount owed on a matched invoice. Lido links credits to original invoices and adjusts the net payable accordingly.
An AP clerk receives an invoice from Ferguson Enterprises for $12,340. They open your ERP, search for the PO, find PO-2026-0774, open the goods receipt, and compare three documents side by side. If the amounts match, they key in the invoice data and move it to the payment queue. If something is off by even a few dollars, they email the requisitioner and wait for a response. Multiply this by 400 invoices per month. Your AP team spends more time matching documents than processing payments.
Configure your match rules once, tolerance thresholds, required fields, fuzzy match sensitivity. Lido extracts and matches every PO-invoice pair automatically. Clean matches flow to payment with no human touch. The 12% of invoices with real discrepancies land in a review queue with both documents and the specific mismatch already identified. Your AP team closes more invoices per day and spends their time on decisions, not comparisons.
| Feature | Lido | Manual process |
|---|---|---|
| Extract and match PO and invoice data automatically | ✓ | ✗ |
| Fuzzy-match vendor names and PO number variants | ✓ | ✗ |
| Line-item level matching with variance flagging | ✓ | ✗ |
| Auto-approve clean matches; queue exceptions only | ✓ | ✗ |
| Full audit trail of match decisions and overrides | ✓ | ✗ |
| Open documents and compare them yourself | ✓ | ✓ |
Set up PO-to-invoice matching in Lido and let your team focus on the 10% of invoices that actually need attention.
A mid-size manufacturer receives 600 supplier invoices per month across 80 vendors. Raw material invoices are matched to line items on blanket POs, catching unit price deviations and quantity overages before the $2.1M monthly payment run.
A wholesale distributor pays 15 carriers weekly. Freight invoices are matched to the approved rate confirmation sheets issued at shipment time. Accessorial charges not on the rate confirmation are flagged automatically before the carrier is paid.
A consulting firm issues POs against statement-of-work agreements for contractors and software vendors. Invoices referencing the SOW PO are matched to ensure billed hours and deliverables align with approved scope and rates before payment.
A holding company with 6 subsidiaries shares vendors across entities. Lido matches invoices to POs within the correct entity, catches cross-entity billing errors, and routes each matched invoice to the right subsidiary AP queue for payment.
%20(1).svg)
