The information in this article applies to administrations with the additional module Authorization management.
Blocking transactions for payment and automatically releasing them is not supported by e-Boekhouden.nl, InformerOnline, Reeleezee, SnelStart, Visma and eAccounting.
It is possible to export transactions directly to the accounting package and block them for payment until the transaction has been approved in the authorization process.
In this case you must configure in the journal settings that transactions must be exported for authorization and that transactions may only be made payable in the accounting package after authorization:
If you enable these options, under 'Transactions' the section 'Payment releases' will appear under 'To export':
Here you will find transactions that have been authorized and still need to be made payable (unblocked) in the accounting package. Just like exporting transactions, this is an action that can be approved manually. You can automatically make transactions payable by enabling the option 'Automatically make authorized transactions payable in the accounting package' in the administration settings.
Working method per accounting package:
The way in which a transaction is blocked for payment differs per accounting package.
AFAS
The transaction field 'Blocked' is used to block transactions for payment.
please note:
AFAS: ensure that the administration setting for 'Automatically block' for payment is disabled. This field can be found via Financial / Management / Administration settings / Payment collection.
AFAS: ensure that workflows that make transactions payable are disabled.
Zenvoices: the default setting for blocking for payment is disabled. For both the purchase journal and the sales journal it can be enabled via Manage / Environment / Administrations / Pencil icon for the relevant administration / tab: AFAS. At the bottom you will find the fields Block purchase invoices (or Sales invoices) for payment in AFAS.
e-Boekhouden.nl
Blocking transactions for payment and automatically releasing them is not supported.
Exact Boekhoud Gemak and Multivers
Blocked transactions are posted with a payment condition that is configured in Exact Boekhoud Gemak and Multivers as 'do not make payable'. The payment condition code to be used must be configured in Zenvoices in the administration settings under the tab 'Boekhoud Gemak and Multivers'.
Exact Globe
The payment terms of the transaction are blocked. This functionality is only available for purchase invoices.
please note: Exact Globe version 417SP10 (dated 03-06-2019) or newer is required to work with payment blocking.
Exact Online
The payment method of the payments of the transaction is changed to cash. As a result, Exact Online will not include the payments in a payment proposal. This can be checked by viewing the payment term of the transaction in Exact Online.
During authorization:
When unblocking, the payment method is changed to the payment method configured in the payment condition of the transaction.
After authorization (example):
The above is the default method since 13-12-2019. If you already worked with payment blocking in Exact Online before this date, you are probably still using the old payment blocking method in which the payment condition of transactions is changed. The disadvantage of this method is that processed transactions or transactions in closed periods in Exact Online can no longer be unblocked. Therefore our advice is to switch to the new method.
You can do this by going to Manage / Environment / Administration / Edit and on the tab 'Exact Online' change the setting 'Payment blocking method' from 'Payment condition' to 'Payment method'. After changing this setting the new method will be used for new transactions. Existing transactions that are still blocked through the payment condition will still be unblocked using the old method.
After changing the setting the selection option disappears and you will work in this administration with the setting 'Payment method' by default.
Exact Online Bouw (formerly Bouw7)
During authorization an invoice receives the status 'new' and after approval it automatically changes to 'open'.
InformerOnline
Blocking transactions for payment and automatically releasing them is not supported.
KING ERP
The transaction field 'Blocked' is used to block transactions for payment.
Open items are unblocked after authorization in the transaction year and the current year (if a new financial year has started in the meantime).
Microsoft Dynamics 365 Business Central
In Microsoft Dynamics 365 Business Central, this is linked to the “On hold” field, which can be viewed in the invoice details. If this field is not visible, it can be added via Personalization.
If the posting is exported as final (see administrative settings), this field can be viewed in Microsoft Dynamics 365 Business Central under the vendor ledger entries.
Octopus
The payment method field 'Blocked' is used to block transactions for payment. When the transaction is made payable, the entire transaction is updated. Any manual changes in Octopus will be overwritten.
Odoo
The field 'Block Payment' (from version 17) is used to block transactions for payment.
Reeleezee
Blocking transactions for payment and automatically releasing them is not supported.
SAP Business One
The transaction field 'Payment blocking' under the tab 'Accounting' is used to block transactions for payment.
SnelStart
Blocking transactions for payment and automatically releasing them is not supported.
Twinfield
The transaction field 'Do not include in payment run' is used to block transactions for payment.
Visma eAccounting
Blocking transactions for payment and automatically releasing them is not supported.
Keywords: payment blocking