ADVANCED BANK RECONCILIATION

IN AX 2012 IMPLEMENTATION
EXPERIENCE- Useful Tips &
Workarounds
Dec 4, 2015

797 views

18 Likes

2 Comments

Share on LinkedIn

Share on Facebook

Share on Twitter

BACKGROUND
Recently for one of major client of AX 2012 R2, we implemented Advanced Bank
Reconciliation.
1

Overall going live with advanced bank reconciliation is easier task but challenges come
when we have to map business scenarios within AX reconciliation feature. Unfortunately
there is limited documentation/material available on mapping such business scenarios
apart from broader feature information.
Scope of customization in this area is limited (should be) and with whatever standard AX
provides, which is quite good enough; we went live and here I'm sharing our experience
of implementing advanced bank reconciliation that can be handy for other
implementations. I have covered information in 3 sections:
1. Considerations
2. Workarounds to map business requirements
3. Useful MS hotfixes for AX 2012 R2
Apart from these tips & tricks, challenges can be faced to map or enable this feature for
business which is already running on AX and has existing AX bank transactions which
needs to be cleared before starting auto reconciliation (we did it through script to mark all
past transactions as reconciled) or start reconciliation from beginning if business requires
(most of cases not necessary for business to reconcile past transactions)
CONSIDERATIONSSTATEMENTS NEED TO BE IN XML FORMAT TO IMPORT ALL
STATEMENTS TOGETHER BUT INDIVIDUAL FILE IMPORT CAN BE STILL
DONE IN .TXT FORMAT
By default we receive all files in .txt format. If we individually import each file, then .txt
file can be used but in case need to import all statement files together, then the file must
be in .xml format.

In cases when I need to import all .txt files together, I rename to change format to .xml
and then use for bulk import like below.

STATEMENT VALIDATION
Cant validate multiple statements together even though validation button will be active
when multiple statements are selected together
Also after validation, Infolog message is not accurate and would need to rely on
statement status to know if validation passes or not. (these looks to be standard AX
drawbacks)
Only once statement status in validated, the lines from statement will be available in
bank reconciliation journal
SETTING UP OF MATCHING RULES WILL BE KEY FOR SUCCESSFUL
IMPLEMENTATION OF ADVANCED RECONCILIATION
The reason I call it key because it determines how much of reconciliation can be done
automatically by system Vs. manual matching.
We have setup multiple matching rules to help maximum automation based on amounts,
payment reference and combination of these.
For e.g., like below rule which match lines based on exact debit/credit amount within
maximum of 10 days difference.

Or like below setup where even if reference number in statement and AX bank
transaction is not exact match (but contains the number), then also auto matching will be
done. Such as if bank statement has cheque number captured as 349230 and AX posted
transaction as UL349230_1, matching rule will still match these two records when it at
least contain payment reference.

We have also setup matching rule set in sequence of rules in such a manner that most
accurate matching rule is run first and then new rule set for repeated rules and any
matching with allowed differences.

WORKAROUNDS:
IN BANK STATEMENT, TRANSACTIONS ARE CAPTURED WITH DEBIT AND
CREDIT (NET EFFECT ZERO) AND THESE ARE NOT AVAILABLE IN AX
o To clear such transactions from bank reconciliation journal, while reconciling, select
the bank statement line and Mark as new for transactions which are net-off already in
bank and not available in AX.
o Continue with reconciliation submission and approval
o Verify statements status changes to Reconciled
o Verify transactions marked as new will be part of adjustments in reconciliation report
Note: Dont proceed with further posting of these New transactions. They will remain
as New un-posted adjustment transactions part of adjustments in reconciliation report
with net impact zero

IN CASH AND BANK MODULE, BANK TRANSACTIONS ARE CAPTURED

WITH DEBIT AND CREDIT (NET EFFECT ZERO), WHEREAS NO
CORRESPONDING ENTRY IN BANK STATEMENT
We have process in AX to clear Open bank document transactions from bank
documents list form only when two marked documents are with same bank account,
transaction type, payment reference and opposite amount.
Steps to follow:
o Go to cash & bank management> common> bank document list
o Open the form
o Select the two records which needs to be cleared
o Click on Clear button from action pane
o If conditions meet, then these two records get cleared from document list and also from
reconciliation worksheet
If conditions dont meet, below info log occurs and records will not be cleared

