FIX: "The company ext does not exist" error when you try to create a SEPA payment file that uses an ISO20022 export format in Microsoft Dynamics AX 2009

This article applies to Microsoft Dynamics AX 2009 for all regions.


Consider the following scenario:
  • You have update 2674468  or update 2769783 installed in Microsoft Dynamics AX 2009.
  • You create a Single Euro Payments Area (SEPA) payment file.
  • You use an ISO20022 CredTrans export format for the payment file.

In this scenario, the payment file is not created and you receive the following error message:

The company ext does not exist.


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, go to the following Microsoft website:You can also contact technical support for Microsoft Dynamics by telephone by using these links for country specific telephone numbers. To do this, go to one of the following Microsoft websites:

PartnersCustomersIn 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

See How to install a Microsoft Dynamics AX hotfix for information about how to install this hotfix.


You must have Microsoft Dynamics AX 2009 Service Pack 1 installed to apply this hotfix.

Restart requirement

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

Objects that are affected

This hotfix affects the following objects:

\Classes\Vendoutpaymrecord_iso20022_gen_be.xpo, method: xmlcdtr()
\Classes\Vendoutpaymrecord_iso20022_gen_be.xpo, method: xmlrmtinf()
\Classes\Vendoutpaymrecord_sepa_be.xpo, method: xmlcdtr()
\Classes\Vendoutpaymrecord_sepa_be.xpo, method: xmlrmtinf()
\Classes\Vendoutpaymrecord_sepa03_be.xpo, method: xmlcdtr()
\Classes\Vendoutpaymrecord_sepa03_be.xpo, method: xmlrmtinf()

Validation of the application hotfix installation

To validate the installation of the application hotfix, open the SysHotfixManifest class in the Application Object Tree (AOT). Then, verify that there is a method name that contains the Knowledge Base (KB) article number of the installed hotfix. Additionally, you can cross-check the affected objects by viewing the KBxxxxxx.txt file against the objects in the AOT. Therefore, you can make sure that the objects are changed correctly in the SYP layer or in the GLP layer.

Note KBxxxxxx.txt is a placeholder for the KB article number of the installed hotfix.
File information


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Article ID: 2801397 - Last Review: 17 ກ.ພ. 2017 - Revision: 2

Microsoft Dynamics AX 2009