Bank and Cash management

Follow the points below which describes the major enhancements.
  1. Additional validation on the Bank account number and routing number(USA and Canadian Bank accounts):
  • Earlier in AX 2009, there was no real-time validation on the bank account number and routing number fields and users could enter any random values into those fields.
  • In AX 2012, new validation have been introduced where only valid bank account numbers  and routing numbers are accepted.
  • These validation are triggered based on the “Address” which you select for the bank account. If the Country of the address is USA, then the bank account number and routing number validation are thrown accordingly. If the Country of the address is CANADA, then the bank account number and routing number validation are thrown as per Canadian bank validation.
  • To verify this go to Cash and Bank Management > Common > Bank Accounts.
  • Select USA OPER bank account.
  • Verify that routing numbers and bank account number fields accept random values with no validation.
  • Now specify an address for the bank under the Address fast tab and System will throw the necessary validation errors/warning for the bank account number and routing number fields when you save the record(In Conjunction with routing number type).
image
image
image
2. Bank Credit Limit check during vendor payments with bank as the offset:
  • We can now define credit limits and credit limit tolerance thresholds for a bank account in AX 2012. These credit limit check gets triggered during making a vendor payment(with bank as offset).
  • System will check for the available balance in the bank account and will throw required tolerance message as per the credit limit specified for the bank.
  • We can define Credit limit related parameters in the Cash and Bank Management parameters form.
image
  • Define the credit limit for a selected bank account under General fast tab.
image
  • Note that the available balance in the USSI OPER bank(CONTOSO demo data) is $72771678.46. We will now record a vendor payment journal with an amount $7277378.46(Bank balance + Credit Limit) and validate the journal. System will successfully validate the journal and say It is Ok.
image
  • So system now allows you pay an amount which is within the (Available balance+Credit limit) range of for the bank. If we try to make a payment for an amount $727737946, this will exceed the credit limit and system will stop us from validating and posting it.
image
       3. Inactivate a Bank account:
  • In AX 2009, there was no way to deactivate or close a bank account from the Bank sub ledger. The only way possible was to close the GL account(Cash account) related to the bank account.
  • Now in AX 2012, we can inactivate bank accounts from the bank sub ledger. The steps below explains this change.
  • Go to Cash and Bank Management and Select a bank account.
  • Expand the General fast tab.
  • You can provide a from and To dates for which the back account will be active.
  • Additionally you can set bank account status to 3 different options such as
Active for all transactions – Bank account is active and transactions are allowed.
Inactivate for new transactions – Bank account is inactive and no new transactions are allowed.
Inactivate for all transactions – Bank account is inactive and no transactions are allowed
BankAccountStatus
    
   4. Bank Account Statement Import and advanced reconciliation
  • A much-needed functionality. AX 2012 now allows importing electronic bank statements and then performing advanced reconciliations.
  • To be able to use the back statement import and reconciliation functionality, you will need a series of one time configurations. Below are the high level steps to do all required configurations .
  • The first step is to configure the setup required for the electronic bank statement import which includes the parameters, bank statement format, transaction code mapping and bank reconciliation matching rules etc.
image
  • The next step is to set up the required AIF inbound ports(Services) and import formats etc.
image
  • After all the setups are done, finally we can import the electronic bank statements(XML/XSLT) formats and perform advanced reconciliation.
image

Comments

Post a Comment

Popular posts from this blog

Table Methods in Ax 2012

Table Methods in Ax 2012 Methods are used for adding X++ code to your application. The code in methods is also referred to as business logic. Whenever records are changed, inserted or deleted from a table various default methods are executed. We can change the default methods and by doing so we are overriding the default methods.To override a method go to the  Methods  node of a table, right click and choose  Override Method . Below are few examples of Overriding commonly used Table methods: initValue(): If we create a new record from the table browser or a form the table method initValue() is executed. It is used to set a default value for the fields.  Example (1): Let’s override intiValue for MyFirstTable and set default value for custGroupId public void initValue() { super(); this.custGroupId = "10"; } After adding this method, open table MyFirstTable  through Table browser and press ctrl+n to create a new record. The field custGroupId wil
Read more

Write/ Read to Excel Sheet

File exists in a Directory:  static void FileExists(Args _args) { str filePath = @”C:\\vani.pdf”; ; if(WinAPI::fileExists(filePath)) { WinAPI::copyFile(filePath,”C:\\1.pdf”); } } Dynamics AX X++ code to Read/Write data to excel Writing Data to Excel file   How it works 1. Use SysExcelApplication class to create excel file. 2. Use SysExcelWorkbooks and SysExcelWorkbook to create a blank workbook(by default 3 worksheets will be available). 3. Use SysExcelWorkSheets to select worksheet for writing data. 4. SysExcelCells to select the cells in the excel for writing the data. 5. SysExcelCell to write the data in the selected cells. 6. Once you done with write operation use SysExcelApplication.visible to open file. static void Write2ExcelFile(Args _args) { InventTable inventTable; SysExcelApplication application; SysExcelWorkbooks workbooks; SysExcelWorkbook workbook; SysExcelWorksheets worksheets; SysExcelWorksheet worksheet; SysExcelC
Read more

Financial Dimensions in AX 2012

Image
Today we will be exploring the new changes  related  to Financial dimensions in AX 2012. Earlier versions AX 2009, 4.0 : Ø   In older version System use to limit the creation of dimensions up to 10.  Ø   By default 3 dimensions were available in the system namely Department, CostCenter and Purpose. Ø   Technically these dimensions were controlled by Enum SysDimension and an array EDT Dimension. Ø   So If we have 3 enum elements in SysDimension, then its corresponding array elements are stored in    dimension EDT and can be referred as Dimension[0], Dimension[1]..... Ø   If you would like to store these dimension values against customized table, then simply we were adding the EDT Dimension to that Table. At  Form  level simply drag and drop field on Group then system use to  show all the array elements as string control. New version AX 2012 (6.0) :   Ø   In AX 2012(6.0), there is no limit to dimension creations. One can create n number of dimensions as per orga
Read more