Invoice Automation in Business Central for Dutch Wholesalers

Every month, an Operations Controller at a Dutch wholesale distributor opens their inbox. Forty vendor invoices are waiting — PDFs, scanned paper, the occasional PEPPOL XML. One by one, they check each invoice against a purchase order. Then they confirm the goods receipt. Next they route it to a manager for approval. Finally, they post it to Business Central.

It takes hours. It produces errors. And it happens every single month. However, this is not really a Business Central limitation. Business Central — the ERP running the business — simply does not do invoice processing at scale on its own.

This article covers three things. First, what Business Central handles natively. Second, where it stops. Third, how invoice automation in Business Central actually runs inside an existing setup — without customization, a new system, or retraining.

In short: invoice automation for Business Central is no longer a question of "if". Instead, the question is "how to roll it out without breaking the ERP layer that runs the rest of the business".

At Lleverage, we help Dutch wholesalers and distributors automate invoice processing directly inside Business Central — no new system, no customization, no parallel workflow. The rest of this guide lays out what Microsoft's native tools do and don't cover, how three-way matching and PEPPOL handling work at volume, and what a Business Central–native automation layer looks like in practice. If you want to see it work against your own invoice pipeline, book a demo.

The invoice processing problem every wholesale Operations Controller knows

Wholesale distributors typically handle hundreds of vendor invoices per month. Each one needs verification against a purchase order and a goods receipt. On top of that, approval has to route across departments. Then the invoice has to land in Business Central by hand. As volumes grow, errors multiply. Furthermore, a missed match or delayed approval costs money. It strains supplier relationships. It also consumes hours of back-office time every week.

For a distributor handling 200 invoices per month, manual work looks like this:

• Cross-referencing each invoice line against the linked purchase order and goods receipt

• Chasing approvals over email when a manager is unavailable

• Re-entering invoice data that already exists in supplier documents

• Month-end backlogs when finance needs everything posted before close

• Disputes with suppliers when a payment is delayed because an invoice sat in someone's inbox

The Operations Controller knows all of this. What they often don't know is how much of it can be eliminated without touching their ERP setup.

What Business Central handles natively — and where it stops

Business Central includes native purchase invoice management. That means manual entry, purchase order linkage, and approval workflows configured via workflow templates. For companies with low invoice volumes and consistent formats, this works fine. However, wholesale distributors face different conditions: high volumes, multiple vendors, varied invoice formats. As a result, the native setup quickly becomes a bottleneck. In turn, the case for invoice automation in Business Central gets hard to ignore.

Here is where the standard Business Central setup lands for a typical wholesale operation:

Business Central does not process invoices at volume. Instead, it stores and posts them once humans have done the work upstream. That distinction is exactly why invoice automation in Business Central has to live as an embedded layer rather than a BC customization.

For the broader picture of how AI sits alongside Business Central, SAP, Infor, Dynamics 365 F&O, AFAS, and Navision in European mid-market operations, read our ERP AI integration guide.

