For many years, electronic invoicing has been presented as one of the major milestones in the digital transformation of finance. In Belgium, that transformation accelerated significantly with the mandatory adoption of PEPPOL for B2B invoicing (since 1st January 2026). The promise is compelling: invoices become structured, digital and standardized, allowing companies to exchange them securely and efficiently while improving transparency, reducing administrative overhead and creating a foundation for further automation. On paper, it sounds like the moment finance departments have been waiting for. If invoices can move automatically from one ERP system to another, shouldn’t Accounts Payable and Accounts Receivable departments become dramatically smaller?
Interestingly, that is not what we are seeing in practice. While PEPPOL adoption is undoubtedly an important step forward, most organizations have not experienced the dramatic reduction in headcount that some initially may have expected. Finance teams continue to process large volumes of invoices, approval workflows remain active, and invoice specialists are still very much needed. This raises an interesting question: if invoices are now digital by default, why hasn’t invoice processing become almost effortless?
The first explanation is surprisingly simple. Although PEPPOL is now legally required for Belgian B2B invoicing, the transition is still incomplete. Many suppliers are still migrating to the new standard, international suppliers often operate under different regulations, and exceptions remain common. In theory, companies could reject invoices that are not submitted through PEPPOL. In reality, business relationships are rarely that black and white. Few organizations are willing to delay payments or jeopardize strategic supplier relationships simply because an invoice arrived as a PDF instead of a structured PEPPOL document. As a result, finance departments continue to process invoices arriving through multiple channels: PEPPOL, email, PDF attachments, supplier portals and, in some cases, even paper documents. As long as multiple input channels coexist, complete automation remains difficult to achieve.
Another important reason is that PEPPOL did not introduce invoice digitization; it merely standardized it. Long before mandatory electronic invoicing, organizations had already invested heavily in digitizing their invoice flows. Dedicated invoice mailboxes, OCR technology, AI-powered document recognition and automatic field extraction had become standard components of many finance departments. Paper invoices were scanned almost immediately upon arrival, while PDF invoices were automatically captured from shared mailboxes and converted into structured accounting data. For these organizations, moving from a PDF interpreted by OCR to a structured PEPPOL XML message is certainly an improvement, but it is an evolution rather than a revolution. Much of the easy efficiency gains had already been realized years before PEPPOL became mandatory.
Perhaps the biggest misconception is that people tend to confuse invoice transmission with invoice processing. Many imagine a simple flow: the supplier sends an invoice through PEPPOL, the customer receives it, payment is executed, and the process is complete. The reality is far more complex. Sending an invoice is merely one small step within a much larger lifecycle. Before an invoice is paid, it must first be received, validated, approved, matched with a purchase order, verified against contractual agreements, checked for VAT compliance, booked correctly in the accounting system, and often routed through several approval levels. If discrepancies are found, exception handling begins, introducing additional manual work before the invoice can continue its journey towards payment, reconciliation, archiving and eventually audit. PEPPOL replaces only one block in this much longer chain.
What PEPPOL does exceptionally well is standardizing the exchange of invoices. It guarantees secure delivery, authenticates sender and receiver, provides a structured data format and ensures integrity throughout transmission. These are significant improvements that create a more reliable and transparent invoicing ecosystem. However, they do not answer the questions finance professionals actually spend most of their time on. Is the invoice correct? Was the service actually delivered? Does the amount match the purchase order? Is the VAT treatment correct? To which cost center should the invoice be booked? Is this perhaps a duplicate invoice? Has the correct legal entity been invoiced? These business validations remain largely independent of the transport mechanism used to deliver the invoice.
In fact, experienced finance professionals know that exceptions, rather than standard invoices, consume the majority of their time. Straightforward invoices that perfectly match purchase orders and contractual agreements are rarely the problem. Complexity arises when purchase orders are missing, deliveries are incomplete, VAT regimes differ, discounts have been applied incorrectly, duplicate invoices appear, or internal approval processes stall. These relatively small percentages of exceptional cases often generate a disproportionate amount of manual effort. Even if 95 percent of invoices arrive digitally, the remaining 5 percent of problematic invoices may still consume most of the available processing time.
The complexity becomes even greater when credit notes enter the picture. Unlike a standard invoice, a credit note often needs to reference existing invoices, reverse accounting entries, adjust VAT calculations, apply rebates or resolve commercial disputes. Matching invoices and credit notes correctly requires additional validation and reconciliation, demonstrating once again that financial processing extends well beyond simply receiving a digital document.
Looking at the complete invoice lifecycle also illustrates why automation remains such a challenging objective. For the supplier, the process begins with generating the invoice, booking anticipated revenue in Accounts Receivable, managing VAT obligations, distributing payment instructions, following up outstanding balances, sending reminders, possibly financing invoices through factoring, matching incoming payments and finally archiving or correcting invoices when necessary. The receiving organization follows an equally extensive journey: receiving the invoice, digitizing or importing it, validating its contents, extracting key information, linking it to purchase orders, applying the correct tax treatment, obtaining approvals, executing payments, reconciling transactions and archiving documentation for compliance purposes. Around these processes exists an entire financial ecosystem involving ERP systems, accountants, banks, payment providers, tax authorities, financing partners and auditors. PEPPOL connects an important part of that ecosystem, but certainly not all of it.
This also explains why the next major wave of innovation will likely be driven less by document exchange and more by data intelligence. Once invoices are consistently available as structured data, artificial intelligence no longer needs to spend its time reading documents. Instead, it can focus on far more valuable tasks: detecting anomalies, identifying fraud, predicting payment delays, proposing accounting entries, recommending VAT treatments, routing invoices automatically to the correct approvers, identifying duplicate invoices and forecasting cash flow. The real opportunity is no longer in digitizing documents, but in interpreting and acting upon the data they contain.
Every major wave of digital transformation tends to automate the most visible step first. With invoicing, that visible step was clearly the exchange of documents. PEPPOL has standardized that exchange and laid an essential foundation for the future. But the real transformation of finance will only happen when the entire end-to-end invoice lifecycle becomes intelligent, interconnected and largely autonomous. That means automating not just transmission, but validation, approval, exception handling, reconciliation and decision-making as well.
Perhaps that is the most important lesson from Belgium’s PEPPOL journey. The expectation was that electronic invoicing would revolutionize finance departments almost overnight. The reality is more nuanced. PEPPOL is not the destination; it is the infrastructure. It provides the standardized foundation upon which the next generation of financial automation can be built. The greatest value will not come from sending invoices differently, but from transforming the complete financial process surrounding them.
Comments
Post a Comment