| Id: | 11276 |
| Product: | finPOWER Connect |
| Type: | NEW |
| Version: | 2.00.00 |
| Opened: | 04/03/2013 |
| Closed: | 13/09/2013 |
| Released: | 04/10/2013 |
| Job: | J011217 |
 High Importance |
|
 Breaking Change |
|
Bank Accounts; add Banking and Processing days calendar
Previously the Entity defined the Banking Days Calendar and whether Direct Debit processing could occur on any day.
This has been changed so that whilst the Entity still defines a "Business/ Banking Day Calendar", each Bank Account defines its own Banking Days and Processing Days Calendars. In addition the "Allow Direct Debit processing on any date?" has been moved to the Bank Account.
Note, this change has been made as Banks may be physically closed on public/ bank holidays but may still accept electronic processing of transactions. In addition Banks are beginning to allow electronic processing of transactions on any day of the week. The Processing Days Calendar becomes the valid dates that Direct Debits and Credits can be processed on.
The Entity's "Business/ Banking Day Calendar" is used is various places, e.g. Workflows when calculating n business days after a specified date, and when calculating a payment's grace days.
In the Process Direct Debit Payments wizard, instead of entering the Entity to process you now enter the Bank Account to Process. The Bank Account's Processing Days Calendar is used to validate the valid days Direct Debits can be processed. This means the finPOWER Connect Business Layer has been broken as follows. The object finAccountDirectDebits no longer includes EntityId and EntityPk properties, instead you should use the BankAccountId or BankAccountPk properties.
Bank Lodgements now use the Bank Account's Banking Days Calendar, i.e. the days you can physically take a lodgement to the Bank.
The following built-in Summary Pages have been updated:
"SummaryPage_AccountDirectDebits_ItemSummary" has been updated to version 1.01 on 4/08/2013.