NetSuite Payment Formats and ISO 20022 Templates

Manage payment formats through Localization Assistant: ISO 20022 base templates, required SuiteApps, country availability, and default mapping checks.

·7 min read·10 views·NetSuite 2026.2·View Oracle Docs

Localization Assistant lets you install country payment formats and create templates from four ISO 20022 bases applicable to all countries. Electronic Bank Payments must be installed first, but the corresponding country localization SuiteApp is not required. Check account restrictions, installation status, and default mappings before using a template.

What Does Payment Format Management Cover?

Localization Assistant supports two distinct tasks: installing an available country payment template and creating a new template from a base version. Both are available through Setup > Localization Assistant > Payment Formats. You do not need the corresponding country localization SuiteApp to use its templates from this page.

The documentation describes these capabilities but does not identify a release in which they were introduced. This is a guide to the documented workflow, not evidence of a new release feature.

For related country-specific context, see Netherlands Localization SuiteApp enhancements. Keep that broader localization scope separate from the payment template prerequisites described here.

Which ISO 20022 Templates Can You Customize?

The Payment Formats page provides Customize links for creating new payment format templates from base templates. The documentation lists four ISO formats as applicable to all countries:

Base templateISO message identifier
CustomerCreditTransferInitiationV09pain.001.001.09
CustomerDirectDebitInitiationV08pain.008.001.08
CustomerDirectDebitInitiationV02pain.008.001.02
CustomerCreditTransferInitiationV03pain.001.001.03

The CustomerCreditTransferInitiation message requests movement of funds from a debtor account to a creditor. The initiating party sends it to a forwarding agent or debtor agent.

Implementation check: Confirm the required message identifier with the receiving bank before choosing a base template. Treat availability for customization as a starting point for that review, not as bank acceptance. Also review the account and licensing considerations below rather than interpreting “all countries” as an exemption from those restrictions.

What Must Be Installed Before Managing Formats?

You must install the Electronic Bank Payments SuiteApp before managing payment formats. The installation documentation covers sending payments to vendors and employees and receiving customer payments within the company’s country of operations.

Installation detailDocumented value
Bundle nameElectronic Bank Payments
Bundle ID533070
LocationProduction
AvailabilityPublic
License Client prerequisiteNetSuite SuiteApps License Client, bundle ID 116144, before purchasing an active Electronic Bank Payments license
New-installation initializationInitialize Electronic Payments Preference at Payments > Setup > Electronic Payments Preference

Electronic Bank Payments is a managed bundle that updates automatically in production. Fixes and enhancements become available after the bundle is updated in the production account. Sandbox installations require manual updates to obtain the latest version. Before comparing customization behavior across environments, check whether the Sandbox installation has been updated.

OneWorld limitation: Available EFT and Direct Debit formats are limited according to the parent subsidiary’s country. Global payments support may also incur additional charges. Contact your NetSuite account representative about enabling payments between banks in different countries.

Plan these as separate checks: the required bundle, preference initialization for new installations, available formats, and licensing. For another localization planning reference, see Chile localization help and license setup; use the Electronic Bank Payments requirements above for this workflow.

How Do You Find and Manage a Payment Template?

  1. Open Setup > Localization Assistant > Payment Formats.
  2. Select Country. The list contains countries according to the available payment formats.
  3. Use Template Type to filter templates, or search for a template name in Search by Keyword.
  4. Review the template’s installation status and choose the required action.

The page exposes these columns and actions:

Page elementMeaning or behavior
Payment FormatsShows payment format types and available templates for the selected country.
Status: InstalledThe template is already installed in the account.
Status: Not InstalledThe template has not been installed in the account.
Actions: InstallInstalls the payment format template.
Actions: ReinstallReinstalls the payment format template.
Actions: CustomizeCreates a new template using the base template.
CountryIdentifies the countries associated with the templates.
Help TopicsProvides an Admin Documentation link to payment file format help.

Before selecting an action, establish whether the task is to install a supplied template, reinstall it, or create a new template from its base. The source does not explain whether reinstallation preserves modifications or specify the permissions needed for these actions. Resolve those questions before changing a production configuration.

Which Country EFT Formats Are Listed?

Every country-specific entry below lists Electronic Bank Payments as its required SuiteApp. Retain the version suffixes shown when identifying a format.

CountryAvailable EFT formats
AustriaSEPA Credit Transfer (ABN AMRO) v2019; SEPA Credit Transfer (Austria) v2019; SEPA Credit Transfer (HSBC) v2019; SEPA Credit Transfer (Germany) v2019; Non SEPA Credit Transfer (Germany) v2019
BelgiumSEPA Credit Transfer (Belgium) v2019; SEPA Credit Transfer (HSBC) v2019; SEPA Credit Transfer (Germany) v2019; Non SEPA Credit Transfer (Germany) v2019
CzechiaSEPA Credit Transfer (HSBC) v2019
DenmarkNordea P27 Credit Transfer
FinlandNordea P27 Credit Transfer
FranceSEPA Credit Transfer (France) v2019; SEPA Credit Transfer (HSBC) v2019; FR International ISO 20022 v2019
GermanySEPA Credit Transfer (ABN AMRO) v2019; SEPA Credit Transfer (Austria) v2019; SEPA Credit Transfer (HSBC) v2019; SEPA Credit Transfer (Germany) v2019; Non SEPA Credit Transfer (Germany) v2019
IrelandSEPA Credit Transfer (Bank of Ireland) v2019; SEPA Credit Transfer (HSBC) v2019
ItalySEPA Credit Transfer (HSBC) v2019
JerseySEPA Credit Transfer (HSBC) v2019
LuxembourgSEPA Credit Transfer (Luxembourg) v2019; SEPA Credit Transfer (HSBC) v2019
NetherlandsSEPA Credit Transfer (Netherlands) v2019; SEPA Credit Transfer (HSBC) v2019; SEPA Credit Transfer (Germany) v2019; Non SEPA Credit Transfer (Germany) v2019; SEPA Credit Transfer (ABN AMRO) v2019
NorwayNordea P27 Credit Transfer
SingaporeCitibank Singapore XML Domestic Transfer v2019; Citibank Singapore XML GIRO v2019; Citibank Singapore XML International Transfer v2019; HSBC Singapore Low and High Value Domestic Payments v2019
SpainSEPA Credit Transfer (HSBC) v2019
SwedenNordea P27 Credit Transfer; SEPA Credit Transfer (SEB) v2019
United KingdomSEPA Credit Transfer (HSBC) v2019

