Skip to content
IFS Wire

Community · Question

ISO20022 remittance info with alphanumeric payment references in IFS Applications 10: what the validation allows and the unstructured option

Asked by IFS Wire DeskEditorial · 6 Nov 2026 · 0 views

Type:
General
Product:
IFS Applications
Version:
10

Sourced from IFS Community · original thread · piswpl

0

In IFS Applications 10, a company needs the supplier invoice's Payment Reference, rather than the invoice number, to appear in the remittance information of the ISO20022 payment file. To achieve this, Company > Invoice > Supplier Invoice Validation Method was set to Used. After that, the Payment Reference field on the Manual Supplier Invoice page is validated and accepts numeric values only. Enabling "Do Not Validate Payment Reference" on the supplier (Invoice > General) does not appear to change this. Is there a way to allow alphanumeric payment references while keeping the company-level validation?

Technical details Product: IFS Applications 10. Area: Financials > Supplier Invoices, Manual Supplier Invoice, External Supplier Invoice, ISO20022 payment file. Settings: Company > Invoice > Supplier Invoice Validation Method ("Supp Inv Validation Method") = Used; supplier Invoice > General "Do Not Validate Payment Reference"; "Mandatory Payment Reference"; "Unstructured payments only" (payment institute or supplier level). XML elements: RmtInf, Strd, CdtrRefInf, SCOR, Ustrd, RfrdDocInf, CINV, RfrdDocAmt, RmtdAmt. Country logic mentioned: KID (Norway), Austria.

Any attachments are visible to signed-in members.

1 answer

0

✓ Accepted answer

No direct bypass was confirmed. Two community members described what drives the behaviour and the options available.

Why references are numeric: payment reference validation uses check algorithms reserved for certain countries, which is why it requires digits only. One member suggested trying "Mandatory Payment Reference" on the suppliers instead.

What the bank may expect in RmtInf (from a member who hit the same issue for an Austrian company):

  1. Structured SCOR creditor reference: <RmtInf><Strd><CdtrRefInf><Tp><CdOrPrtry><Cd>SCOR</Cd></CdOrPrtry></Tp><Ref>123456</Ref></CdtrRefInf></Strd></RmtInf>
  2. Unstructured text: <RmtInf><Ustrd>Test invoice no</Ustrd></RmtInf>
  3. What IFS generates when the payment reference is empty, using the invoice number (their bank rejected this): <RmtInf><Strd><RfrdDocInf><Tp><CdOrPrtry><Cd>CINV</Cd></CdOrPrtry></Tp><Nb>000TESTINGG</Nb></RfrdDocInf><RfrdDocAmt><RmtdAmt Ccy="EUR">34</RmtdAmt></RfrdDocAmt></Strd></RmtInf>

Options:

  • To get format 1 (pay each invoice separately by its reference): set Company > Invoice > General, "Supp Inv Validation Method" = Used, and enter the payment reference in the field on the manual supplier invoice. The reference must then pass the numeric validation.
  • If the bank accepts format 2: leave the company setting unchanged and enable "Unstructured payments only" at payment institute or supplier level. The trade-off is that several invoices for the same supplier are combined into one payment instead of being paid separately. That member chose this option at payment institute level.

Open point: how the validation logic applies to Austria remained unclear in the thread; the same member reported that in a Norwegian company the payment reference works as expected using KID number logic.

Status: suggestions and one member's implemented choice; the original poster had not confirmed a solution.

Prerequisites and limitations Requires agreement with the bank on which RmtInf format it accepts. "Unstructured payments only" combines multiple invoices per supplier into one payment. Numeric validation is tied to country-specific algorithms; behaviour for Austria was not resolved. No confirmed way to keep company validation and allow alphanumeric references.

Sourced from IFS Community · original thread · piswpl

Answered by IFS Wire DeskEditorial · 6 Nov 2026