What the Business Central Payables Agent does (and what it can't)

Microsoft's Payables Agent is part of the 2025 Wave 1 update. It automates part of the invoice intake process in Business Central. Specifically, the agent reads invoices from email, creates draft purchase invoices, and maps line items to vendors and purchase orders. It processes up to 100 emails per day. It also handles PDF attachments up to 5MB and 10 pages. However, it never auto-posts — a human confirms every invoice before it enters the ledger.

For many Business Central users, the Payables Agent is the first time the invoice process has felt automated. And for low-volume setups, it is a genuine improvement over fully manual intake.

However, for wholesale distributors the gaps matter. In particular, the Payables Agent is not a complete invoice automation solution for Business Central:

• Volume limits: 100 emails per day, 50 per batch. A mid-size distributor with active suppliers hits this ceiling.

• No three-way matching: The agent creates a draft invoice. It does not validate the invoice against a goods receipt and purchase order automatically.

• No approval workflows: The agent does not route invoices to approvers based on value, vendor, or exception type.

• No PEPPOL handling: The agent does not process PEPPOL/NLCIUS formatted invoices natively for Dutch compliance requirements.

• Draft only: Every invoice the agent creates still requires a human to review and post.

The Payables Agent reduces manual intake. It does not remove manual processing. For a wholesale operation with real volume, it is a starting point — not an end state.

Source: Microsoft Learn — FAQ for Payables Agent

How three-way matching works in Business Central — and why it breaks down manually

Three-way matching verifies that a vendor invoice aligns with its purchase order and goods receipt before finance approves payment. In Business Central, this process exists. However, it requires manual line-by-line review. For a wholesale distributor receiving 200+ invoices monthly, manual three-way matching is exactly where time gets lost. It is also where errors enter the ledger. For example, a single missed price variance can ripple into a supplier dispute weeks later.

Without invoice automation Business Central users run the process manually, and it looks like this:

1. Invoice arrives — by email, PDF, or post

2. Accounts payable staff locates the corresponding purchase order in Business Central

3. Staff checks invoice quantities and prices against PO lines

4. Staff confirms goods receipt is posted for the relevant lines

5. Any discrepancy — a price variance, a partial delivery, a missing GR — stops the process

6. Staff escalates the exception to the buyer or warehouse

7. Exception is resolved (or sits in a queue)

8. Invoice is approved and posted

The five most common places this breaks down in wholesale:

• Partial deliveries: Supplier invoices for full quantity before all goods have arrived

• Price variances: Invoice price differs from PO price due to freight, currency, or supplier error

• Missing goods receipts: Warehouse hasn't posted the GR yet when invoice arrives

• Early invoicing: Supplier invoices before the PO is confirmed or closed in BC

• Volume overload: Month-end invoice surge means backlogs, rushed checks, and posting errors

Each exception requires human time to resolve. At scale, exceptions are not edge cases — instead, they become a significant share of invoice volume. Therefore, any serious invoice automation for Business Central has to handle exception flow as a first-class problem, not a feature added later.

See how Lleverage handles back-office automation for wholesale and distribution, or go deeper into the invoice processing automation flow for wholesale and distribution.

What invoice automation in Business Central actually looks like in practice

An AI layer embedded in Business Central does four things. First, it captures invoices from email and PDF. Second, it validates them against purchase orders and receipts. Third, it routes exceptions to the right approver. Fourth, it posts confirmed invoices without manual re-entry. For clarity: this process runs inside Business Central. As a result, there is no new system, no retraining, no change to existing workflows.

The invoice automation Business Central flow, end to end:

1. Capture — Invoice arrives by email or PDF upload. The system extracts vendor, invoice number, line items, quantities, and amounts automatically.

2. Match — Invoice lines are matched against the linked purchase order and goods receipt in Business Central. Matches within tolerance are confirmed automatically.

3. Flag exceptions — Lines with price variances, quantity mismatches, or missing receipts are flagged and routed to the responsible person — buyer, warehouse manager, or accounts payable — based on configured rules.

4. Approve — Confirmed invoices proceed to an approval workflow if required by value threshold or vendor type. Exceptions route to the right approver directly.

5. Post — Approved invoices are posted to Business Central with a full audit trail — document, match result, approver, timestamp.

Proof point: Topa Bathroom Products — +90% of document intake into Business Central, handled automatically

Topa Bathroom Products is a Dutch importer and wholesaler serving around 700 customers. The business runs on Microsoft Dynamics 365 Business Central. Before working with Lleverage, Topa had nearly four full-time employees — 3.8 FTEs — reading plain-text emails, PDFs, CSVs, and Excel sheets all day long, and keying every incoming document into Business Central by hand.

"We had four and a half people — about 3.8 full-time equivalents — sitting there all day long, manually entering every single order into our Business Central ERP." — Bryan van Ingen, Operations Director, Topa Bathroom Products

After going live with the Lleverage AI agent, over 90% of incoming documents now flow directly into Business Central without any manual input. Customer order confirmations go out within 30 seconds of the email arriving. The 3.8 FTEs previously stuck on data entry have been fully redeployed — service planning, after-sales support, customer-facing roles that were impossible before. At year-end, the Topa team returned from the holiday break to find everything already processed, with zero backlog to clear.

The same Lleverage AI-agent pattern that turns unstructured order emails into clean Business Central sales orders is the exact pattern that turns unstructured vendor invoice emails into clean Business Central purchase invoices. Same ingestion layer, same BC integration, same exception-routing logic — pointed at a different document type.

Topa itself found Lleverage through another Dutch wholesaler already running the same approach: Koninklijke Dekker, the 140-year-old timber wholesaler, also on Business Central. Read the full Topa customer story for the detailed walkthrough.

See it work with your data — book a demo.

PEPPOL and e-invoicing: what Dutch wholesalers need to handle in 2026

Since January 2026, electronic invoicing via PEPPOL has been mandatory for B2B transactions between VAT-registered companies in the Netherlands. As a result, Dutch wholesalers using Business Central need to handle PEPPOL automatically. Specifically, the NLCIUS format has to work both for invoices they send and for invoices they receive from suppliers adopting the standard.

PEPPOL (Pan-European Public Procurement On-Line) is the European standard for structured electronic invoices. NLCIUS is the Dutch implementation. In practice, it is the format Dutch companies must use to exchange invoices electronically.

What this means in practice for a wholesale distributor:

• Suppliers are increasingly sending PEPPOL-formatted invoices. Therefore, your processing system needs to receive, validate, and route them.

• Customers may require PEPPOL-formatted invoices from you. In particular, government entities and larger corporates tend to require this first.

• Business Central has some PEPPOL support out of the box. However, full NLCIUS compliance at volume typically requires additional configuration. Specifically, handling incoming supplier invoices across multiple vendors usually needs an automation layer that does format validation natively.

For an Operations Controller managing 300+ supplier invoices per month, a manual PEPPOL transition is simply not viable. Instead, invoice automation Business Central tooling needs to handle PEPPOL as part of the normal processing flow.

For a Lleverage-led Business Central invoice automation rollout including PEPPOL handling, explore our wholesale and distribution solutions — or talk to us about your specific Dutch compliance requirements.

What to look for in an invoice automation layer for Business Central

The right invoice automation for Business Central works inside your existing setup. That means no new ERP, no parallel system, no retraining. Specifically, look for automated three-way matching and email and PDF capture. In addition, it needs exception-based approval routing, PEPPOL/NLCIUS support, and a full audit trail. Finally, it has to handle your invoice volume without manual intervention at scale.

For an Operations Controller evaluating invoice automation Business Central options, this is the checklist that matters:

Two things to verify in any evaluation. First, does the system configure around your existing business rules — vendor tolerances, approval thresholds, entity structures? Second, does it produce a full audit trail your finance team can rely on for compliance and dispute resolution?

Lleverage builds the same Business Central–native pattern across every back-office vertical: explore our solutions for manufacturing, logistics, and wholesale and distribution. For the invoice-processing deep dives per vertical, see invoice processing for manufacturing and invoice processing for logistics.

Frequently asked questions

What are the limitations of the Business Central Payables Agent?

The Payables Agent processes up to 100 emails per day (50 per batch). It handles PDF attachments up to 5MB and 10 pages. It creates draft invoices. However, it never auto-posts. In addition, it does not automate three-way matching, approval workflows, exception handling, or PEPPOL compliance. For high-volume wholesale operations, it reduces manual intake. However, it does not remove manual processing.

Does Business Central support PEPPOL / NLCIUS invoicing?

Business Central has some PEPPOL support. However, full NLCIUS compliance at volume usually requires configuration. For most wholesale operations, it also requires an additional automation layer. Dutch B2B e-invoicing via PEPPOL has been mandatory since January 2026. As a result, wholesale distributors receiving or sending PEPPOL invoices across multiple vendors need their processing system to handle format validation and routing automatically.

How does three-way matching work in Business Central?

Three-way matching in Business Central compares a vendor invoice against its linked purchase order and posted goods receipt. The comparison happens on quantity, price, and vendor. Natively, this is a manual process. An Operations Controller or AP staff member reviews each invoice line before approving. However, at volume, automated matching handles confirmed invoices automatically. It then routes only exceptions for human review.

Can you automate invoice processing in Business Central without customization?

Yes. An AI automation layer embeds inside Business Central's existing structure. Specifically, it uses standard BC data, workflows, and user roles — without custom development. Invoice automation in Business Central configures itself around your existing business rules rather than hardcoding them. As a result, your ERP setup does not change.

What is the ROI of automating accounts payable in Business Central?

The measurable outputs fall into three buckets. First, hours saved per week in manual processing. Second, a reduction in invoice posting errors. Third, faster supplier payment cycles, which may secure early payment discounts. For wholesale distributors handling 200+ invoices per month, the processing overhead eliminated by automation typically covers implementation cost within the first quarter.

Ready to automate invoice processing inside your Business Central setup?

Show me a similar case → Book a demo

See how a Dutch wholesale distributor deployed invoice automation Business Central, end to end — without changing their ERP setup.