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.
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 template | ISO message identifier |
|---|---|
| CustomerCreditTransferInitiationV09 | pain.001.001.09 |
| CustomerDirectDebitInitiationV08 | pain.008.001.08 |
| CustomerDirectDebitInitiationV02 | pain.008.001.02 |
| CustomerCreditTransferInitiationV03 | pain.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 detail | Documented value |
|---|---|
| Bundle name | Electronic Bank Payments |
| Bundle ID | 533070 |
| Location | Production |
| Availability | Public |
| License Client prerequisite | NetSuite SuiteApps License Client, bundle ID 116144, before purchasing an active Electronic Bank Payments license |
| New-installation initialization | Initialize 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?
- Open Setup > Localization Assistant > Payment Formats.
- Select Country. The list contains countries according to the available payment formats.
- Use Template Type to filter templates, or search for a template name in Search by Keyword.
- Review the template’s installation status and choose the required action.
The page exposes these columns and actions:
| Page element | Meaning or behavior |
|---|---|
| Payment Formats | Shows payment format types and available templates for the selected country. |
| Status: Installed | The template is already installed in the account. |
| Status: Not Installed | The template has not been installed in the account. |
| Actions: Install | Installs the payment format template. |
| Actions: Reinstall | Reinstalls the payment format template. |
| Actions: Customize | Creates a new template using the base template. |
| Country | Identifies the countries associated with the templates. |
| Help Topics | Provides 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.
| Country | Available EFT formats |
|---|---|
| Austria | SEPA 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 |
| Belgium | SEPA Credit Transfer (Belgium) v2019; SEPA Credit Transfer (HSBC) v2019; SEPA Credit Transfer (Germany) v2019; Non SEPA Credit Transfer (Germany) v2019 |
| Czechia | SEPA Credit Transfer (HSBC) v2019 |
| Denmark | Nordea P27 Credit Transfer |
| Finland | Nordea P27 Credit Transfer |
| France | SEPA Credit Transfer (France) v2019; SEPA Credit Transfer (HSBC) v2019; FR International ISO 20022 v2019 |
| Germany | SEPA 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 |
| Ireland | SEPA Credit Transfer (Bank of Ireland) v2019; SEPA Credit Transfer (HSBC) v2019 |
| Italy | SEPA Credit Transfer (HSBC) v2019 |
| Jersey | SEPA Credit Transfer (HSBC) v2019 |
| Luxembourg | SEPA Credit Transfer (Luxembourg) v2019; SEPA Credit Transfer (HSBC) v2019 |
| Netherlands | SEPA 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 |
| Norway | Nordea P27 Credit Transfer |
| Singapore | Citibank 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 |
| Spain | SEPA Credit Transfer (HSBC) v2019 |
| Sweden | Nordea P27 Credit Transfer; SEPA Credit Transfer (SEB) v2019 |
| United Kingdom | SEPA 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 element | XML tag | Mapping detail shown |
|---|---|---|
| GroupHeader | GrpHdr | Parent element. |
| MessageIdentification | MsgId | Uses pfa.id with setMaxLength and argument 35. |
| CreationDateTime | CreDtTm | Formats the file creation timestamp as date and time, separated by T. |
| NumberOfTransactions | NbOfTxs | References the total-transactions field with setMaxLength and argument 15; the expression is incomplete. |
| ControlSum | CtrlSum | Uses formatAmount with computeTotalAmount. |
| InitiatingParty | InitgPty | Parent element. |
| Name | Nm | References the bank statement name with setMaxLength and argument 140. |
| Country | Ctry | References the bank country field. |
| OrganisationIdentification | OrgId | Parent element. |
| AnyBIC | Incomplete | The excerpt ends during the XML tag; no complete mapping is supplied. |
Two complete expressions shown in the source are:
${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?
What needs to be installed or initialized before I manage payment formats?
How do OneWorld subsidiary country restrictions affect EFT and Direct Debit formats?
Can I use the default ISO mapping values as a complete payment template?
Weekly Update History (1)
Updated Managing Payment Formats in Localization Assistant SuiteApp to add new countries and their payment templates.
View Oracle DocsWas this article helpful?
More in Banking
- Enriched Bank Data for Improved Transaction Matching in NetSuite
Updated for NetSuite 2026.1: Enriched Bank Data feature enhances transaction matching accuracy using generative AI.
- NetSuite Match Bank Data: Match, Clear and Reconcile
Use Match Bank Data to review bank lines, resolve exceptions and submit transactions before completing a NetSuite statement reconciliation.
- Testing Versapay Payment Gateway Connection in NetSuite Pay
Connect and test Versapay Payment Gateway for NetSuite Pay, verifying configurations safely without financial risk.
- Australia Bank Feeds SuiteApp Enhancements for NetSuite 3.0.0
NetSuite 2026.2 adds ANZ reporting updates, Singapore billing validations and GST InvoiceNow access, and UAE electronic invoicing.
Also from NetSuite 2026.2
- Bank Matching and Reconciliation Enhancements in NetSuite 2026.2
Bank matching and reconciliation pages in NetSuite 2026.2 receive critical UI enhancements for improved transaction management.
- System Notes Enhancement for Reconciliation in NetSuite 2026.2
System notes enhancement tracks GL transaction events in NetSuite 2026.2, improving reconciliation auditing and review.
- SuiteCloud CLI License Acceptance for Automation
Set SUITECLOUD_CLI_ACCEPT_LICENSE=true to suppress the SuiteCloud CLI license prompt during scripted npm installation.
- NetSuite Next: Readiness, Preview, and Ask Oracle
Eligible administrators can request a NetSuite Next preview, set up Ask Oracle, and prepare data, roles, customizations, and navigation.
Advertising
Reach Banking Professionals
Put your product in front of NetSuite experts who work with Banking every day.
Sponsor This Category