Scenario 1
Invoice: 96 units, PO: 100 units, receipt: 96 units
What Glimps checks
Compares invoice quantity with the goods receipt, not blindly with the full PO.
Action
Auto-approve when price and receipt match.
Trading team solution
Invoice processing for trading and wholesale teams using Exact Online
Trading and wholesale companies process supplier invoices with many lines, freight charges, discounts, backorders, and partial receipts. Glimps helps finance teams capture, match, and post that flow into Exact Online with control.
Line 1: 6 ordered, 6 received, 6 invoiced
Typical bottleneck
Lines and exceptions
The PDF is not the real problem. The work is checking prices, quantities, freight, and receipt data.
Main control
PO + receipt
Goods invoices should match what was ordered and what was actually received.
Goal
Review exceptions only
Let standard invoices flow through and route exceptions to finance or purchasing.
Benchmark: Ardent Partners (2024) reported $9.40 average cost per invoice, 9.15 days processing time, 32.6% straight-through processing. Source
Does this match your situation?
Where this solution fits, and where it doesn't
Good fit
- You process hundreds or thousands of supplier invoices per month.
- You use purchase orders, goods receipts, or warehouse data to validate invoices.
- You want to find exceptions faster without manually checking every invoice line.
Less relevant
- You receive only a small number of simple expense invoices per month.
- You do not use Exact Online as your finance system.
Process design
From intake to controlled posting
Glimps handles the routine so finance can focus on the exceptions, not the data entry.
01
1. Receive supplier invoice
Invoices arrive by email or upload. Glimps captures supplier, invoice number, amounts, VAT, and line tables.
02
2. Match lines with PO and receipt
The invoice is compared with purchase order lines, receipt lines, and tolerances for price and quantity differences.
03
3. Route exceptions
Glimps routes only the exceptions: missing receipt, price variance, freight line without PO, or possible duplicate invoice.
04
4. Post to Exact Online
Approved invoices sync with attachment, coding proposal, dimensions, and audit trail.
Where things get stuck
The real value is in the exceptions
High-volume AP automation only pays off when it is clear what can flow through safely, and what must be reviewed by a human.
Focused on exceptions, not data entry
Many lines per invoice
A supplier invoice can contain dozens or hundreds of lines. The value is line recognition, not only header capture.
Freight, surcharges, and discounts
Trading invoices often include freight, packaging, volume discounts, or credit lines that need separate handling.
Split deliveries
One order can arrive in multiple deliveries and invoices. Matching needs to account for open PO balances and partial receipts.
Concrete exceptions
How Glimps handles the cases that would otherwise stall
Scenario 2
Freight line without PO line
What Glimps checks
Recognizes charge type, supplier, and configured tolerance.
Action
Route to finance or purchasing for review.
Scenario 3
Same invoice number submitted again
What Glimps checks
Supplier, invoice number, amount, date, and prior postings.
Action
Block as a possible duplicate payment.
Exact Online setup checklist
The prerequisites to get this solution into production.
- Suppliers and VAT numbers are synced with Exact Online.
- GL accounts, VAT codes, and dimensions are current.
- PO and receipt data is available through Exact Online, database, or API.
- Tolerances are agreed for price, quantity, and freight charges.
What Glimps automates for you
The concrete parts of the process Glimps takes off your hands.
- Line extraction for supplier invoices with large tables.
- 2-way and 3-way matching with tolerance rules.
- Exception queue for finance, purchasing, and operations.
- Posting and attachment synchronization with Exact Online.
FAQ
Frequently asked questions
Specific questions about this solution for trading & wholesale.
Want to see it yourself?Open the demo
Yes. This use case is built around supplier invoices where line recognition, PO data, and receipt data matter more than header capture alone.
They can be recognized as separate lines and either processed automatically or routed for review based on tolerance settings.
No. The goal is for matching invoices to flow through automatically while exceptions get attention.
Read next
View PO matching