Several country entries include templates whose names reference another country. For example, Austria includes SEPA Credit Transfer (Germany) v2019. Use the documented country association when building a shortlist, then confirm the bank’s requirements rather than selecting or rejecting a template solely by its name.

How Do Default ISO Mappings Work?

Default mapping values are editable references drawn from previous templates. Selecting a tag with a tick mark displays its default mapping and provides guidance for using FreeMarker functions. To remove an unwanted default, clear the tag’s Mapped Value text box and save. In the documentation tables, bold message elements identify parent tags and their hierarchy positions.

The supplied CustomerCreditTransferInitiationV09 excerpt includes these elements:

Message elementXML tagMapping detail shown
GroupHeaderGrpHdrParent element.
MessageIdentificationMsgIdUses pfa.id with setMaxLength and argument 35.
CreationDateTimeCreDtTmFormats the file creation timestamp as date and time, separated by T.
NumberOfTransactionsNbOfTxsReferences the total-transactions field with setMaxLength and argument 15; the expression is incomplete.
ControlSumCtrlSumUses formatAmount with computeTotalAmount.
InitiatingPartyInitgPtyParent element.
NameNmReferences the bank statement name with setMaxLength and argument 140.
CountryCtryReferences the bank country field.
OrganisationIdentificationOrgIdParent element.
AnyBICIncompleteThe excerpt ends during the XML tag; no complete mapping is supplied.

Two complete expressions shown in the source are:

text
${setMaxLength(pfa.id,35)}
${formatAmount(computeTotalAmount(payments,false),"decLessThan1")}

These are individual mapping examples, not a complete payment template. Do not reconstruct a working template from the partial excerpt: the transaction-count expression is incomplete, the timestamp entry has trailing punctuation, and the AnyBIC entry is truncated.

For validation, compare transaction counts and control sums with the intended payment set, inspect timestamp formatting, and confirm initiating-party details. Review the complete mappings before testing generated files rather than assuming the reference defaults suit the intended payment workflow unchanged.

Who This Affects

  • Administrators: Check prerequisite bundles, new-installation preference initialization, and production versus Sandbox update readiness.
  • Payment and treasury teams: Review country format availability and confirm the receiving bank’s required message identifier.
  • Template maintainers: Review ISO message versions, editable default mappings, and the completeness of expressions used in templates.
  • OneWorld administrators: Check parent-subsidiary country restrictions and discuss cross-country payment licensing before rollout.

Key Takeaways

  • Four ISO 20022 base templates are documented for customization across all countries.
  • Electronic Bank Payments is required; the corresponding country localization SuiteApp is not required to use its templates from this page.
  • Customize creates a new template from a base; Install and Reinstall are separate actions.
  • Review OneWorld restrictions, licensing, Sandbox updates, and default mappings before deployment.
  • The source documents functionality but does not establish a NetSuite 2026.2 introduction.

Frequently Asked Questions (4)

Do I need the country localization SuiteApp to install or customize a country payment format?
No. You need the Electronic Bank Payments SuiteApp, but the corresponding country localization SuiteApp is not required to use payment templates from Setup > Localization Assistant > Payment Formats. The countries shown depend on available payment formats.
What needs to be installed or initialized before I manage payment formats?
Install the Electronic Bank Payments SuiteApp first. For a new installation, initialize Electronic Payments Preference at Payments > Setup > Electronic Payments Preference. The documentation also identifies the NetSuite SuiteApps License Client as a prerequisite before purchasing an active Electronic Bank Payments license.
How do OneWorld subsidiary country restrictions affect EFT and Direct Debit formats?
In OneWorld, available EFT and Direct Debit formats are limited according to the parent subsidiary’s country. Global payments support may incur additional charges; contact your NetSuite account representative about enabling payments between banks in different countries.
Can I use the default ISO mapping values as a complete payment template?
No. Default mappings are editable references drawn from previous templates, and the documented CustomerCreditTransferInitiationV09 excerpt is incomplete. Review complete mappings and validate transaction counts, control sums, timestamp formatting, and initiating-party details before testing generated files.

Weekly Update History (1)

Country-Specific Featuresupdated

Updated Managing Payment Formats in Localization Assistant SuiteApp to add new countries and their payment templates.

View Oracle Docs
Source: Managing Payment Formats — Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in Banking

View all Banking articles →

Also from NetSuite 2026.2

View all NetSuite 2026.2 changes →