Party To Account File Upload

1.28 Party To Account File Upload

This topics describes the information to perform the bulk upload for the Party-to-Account relationships for Retail and SMB parties in common core.

This process ensures proper account ownership, role assignment, and statement preferences, while providing flexible referential validation against migration datasets.

Note: OB Party expects data to be provided strictly in the required file format for additions, replacements, or removals. The system will not perform any data transformation, derivation, cleansing, or enrichment. All data quality checks must be completed prior to submitting the data to OB Party.

Note: Any Card Numbers should not be directly provided in the Upload File as OB Party will not store the Card Numbers directly.

File Template:

This process allows user to add, replace or remove records in Party To Account data segment.

File Type Supported - csv

File Naming Convention - ObpyPtyToAct_<UniqueName>.csv

Note:

Replace the <UniqueName> for each file upload.

Note:

The fields marked as Required are mandatory.

Table 1-38 File Template

UI FIELD NAME	UPLOAD FIELD NAME	DESCRIPTION	FIELD (MANDATORY/OPTIONAL/CONDITIONAL)
NA	PTY_ACC_REL_OPERATION	Operation to be performed on a Party to Account Relationship such as "add", "replace" or "remove"	Mandatory
CIF ID	PTY_ACC_REL_CIF_ID	CIF ID if the party holding and account with financial institution	Mandatory
Account Number	PTY_ACC_REL_ACCOUNT_NUMBER	Account number related to CID ID	Mandatory
Account Type	PTY_ACC_REL_ACCOUNT_TYPE	Type of account	Optional
Party Relationship	PTY_ACC_REL_PARTY_RELATIONSHIP	Relationship of party with account (NFCU "Relationship Codes")	Mandatory
Party Role	PTY_ACC_REL_PARTY_ROLE	Role of party in account (NFCU "Relationship Key")	Mandatory
Ownership Type	PTY_ACC_REL_OWNERSHIP_TYPE	Ownership of party on account	Optional
Responsibility Type	PTY_ACC_REL_RESPONSIBILITY_TYPE	Responsibility type of the party in account	Optional
Application Type	PTY_ACC_REL_APPLICATION_TYPE	Application of account origination	Mandatory
Product Group	PTY_ACC_REL_PRODUCT_GROUP	Product group of account	Mandatory
Combined Statement	PTY_ACC_REL_COMBINE_STATEMENT	Flag to identify, if combined statement is required for the party	Mandatoty (true/false)
Nick Name	PTY_ACC_REL_NICK_NAME	Party to Account Relationship Nick Name	Optional
Start Date	PTY_ACC_REL_START_DATE	Party to Account Relationship start date	Mandatory
End Date	PTY_ACC_REL_END_DATE	Party to Account Relationship end date	Optional
Nick Name 2	PTY_ACC_REL_NICK_NAME_2	Party to Account Relationship Nick Name	Optional
Percentage of Owner(%)	PTY_ACC_REL_PERCENT_OWNER	Percentage Ownership	Optional
Title Position	PTY_ACC_REL_LEGAL_POSITION	Legal title position	Optional

Target Persistence Mapping:

Table 1-39 Target Persistence Mapping

UPLOAD FIELD NAME	TABLE	TABLE COLUMN	HISTORY TABLE
PTY_ACC_REL_OPERATION	NA	NA	NA
PTY_ACC_REL_CIF_ID	OBPY_TW_PARTY_ACCOUNT_RELATIONSHIP	EXTERNAL_CUSTOMER_NO	OBPY_TH_PARTY_ACCOUNT_RELATIONSHIP
PTY_ACC_REL_ACCOUNT_NUMBER	OBPY_TW_PARTY_ACCOUNT_RELATIONSHIP	ACCOUNT_NUMBER	OBPY_TH_PARTY_ACCOUNT_RELATIONSHIP
PTY_ACC_REL_ACCOUNT_TYPE	OBPY_TW_PARTY_ACCOUNT_RELATIONSHIP	ACCOUNT_TYPE	OBPY_TH_PARTY_ACCOUNT_RELATIONSHIP
PTY_ACC_REL_PARTY_RELATIONSHIP	OBPY_TW_PARTY_ACCOUNT_RELATIONSHIP	PARTY_RELATIONSHIP	OBPY_TH_PARTY_ACCOUNT_RELATIONSHIP
PTY_ACC_REL_PARTY_ROLE	OBPY_TW_PARTY_ACCOUNT_RELATIONSHIP	PARTY_ROLE	OBPY_TH_PARTY_ACCOUNT_RELATIONSHIP
PTY_ACC_REL_OWNERSHIP_TYPE	OBPY_TW_PARTY_ACCOUNT_RELATIONSHIP	OWNERSHIP_TYPE	OBPY_TH_PARTY_ACCOUNT_RELATIONSHIP
PTY_ACC_REL_RESPONSIBILITY_TYPE	OBPY_TW_PARTY_ACCOUNT_RELATIONSHIP	RESPONSIBILITY_TYPE	OBPY_TH_PARTY_ACCOUNT_RELATIONSHIP
PTY_ACC_REL_APPLICATION_TYPE	OBPY_TW_PARTY_ACCOUNT_RELATIONSHIP	APPLICATION_TYPE	OBPY_TH_PARTY_ACCOUNT_RELATIONSHIP
PTY_ACC_REL_PRODUCT_GROUP	OBPY_TW_PARTY_ACCOUNT_RELATIONSHIP	PRODUCT_GROUP	OBPY_TH_PARTY_ACCOUNT_RELATIONSHIP
PTY_ACC_REL_COMBINE_STATEMENT	OBPY_TW_PARTY_ACCOUNT_RELATIONSHIP	COMBINED_STATEMENT	OBPY_TH_PARTY_ACCOUNT_RELATIONSHIP
PTY_ACC_REL_NICK_NAME	OBPY_TW_PARTY_ACCOUNT_RELATIONSHIP	NICK_NAME	OBPY_TH_PARTY_ACCOUNT_RELATIONSHIP
PTY_ACC_REL_START_DATE	OBPY_TW_PARTY_ACCOUNT_RELATIONSHIP	START_DATE	OBPY_TH_PARTY_ACCOUNT_RELATIONSHIP
PTY_ACC_REL_END_DATE	OBPY_TW_PARTY_ACCOUNT_RELATIONSHIP	END_DATE	OBPY_TH_PARTY_ACCOUNT_RELATIONSHIP
PTY_ACC_REL_NICK_NAME_2	OBPY_TW_PARTY_ACCOUNT_RELATIONSHIP	SEC_NICK_NAME	OBPY_TH_PARTY_ACCOUNT_RELATIONSHIP
PTY_ACC_REL_PERCENT_OWNER	OBPY_TW_PARTY_ACCOUNT_RELATIONSHIP	OWNER_PERCENT	OBPY_TH_PARTY_ACCOUNT_RELATIONSHIP
PTY_ACC_REL_LEGAL_POSITION	OBPY_TW_PARTY_ACCOUNT_RELATIONSHIP	TITLE_POS	OBPY_TH_PARTY_ACCOUNT_RELATIONSHIP

