Configure ISO Code Sets Across Multiple Dimensions
- Configure bank integrations for these ISO 20022 templates:
- WPN - ISO 20022 V2 Direct Debit (Enhanced Performance)
- WPN - ISO 20022 V3 (Enhanced Performance)
- Security:Set Up: Payment Configurationdomain in the Banking and Settlement functional area.
You can define ISO 20022 code set values across multiple payment dimensions for these integration attributes:
- Category Purpose
- Charge Bearer
- Local Instrument
- Payment Purpose
This enables you to centralize payment configurations and reduce the number of integrations for outputting data into payment files.
Edit your integration system to remove any existing configurations for the integration attributes so that they don't override the code set values.
- Access theCreate Payment Configurationtask.
- As you complete the task, consider:
Option Description Integration AttributeSelect the attribute for the payment configuration.Integration TemplateSelect the ISO 20022 template that's applicable for your configuration.ContextSelect to output the code assignments at the payment or payment message group level in the payment file. - As you complete theLines, consider:
Option Description Schema LocationThe XML tags in the payment file where Workday outputs the codes. Select:- Codewhen you're using the ISO standard codes.
- Proprietarywhen you're using any non-ISO standard code.
Return DataThe integration attribute value that's output in the payment file when Workday evaluates the associated rules.Condition RulesThe rules that you configure to output the return data. - Define each condition for the payment configuration rules:
Option Description Source External Field or Condition RuleThe source data for which you’re defining a rule condition. You can select from delivered Workday sources, or condition rules and custom worktags that you've already defined.Relational OperatorSelect how you want to compare the source data to the next value in your condition. The options depend on the data type of the source.Comparison TypeSpecify whether the source is to be compared to another field or to a value that you enter in theComparison Valuecolumn.Comparison ValueEither select a comparison field or enter the value to be compared to the source.OrderWorkday evaluates conditions in the order that you specify.( )Use parentheses to group one or more conditions together.Example:, to say(a and b) or cuse the opening parenthesis at the beginning of statementa, anAndbefore statementb, a closing parenthesis at the end of statementb, and anOrat the beginning of statementc.
During settlement, Workday evaluates the dynamic rules you configured for the integration attributes and applies the values from the applicable rule to your payment files.
You set up a configuration to output charge bearer codes in 2 separate payment files that you're sending to banks in the U.S. and SEPA countries:
Return Data | Condition Rule |
|---|---|
Charge Bearer / DEBT
| DEBT-US
|
Charge Bearer / SHAR
| SHAR-SEPA
|
You define these conditions for each rule:
Condition Rule | Source External Field or Condition Rule | Relational Operator | Comparison Type | Comparison Value |
|---|---|---|---|---|
DEBT-US
| Payment to Country/Settlement Bank Account Country
| in the selection list
| Value specified in this filter
| U.S.
|
SHAR-SEPA
| Payment to Country/Settlement Bank Account Country
| in the selection list
| Value specified in this filter
| Austria Belgium Bulgaria Croatia Cyprus |
You create a settlement run with supplier invoice payments to the U.S. and a SEPA bank location. When settlement processing completes, Workday generates 2 payment files and adds each of these charge bearer codes to the applicable file:
- DEBTfor the U.S. payment
- SHARfor the SEPA payment
To view your completed payment configurations, use the
View Payment Configurations
report. You can also use the report to add or maintain payment configurations.