There are many relationship fields used in Financial Performance Suite (FPS). These fields are set up on the File Layout Setup page for the daily update process or monthly update process.
On the File Layout Setup page, required fields are noted with an asterisk. Required fields can change based on the selected file layout and which modules the institution is licensed for. If a required field is not mapped, then exceptions can occur.
| FPS Relationship Fields | Field Descriptions | Notes |
|---|---|---|
| Account Name | The name associated with the account. | N/A |
| Account Number | An identifier that is used to determine an account. | This number must be unique for each row in the file. |
| Application ID | An identifier that is used to determine the type of account. For example, L represents a loan and CD is a time deposit. | Provide a list of codes that your institution uses. |
| Customer ID | A unique value that identifies the customer. | Same identifier as provided in the customer file. |
| Customer Name | The field that is used as a name for the customer. | N/A |
| Relationship Code | An identifier that defines how a customer is related to that account. For example, P is the primary and S is a signer. | Provide a list of codes that your institution uses. |
| Relationship ID | The field that is used to identify which relationship the customer belongs to. | N/A |
| Relationship Name | The field that is used as the name for the relationship. | N/A |