Connect AFAS via connection keys for automatic e-invoicing. Including instruction video.
With the integration between AFAS and eConnect, you can send and receive in 2026 e-invoices automatically via Peppol, directly from your AFAS environment. The integration works with connection keys and can be configured per customer or environment.
Make sure you have the following ready:
An instruction video is also available that guides you through the configuration step by step.
Send a test invoice from AFAS and check in your eConnect Outbox whether the invoice has been processed and delivered correctly.
After the integration, you can send sales invoices from AFAS via eConnect over Peppol. Before this runs automatically, you need to set up the sending configuration and provide your contacts with the correct Peppol identification number.
Configure the sending settings in AFAS so that invoices are automatically submitted via eConnect.
To send an invoice via Peppol, the contact (customer) in AFAS must have the correct Peppol identification number, such as a Chamber of Commerce number or OIN.
After configuring the sending and contact settings, you can create and send an invoice. Upon posting, the invoice is automatically submitted to eConnect and delivered via Peppol.
Purchase invoices received via eConnect are automatically forwarded to your AFAS environment. The invoice appears in your administration, ready for processing and approval.
AFAS Small Business has limitations compared to the full AFAS version. For example, Small Business lacks the ability to fully break down VAT from UBL files. Keep this in mind if you are working with the more compact version.
AFAS now also offers Peppol sending as its own Access Point. This means an organization cannot be active simultaneously via AFAS and via eConnect for the same Peppol identifier.
The difference: AFAS Peppol works well for basic point-to-point sending. eConnect offers the complete e-invoicing chain, including receiving, PDF conversion (IDR), archiving, multi-network routing to other procurement networks, workflows and partnerships. For organizations that need more than just sending, eConnect provides a broader solution.
The integration can be configured per customer and per environment. If you have multiple AFAS environments, set up the connection keys separately for each environment.
If invoices from different suppliers happen to have the same invoice number and the same invoice date, the duplicate detection may incorrectly flag them as duplicates. This is a known issue on the eConnect side. If you encounter this, please contact support so the document can be marked as original.
eConnect does not perform field mapping for the AFAS integration. When receiving ("delivering to AFAS"), AFAS receives the XML as it is stored on the platform, without any transformation. How AFAS reads the fields from the XML and maps them to projects, orders or other entities is AFAS's responsibility. Questions about field mapping should be directed to AFAS, not to eConnect.
Need help with the integration? Contact support.
Start the integration