This article applies to Microsoft Dynamics AX for the Spanish (es) region.

When the supplier (vendor) changes taxation policy from cash accounting schema to general one in the Spanish version of Microsoft Dynamics AX 2012 R3 and Microsoft Dynamics AX 2009 SP1, the 347 report for year must reflect amounts posted under different taxation policies separately.

In case when the supplier (vendor) changes his taxation policy from cash accounting schema to general one (for instance, 2014 – CAS, 2015 – non-CAS), the 347 report for year 2015 must reflect amounts posted under different taxation policies separately. Current implementation does not support this scenario, the amounts under cash accounting regime for the previous year are not reported in the reporting year on 347 report.

This hotfix resolves this issue: in case when the supplier (vendor) had a cash accounting schema in previous year, then in current year all invoices posted in previous year that stayed open (not fully settled) up to the beginning of the reporting year are collected and reported under cash accounting regime.

With this hotfix, the processing of prepayments is updated as well: they are reported independently of the cash ledger accounts setting.

To store history of taxation policy switching, instead of a check box Special regime for cash accounting method in General ledger parameters and in Vendor form a new form of the same namewas introduced. It is called from:

For Microsoft Dynamics AX 2009 SP1:
General ledger > Setup > Parameters > Sales tax tab > Special regime for cash accounting method button
Accounts payable > Vendors > Setup button > Special regime for cash accounting method menu item

For Microsoft Dynamics AX 2012 R3:
General ledger> Setup > General ledger parameters > Sales tax tab > Special regime for cash accounting method 
Accounts payable > Vendors > Invoice and Delivery fast tab > Special regime for cash accounting method link under Spanish VAT books group 

This new form Special regime for cash accounting method has three fields From year, To Year, and Enable. In case the policy should be changed, add a new record in there.

When changing policy for the 1st time, set the From Year field with the value when a new policy is enforced. The To year field is left blank and not editable. Enable check box is set to Yes (it is also not editable).

When you need to change policy once more, you should create one more record and set From Year with the value when a new policy is applied. The system updates the To year field for the previous record (policy) automatically, the Enable check box is also updated automatically, depending on the value in the previous record, it switches to the opposite value.

It is allowed to delete records in a chronological order only, starting form the greatest value of the year.

NOTE Before installing a fix you need to identify all vendors with a Cash accounting check box switched on, and store a list of them. After installing the fix, you should update the state for these vendors manually or you can utilize the sample of the script below. In case your company applies a Cash accounting regime, you should update the table in the General ledger parameters.

Sample of the update script which creates a record in the new table for Microsoft Dynamics AX 2012 R3:

staticvoid updateCashAccounting(Args _args)
{
    container vendAccounts = ['AAA', 'BBB', 'CCC']; //List of vendor accounts in single or double quotes
    int sinceYear = 2014; //set the start year for applying a Cash accounting policy
    int i ;
    VendTable   vendTable;
    CashAccountingRegime_ES cashAccountingRegime;   
    for (i = 1; i <= conLen(vendAccounts); i++)
    {
        vendTable = VendTable::find(conPeek(vendAccounts, i));
        cashAccountingRegime.clear();
        cashAccountingRegime.Party = vendTable.Party;
        cashAccountingRegime.VendAccount = vendTable.AccountNum;
        cashAccountingRegime.FromYear = sinceYear;
        cashAccountingRegime.Enable = true;
        cashAccountingRegime.insert();
    }   
}

Resolution

The changes in the hotfix resolve this issue.

Hotfix information

A supported hotfix is available from Microsoft. There is a "Hotfix download available" section at the top of this Knowledge Base article. If you are encountering an issue downloading, installing this hotfix, or have other technical support questions, contact your partner or, if enrolled in a support plan directly with Microsoft, you can contact technical support for Microsoft Dynamics and create a new support request. To do this, visit the following Microsoft website:

https://mbs.microsoft.com/support/newstart.aspx You can also contact technical support for Microsoft Dynamics by phone using these links for country specific phone numbers. To do this, visit one of the following Microsoft websites:

Partners

https://mbs.microsoft.com/partnersource/resources/support/supportinformation/Global+Support+ContactsCustomers

https://mbs.microsoft.com/customersource/support/information/SupportInformation/global_support_contacts_eng.htmIn special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.


Installation information

If you have customizations for one or more of the methods or the tables that are affected by this hotfix, you must apply these changes in a test environment before you apply the hotfix in a production environment.
For more information about how to install this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:

893082 How to install a Microsoft Dynamics AX hotfix

Prerequisites

You must have one of the following products installed to apply this hotfix:

  • Microsoft Dynamics AX 2012 R3

  • Microsoft Dynamics AX 2009 SP1

Restart requirement

You must restart the Application Object Server (AOS) service after you apply the hotfix.

File information

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×