Implementing e-invoicing software: steps, decisions, and risks

In short

• Configure document series, VAT rates, and templates.
• Connect to the tax authority portal and test with a limited invoice set.
• Define recurring contracts and billing schedules.
• Enable ERP synchronisation and payment reconciliation.

The implementation steps, in order

Each step must conclude with a formal decision made by a company stakeholder, not the software provider.

• **Master Data Setup:** Configure document series, VAT rates, and templates compliant with EN 16931 / Peppol BIS 3.0.
• **Connectivity & Testing:** Connect to the national tax authority and test transmission with a restricted set of documents.
• **Automation Rules:** Define recurring contracts, subscription cycles, and billing schedules.
• **Financial Loop:** Enable bi-directional synchronisation with your ERP and automate payment reconciliation.

Decisions required before configuration

These decisions determine the project's duration. If delayed, they become bottlenecks by the third week.

• **Monthly invoice volume** - define the scale and throughput requirements before starting.
• **Legal entities and document series** - map out the multi-company structure and numbering logic.
• **ERP Integration strategy** - define how data flows between CRMconnect and systems like SAP Business One, Microsoft Dynamics 365, or Sage.

What to verify after go-live

Thirty days after launch, compare your current performance against your historical benchmarks:

• Invoices issued without manual intervention
• Documents rejected by the tax authority portal
• Average Days Sales Outstanding (DSO)
• Missed or failed recurring invoices

How it connects to your ERP

CRMconnect issues and transmits the invoice, while your ERP (SAP, Dynamics, Odoo) maintains the accounting ledger. The synchronisation runs in both directions for documents and payment status, ensuring a single source of truth.

Frequently asked questions