Finance Utilities
Finance Utilities - Release notes
Finance Utilities - Release notes
This document describes the features that are either new or changed in the release version mentioned.
The matrix shows the minimum DXC build versions compatible per Microsoft versions and builds.
If blank: investigations are ongoing.
| D365 Version | Any issues found in testing? | Product version tested |
|---|---|---|
| Product version: 10.0.40 App build: 10.0.1935.5 |
• No functional issues • Build error fixed in 17981 |
• Functional: 10.0.37.2024032522 • Build error fixed in: 10.0.37.202405302 |
| Product version: 10.0.41 App build: 10.0.2015.16 |
Yes • 18802 - Azure connections |
Fix available in 10.0.40.202409162 |
| Product version: 10.0.42 App build: 10.0.2095.13 |
No | DXC Finance Utilities 10.0.40.2024091931 DXC ABN Validation 10.0.40.2024091931 DXC Encryption 10.0.40.202409162 |
| Product version: 10.0.43 App build: 10.0.2177.18 |
Yes • 21291 - Export file name on vendor payment journal line • 21612 - Build error |
DXC Finance Utilities 10.0.40.202501221 DXC ABN Validation 10.0.40.202501221 DXC Encryption 10.0.40.202412121 21612 Build error fixed in 10.0.42.202504081 |
| Feature | 10.0.43 Feature state |
|---|---|
| Modern bank reconciliation | On by default, needs to be manually disabled |
Release notes for other models included in product:
DXC Finance Utilities 10.0.42 runs on the following Microsoft releases
| Base | Version | Release |
|---|---|---|
| Microsoft Dynamics 365 application | 10.0.42 | What’s new or changed in Dynamics 365 application version 10.0.42 |
| Microsoft Dynamics 365 application | 10.0.43 | What’s new or changed in Dynamics 365 application version 10.0.43 |
Release date: 8 April 2025
Bug fixes
| Number | Module | Functionality | Description |
|---|---|---|---|
| 21612 | Various | 10.0.43 build issue | Fix 10.0.43 build issue on Validate connection for API Endpoint connection type. Microsoft.IdentityModel.Clients.ActiveDirectory has been deprecated and no longer supported by FinOps and needs to be upgraded to now use Microsoft.Identity.Client Microsoft notice |
| 21732 | Various | ABN validation | Incorrect GST registered status where ABN hasn’t registered for GST and the ABN has been cancelled - showed GST registered as Cancelled |
New features
| Number | Module | Functionality | Description |
|---|---|---|---|
| 21215 | Various | ABN validation | Where the ABN isn’t registered for GST, use the earliest ABN entity status from date for GST from date. |
| 21210 | Various | Encryption and Decryption | Filtered drop-down options: • Import connections to decrypt key types • Export connections to encrypt key types   |
| 20946 | Cash and bank management | Bank statement periodic import | Where the bank statement has no transactions - now moving the file to archive instead of error folder. Also updated error message to infolog ‘No bank statement was created as file contained no transactions’ |
| 17536 | Cash and bank management | Import bank statement | New Financial utilities parameters field Enable date range for custom bank statement formats controls the From date and To date inputs on Import bank statement for custom bank statement formats. • No (default) - From and To date won’t be mandatory anymore and automatically calculate the from date as earliest date in file and To date as latest date in the file. Similar to our periodic import job. • Yes - From and To date is still mandatory for custom bank statement formats. This is useful where a company only needs to import a certain date range for the particular bank statement. |
| 17536 | Cash and bank management | Modern bank reconciliation | Where the feature ‘Modern bank reconciliation’ is enabled, the bank statement form has been replaced with a new std form. Similar to Bank statement form with feature disabled, we replaced ‘Import bank statement’ dialog with Finance Utilities dialog which supports importing Finance Utilities custom formats. |
| 21806 | Various | Azure connections | Added ability to use container level shared access signature URI by setting new field Disable storage account access to Yes.   |
| 21689 21102 |
Various | DXC Connections | New DXC Connections release 10.0.42.202504042 - Release notes • SFTP connection migrated to DXC Connections model. • Azure blob connection: added ability to use container level shared access signature URI • Upgraded SFTP to latest 2024.2.0 |
| 21719 | Various | DXC Encryption | New DXC Encryption release 10.0.42.202504041. See below for details. |
New features
| Number | Module | Functionality | Description |
|---|---|---|---|
| 20654 | DXC Encryption | Generate keys | Ability to Generate encryption keys within FinOps on DXC encryption parameters  |
| 21545 | DXC Encryption | Key values | Previously the module only included the option for SAS URL to Azure blob file to store the Encryption keys. This change provides support for Secrets in Azure containing base 64 encoded data of the actual keys into D365 key vault. These secrets will then be pulled into FinOps as base64, and decoded before being used for encryption/decryption purposes. |
| 21698 | DXC Encryption | Key values | New field Key source provides the ability to store key values as string within FinOps. Options: • Key vault (default) - Azure Storage SAS URL & Azure Secrets • String - Store keys within FinOps without Azure + key vaults. Also includes option to download the public key  |
| 21548 | DXC Encryption | Setup | Moving Private key and Counter party’s public key around in DXC encryption parameters |
| 21551 | DXC Encryption | Validate | Ability to validate encryption / decryption key name. Select applicable Encryption key name, click Validate which will open a dialog to browse to a file. • Encrypt / Encrypt and sign - select a file that should be encrypted, if setup is correct the encrypted file will be created that can be sent to counter party for testing. • Decrypt / Decrypt and verify - select encrypted file that should be decrypted, if setup is correct a decrypted file will be created.  |
This section describes the features that have been removed, or planned to be removed from a Finance utilities version.
Note: The Finance utilities fields (Biller code and Lodgement reference) have been added to standard ‘Vendor bank account approval’ FastTab in Accounts payable parameters in Finance Utilities version 10.0.35.202307311.
Approximately one year of previous versions are included below.
Release date: 22 January 2025
New features
| Number | Module | Functionality | Description |
|---|---|---|---|
| 20611 | Cash and bank management | Bank statement format | Increased Custom line code’s Line code from 5 to 10 characters |
| 20434 | Various | Encryption | DXC Encryption 10.0.40.202412121. Ability to setup lower level of encryption. User guide Key type options: • Encrypt • Encrypt and sign • Decrypt • Decrypt and verify  |
Bug fixes
| Number | Module | Functionality | Description |
|---|---|---|---|
| 20860 | Cash and bank management | Mark as new - offset to intercompany account | When using Post button in bank reconcilidation’s New transactions and unselected new transaction record’s Line details were offset to intercompany account, these records were also incorrectly posted in the intercompany and also still showed as unposted on the bank reconciliation. |
| 20960 | Cash and bank management | Import bank statements | Removed Recurrence on Batch processing for Import bank statements. Also fixed issue where duplicate bank statements where imported when: Batch processing enabled and Was an issue with automatic reconcile after import and running default matching rule set. |
| 20959 | Cash and bank management | Reconcile after import with default matching rule set | Similar to 18174, also fixed issue where subsequent rules not run when the matching rule set contains a rule that errors and was automatically run with reconcile after import (set as default matching rule set on bank account). |
Release date: 4 December 2024
New features
| Number | Module | Functionality | Description |
|---|---|---|---|
| 18867 | Various | IRD number validation | Modulus 11 digit check, length, digit separator validation for New Zealand IRD numbers. Supports format xxx-xxx-xxx and xxxxxxxxx. This option is enabled by allocating the applicable country, for example NZL, on the Legal entity. Examples: • Incorrect number / Check digit: Expecting check digit 9, but found 8 for IRD no. 086689918 • Not a number format/incorrect separator: Invalid IRD number format. It should only contain digits having format xxx-xxx-xxx or xxxxxxxxx. • Length: Invalid IRD number length, IRD number should be 9 digits long.   |
| 18875 | Data management | ABN validation | Data entities added |
| 19026 | Organization administration | ABN validation review | Where ABN validation is enabled for the legal entity, users can use new button Change history to view changes made in D365 for each ABN.   |
| 19549 | Organization administration | ABN validation review | Enabled the following buttons: New and Delete. Added the following buttons: ABN lookup and ABN status  |
| 20197 | Accounts payable | Self billing invoicing Recipient-Created Tax Invoice (RCTI) |
Ability to automatically create vendor invoices after a product receipt. The invoice can be automatically created at the same time of product receipt, or split/consolidate using the periodic task. The periodic task split/consolidate options include: • Product receipt • Purchase order • Invoice account • Receipt date Post options: • Do not post - Created invoice is not posted and remains as pending vendor invoice • Post - Created invoice is automatically posted. If post failed, it will remain as pending vendor invoice • Post and print - Created invoice is automatically posted. If post failed, it will remain as pending vendor invoice. The posted invoice is also automatically printed/sent as per Print management destination. The following print management destination options are supported: Smart Send (where licensed, Email and Electronic reporting export connections Setup Processing |
| 20304 | Accounts payable | Method of payment - BPAY | Payment control Payment ID and Payment attributes Payment ID is still defaulted to Yes, but now no longer disabled |
| 17514 | DXC License manager | Licensing | New DXC License manager 10.0.40.202412041. See Release notes for more detail. |
| 20389 | DXC Connections | All Azure connections | New DXC Connections 10.0.40.202412041. See Release notes for more detail. |
Bug fixes
| Number | Module | Functionality | Description |
|---|---|---|---|
| 19459 | Cash and bank management | Reconciliation matching rules - Offset type Ledger | When entering new Offset account number, limited to only Main accounts (no financial dimensions). Offset financial dimensions needs to be entered Financial dimensions > Offset account |
| 19527 | Various | ABN validation | Fix to From date for Cancelled GST records |
| 20187 | Accounts payable | BPAY | When overriding the vendor bank’s default lodgement reference on a BPAY method of payment invoice and manually selecting the invoice for settlement on the payment journal line, the default lodgement reference wasn’t overridden by the actual lodgement reference on the invoice. This issue only applied to manual settlement, not payment proposal process. |
Release date: 19 November 2024
Bug fixes
| Number | Module | Functionality | Description |
|---|---|---|---|
| 19934 20173 |
Cash and bank management | Mark as new - offset to intercompany account | 1. Fix to related vouchers for intercompany vouchers. 2. Fix to financial dimensions, as per below. This also resolves the incorrect warning where a financial dimension is used for intercompany offset, but suspended for bank recon’s legal entity.  |
| 20177 | Cash and bank management | Mark as new | Blank distribute amount |
| 20180 | Cash and bank management | Bank statement | New Security privilege ‘Maintain vouchers to be reversed’ added to DFUBankStatementReversalDialog. Added to std duty ‘Enable bank management process’ |
| 20184 | Cash and bank management | Mark as new - offset to intercompany account with tax | Where the intercompany offset type ledger included tax, the tax was incorrectly posted in bank recon’s legal entity. Tax is now posted with the expense/income in the intercompany legal entity. |
Release date: 28 October 2024
Bug fixes
| Number | Module | Functionality | Description |
|---|---|---|---|
| 19587 | Cash and bank management | Reconciliation matching rules - offset to intercompany customer and settling invoice | Issue with finding the intercompany invoice |
| 19571 | Cash and bank management | Mark as new - offset to same bank account | Missing subledger entry when offsetting to same bank account. Issue came from 18692 in release 10.0.38.202408071 |
| 19576 | Cash and bank management | Mark as new - offset to intercompany account | Offset ledger, customer and vendor not posted in Intercompany legal entity |
Release date: 3 October 2024
Bug fixes
| Number | Module | Functionality | Description |
|---|---|---|---|
| 19353 | Various | Azure connections | Fix to Azure blob connection types using Shared access signature (SAS) to access Azure Blob Storage at account level. Fix for error: “No valid combination of account information found” Applicable to versions 10.0.40.202409162 & 10.0.40.202409191 • Cash and bank management > Setup > Advanced bank reconciliation setup > Financial utilities • Organisation administration > Electronic reporting > Electronic reporting export connections. |
Release date: 19 September 2024
New features
| Number | Module | Functionality | Description |
|---|---|---|---|
| 18827 | Cash and bank management | Reconciliation matching rules - offset to customer | New option Auto-post and transfer customer payment journal enables customer payment journal to be posted and any error lines transferred to a new unposted journal (example stopped customer). Both customer payment journals’ Document will refer to the Bank reconciliation.  |
| 19151 | Cash and bank management | Reconciliation matching rules - data entity | Field ‘Description mask’ added to data entity |
| 18837 | Accounts payable | Payments report | Use Vendor bank account’s BPAY Biller code and Lodgement reference fields where payment line’s method of payment BPAY method of payment is Yes. User guide  |
Release date: 16 September 2024
New features
| Number | Module | Functionality | Description |
|---|---|---|---|
| 18870 | Various | ABN lookup | New field Search by ABN available in ABN lookup. When set to: • No: Search by Company name • Yes: Search by ABN  |
| 18851 | Various | ABN status | Where the GST is Cancelled for an ABN, the From date will be obtained from Historical details to indicate from which date the GST has been cancelled.  |
| 18987 | Various | ABN / TaxVatNumTable | New fields added to TaxVatNumTable: • Created by • Created date and time • Modified by • Modified date and time • Reviewed date |
| 18509 | Accounts receivable | AR Utilities | Ability to obtain part of a field in the remittance file, by using Field format on below fields: • Customer reference • Tax invoice User guide   |
| 19087 | Various | Azure connections | Azure dll moved to new model called DXCConnections. DXC Connections release 10.0.40.202409192 - Release notes |
| 19023 | Accounts payable | Sundry method of payment | Allow Generic electronic Export formats where Sundry method of payment is set to Yes. |
Bug fixes
| Number | Module | Functionality | Description |
|---|---|---|---|
| 18984 | Organisation administration | ABN validation review | When Reviewed changes from Yes to No by an update to the ABN record, the Reviewed by used to still store the previously reviewed by user which is not valid since the record is not reviewed anymore. |
| 19014 | Cash and bank management | Web API import & DXC Encryption | Added a check on warning for files imported via WebAPI . If file is empty, a warning will be added to the batch job logs and no files will be added for further process of mapping from file to BankStatement tables. In addition to this, a check and warning has been added in the DXC Encryption model code. If an empty is received for decryption, a warning will be displayed to the user to indicate file stream is empty. New DXC Encryption version 10.0.41.202409161 |
| 18802 | Various | Azure connections | Unable to find manual secret value |
Release date: 28 August 2024
Bug fixes
| Number | Module | Functionality | Description |
|---|---|---|---|
| 18893 | Cash and bank management | Bank statement import via Web API with decryption | Fix for error ‘This stream does not support seek operations. Batch task failed: NotSupportedException’ |
Release date: 23 August 2024
Bug fixes
| Number | Module | Functionality | Description |
|---|---|---|---|
| 18858 | Cash and bank management | Bank statement import with decryption | Error decrypting ER bank statement formats |
Release date: 7 August 2024
Bug fixes
| Number | Module | Functionality | Description |
|---|---|---|---|
| 18347 | Cash and bank management | Bank accounts | Only enable field ‘Include balance line in record count’ when field ‘Extra balance line on EFT’ is enabled. |
| 18550 | Cash and bank management | Bank reconciliation | Disable button ‘Match id’ in Bank reconciliation Worksheet when Financial utilities parameter field ‘Auto assign Match Id’ is set to Yes. Else it errors with ‘No statement lines have been marked’. Clicking Match Id is unnecessary as the Match id will automatically be assigned when user clicks button ‘Match’ in the Bank reconciliation Worksheet. |
| 18692 | Cash and bank management | Bank reconciliation | When feature ‘Enable posting of new transactions in bank reconciliation’ is enabled, the ability to post mark new transactions are available in the Bank reconciliation Worksheet. If user used this posting, and also posted the bank statement, a duplicate mark new transaction was posted. This was only relevant for offset types Customer (when manually marked as new in Recon - not via recon rule that creates customer payment journal), Vendor or Bank. |
| 18689 | Organisation administration | ABN validation report | Previously when running report ‘ABN validation’ the API was run for each vendor/customer with an ABN allocated. Since the fields are now stored on the TaxVatNumTable the report will now not run the API anymore. The relevant fields on the TaxVatNumTable can be updated to current Australian Business Register data by either: • Organisation administration > Periodic > Update ABN validation • ‘Run update’ on ‘Organisation administration > Enquiries and reports > ABN validation review. |
| 18158 | Various | SFTP Connection | PR fixes to 18158 SSH key vault Azure blob storage |
Release date: 25 June 2024
Manual steps required
New features
| Number | Module | Functionality | Description |
|---|---|---|---|
| 18126 | Accounts payable | Generate file per payment line | New option called Generate file per payment line on Methods of payment for Electronic reporting export formats. When set to Yes, the vendor payment’s Generate payments will create an EFT file per journal line.  |
| 17230 | Various | Azure Connection | Ability to use Azure SAS Storage account level token for Connection string on Azure connections. Applicable to: • Cash and bank management > Setup > Advanced bank reconciliation setup > Financial utilities connections • Accounts receivable > Payments setup > Financial utilities connections (AR utilities feature) • Organization administration > Electronic reporting > Electronic reporting export connections |
| 18158 | Various | SFTP Connection | New Credential type option Private key provides the option to store SSH key file in Azure, setup in D365 as Key vault parameter and use on Finance utilities SFTP connection. Applicable to: • Cash and bank management > Setup > Advanced bank reconciliation setup > Financial utilities connections • Accounts receivable > Payments setup > Financial utilities connections (AR utilities feature) • Organization administration > Electronic reporting > Electronic reporting export connections  |
| 17274 | Organization administration | DXC encryption parameters | Public key (sender’s public key) and Receiver’s public key replaced with new field Counter party’s public key. Note: Manual step required to update new field with the applicable key. |
| 18149 | Budgeting | Import budget | Ability to Generate template based on setup on Budget utilities parameters: • Number of months • Dimension format  |
Bug fixes
| Number | Module | Functionality | Description |
|---|---|---|---|
| 18174 | Cash and bank management | Reconciliation matching rule set - Customer offset type | Where the Reconciliation matching rule set contained: • Multiple Mark new transactions rules offsetting to Customer and • Set to automatically post the journal and • One of the rules failed to post the journal (for example customer was stopped for payments) The subsequent rules were not run. |
| 18202 | Accounts receivable | Interest notes - Due date | When AR parameter field ‘Use customer payment terms’ for Interest notes is set to Yes, the Due date correctly included payment terms for the interest note in Customer transactions, but not on ‘Settle transactions’ or ‘Detailed due date list report’. |
Release date: 30 May 2024
New features
| Number | Module | Functionality | Description |
|---|---|---|---|
| 17215 | Various | Azure Connection | Replace deprecated Microsoft.WindowsAzure.Storage with Azure.Storage.Blobs. Applicable to: • Cash and bank management > Setup > Advanced bank reconciliation setup > Financial utilities connections • Accounts receivable > Payments setup > Financial utilities connections (AR utilities feature) • Organization administration > Electronic reporting > Electronic reporting export connections DXC_AzureClient 2024.05.30.1 |
| 16595 | Various | Error messages | Improved error messages for: • Electronic reporting export connections - for errors with setup when generating ER file. • Run reconcilation matching rule that can’t find the customer account - include value of bank statement field with issue |
| N/A | DXC License | Licensing | New DXC License model 10.0.37.202405231. See Release notes for more details. |
Bug fixes
| Number | Module | Functionality | Description |
|---|---|---|---|
| 17981 | Accounts payable | Pending invoice | 10.0.40 build error caused by missing reference for the ProcessAutomation Model which is now used by the VendInvoiceInfoTable. Used to determine whether the Pending invoices button is enabled/disabled in the Vendor Purchase Invoice form. |
| 17990 | Cash and bank management | Reconciliation matching rule - Customer offset type using Customer references | The created customer payment journal uses the first customer account for all the found lines |
| 18014 | ABN validation | Security | New privileges added to access ABN lookup and ABN status: • ABN Validation • Maintain ABN Status • Maintain ABN validation lookup • Maintain ABN validation review • View ABN Status • View ABN validation lookup • View ABN validation review |
| 17998 | ABN validation | Rename objects | Rename objects ending with DXC_Extension: • TaxVATNumTableForm_DXC_Extension • TaxSalesTaxProcessReferenceDataInquire.DXC_Extension • TaxSalesTaxTransactionStatusInquire.DXC_Extension • TaxSalesTaxTrnStatusInquirWithoutTaxPrv.DXC_Extension • TaxVATNumTable.DXC_Extension |
| 18018 | Various | Rename objects | Rename objects ending with DXC_Extension: • BankStatementFormatForm_DXC_Extension • BankChequeTableForm_DXC_Extension • VendPaymMode_DXC_Extension • BankTreasurerWorkspace_DXC_Extension • VendorPaymentHistory_DXC_Extension • BankReconciliationMatchRule_DXC_Extension • CustPaymMode_DXC_Extension • BankStatementTableForm_DXC_Extension |
Release date: 16 May 2024
New features
| Number | Module | Functionality | Description |
|---|---|---|---|
| 17524 | Various | SFTP connection | Upgrade SFTP SSH.NET to latest 2024.0.0 release. Applicable to: • Cash and bank management > Setup > Advanced bank reconciliation setup > Financial utilities connections • Accounts receivable > Payments setup > Financial utilities connections (AR utilities feature) • Organization administration > Electronic reporting > Electronic reporting export connections |
Bug fixes
| Number | Module | Functionality | Description |
|---|---|---|---|
| 17966 | Accounts receivable | Generate payments | Fix for error ‘Root element is missing’, when generating a payment using a non ER Export format. |
Release date: 26 April 2024
New features
| Number | Module | Functionality | Description |
|---|---|---|---|
| 17385 | Cash and bank management | Reconciliation matching rule | Ability to set a Description mask for Mark new transactions for offset types Ledger, Vendor and Bank. Related to 17290 that added this functionality for offset type Customer. Editor provides the ability to set a combination of static fields and placeholders: • Currency • Description • Amount • Document number • Entry reference • Bank statement transaction code • Reference No. • Related bank account • Name (Trading party) • Bank account • Bank account number • Bank groups Note: If File name mask is not populated, the Bank statement line’s Description will be written to new transaction’s Description.  |
| 17724 | Licensing | N/A | Improvements to licensing - see Licensing release notes for detailed information. |
Bug fixes
| Number | Module | Functionality | Description |
|---|---|---|---|
| 17633 | Accounts receivable | Interest notes - Due date | When AR parameter setting ‘Use Customer payment terms’ was set to Yes, it resulted in incorrect due dates for Free text invoices. Only relevant to release 10.0.36.202403251 |
| 17448 | Accounts payable | Method of payment - EFT file name Placeholders | Editor Placeholder picker displayed Bank statement fields added for Reconciliation matching rule’s Description mask. Only relevant to release 10.0.36.202403251 |
| 17479 | Accounts receivable | Method of payment - EFT file name Placeholders | Editor Placeholder picker displayed Vendor’s Method of payment and Description. Updated to use Customer for these two fields. Only relevant to release 10.0.36.202403251 |
Release date: 25 March 2024
New features
| Number | Module | Functionality | Description |
|---|---|---|---|
| 17092 | Accounts payable Accounts receivable |
ABN and GST validation | Only applicable to Australia and only visible where ABN validation is enabled for the Legal entity • New fields added to TaxVatNumTable: - Status: ABN status for example Active or Cancelled - Entity type: Entity type for the ABN, for example ‘Australian Private Company’ - GST from: Populated where the ABN is registered for GST * - GST to: Populated where the ABN is registered for GST * - GST registered: Set to Yes where ‘GST to’ date is in the future *  * The three new GST fields have also been added to the ABN status dialog.  Above new fields are updated to current government data when running either: • Update ABN validation periodic task • Run update on ABN validation review form • When adding new records via ABN lookup User guide |
| 17159 17233 |
Accounts payable Accounts receivable |
ABN validation | Only applicable to Australia and only visible where ABN validation is enabled for the Legal entity New form ABN validation review for users to review new/updated ABN records. For example an ABN is not registered for GST anymore. Select applicable record(s) and select Mark as reviewed to update their reviewed status. Run update can be used to run the web service to update ABNs with current data from the Australian Business Register. Update can also be run via ‘Organization administration > Periodic > Update ABN validation  |
| 17286 | Accounts payable | ABN validation | Only applicable to Australia and only visible where ABN validation is enabled for the Legal entity Ability for users to check the current ABN and GST status for a vendor while entering an invoice. ABN status button is enabled when the ‘Tax exempt number’/’ABN’ is populated for the vendor invoice line.  |
| 16924 | Organisation administration | Electronic reporting export connections | Log functionality added  |
| 17248 | Cash and bank management Organisation administration |
• Financial utilities connections • Electronic reporting export connections |
New Connection type option API Endpoint. Can thus now import bank statements as an inbound web service or export ER files as an outbound web service. Also works with Azure function. Import user guide Export user guide Web API Endpoint Technical guide |
| 17290 | Cash and bank management | Reconciliation matching rule | Ability to set a Description mask for Mark new transactions. This release includes only Customer offset types. Roadmap: include the other offset types Vendor, Bank and Ledger. Editor provides the ability to set a combination of static fields and placeholders: • Currency • Description • Amount • Document number • Entry reference • Bank statement transaction code • Reference No. • Related bank account • Name (Trading party) • Bank account • Bank account number • Bank groups Note: If File name mask is not populated, the Bank statement line’s Description will be written to new transaction’s Description.   |
| 16827 | Accounts receivable | EFT file name on Method of payment | Ability to set EFT file name for Customer payment files (direct debits) on the Method of payment. User guide |
| 16600 | Accounts payable | Vendor payment journal | When the vendor payment is generated, the Export file name displayed on the Generate payments dialog is written to the relevant vendor payment journal lines’ new field called Export file name. Note: This does not yet include file names generated by Electronic reporting config.  |
| 17422 | N/A | N/A | Update to Table groups to support “transaction” types being truncated in copy environment feature via Power platform admin center. |
Bug fixes
| Number | Module | Functionality | Description |
|---|---|---|---|
| 16997 | Accounts payable | EFT file name editor on Method of payment | Refresh required to save updates to the file name using Editor  |
| 16827 | Accounts receivable | EFT file name on Method of payment | If the same payment method PaymMode exists in the Accounts payable (AP) module, the EFT file name setup from the AP method of payment was used |
| 17063 | Accounts receivable | Interest notes - Due date | Due date now updated before the transaction records are created. Resolves error: “Cannot edit a record in Customer transactions (CustTrans). An update conflict occurred due to another user process deleting the record or changing one or more fields in the record.” |
| 17119 | Accounts payable Accounts receivable |
ABN lookup | Fix to ‘Company name’ in Search results |
| 16925 | Organisation administration | Electronic reporting jobs | When using an Electronic reporting destination with document type in conjunction with Electronic reporting export connection, the record created in the Electronic reporting jobs will now also contain: • Document handling attachment - ensure your file extension is added to supported File types in Document management parameters • Field ‘Files’ populated with the file name. |
| 17012 | Cash and bank management | Reverse mark as new transaction | Support added for reversing mark as new transactions offsetting to vendor, bank or customer within the same legal entity. 15693 resulted on an incorrect sign on the reverse transaction on the bank, vendor and customer Supports features: • Enable bank reconciliation reversal even new transactions exist in posted bank statement • Reverse posted bank statement with new transactions |
| 17126 | Cash and bank management | Reconciliation matching rule | When used to create automatically posted Customer dishonour payments, the automatically matching in the Bank reconciliation failed. |
| 17437 | Cash and bank management | Bank statement periodic import | Archive issue when connection has high latency. File deleted before it could copy to Archive. Change: Before delete the result of copy is awaited and retried for 1 seconds 3 times before marking as an exception. |
Older releases notes can be accessed here
To align with MS best practice and to protect our IP the following applies to the release process.
Depending on the installation history follow one of these guides to install the new release.
If you’re installing the new release in an installation that already has a previous version of the product installed and you’re not using it for debugging or extension. We recommend that you;
If you’re using our model source code for extension or debugging and would like to continue using it, please do the following to apply the new release with the source code.
If you don’t follow these instructions and continue building your installation deployable package using the license model source code, the installation will continue using the same license model as before applying the release.
Enable the following features in D365 Feature management:
If above feature is not visible, press Check for updates to refresh the feature management list.