Connect Unit4: ERPx via Autopilot, ERP CR via SFTP, Financials via HTTPS.
Unit4 offers in 2026 three variants, each with its own integration method. Which one applies depends on your Unit4 product.
You connect Unit4 ERPx via the Autopilot. Purchase invoices are automatically imported and posted. The configuration is set up during the implementation with eConnect.
The Autopilot configuration is done via a step-by-step wizard in the eConnect platform:
Note: Process all documents via the old route before switching. The integration configuration is not performed by the customer but during implementation.
When posting via Unit4 ERPx, you may see the message [U4OK.JSON]: System.Int32 overflow. Cause: the invoice number is numerically so large that it exceeds the limit of a 32-bit integer (maximum 2.147.483.647). In that part of the Unit4 processing, the system cannot handle the number. This is a limitation in Unit4 itself, not in the eConnect link or our integration code.
In practice, you see this at organizations that use very high ranges for outgoing invoice numbers (for example, values well above 2 billion).
What can you do? The solution must come from Unit4. Changing the invoice number in the source XML via eConnect is not a workable workaround without risk to your administration and numbering. Unit4 is aware and is working on a structural fix. Until then: escalate to your Unit4 administrator or partner and use the XML download from the eConnect platform (Inbox) if needed to support your case.
Unit4 ERP CR (including ERP7) and Unit4 Financials by Coda connect via SFTP and HTTPS respectively. These enterprise integrations require a contract and are configured by Unit4 or a Unit4 partner in collaboration with eConnect.
The standard integration method for Unit4 ERP CR and ERP7 is SFTP (Secure File Transfer Protocol). For more information about how an SFTP integration is technically set up, see the article SFTP integration.
It may happen that an invoice is successfully posted in Unit4 ERPx, but the PDF attachment does not come through. The posting is then correct in the system, but the original invoice document is missing as an attachment. The attachment upload fails without a visible error message in the logs.
eConnect is aware of this issue and is working with Unit4 on a structural solution. Improvements to the retry mechanism and more extensive logging are on the development backlog.
Tip: the invoice itself can always be downloaded from the eConnect platform (Inbox, three dots next to the document). Forward the document manually to your Unit4 administrator if needed.
When processing invoices via the ABWInvoice transformation (used with Agresso/Unit4 integrations), the error message [API400]: Initializing failed. Unhandled error occurred. may occur. The cause is that the transformation was built based on the original test documents. Deviating document variants (such as free text invoices) contain fields that are missing in the mapping, causing the transformation to fail.
A change request is in progress to extend the transformation for multiple document types. If you encounter this error message, please contact support.
For Unit4 integrations with foreign currencies (e.g. USD with exchange rate), the currency configuration is the customer's responsibility in the Unit4 environment. eConnect processes what the ERP delivers. Support questions about foreign currencies refer to the customer's ERP configuration.
Want to connect Unit4? Contact Unit4 or your Unit4 partner, or eConnect sales for an intake meeting.
Start the integration