Party to Account API:

Following API should be used to Create, Update and Delete Party to Account Records. All Existing validations as per the Existing APIs should be followed.

Endpoint url - /ob/obpy/party/v1/partyToAccount

Payload

{
  "externalCustomerNo": "231312313",
  "applicationNumber": "231312313",
  "sourceProductId": "OBPY",
  "patchOperations": [
    {
      "op": "replace",
      "params": {
        "accountNumber": "string",
        "partyRelationship": "string"
      },
      "values": {
        "cifId": "231312313",
        "accountNumber": "452343543",
        "accountType": "35",
        "partyRelationship": "IND",
        "partyRole": "PRIIND",
        "ownershipType": "P",
        "responsibilityType": "D",
        "applicationType": "CC",
        "productGroup": "MC",
        "combinedStatement": true,
        "nickName": "AB",
        "secondNickName": "AB",
        "percentOwner": 100,
        "titlePosition": "4",
        "startDate": "2010-01-01",
        "endDate": "2019-01-01",
       }
    }
  ]
}

Business Rules for Party-to-Account Relationship Upload:

Operation Identification
- PTY_ACC_REL_OPERATION determines the action:
  - add → Create a new record
  - replace → Update an existing record
  - remove → Delete an existing record
Immutable Identifiers
- The following fields are immutable and cannot be updated:
  - PTY_ACC_REL_CIF_ID
  - PTY_ACC_REL_ACCOUNT_NUMBER
  - PTY_ACC_REL_PARTY_RELATIONSHIP
Record Identification
- For replace and remove, a record will be uniquely identified using:
  - PTY_ACC_REL_CIF_ID + PTY_ACC_REL_ACCOUNT_NUMBER + PTY_ACC_REL_PARTY_RELATIONSHIP
- If combination does not resolve to a single unique record, the operation will be rejected.
Scope
- Updates are applicable only for Retail and SMB parties.
External Validations
- No validation for CIF ID and Account Number
Duplicate submissions overwrite existing records (upsert – last write wins).
Date Validation
- If an End Date is provided, it cannot be earlier than the Start Date.
Record History
- On update (replace), previous record details will be stored in a history table.
Values Handling
- Empty ("") or Literal "null"
  - Meaning: Explicit request to delete the existing value.
  - Action: System overwrites the field and sets it to blank/removed.
- Literal "no_update"
  - Meaning: No change intended; retain the current value.
  - Action: System ignores this field and keeps the existing value unchanged.
File Name should be unique "ObpyPtyToAct_<UniqueName>.csv"
Feed Name: ObpyPartyToAccount

Handling Duplicates:

Table 1-40 Handling Duplicates

UPLOAD FIELD NAME	TABLE	TABLE COLUMN	HISTORY TABLE
Duplicate in Upload File	Second record rejected	Subsequent records overwrite (upsert)	Subsequent record rejected (not found)
Existing Duplicate in System	Insert rejected	Invalid scenario	Invalid scenario

Preconditions:

Entity Code Configuration for Account Type, Party Relationship, Party Role, Ownership Type, Responsibility Type, Application Type, and Product Group is loaded and active.
Plato Feed endpoint is configured for the Party to Account segment; file ingestion job is enabled.

Note:

For more information on File Upload Process, refer section: File Upload.

Parent topic: Configurations