.png)
Release Date:
Version: 1.7.13661.0.
Summary
This release makes connected bank-account matching substantially more reliable — tolerating formatting differences and supporting masked credit-card numbers — adds a new administrator control over currency-code updates during bank feed mapping, and fixes two issues where upgrade migrations or stale stored values could silently override what the customer saw or chose.
Release Highlights
-
Map Connected Bank Accounts — far more reliable account matching: Connected bank accounts now match your Business Central bank accounts even when BSB or account numbers are formatted differently (dashes, spaces), and credit cards with masked numbers from the bank can now be matched safely on their last four digits.
-
New Currency Code Update Mode setting: Administrators can now control whether mapping a bank feed writes the feed's currency code onto the bank account — never, always, or only for foreign (non-local) currencies. Existing customers maintain their current behaviour; new installs default to updating only foreign currencies.
-
Statement Balance Option choice now preserved across upgrades: Fixed an issue where every release upgrade could silently switch a customer's "Leave Blank" statement balance setting back to "Use ACSISS EOD Balance".
-
Accurate "Days to Expiry" figure: The Map Connected Bank Account page now recalculates the consent days-to-expiry at display time, so it always matches the expiry date shown beside it.
🆕 New Features
Currency Code Update Mode
A new "Currency Code Update Mode" field is available in the Options group on the ACSISS Bank Feeds Setup page. It controls whether the Map Bank Feed action writes the feed's currency code onto the Business Central bank account.
-
Never Update — The bank account's Currency Code is never touched when mapping a feed.
-
Update All Currencies — The feed's currency code is written whenever the bank account's Currency Code is blank, and the currency exists in the Currencies list. This matches the behaviour of all prior releases and is what existing customers are migrated to.
-
Update Non-LCY Only — The currency code is written only when it differs from the company's local currency (LCY). Local-currency accounts keep a blank Currency Code, which is the Business Central convention. This is the default for new installs.
In every mode, an already-populated Currency Code is never overwritten. The comparison against the local currency is case-insensitive, and if the ACSISS Bank Feeds Setup or General Ledger Setup record cannot be read, the field is safely left untouched.
Upgrade Behaviour
|
Scenario |
Result |
|---|---|
|
Existing customer upgrading to this release |
Update All Currencies — preserves the behaviour of prior releases |
|
New install |
Update Non-LCY Only |
|
New company added to an existing multi-company tenant |
Update Non-LCY Only |
|
Any customer who later changes the setting, on subsequent upgrades |
Unchanged — the migration runs exactly once, so the customer's choice is preserved |
New error code added: ACSISS-0014 (Info): Set Currency Code Update Mode to Update All Currencies during upgrade.
Known Issues
-
No known issues in this release