Catch invoice errorsbefore you pay.
OperaLayer connects your warehouse, accounting and ERP to check every invoice against what you ordered and received. Wrong prices, missing quantities and different products reach your team before the bill is approved. Give your team its mornings back.
For wholesalers, distributors and retailers buying stock from many suppliers.
Thirty cents is easy to miss. On 1,000 units, that is €300.
“Our employees smiling again. Two hours per person of ‘monkey work’ gone.”
Māris Renigers, E-business Manager, ESELO
A supplier can send you a perfectly good invoice for the wrong thing.
A small price change quietly eats into your margin.
The order says €4.80. The invoice says €5.10. The total is calculated correctly, so the extra €300 on a thousand units is easy to approve.
The paperwork can agree while the delivery comes up short.
The supplier dispatches 100 cartons on paper. Your warehouse counts 92. Unless accounting sees that count before posting the bill, someone has to chase the difference afterwards.
Your most experienced people spend the morning checking the easy lines.
One supplier sells by the box, another by the piece. The buyer knows the codes, receiving has the count and accounting has the invoice. All three get involved before anyone knows which line actually needs attention.
Follow one invoice with three different problems.
Switch between the lines. In each example you can see what the supplier billed, what the order says and who can settle the difference.
An extra €300 on one line
The order and warehouse receipt both show 1,000 M20 cable glands. The supplier billed all 1,000 at a higher unit price.
- Item
- M20 cable gland
- Quantity
- 1,000
- Unit price
- €4.80
- Item
- M20 cable gland
- Quantity
- 1,000
- Unit price
- Agreed on PO
- Item
- M20 cable gland
- Quantity
- 1,000
- Unit price
- €5.10
Why it matters
The agreed line value is €4,800. The supplier billed €5,100. A quantity check alone would let the difference through.
Suggested action
The buyer checks for an agreed price change. If €4.80 still applies, accounts payable requests a corrected invoice or €300 credit and keeps the line on hold.
From the supplier inbox to an invoice you can approve.
Upload the invoice
Read the invoice, delivery note or CMR transport document from the agreed inbox, upload or photo.
Match it to your order
Find the purchase order and link supplier codes, packs and units to your own items.
Compare every line
Check prices, quantities and item details. Include the warehouse count when a receipt is available.
Review and send to the ERP
Show the differences for review. Send accepted records to the ERP under your posting rules.
OperaLayer reads the documents, finds the purchase order in your ERP and compares the lines. Your rules decide what can move ahead and what needs a buyer, a warehouse colleague or an accountant.
What changed for an electrical goods distributor
For one of our customers, electrical goods distributor ESELO, buying from more than 150 suppliers meant working through different document layouts, product codes and pack sizes. Purchasing, warehouse and finance now use OperaLayer to compare orders, deliveries and invoices.
“From demo to live in weeks. Fastest implementation we have experienced so far for such a complex system and functionality.”
Māris Renigers, E-business Manager, ESELO- Invoiceinbox
- Delivery noteupload
- CMRphoto
Matching accuracy improved from 69% to 87% in the first week, then reached 98.5% in the second week.
The recorded median time from invoice upload to posting in Microsoft Dynamics NAV was 36 seconds, measured in August 2026.
The customer reports two hours per person of routine checking removed. Buyers, receivers and accountants have more time for the lines that need their attention.
What does it change for you?
Finance director or owner
- See the value of a disputed price or quantity before approving the bill.
- Separate money questioned from credits the supplier actually issued.
- Measure how much staff time the process gives back each month.
Accounts payable
- Open the invoice at the line that needs a decision.
- See the order and receipt alongside it without retyping every line.
- Know which invoices can be posted and which are waiting for an answer.
Buyer or purchasing manager
- See when a supplier changed the price, pack or product code.
- Check an agreed substitution against the original order.
- Give the supplier the exact line and amount to correct.
Warehouse or receiving lead
- Capture the delivery document while the goods are in front of you.
- Record the actual count and check the label when a product is uncertain.
- Give accounting a receipt it can use to settle a shortage.
Operations director
- See whether a bill is waiting on purchasing, receiving or finance.
- Find the supplier formats and pack sizes that cause repeated work.
- Measure whether the next delivery from that supplier is easier to process.
IT or ERP owner
- Start with a working Microsoft Dynamics NAV reference.
- Agree which fields OperaLayer can read and which records it can write.
- Test approvals, failed exports and retries before enabling automatic posting.
Built for businesses that buy stock from many suppliers
Electrical and industrial distribution, wholesale, food service supply and multi-store retail.
- A busy team still opens supplier PDFs and compares them with purchase orders by hand.
- Product codes, packs, units or partial deliveries make a simple total check unreliable.
- Purchasing, receiving and accounting each hold part of the answer.
- Your ERP already holds the orders and you want accepted invoices recorded there.
What is invoice checking costing you?
Put in your own numbers. You will see how many hours your team gets back in a year, and how much comes off invoices your suppliers got wrong.
Start with our example, then use your numbers
- 1,600 hours your team gets back
- €40,000
- Taken off invoices your suppliers got wrong
- €6,240
Hours saved turn into cash when they cut overtime, hiring or other spending. The cost of OperaLayer is not taken off this total.
Start with one supplier and one real invoice.
Choose an invoice your team knows well. The best example is one where somebody had to call the warehouse, check a price or ask what the supplier meant.
- 1
Choose the checks that matter
Your team brings a clean invoice and a few difficult ones, with their orders and available receipts.
With OperaLayer, agree which price, quantity and product differences should stop a line.
- 2
Connect the order and receipt records
Your ERP owner identifies the purchase order, receipt and posting fields and approves access.
The OperaLayer team sets up the agreed connection and tests it with sample records. Microsoft Dynamics NAV has a working connection. Other systems are scoped against their own interfaces.
- 3
Review the first matches together
Your buyer, receiver and accountant check what passed and what was held.
The OperaLayer team adjusts pack conversions and price tolerances with them. Test known mistakes and clean invoices before allowing a line to pass automatically.
- 4
Agree who owns each exception
Your team agrees who checks a price, confirms a shortage and authorises a posting.
The OperaLayer team sets up the review and export rules. Together you measure time spent, useful alerts and confirmed corrections.
Choose the checks that matter
Your team brings a clean invoice and a few difficult ones, with their orders and available receipts.
With OperaLayer, agree which price, quantity and product differences should stop a line.
Connect the order and receipt records
Your ERP owner identifies the purchase order, receipt and posting fields and approves access.
The OperaLayer team sets up the agreed connection and tests it with sample records. Microsoft Dynamics NAV has a working connection. Other systems are scoped against their own interfaces.
Review the first matches together
Your buyer, receiver and accountant check what passed and what was held.
The OperaLayer team adjusts pack conversions and price tolerances with them. Test known mistakes and clean invoices before allowing a line to pass automatically.
Agree who owns each exception
Your team agrees who checks a price, confirms a shortage and authorises a posting.
The OperaLayer team sets up the review and export rules. Together you measure time spent, useful alerts and confirmed corrections.
See it before connecting your ERP
The first call uses example documents. Follow a price change, a short delivery and a different product code, then discuss the suppliers and records that matter in your business.
- Microsoft Dynamics NAV
- Microsoft Business Central
- Oracle NetSuite
How OperaLayer knows two different lines refer to the same item
Your PO might say 120 pieces. The supplier might write 10 boxes of 12 and use its own item code. OperaLayer has to establish the product and the unit before a price comparison means anything.
OperaLayer extracts the invoice number, supplier, item code, description, quantity, unit and price from the incoming document. A poorly read field carries a warning so the reviewer can check it against the original.
Frequently asked questions
Not answered here? Pick a time on Calendly (opens in a new tab)
Starting and using OperaLayer
Do all our suppliers have to change how they invoice us?
Suppliers can keep sending the formats they use today. We start with a sample of your PDFs, scans and delivery notes, including the difficult ones, to see which can pass and which need review.
What if we receive one purchase order in several deliveries?
The warehouse records each receipt. The reviewer can check the invoice against the deliveries recorded so far and see what is still outstanding. We test your partial-delivery rules as part of setup.
What if we accept small price differences?
Choose tolerances with finance and purchasing. Test them against rounding, discounts and known overcharges. In the first review, count how many alerts led to action and adjust the thresholds before widening automation.
Who speaks to the supplier when there is a problem?
Your buyer or accounts payable team owns the conversation. OperaLayer supplies the document, order line and amount in question so they can ask for a correction with the evidence in front of them.
Data and confidence
Can it tell what physically arrived?
It can compare the recorded receipt with the order and invoice. Your warehouse still counts the goods and checks labels or damage. A supplier delivery note or CMR shows what the supplier or carrier documented.
Could it accept the wrong item because the description looks similar?
An exact code or approved mapping gives a stronger match. Where the code, specification or pack is unclear, the line can wait for a person to compare it with the original and the item record.
Who decides whether an invoice can post?
You set the approval and posting rules. Start with human review, then enable automatic export for document types and checks that pass your tests. Payment approval stays with your finance team.
What happens to our supplier and price data?
Before setup, we agree the documents and ERP fields in scope, who can access them, where they are processed and stored, and how long they are kept. Your IT team reviews those details for your deployment.
How do we know whether it pays off?
Measure handling time on the same suppliers before and after the pilot. Track accepted invoice reductions and supplier credits separately. Compare the measured benefit with setup and running costs.
Comparing approaches
Our ERP already matches invoices. Where would OperaLayer help?
Follow one invoice from the supplier inbox to the posted entry. If someone still reads the PDF, translates a pack size or calls the warehouse about a mismatch, start the demo at that step.
How does it compare with Continia Document Capture?
Continia offers invoice and receipt matching inside Microsoft Dynamics 365 Business Central. OperaLayer has a working NAV example across purchasing, receiving and accounting. Compare both with the same supplier documents, ERP version, receipt data, setup and support costs.
Could we do this with OCR or a general AI assistant?
Reading the PDF gives you the supplier’s numbers. You still need the right order, the warehouse count, the pack conversion and a controlled way to post the accepted result. Bring a tricky invoice to the demo and follow it through all five steps.
Will it work with SAP or our warehouse system?
The live reference on this page uses Microsoft Dynamics NAV. For SAP or another ERP, we review the available interfaces for orders, receipts and postings. We quote the connection and test it with your records before rollout.
News
Press
- IT Wirescandiweb’s OperaLayer ships 72-hour MVPs to plug the gaps your ERP can’t see (opens in a new tab)
- Retail Tech Innovation Hubscandiweb releases new version of OperaLayer to help retailers respond faster to supply chain disruptions (opens in a new tab)
- The European Business Reviewscandiweb Announces Stock and Shipment Control Cockpit and Exception Allocation Technology Built on OperaLayer to Help Retailers Respond Faster to Supply Chain Disruptions (opens in a new tab)
- scandiwebscandiweb Acquires LegacyBridge to Modernize the Systems Behind Customer Experience (opens in a new tab)
Events
Catch scandiweb at the next event and ask us about OperaLayer. Or skip the trip. Pick a time on Calendly (opens in a new tab)
Recently
- B2B Online AtlantaAtlanta
- Meet Magento NetherlandsAmsterdam
- B2B eCommerce World AmericasIndianapolis
- Commerce Unboxed SummitBrussels
- Meet Magento GermanyMainz
- AI WEEKMilan
AI WEEK, Milan
Bring the invoice that made three people stop working.
See which line OperaLayer would flag, the evidence the reviewer would see, and how an accepted invoice gets back into your ERP.
Start with our example records. You leave knowing which documents, checks and connections to test in your own business.
Book a demo call (opens in a new tab)Or leave your details
We will get in touch to set up the call.
