In almost every e-invoicing project I have supported, the first meetings follow the same pattern. We talk about mandates, deadlines and formats: XRechnung in Germany, Factur-X in France, Peppol in Belgium. Then, usually in the second or third meeting, someone from accounts payable or accounts receivable asks the question that really matters to them: “What will my day actually look like after go-live?”
That question deserves more attention than it gets. E-invoicing for AP and AR is often framed as an IT or compliance topic, but the people who feel the change most are the clerks, team leads and controllers who handle invoices every day. E-invoicing operations change how the work is done, not only which file format is used. Here is what I have seen change on both sides of the ledger.
What Changes for Accounts Payable
Before e-invoicing, most AP teams I meet spend a large part of their week on the same routine: opening emails, downloading PDFs, scanning paper, typing invoice data into SAP and chasing approvers who are travelling. Errors creep in, and duplicate payments or missed discounts are a constant risk.
With e-invoicing for AP, the team no longer needs to manually read and retype every invoice field. It arrives as structured data via the Peppol network or a national platform, is validated automatically and can flow directly into the ERP. Through the Melasoft Peppol Access Point and our SAP Add-On for incoming invoices, the data flows into SAP without anyone retyping a single field. Companies without a deep SAP integration receive and validate their invoices in the cloud through the Docnova Portal.
This is where accounts payable automation really starts. Approval routing, matching and posting can run on rules instead of email chains. Our AP Automation module manages the approval workflow, so each invoice reaches the right person with the right data at the right time.
The biggest change I observe, though, is in the role itself. AP clerks move from data entry to exception handling. Their new daily tasks are reviewing rejected or non-compliant invoices, keeping supplier master data clean and monitoring the inbound channel. AP invoice compliance becomes something the system checks before posting, rather than something an auditor finds months later.
One practical point: there is always a transition period, because not every supplier sends structured invoices on day one. MelaAI, our OCR engine, reads the PDF invoices that keep arriving and converts them into the same data structure, so the team works with one process instead of two.
What Changes for Accounts Receivable
On the receivables side, the old world is usually a PDF attached to an email, followed by uncertainty. Did the customer receive it? Did it land in the right inbox? Was it rejected for a missing purchase order number?
Accounts receivable e-invoicing replaces that uncertainty with transparency. With our SAP Add-On for outgoing invoices, invoices are generated directly from SAP in the required format, whether XRechnung, ZUGFeRD, Factur-X or Peppol BIS, and sent through the right channel. Status feedback comes back: delivered, accepted or rejected. AR digital invoicing means the team sees exactly where every invoice stands.
The daily work shifts accordingly. AR teams now monitor delivery status, respond quickly to rejections and correct master data errors such as wrong VAT IDs, missing Peppol participant IDs or missing buyer references. In more than one e-invoicing for AR rollout, I have watched clients discover that poor customer master data had quietly been delaying payments for years. Fixing it is often one of the quickest wins of the entire project.
Two further modules support this side of the house. Payment Reminder automates dunning messages once invoices are overdue, and E-Reconciliation aligns open items with customers and partners without endless spreadsheet exchanges.
Where AP and AR Meet
The most successful projects I have worked on treat e-invoicing as one shared platform rather than two separate projects. When incoming and outgoing invoices run through the same infrastructure, finance workflow automation becomes much easier to scale. Teams get one archive, one compliance view across countries and one place to look when the auditor calls. All documents processed through Docnova are archived in Germany, and Melasoft is ISO 27001 certified, which matters a great deal to the controllers and data protection officers I speak with. For groups active in several of the 30+ countries we cover, a new mandate then becomes an extension of an existing setup instead of a new project.
Three Lessons from the Field
- Clean up master data before go-live. Supplier and customer data quality decides whether invoice processing automation runs smoothly or produces a flood of rejections.
- Define who owns exceptions. Someone must be responsible for rejected invoices on both the AP and the AR side, with clear response times.
- Plan for the hybrid period. Paper, PDF and structured invoices will coexist for longer than most companies expect. A solution that handles all three in one workflow saves a lot of frustration.
Conclusion
E-invoicing is usually introduced because a law requires it. In my experience, the companies that benefit most are those that use the mandate to rethink their finance workflows. AP teams gain time for analysis and supplier relationships, and AR teams gain visibility and faster cash collection.
If you would like to see how this works in practice, book a Docnova demo or talk to us about the Melasoft SAP Add-On. I am happy to share what we have learned from projects across Europe and beyond.