Locked transactions created from the Bank statement


This page explains why and how the Bank Reconciliation Suite App locks transactions.


Introduction

The Bank Reconciliation Suite App protects all transactions that are linked or created by the solution against editing for regular users. This design has been chosen because when a particular date range is reconciled the date range can be compared to a closed accounting period. All transactions are checked and confirmed with the bank statement and should not change anymore. If a transaction would be changed by a user it should only be a change that is not GL impacting. A GL impacting change won't reflect on the bank statement and could lead to mismatches in data. The Bank Reconciliation Suite App does provide the option to change the locking behavior, but this is not recommended by Fast Four. Any issues that potentially arise due to changing the locking behavior won't fall under the support agreements.

Altering the workflow that is locking the transactions is not recommended by Fast Four and potential issues that arise due to altering this workflow won't be covered by support agreements from the Bank Reconciliation Suite App

We advise using the standard behavior to change potentially incorrectly created transactions. The exact steps can be found on the documentation page “Making changes to processed transaction”.

Unlock transactions

In the Bank Reconciliation Suite App we are using a workflow to lock all the transactions that are linked or created by the solution. This workflow is named "Lock Transactions Bank Statement" and by default, this workflow is running for all user roles except for administrators. To alter the behavior navigate to Customization > Workflow > Workflows and open the workflow named "Lock Transactions Bank Statement". We do not recommend disabling the workflow in full, but instead, alter the Lock Record action and for example exclude certain users or user roles.

To allow a user or user role to alter transactions first click on the Lock Record Action (Step 1). In the next pop-up click on the arrows pointing down (step 2) and in the newly opened pop-up select the following

  • Field id: Select here for example user or user role. Recommend is to use a user so the option to edit is really limited.

  • Compare type: Set here none of

  • Selection: Select here one or multiple users or user roles.

Now save the workflow to apply the changes.

After upgrading to a new version

When Fast Four updates the installed version to a new version the changes made to the workflow will be reversed and should be applied again. When an update has been deployed all the system administrators will receive an update notification by mail and this should be the trigger to re-apply the changes to the workflow when there were any.