-
Print
-
DarkLight
-
PDF
Inbound Customer Spreadsheet Upload (ARI006)
-
Print
-
DarkLight
-
PDF
Interface Description
Florida PALM provides a customer record structure that allows each agency to maintain its own customer information for tracking receivables and revenues. This structure allows the agencies to capture unique customer information. Customer records include general information, such as name, addresses, payment term, payment method, collector and credit analyst associated with customer. Contact information like name, email address, and phone is captured on the customer record. Florida PALM also records important customer information like Taxpayer Identification Number (TIN) or Social Security Number (SSN), and Customer Type, e.g., General and FACTS related Customer Types. Additional fields are also provided to capture agency specific data.
This interface uses a spreadsheet upload and custom process to load data into customer records.
Click below to view the interface file layout and sample data file.
Business Process Model
This interface can be found in the following business process:
Run Control Parameters
The interface data selection criteria includes the following:
Data Field | Data Field Details |
---|---|
Attached File (Required) | Attach the excel file from which data needs to be loaded. |
File Layout
Field names and descriptions from the interface layout are provided below.
Data Field | Record Type | Data Field Description |
---|---|---|
Set ID | Customer Header | This field is used to specify Customer Set ID which is agency specific. |
Customer ID | Customer Header | Uniquely identifies an individual or entity, that conducts business and/or financial transactions with the State of Florida or otherwise is obligated to pay funds or incurs debt to the State. |
Customer Status | Customer Header | Current Status of the Customer. If updating existing customer to I - Inactive, provide required Customer Header record information only. |
Customer Type | Customer Header | Type of Customer. Used to identify customer categories in reports. |
Date Added | Customer Header | Enter the date when you established the customer in the system. If unknown, populate with a date of 01/01/1901. |
Since Date | Customer Header | Specify that the customer has been a customer since a certain date, which may be the date added. If unknown, populate with the same date as the ADD_DT field. |
Name 1 | Customer Header | Primary Name of the Customer. System will provide a warning in the Process Monitor if the customer’s name is duplicated. Agencies can utilize up to 40 characters to create a unique customer name. |
Name 2 | Customer Header | This is an overflow of the name of the customer that will be maintained in Florida PALM. |
Short Name | Customer Header | Short Name of the Customer. Could be used as a unique identifier if the same customer “Name 1” is used across agency business systems or agency divisions. If left blank, system will default the Short Name to be the first 10 characters of the Name 1 data element. |
Agency Customer ID | Customer Header | Agency Customer ID is created or provided by the agency for linking customer numbers. |
Corporate Customer Checkbox | Customer Header | This field is used to identify if the customer is Corporate/Parent Customer. If left blank, system should default as 'Y' |
Agency Parent Customer ID | Customer Header | Agency Parent Customer ID is provided for linking Parent and Child relationship. |
Cust Char30 C | Customer Header | Field for Agency use |
Cust Char30 D | Customer Header | Field for Agency use |
Cust Char10 A | Customer Header | Field for Agency use |
Cust Char10 B | Customer Header | Field for Agency use |
Cust Char10 C | Customer Header | Field for Agency use |
Cust Char10 D | Customer Header | Field for Agency use |
Cust Char2 | Customer Header | Field for Agency use |
Cust Char4 | Customer Header | Field for Agency use |
Cust Char6 | Customer Header | Field for Agency use |
Cust Char8 | Customer Header | Field for Agency use |
Cust Char1 A | Customer Header | Field for Agency use |
Cust Char1 B | Customer Header | Field for Agency use |
Cust Char1 C | Customer Header | Field for Agency use |
Cust Char1 D | Customer Header | Field for Agency use |
Cust N12.3 A | Customer Header | Field for Agency use |
Cust N12.3 B | Customer Header | Field for Agency use |
Cust N12.3 C | Customer Header | Field for Agency use |
Cust N12.3 D | Customer Header | Field for Agency use |
Cust Nbr15 A | Customer Header | Field for Agency use |
Cust Nbr15 B | Customer Header | Field for Agency use |
Cust Nbr15 C | Customer Header | Field for Agency use |
Cust Nbr15 D | Customer Header | Field for Agency use |
Customer Bill To Options Effective Date | Bill To Customer Option | Customer Bill To Options are needed to save a customer. Indicates the date the billing options are available for AR item transactions. |
Customer Bill To Options Effective Status | Bill To Customer Option | Customer Bill To Options are needed to save a customer. This field is used to indicate Status of billing options available for AR item transactions. |
Address Sequence Number | Customer Address Detail | Represents a unique, sequential identifier for a customer billing address. A customer can have multiple addresses associated with it. For each new customer, start the address sequence with the number 1 and increment for each additional address. For updating existing customer address, provide the current Address Sequence Number which is equal to the Location online. |
Effective Date | Customer Address Detail | Indicates the date the address is available for transactions. In case of update to existing customer address, new effective dated row should be provided. |
Effective Status | Customer Address Detail | This field is used to indicate Status of address. In case of update to existing customers, if Status changed from A to I then there has to be one Active row present with latest effective date for the customer address |
Description | Customer Address Detail | Agencies will provide an Address Description to help identify the location. Description will be mentioned for each unique address sequence numbers. |
Primary Bill To | Customer Address Detail | Indicates whether the address is a Primary Bill To address for the customer. Only one address must be designated as the primary/default Bill To address for the customer. |
Primary Ship To | Customer Address Detail | Indicates whether address is the primary ship to address for the customer. Only one address must be designated as the primary/default Ship To address for the customer. |
Primary Sold To | Customer Address Detail | Indicates whether address is the Primary Sold To address for the customer. Only one address must be designated as the primary/default Sold To address for the customer. |
Address 1 | Customer Address Detail | First Line of the Address. |
Address 2 | Customer Address Detail | Second Line of the Address. |
Address 3 | Customer Address Detail | Third Line of the Address. |
Address 4 | Customer Address Detail | Fourth Line of the Address. |
City | Customer Address Detail | City for the customer address. |
County | Customer Address Detail | County. |
State | Customer Address Detail | State for the customer address. |
Postal | Customer Address Detail | Postal code for the customers address. |
Country | Customer Address Detail | Country Code. |
Contact ID | Customer Contact | Assigning contacts to a customer is optional. A Customer can have more than one Address. A Contact can only be associated with one Address per Customer. A Contact can be associated with multiple Customers. A Contact associated with multiple Customers will have their own Contact/Address relationship. |
Effective Date | Customer Contact | Indicates the date the contact is available for transactions. In case of update to existing customer contact, new effective dated row should be provided. |
Effective Status | Customer Contact | This field is used to indicate Status of contact. In case of update to existing customers, if Status changed from A to I then there has to be one Active row present with latest effective date for the customer contact. |
Contact Flag | Customer Contact | An attribute that describes the specific purpose of a given bank/counterparty contact person. |
Salutation Code | Customer Contact | Salutation for the contact. |
Address Sequence Number | Customer Contact | Customer address that the contact should be linked to by using the Address Sequence Number or Location online. |
Primary Bill Contact | Customer Contact | Indicates whether the contact is the Primary Bill To Contact for the customer. |
Primary Ship Contact | Customer Contact | Indicates whether the contact is the Primary Ship To contact for the customer. |
Primary Sold Contact | Customer Contact | Indicates whether the contact is the Primary Sold To contact for the customer. |
Title | Customer Contact | Title of the contact. |
Name | Customer Contact | Name of the contact. |
Communication Method | Customer Contact | Preferred Communication. |
Email ID | Customer Contact | A User's Email ID. |
Phone Type | Customer Phone Contact | Phone number type (i.e., Business Phone, Cell Phone, etc.) associated with the contact. |
Phone | Customer Phone Contact | Telephone number. |
Extension | Customer Phone Contact | Extension to the phone number associated with the contact. |
Primary Phone | Customer Phone Contact | Indicate if the phone number represents the primary number for the contact. |
Effective Date | Customer Correspondence | Indicates the date this correspondence options are available for transactions. |
Effective Status | Customer Correspondence | This field is used to indicate Status of correspondence |
Dispute Checkbox | Customer Correspondence | Indicates whether the customer is in dispute. |
Dispute Status | Customer Correspondence | Indicates the reason of dispute. |
Dispute Date | Customer Correspondence | Indicates the date when the customer was in dispute. |
Standard ID Qualifier | Customer Numbers | Standard ID Qualifier. |
Standard ID Number | Customer Numbers | ID number. |
Version History
Date | Revision Description |
---|---|
01/07/2024 | Original Version |
04/19/2024 | Updated descriptions for Name 1 and Short Name fields. |
08/28/2024 | Update perversion history date of 07/31/2024: Administrative update to modify the Processing Rule of fields that were set to Conditional |