Title: How to add 'Payment ID' field from Vendors/Suppliers "Payment" section to 'ISO20022 Credit transfer (FI)' format
Description: This guiding document is an example of how you can add the value of 'VendPaymentID' node to be fetched with Vendors/Suppliers "Payment" section > Payment ID field using 'ISO20022 Credit transfer (FI)'
How-to-do steps:
[1] Go to Accounts payable > Vendors > All vendors > "Payment" section > and verify if "Payment ID" field is filled in as needed.
Please note that data source for this field is stored into VendTable AXDB table on data field name: PaymID.
[2] Go to Accounts payable > Payments > Vendor payment journal > New > create new journal line entry > then click on "Payment" tab where we can see that "Payment ID" is automatically filled in with the value set on previous step onto Vendor | "Payment" section.
This "Payment ID" will be the field read while the system is generating the payment xml file.
Please note that the data source for this "Payment ID" field is LedgerJournalTrans AXDB table with data field name: PaymID.
[3] From Electronic Reporting framework > Configuration providers > select Microsoft repositories > Global > Open
[4] Select and import latest version of "ISO20022 Credit transfer (FI)" format
[5] From Electronic Reporting framework > Reporting configurations > select 'Payment model' config. and click on 'Create configuration' option > choose 'Derive from Name: Payment model, Microsoft' > add name "derived PaymentModelFI" > select 'Create configuration'.
[6] Select the "derived PaymentModelFI" and click designer, then expand Customer Direct Debit Initiation(CustomerDirectDebitInitiation) | (*)Payments | (*)Debtor Account(DebtorAccount) and click on 'Identification' or any other existing element > and press + New > "Sibling of an active node" option > add 'VendPaymentID' under Name and Label > and save the changes. Afterwards select the "derived PaymentModelFI" we just saved and change its status to completed.
[7] Select 'Payment model mapping to destination ISO20022' config, click on 'Create configuration' option > choose 'Derive from Name: Payment model mapping to destination ISO20022, Microsoft' > add name "derived PaymentmodelmappingtodestinationFI" > Target model: derived PaymentModelFI > 'Create configuration'.
[8] Select 'Payment model mapping 1611', click on 'Create configuration' option > choose 'Derive from Name: Payment model mapping 1611, Microsoft' > add name " derived Payment model mapping 1611 FI" > Target model: derived PaymentModelFI > 'Create configuration'.
[9] Open in designer the "derived Payment model mapping 1611 FI" and open it in Designer > CustomerCreditTransferInitiation > and from Data source select "Transactions: Table 'LedgerJournalTrans' records" > Payment ID(PaymId) field and bind it with Data model > Payments > VendPaymentID field.
Afterwards, please save the changes and close the window. Then mark "derived Payment model mapping 1611 FI" as being "Default for model mapping" and change the status to completed.
[10] Select the standard "ISO20022 Credit transfer (FI)" config, click on 'Create configuration' option > choose 'Derive from Name: ISO20022 Credit transfer (FI), Microsoft' > add name "derived ISO20022CT FI" > Target model: 'derived PaymentModelFI' > 'Create configuration'.
[11] Open "derived ISO20022CT FI" in designer and bind the desired xml element from Format designer with VendPaymentID element we added and that is on Mapping under model > Payments > DebtorAccount > VendPaymentID.
Please note that in this example, on Format designer we created the VendPaymentID and PaymentID XML elements, and then PaymentID string to bind it with the same VendPaymentID element from model.Payments.DebtorAccount.VendPaymentID.
Save the changes and complete the status of "derived ISO20022CT FI" format.
[12] From Accounts payable > Payments > Vendor payment journal > generate the payment. When we check the xml report file, the Vendor | Payment ID value is fetched as expected under PaymentID tag:
*This post is locked for comments