Automatically post invoices to your software via Autopilot. Connections, general ledger coding and the dashboard.
In short Autopilot creates a direct connection with your accounting software and posts received invoices automatically, or forwards them from the platform to your software package. The dashboard shows immediately whether postings succeeded.
With Autopilot you connect the eConnect platform to your accounting software. Received invoices are posted automatically or forwarded to the software package, without copying them by hand. Autopilot supports connections with Exact Online, SnelStart, Unit4 and Business Central.
The Autopilot app has its own sub-navigation in the sidebar:
Click New Connection in the sub-navigation of the Autopilot app.
Choose the organisation for which you want to create the connection.
Select the software package you want to connect (Exact Online, SnelStart, Unit4 or Business Central).
Configure the posting scheme. This determines how VAT types are posted in your software. The scheme is used for every automatic posting.
Save the connection. The connection is now active and invoices are processed automatically.
Autopilot learns from earlier postings and applies that knowledge to new invoices. For each invoice the system analyses the supplier, the amount, the cost type and historical posting patterns to build a complete posting proposal: general ledger account, cost centre and VAT rate. The more invoices that pass through the connection, the more accurate the proposals become.
With sufficient confidence the invoice is posted automatically, without intervention. With lower confidence the proposal is offered for approval. The threshold for automatic posting is configurable per connection, so your organisation decides which level of control is required.
Debtors and creditors are created automatically in your software. Administration therefore continues in real time, including weekends and holidays.
The platform can link invoice lines to order lines automatically. Matching uses a unique unit price, the description and a single order line. Order information is retrieved via the interface or from the archive of previously sent orders. Matching works on both e-invoices and OCR-processed PDFs and raises the percentage of straight-through processing.
The Document Journal is the Autopilot log. For each active connection a journal records the status of every posted document.
Delivered/Received is not a journal row. Status Delivered (NL UI: Ontvangen) in the Inbox means the invoice has arrived and is available in eConnect. That is not a posting result and does not create a Document Journal row. If a search on invoice number returns 0 hits in Document Journals while the Inbox shows Delivered/Ontvangen, that is expected as long as there has been no Booked or Booking failed step. See also Invoice statuses.
First step when Delivered has no journal row:
When a posting fails you can view the error and choose one of two actions:
Each journal row contains a direct link to the original document in the Inbox, so you can quickly check which invoice it concerns.
The status labels the platform attaches to an incoming invoice differ per connection type. Only the Autopilot to Unit4 ERPx route explicitly returns Booked or Booking failed. Other Autopilot routes use Downloaded (Gedownload) with a different meaning per connection type. For the full explanation and the diagnostic paths when platform and ERP diverge, see Autopilot in your own integrations.
Since the October 2026 release, Autopilot determines which general ledger account an invoice lands on. This applies to purchase invoices. For Exact Online and SnelStart it also applies to sales invoices.
cbc:AccountingCost per invoice line and add dimensions. Whether a rule leaves existing codes or overwrites them depends on the rule. SBI coding fills only lines without a code by default. That rule can also be set so that it replaces existing codes.A wrong general ledger account comes from one of these three steps: what was on the invoice, what Rule Based Enrichment filled in, or how Autopilot translates the code.
Per connection, a scheme determines how RGS codes map to general ledger accounts. A custom translation table on the connection always takes precedence over the scheme. Both are settings in Autopilot, not in Rule Based Enrichment. The SBI mapping in Rule Based Enrichment chooses an RGS code for a combination of sectors. That is not the translation table in Autopilot.
A rule can apply to all customers and be configured differently for one customer. The customer setting wins. A rule can be limited to certain invoices, for example from one supplier. Tech support turns coding off for one customer. For the other customers it stays on. That is not self-service.
A dimension is an extra classification next to the general ledger account: cost centre, cost unit or project. Dimensions apply only with Exact Online. Autopilot checks those dimensions against the customer's administration.
The Autopilot dashboard shows all postings: how many documents were posted successfully and how many failed. You can see at a glance whether automatic processing is running well.
When a posting fails, a workflow task is created automatically. You can view the error in the Document Journal and choose "Resend to ERP" (after resolving the error) or "Mark as Done" if the document does not belong in the software.
You can create a separate connection per organisation via New Connection in the Autopilot app. Each connection has its own posting scheme and can point to a different software package.
The posting scheme determines how VAT types are posted in your software. You can change the scheme in the settings of the relevant Autopilot connection. Changes apply to new postings.
Check three steps. Were there already codes on the invoice lines? Did Rule Based Enrichment fill in or overwrite an RGS code or dimension? And does the scheme or the connection's own translation table translate that code to the right general ledger account? The own translation table takes precedence over the scheme. Turning coding off for one customer is done by tech support, not self-service. Dimensions (cost centre, cost unit, project) apply only with Exact Online.
Rule Based Enrichment (RBE) is a rule-based engine that adjusts the XML of an invoice just before sending or just after receipt. The aim is extra flexibility where the ERP system or the partner delivery cannot provide it. Rules are set up by the eConnect tech team (currently via JavaScript) and activated through a filter, for example for a specific supplier. For every invoice that RBE adjusts, the engine looks up validated party data (VPD) of sender and receiver: party IDs and sector codes (SBI, NACE). A rule can therefore filter on a party or a sector, even if that ID is not on the invoice. If the party is missing from VPD, or VPD is unreachable, processing continues without that data. RBE is also an alternative for partners who hard-code customer-specific XML changes: the partner always delivers the XML in the same way, and RBE handles the customer-specific mapping. Self-service rule management is not offered.
Besides posting energy invoices (EAN to property number) and cleaning purchase order numbers, RBE is also used for field mapping (for example UWV flows where a required XML field is missing), merging or grouping invoice lines into a workable number of posting lines, and mapping tables that convert or enrich field values. Autopilot is self-service. RBE requires support from the eConnect tech team and is not self-service. Both components work best together. Custom work uses the regular consultancy rate.
Invoice line grouping. Invoices with hundreds to thousands of lines (for example in retail, construction or telecom) sometimes fail in the accounting software because it accepts only a limited number of lines per invoice, or they produce an unreadable posting when processed one-to-one. The same need appears after line recognition via IDR, when many lines are recognised. RBE then groups the lines into a valid invoice with fewer, summarised lines. The standard template rbe-autopilot-group-lines groups by VAT category. Other group keys (for example per telephone number on a telecom invoice) are possible as a custom RBE setup within the existing options, without development. Setup is done by the eConnect tech team, charged via strippenkaart hours (if available) or a remote support session.
For EAN mapping (EAN number to property number/IO number), eConnect currently recognises the EAN number only on e-invoices (XML/UBL), not on PDF invoices. A visible EAN on a PDF invoice is not enough for this mapping. The value must come from the e-invoice structure. This is separate from order line matching, which does work on both e-invoices and OCR-processed PDFs.
Want to set up an invoice connection? Go to the Autopilot app on the platform and create a new connection.
Create connection