DURING RECONCILIATION PROCESS, TRANSACTIONS MARKED AS

NEW (BANK CHARGES) CAN BE POSTED IN CURRENT MONTH IF
PREVIOUS MONTH IS ALREADY ON HOLD?
There will be possibility that transactions like bank charges are not entered to the system
for the month and will result in difference between the general ledger amount and bank
statement balance. Such transactions needs to be marked as New while working on
bank reconciliation journal
If there are any transactions that you have marked as new, these can be posted.
o Log in to Microsoft Dynamics AX 2012 rich client
o Go to Cash and bank management > Common > Bank statements> then edit the
appropriate statement
o Select the line marked as New
o On the line details FastTab, enter the appropriate financial details and financial
dimension values

o Then click Post to post the transaction.

o The transaction will now have been posted in the current period (system date of
posting) and marked as reconciled

USEFUL MS HOTFIXES FOR AX 2012 R2 BANK

RECONCILIATION PROCESS
HOTFIXES KB2997398, KB3065100 and KB2962564
===============================================================
============================
Hotfix KB2997398 build 6.2.1000.8862
Direct Download link:
http://hotfixv4.microsoft.com/Microsoft%20Dynamics%20AX
%202012%20R2/nosp/KB2997398/6.2.1000.8862/free/478569_intl_i386_zip.exe
Microsoft Issue/Design Scope reference:
Advanced Bank Recon - Enable many to many matching between bank statement lines
and bank document lines
Feature request to support many to many matching on bank document and bank statement
There will be some limitations:
1. The many to many will work only if total on left hand side and total on right hand side
are exactly equal
2. Penny difference will not be supported (as we do not know which transaction
originates penny difference). Even if the penny difference is set up by user, if the left and
right side do not match exactly, we cannot reconcile.
3. Automatic reconciliation rules will not be supported for many to many matching.
Release details for KB2997398
The following application objects were modified as part of this fix:
Layer syp, solution foundation
Classes/BankReconciliationMatchingMatch.xpo
The following application objects are included due to application dependencies:
Layer syp, solution foundation
Classes/BankReconciliationMatchingMatch.xpo
8

Classes/BankReconciliationMatchingMatchProcessor.xpo
This hotfix includes the following encompassed fixes:
KB2962564
NOTE: The KB2997398 hotfix package already includes KB2962564
===============================================================
==============================
Hotfix KB3065100 build 6.2.2000.682
Direct Download link:
http://hotfixv4.microsoft.com/Microsoft%20Dynamics%20AX
%202012%20R2/nosp/KB3065100/6.2.2000.682/free/484580_intl_i386_zip.exe
Microsoft Issue/Design Scope reference:
In bank reconciliation user cannot mark bank document transactions first
Release details for KB3065100
The following application objects were modified as part of this fix:
Layer syp, solution foundation
Classes/BankReconciliationWorksheetFormView.xpo
Classes/BankReconciliationWorksheetViewModel.xpo
===============================================================
==============================
Hotfix KB2962564 build 6.2.1000.7489
NOTE: KB2962564 is already included in the KB2997398 hotfix package
Direct Download link:
http://hotfixv4.microsoft.com/Microsoft%20Dynamics%20AX
%202012%20R2/nosp/KB2962564/6.2.1000.7489/free/474881_intl_i386_zip.exe
Microsoft Issue/Design Scope reference:
Advanced bank account statement reconciliation: not possible to reconcile two
transactions on bank account (bank) with one transaction on bank account in AX
Release details for KB2962564
The following application objects are modified as part of this fix:
Layer syp, solution foundation
Classes/BankReconciliationMatchingMatch.xpo
Classes/BankReconciliationMatchingMatchProcessor.xpo
By,
Nikitasha Haval, Dynamics AX Financials Consultant, Sonata Software
Can reach me at- nikitahaval@gmail.com