We have a Payment Method set up for 'BACS' (UK bank transfers) and this is set to deposit to a specific account (1200 - our (old) primary bank account).
We have recently set up a new primary bank account (which is account 1207).
Payment Option on the Payment transaction screen is a mandatory field, and when set to 'BACS' it sets the account to 1200 (all other Payment Types are set to undeposited funds, and they set the account to 1202).
When we import bank transactions using the new screens (released last year), we do this by Account (i.e. 1200 or 1207). When the Payments are created from the 1200 bank account, the Payment Option is set to BACS (as expected). When the Payments are created from the 1207 bank account, the Payment Option is left blank (despite it being a required field).
Is this a problem? Do we need another Payment Type setup with the 1207 account for these transactions?
The reason this problem has come to light is that if a Payment needs to be edited manually, then the Payment Option is a required field, and when selected, this changes the Account to the default for the Payment Type. This is a particular problem when the Bank Account has been reconciled for that day.
Is there any way to determine from a transaction (via Workflow) if the Account has been reconciled and prevent the Account from being updated?