Matching commitments is only available in the Pro and Compleet subscriptions.

Only files with the extension .pdf can be sent to Exact Online Bouw. Documents submitted in other supported formats via Zenvoices are automatically converted to PDF. See this related article to read what files can be imported by us.

Only purchase transactions are supported.

Zenvoices connects directly with Exact Online Bouw. Transactions are shown under ‘Purchase invoices’. From Exact Online Bouw, transactions can be manually or automatically posted to Exact Online. See this related article for more information.

Branches (Filialen)* can be created in Zenvoices as administrations via Manage / Organisation / Companies. There is also one main administration, corresponding to no branche (‘geen filiaal’)* in Exact Online Bouw. Master data is shared between branches, even though in Exact Online Bouw a filiaal can be linked to, for example, a project.

Projects with the status Delivered or Invoiced are retrieved when the administration setting ‘Show closed projects’ is enabled.

Contacts* can be created in Zenvoices as suppliers. Contacts created in Zenvoices are created in Exact Online Bouw under contract type ‘Supplier’.

In addition to Suppliers*, the following relation types are also available in Zenvoices: Contacts*, Subcontractor*, Own organisation* and Consultancy firm*.
If a relation is both a customer and a supplier, we recommend adding an identifier to the company name to clearly distinguish the correct relation. Use a relation assignment rule to automate this.

Client* is not available in Zenvoices, as invoices cannot be posted to this relation type due to Exact Online Bouw restrictions.

General ledger accounts are branch-specific.

Commitments are matched automatically. If a commitment is not fully settled, a new commitment is created in Exact Online Bouw for the remaining amount. Administration settings are available for automatically creating remaining commitments.

Commitments with non-unique codes are supported (e.g. one commitment code with multiple project codes).

The due date of a transaction is determined based on the payment term or the number of due days set per relation in Zenvoices. The payment term is leading.

Ensure that the administration being linked is connected to a branch.
If new branches are added in Exact Online Bouw after the connection has been created in Zenvoices, these must be manually linked. Otherwise, general ledger accounts will not be available. Please contact support for assistance.

When a new general ledger account is created in Exact Online, it must first be synchronised with Exact Online Bouw. After that, a synchronisation in Zenvoices is required to make the new ledger account available.

The header description entered in Zenvoices is not exported to Exact Online.
Exact Online Bouw replaces it with: “Invoice number # – project number #” The line description is transferred.

The integration between Zenvoices and Exact Online Bouw is established using an API key, which can be retrieved in Exact Online Bouw.

See the recorded webinar created in collaboration with Exact Online Bouw for more information.

Multiple administrations via one accounting software connector: Yes

Upload transaction document: Yes, maximum 1 per transaction

Maximum transaction document size: 100 MB

Archive link in transaction: No

G-account support: Yes

Spread transactions: No

Project support: Yes

Cost centre support: Yes*

Cost unit support: No

Currency support: No

Payment reference: Yes

Enter date in transaction line: No

Financial year / period support: No

Authorisation: Block for payment: Yes

Authorisation: Update audit report during authorisation: No

Payments: Payment term support: Yes
If the payment term field is left empty, the due date is determined based on the number of due days in the creditor master data.

Purchase to Pay: No

Matching commitments: Yes