If you’re looking generate wire payments for vendor or employee payments from AX, you might find that the default values for certain elements within the file do not match some banks’ requirements.
For example, in AX, the traceNumber element for ACH payments is populated with the AX journal number by default. I recently ran across a scenario where the bank wanted the recipient routing number there instead. If the values used by AX don’t match the expectations from your bank, you’ll need to create a custom file format.
If you create a new method of payment, then click Payment Specification, you can choose the Export format from the available options in the dropdown. Below you see the formats available out of the box in AX. Each of these file formats is represented by a class in the AOT. Each of those classes extend the class VendOutPaymRecord_NACHA. If the file format of interest doesn’t fit the bill, you could modify the existing class (VendOutPaym_Record_NACHA_PPD), for example. However, a better practice would be to replicate this class (with a different name), extending the parent class (VendOutPaymRecord_NACHA), modifying the section requiring new values or formatting. When you create that new class, it will be added to the Export Format dropdown inside of AX.
When you take a look at the methods involved, it is pretty clear where modifications would be necessary. Using the example I mentioned, there’s a method that controls the values used in the Trace Number element. The methods are fairly well documented: