The Autopilot creates a direct connection with your cloud software. Available for Exact Online, SnelStart, D365 BC.
The Autopilot is the most seamless way to connect your cloud software with eConnect. After a one-time OAuth connection, invoices are fully automatically imported, processed and posted in your accounting package, without any manual intervention.
In short The Autopilot creates a direct connection with your cloud software via OAuth. The Autopilot runs on the eConnect platform for Exact Online, SnelStart and Dynamics 365 Business Central. For Unit4 ERPx, the Autopilot runs via the PSB. Purchase invoices are automatically posted. For Dynamics 365 Business Central, sales invoices are also automatically sent via Peppol. Available for Exact Online, Dynamics 365 BC, SnelStart and Unit4 ERPx.
The Autopilot establishes a direct, secured connection with your cloud software via OAuth authorization. Once connected, the Autopilot communicates automatically with your accounting package:
The Autopilot runs in the background and requires no further action after the initial setup.
The Autopilot is available for:
The installation differs per software package, but the basic process is the same:
After connecting, the Autopilot is immediately active.
Each Autopilot connection has its own prerequisites. Below you will find per package what you need to arrange before activating the Autopilot.
If your organization was previously connected through exactonline.everbinding.nl, you need to disconnect that connection first. As long as the old connection is active, the Autopilot cannot connect.
For multiple administrations, it is best to migrate all administrations in a short timeframe. This prevents some administrations from running through the old route and others through the Autopilot.
Invoices received before the Autopilot connection are not automatically reprocessed. If you want to retrieve those, use the "Re-offer to API" option in the eConnect platform.
Note: You need a full Exact Online user. MijnKantoor accounts do not have API access and cannot be connected. Read more in the Exact Online article.
Your administration must be online in SnelStart. Without an active online administration, the Autopilot cannot connect.
Note: First process all pending documents through the old route (the cloud icon in SnelStart). If you activate the Autopilot while documents are still in the queue, they may be lost or processed twice.
Then remove the old connection in SnelStart itself. If you don't, invoices may arrive twice.
Before you can activate the Autopilot, you need to arrange three things in Business Central:
First process all pending documents through the existing route. Further configuration of the Autopilot is set up during implementation together with eConnect; this is not a self-service connection.
The Autopilot goes beyond just forwarding invoices. In combination with the eConnect processing engine, it also offers automatic posting suggestions:
The posting suggestions work best when the Autopilot is combined with the internal rule engine (RBE), which can enrich and adjust invoices based on smart instructions. The Autopilot itself is fully self-service configurable; the RBE requires support from the tech team.
If you previously used a different connection (for example connection keys or the Email Receiver), you must disconnect it first before activating the Autopilot. Two active connections to the same administration can conflict.
For SnelStart specifically: if an old connection is active, it must first be disconnected in both SnelStart and eConnect.
The status labels the platform assigns to an incoming invoice differ per connection type. Only the Autopilot ↔ Unit4 ERPx route explicitly returns Booked or Booking failed; other Autopilot routes use Downloaded with a meaning that varies per connection type. For the Unit4 ERPx route, postings are also idempotent: when there is a match on invoice number, customer and supplier, no new posting is created and a Booked status may refer to a previous processing run.
For the full status meanings per connection type, the diagnosis path for "invoice Booked but not visible in ERPx" and other deviations between the platform and the ERP package, see ERP troubleshooting.
The VAT mapping for Autopilot is configurable per connection via Platform > Autopilot > Connection > Posting scheme > MANAGE SCHEMES > VAT. For outgoing invoices via Unit4, eConnect does not handle the VAT mapping: Unit4 supplies the XML and is responsible for the correct UNCL5305 Tax Category codes in line with the Peppol BIS validation.
Want to connect multiple Business Central environments with the same partyId? Use a unique Entra ID account per environment. The same combination of partyId and Entra ID user overwrites the existing connection, and multiple Entra ID users in the same tenant cause InvoiceSent hooks to be delivered to only one BC environment.
Want to know if the Autopilot is available for your software? View all integration methods.
Connect your software