Skip to main content

Advanced bank reconciliation [AX 2012 R3]

This is only my opinion but I feel Advanced bank reconciliation has caused a lot of confusion. This is because Microsoft has made it very technical (very cool but a bit painful first time). Also, I feel some of the documentation is lacking in detail.

Below is my quick summary for anyone who wants to start with this topic.

To import a statement file:

Official Microsoft Links

http://blogs.msdn.com/b/axsupport/archive/2014/05/20/advanced-bank-reconciliation-setup-in-ax-2012-r2.aspx

Supported formats are very limited. But the big one is the BAI2 is very common but not all banks use it.

Good non Microsoft Links

Same as the Microsoft one but with screenshots.

http://andym62.blogspot.com.au/2014/06/ax2012-r2-import-bai2-bank-statement_30.html

For developers who want to support different file formats. I would recommend using transformation class, rather than xslt.

Follow this step by step in detail. You will want to extend on it to include additional fields etc but a very good start.

http://dawsb.blogspot.com.au/2014/06/import-bank-statement-csv-format-ax.html

 

To reconcile (Auto and manual)

Official Microsoft Links

http://blogs.msdn.com/b/axsupport/archive/2013/09/09/ax-content-advance-bank-reconciliation-for-microsoft-dynamics-ax-2012-r2.aspx

http://technet.microsoft.com/en-us/library/aa572690.aspx

Good non Microsoft Links

http://andym62.blogspot.com.au/2014/06/ax2012-r2-perform-advance-bank.html

http://www.stoneridgesoftware.com/how-to-use-advanced-bank-reconciliation-matching-rule-sets-in-ax-2012/

 

FAQ

This is a great post which talks about some consideration before turning on Advanced bank reconciliation.

http://dynamicsaxandme.blogspot.com.au/2014/08/details-to-consider-before-turning-on.html

For developers you can debug xslt as per my previous post.

http://dynamicsnavax.blogspot.com.au/2014/07/how-to-debug-xslt-transformation-using.html

If you need to write one for a different file format I would recommend a transformation class as opposed to xslt. xslt is a pain to write and debug.

This is a great link:

http://dawsb.blogspot.com.au/2014/06/import-bank-statement-csv-format-ax.html

 

BAI2 Issues and bugs

Because it is BAI2 don’t think it is the same for every country. Some countries might do slight different things.

In Australia – there was a mandatory field that was missing in the file, the bank number string format is different. The date I found YYYYMMDD and YYMMDD.

Lastly, this bug is very annoying to figure out. I found a KB that you must download for R3.

https://fix.lcs.dynamics.com/Issue/Resolved/616114?kb=2964064&bugId=1690163&qc=1b943f37531d2577142e97636270aa85

2014-10-29_1513 

Next time I will try to discuss the matching rules and how they work – both the good and bad.

Popular posts from this blog

AX - How to use Map and MapEnumerator

Similar to Set class, Map class allows you to associate one value (the key) with another value. Both the key and value can be any valid X++ type, including objects. The types of the key and the value are specified in the declaration of the map. The way in which maps are implemented means that access to the values is very fast. Below is a sample code that sets and retrieves values from a map. static void checkItemNameAliasDuplicate(Args _args) { inventTable inventTable; Map map; MapEnumerator mapEnumerator; NameAlias nameAlias; int counter = 0; ; map = new Map(Types::String, Types::Integer); //store into map while select inventTable { nameAlias = inventTable.NameAlias; if (!map.exists(nameAlias)) { map.insert(nameAlias, 1); } else { map.insert(nameAlias, map.lookup(nameAlias) + 1); } } //retrieve fro

AX - How to use Set and SetEnumerator

The Set class is used for the storage and retrieval of data from a collection in which the values of the elements contained are unique and serve as the key values according to which the data is automatically ordered. You can create a set of primitive data types or complex data types such as a Class, Record or Container. Below is sample of a set of records. static void _Set(Args _args) {     CustTable       custTable;     Set             set = new Set(Types::Record);     SetEnumerator   setEnumerator;     ;     while select custTable     {         if (custTable && !set.in(custTable))         {             set.add(custTable);         }     }     if (!set.empty())     {         setEnumerator = set.getEnumerator();         setEnumerator.reset();         while (setEnumerator.moveNext())         {             custTable = setEnumerator.current();             info(strfmt("Customer: %1",custTable.AccountNum));         }     } } Common mistake when creating a set of recIds

Import document handling (attachment) files #MSDyn365FO

Out of the box you have limited data entities for migrating attachments. If you search what is already in the AOT, you will see a few various examples. I suggest you look at the LedgerJournalAttachmentsEntity as it is the simplest and cleans to copy from. I wont go into detail but I will give a quick run down of what it looks like. Use the DocuRefEntity as your main datasource. It does most of the work for you. Set your table you want to import for as the child datasource Add the Key You will need to add the postLoad method. There is minor code to update the virtual field FileContents. Below is an export I did for the general journal attachments. The import zip structure should be the same way. It will create the usual artifacts such as the excel, manifest and package header xml files. You will see a Resources folder under that. If you drill down to the resources you will see the attachments. This is an export and it used the document GUID for uniqueness. The other thing is the extensi