Skip to main content
Question

Unable to bypass Payment Reference validation when Supplier Invoice Validation Method = Used


Forum|alt.badge.img+1

Our customer is facing an issue in IFS Applications 10 related to Payment Reference validation when generating ISO20022 payment files.

For ISO20022 payment files, they need the Payment Reference (not the Invoice Number) to be populated as remittance information.
To achieve this, they have set the following:
Company → Invoice → Supplier Invoice Validation Method = Used


However, Once Supplier Invoice Validation Method is set to Used, IFS enforces validation on the Payment Reference field in the Manual Supplier Invoice page as the validation allows only numeric values.
In order to bypass this validation, they have also enabled “Do Not Validate Payment Reference" option at the supplier level > Invoice > General. But it does not seem to work.


Is there any workaround or configuration that allows alphanumeric payment references without disabling the company‑level validation?

2 replies

piswpl
Hero (Partner)
Forum|alt.badge.img+6
  • Hero (Partner)
  • May 1, 2026

Have you tried using Mandatory Payment Reference on the suppliers instead? The payment reference validation uses certain algorithms and is reserved for certain countries only. That is why it requires digits only as these are numerical payment references.


uaksoy
Sidekick (Customer)
Forum|alt.badge.img+5
  • Sidekick (Customer)
  • October 21, 2026

Hi,

We have experienced the same issue with our Austrian company. I discussed  it with the Bank, and they confirmed that they expect 2 alternative format for RmtInf as shown in options 1 and 2 below.

Structured payment ref

If you pay each invoice separately using its payment reference then you have to use option 1 and option 3.

For IFS to generate option 1,the following setup is required:

  • Company>invoice>general ‘supp inv validation method’ = Used
  • Enter payment reference in the relevant field on the manual supplier invoice  

If the payment reference field is left empty, IFS creates option 3 using invoice no instead of payment reference, which  our bank does not accept this format.

I still don’t know how the payment reference validation logic works in Austria. In our Norwegian Company, the payment reference works fine based on KID number logic.

Unstructured remittance information

If the bank accepts option 2, the set up is simpler. You don’t have to change supp inv validation method setting at company level. Instead you only need to enable Unstructured payments only at payment institute or supplier level.

The disadvantage is that if a supplier has multiple invoices, IFS combines them into a single payment rather than paying each invoice separately.

We’ll proceed with option 2 by enabling unstructured payments at payment institute level.

 

Option 1:

<RmtInf>
<Strd>
<CdtrRefInf>
<Tp>
<CdOrPrtry>
<Cd>SCOR</Cd>
</CdOrPrtry>
</Tp>
<Ref>123456</Ref>
</CdtrRefInf>
</Strd>
</RmtInf>


Option 2:


<RmtInf>
<Ustrd>Test invoice no</Ustrd>
</RmtInf>

Option 3:

<RmtInf>
<Strd>
<RfrdDocInf>
<Tp>
<CdOrPrtry>
<Cd>CINV</Cd>
</CdOrPrtry>
</Tp>
<Nb>000TESTINGG</Nb>
</RfrdDocInf>
<RfrdDocAmt>
<RmtdAmt Ccy="EUR">34</RmtdAmt>
</RfrdDocAmt>
</Strd>
</RmtInf>