Mapping Files
Skillset Requirement
Ultracs Operator
This section defines the various mapping files to enable HaaS Connector for Universe (HCU) to translate from customer specific definitions within Ultracs to the Data Adapter requirements of the HaaS environment.
These mapping files are essential for establishing consent arrangements and ensuring that individual and organisational relationships are accurately represented.
Transaction Type Mapping
The transaction type mapping file is used to correlate transactions within Ultracs to the transaction types used within the CDR.
Fields used in this file are as follows:
- Code: Ultracs Transaction Code
- Description: Description of the Ultracs Transaction Code
- CDR Type: The CDR Type to map, current values are
DIRECT_DEBIT: Direct Debit TransactionFEE: A bank fee or chargeINTEREST_CHARGED: Interest charged to the accountINTEREST_PAID: Interest paid into the accountOTHER: Other transaction typePAYMENT: A payment to a merchantTRANSFER_INCOMING: A bank transfer received into the accountTRANSFER_OUTGOING: A bank transfer sent out of the account
- Details Type: For transactions containing more information this specifies the details type. Valid values are
BPAY: A payment sent via BPAY networkCREDIT_CARD: A credit card transaction (contains merchant category code)X2P101: A payment sent over the New Payments Platform (NPP) using X2P1.01 format
- Prepend Description: Whether the
referenceused when presenting the data should be prepended with the Description field.
Account Relationship Mapping
The account relationship mapping file is used to map individual account relationship codes within Ultracs to CDR specific nomenclature.
Fields used in this file are as follows:
- Relationship: Ultracs Account Relationship
- CDR Individual Mapping: The nature of the relationship if the account is individually owned. Currently valid values are
OWNER: This user has full authority to be able to share this account. On individual joint accounts, this allows the user to participate in Disclosure Options Management Service (DOMS) requests to vote on changing the disclosure status of the account.SECONDARY_USER: This is a secondary user on individual or individual joint accounts that can share the account but not participate in DOMS.POWER_OF_ATTORNEY: This user has a power of attorney relationship over the individual primary account owner and can share the account.NONE: No relationship relevant for CDR.
- CDR Non Individual Mapping: The nature of the relationship if the account is non-individually owned. Currently valid values are
OWNER: This user has full authority to be able to share this account.NOMINATED_REPRESENTATIVE: A user that has authority to share this account of a non-individual consumer. Does not apply to personal accounts.NONE: No relationship relevant for CDR.
- Principal Type: Relationships which are the primary account owner must have this field. Currently valid values are
INDIVIDUAL: Designates that the account is individually owned. This implies that the account is an individual/consumer account.NON_INDIVIDUAL: Designates that the account is non-individually owned. This implies that the account is a non-individual/business account.
- Empty. Leave this field empty if the relationship code does not refer to the primary account owner.