An API key and security code are required to establish the connection.
These can be found in InformerOnline under:

The InformerOnline API does not support filtering between customers and suppliers. Therefore, under Manage / Company / Accounts, all accounts are available as both customer and supplier.

Only files with the extension .pdf can be sent to InformerOnline. Other supported file formats submitted via Zenvoices are automatically converted to PDF.

If a cost centre is set as mandatory or optional in the general ledger settings in InformerOnline, this setting is applied in Zenvoices.

transaction numbers generated in InformerOnline are not visible in the Zenvoices archive (not supported by the InformerOnline API).

InformerOnline distinguishes between two types of accounts: companies and private individuals. When synchronising accounts, the account type is not provided by the API. Therefore, all accounts are treated as ‘company’, and new or updated accounts are uploaded as type ‘company’.

In the purchase journal, the selected payment term is only used to calculate the due date*.

The account field ‘authorisation’ (direct debit mandate) is not transferred to processed purchase invoices. As a workaround, you can apply a payment term with a far-future due date to prevent automatic payment.

InformerOnline does not support foreign currency processing in the purchase journal. In the accounting software, currency is only used as a calculation tool where the exchange rate must be entered manually. A currency selected in Zenvoices for a purchase transaction has no effect.

For purchase transactions, the VAT amount may deviate from the calculated VAT amount based on the net amount and selected VAT code (e.g. €101.00 excl. VAT and €20.00 VAT at 21%, total €121.00). For sales transactions, this deviation is not allowed.

If duplicate invoice numbers are detected for the same account, a warning is shown in Zenvoices. The transaction can still be exported to InformerOnline.

The InformerOnline API does not support retrieving or using the preferred general ledger account per account in Zenvoices. Therefore, we recommend not using the proposal strategy ‘Master data’.

Multiple administrations via one accounting software connector: No (each administration requires a separate connection)

Upload transaction document: Yes, maximum 1 per transaction

Maximum transaction document size: 8 MB

Archive link in transaction: No

G-account support: No

Spread transactions: No

Project support: No

Cost centre support: Yes

Cost unit support: No

Currency support: No

Payment reference: No

Enter date in transaction line: No

Financial year / period support: No
(Available in the transaction screen, but not functional)

Authorisation: Block for payment: No

Authorisation: Update audit report during authorisation: No

Payments: Payment term support: Yes
The due date is determined based on the selected payment term.*

Purchase to Pay: No