Skip to main content

Points of attention when integrating with Octopus

Read here about the key considerations and supported functionalities for the integration with Octopus.

Written by Jèsel Broekema
Updated over 2 weeks ago

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

  • Journals and general ledger accounts are defined per financial year in Octopus.
    Zenvoices retrieves master data from the latest financial year.

  • For accounts, only the number of due days is retrieved from Octopus if it is set to ‘days after invoice date’.

  • When creating or modifying accounts, a VAT scenario must be specified. This mandatory field determines the VAT liability of the account.

  • Retrieving and modifying the payment method of an account is not supported.

  • When an account is modified, the number of due days in Octopus is automatically set to ‘days after invoice date’.

  • The ‘comment’ field in Octopus is enriched by Zenvoices with the transaction header description field, which is by default filled with the variable {invoicenumber}. During export, this field is used for the invoice uniqueness check. We therefore recommend not adding additional text to this field. Additional descriptions can be entered at line level.

  • The administration language settings determine the language of master data descriptions.

  • The country field is mandatory when modifying an account card.

  • Define preferred VAT codes and a preferred general ledger account in the journal settings (e.g. ledger account 600000 + VAT codes H21, H12, H6 and H00).
    These will be proposed if no preferences are configured in the supplier master data.

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

  • An accountant must use the Octopus webservices subscription to enable the integration.
    For internal files, this is an additional module per file. For client files, it is included.

  • For newly connected administrations, the IBAN of the administration must be manually excluded from recognition, as it cannot be retrieved from Octopus.
    This is particularly important when processing sales transaction. Please refer to this related article for more information.

Overview of supported functionalities

  • Multiple administrations via one accounting software connection: Yes

  • Upload transaction document: Yes, maximum 1 per transaction

  • Maximum transaction document size: 100 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: Yes

  • Payment reference: Yes

  • Enter date in transaction line: No

  • Financial year / period support: Yes

  • Authorisation: Block for payment: Yes

  • Authorisation: Update audit report during authorisation: No

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

  • Purchase to Pay: No

  • Non-deductible VAT % / Private use % view and edit: Yes (Belgian administrations only)

Did this answer your question?