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.

Labels:

Popular posts from this blog

Approve Workflow via email using template placeholders #Dyn365FO

Dynamics 365 for Finance and Operations has placeholders which can be inserted into the instructions. Normally you would want this to show up in the email that is sent. One of the most useful ones is the URL link to the exact record that you are approving. In the workflow configurations use the placeholder and build up your message. Towards the end it has workflow specific ones. The URL token is %Workflow.Link to web% . For the technical people the token is replaced in this class WorkflowDocumentField. This is what I inserted into my email template. <BODY> subject: %subject% <BR> message: %message% <BR> company: %company% <BR> for: %for% <BR> </BODY> Should look like this. The final result looks like this. If you debug these are the place holders that are put together.
Read more

Purchase requisition – Price

The price fields on the purchase requisition are non-editable for catalogue items. It is expected that a trade agreement be created. The price fields are only editable for these conditions: Form is opened view AP -> Periodic -> Purchase Requisition -> All purchase requisition, or Line type is “Non-catalogue item”, or User is task owner. Ie. The task is assigned to the user. In other words he/she maybe the purchaser that gets the price. User is approval owner. Ie. The approval is assigned to the user. In other words he/she maybe the manager that approves the final requisition. For catalogue items on the purchase requisition line can only select between the vendor directly associated with the item and the cheapest vendor as found through the purchase price trade agreements. If another vendor is requested the vendor can be blanked and the user can enter a “Proposed vendor” in the proposed vendor field on the general tab page for the purchase requisition line.   NOTE: ...
Read more

Dynamics 365 Invoice Capture Feature

Microsoft recently released the new Invoice Capture for Dynamics 365 Finance. I ran through installing and configuring it.  From that experience, below is my brain dump and hopefully it can help with things that are not so obvious. Three type of invoice captures There are three invoice type paths that can be captured. These drive the screen layout and what kind of information is mandatory. PO invoice Header-only Cost invoice When an invoice comes in, you can select one of the three invoice types. Below are the three screen layouts and differences. PO invoice – Invoices of this type are associated with purchase orders. The purchase order details must be determined on each invoice line. Both the header and the lines must be reviewed in Invoice capture. This will create a pending vendor invoice. Header-only – Invoices of this type are associated with purchase orders. The purchase order field on the invoice header is a mandatory field. If the Automatically create invoice lines featur...
Read more