Skip to main content

Points of attention when integrating with Reeleezee

Points of attention when integrating with Reeleezee

Written by Jèsel Broekema
Updated over 2 weeks ago

When integrating with Reeleezee, please take the following into account:

  • Only full synchronisation of master data is supported.

  • Adjusted VAT amounts are only transferred to Reeleezee when using VAT code:
    “NL, specify VAT amount manually”.

  • Only files with the following extensions are sent to Reeleezee:
    ​.pdf, .jpg, .jpeg, .png, .tif, .tiff, .xls, .xlsx

  • Supplier numbers are not displayed in Zenvoices and cannot be entered.

  • Posting to sections (rubrics) is not supported.

  • The transaction description field is not supported by Reeleezee.

  • Transactions are created as draft entries in Reeleezee by default.
    This can be configured per administration via the ‘Reeleezee’ tab in the administration settings: Manage / Organisation/ Companies.

  • The connection is established using a user account from Reeleezee. We recommend creating a dedicated integration user, with access granted to at least two employees.

  • If you use two-factor authentication (2FA) to log in to Reeleezee, you must create a webservice integration. See the Reeleezee support article: https://support.reeleezee.nl/s/article/Webservice-koppeling-aanmaken.

Overview of supported functionalities

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

  • Upload transaction document: Yes

  • Maximum transaction document size: 30 MB

  • Archive link in transaction: No

  • G-account support: No

  • Spread transactions: No

  • Project support: No

  • Cost centre / cost unit support: No

  • Currency support: Yes

  • Payment reference: No

  • Enter date in transaction line: No

  • Financial year / period support: No

  • 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 number of due days in the relation master data.

  • Purchase to Pay: No

Did this answer your question?