Transaction Defaults Import

Use the Transaction Default import files to create, update, or remove the default accounting codes that are automatically allocated to transactions as they are processed in PaymentNet.

The Transaction Defaults Import File Layout table outlines the requirements for entering your data into a Transaction Defaults Import template. To ensure a successful import, review the considerations outlined below before beginning the import. In addition, be sure to familiarize yourself with the guidelines found in General Import File Tips.

You must create a chart of accounts before you can assign transaction defaults; otherwise, the Transaction Defaults import will fail.
The number of transaction custom fields is variable, depending on how the system is configured for the organization. All transaction custom fields are required in the header of the import file; however, it is NOT required that all transaction custom fields in the import file have a value. Unused custom fields should be left blank.
The Hierarchy ID field is only relevant for those objects that use a hierarchy ID. If this field is left blank, these objects will be globally available (that is, they will be assigned to the top node in the hierarchy).
If the duplicate hierarchy ID function is enabled, the hierarchy ID you enter must contain the full path, starting from the root and separating the nodes with a backslash (\). For example, the hierarchy of Root > Chicago > JPMC > Finance would be entered as Root\Chicago\JPMC\Finance
Accounting code segments must be combined or linked together (concatenated) into a single cell, with individual segment values divided by the pipe (|) delimiter.
When replacing a Transaction Defaults import, all existing default types are replaced.
If you are validating chart of account values (validation check box is selected), you must create the chart of accounts prior to loading defaults. If you try to load defaults before creating the chart of accounts, the import will fail.
If you need to modify one accounting code in a transaction default, you must enter the complete accounting code string in order to retain the other information. For example, if you want to change the first code from None to 151, you must still enter the complete string; for example, 151|999|11|N/A|N/A. If you enter dashes for the other codes or leave them blank, all the other codes will be set to null or blank values.

Transaction Defaults Import File Layout
Column	Name	Description	Required	Valid Codes
A	Default Type	Import default type	Yes	Valid values are: Account MCC Merchant Employee Customer code Hierarchy
B	Object ID	Code to be updated	Yes	Valid values are: Account Number MCC ID Merchant ID Employee ID (User ID) Customer Code (17 characters max) Hierarchy ID
C	Hierarchy ID	The name of the hierarchy node if applicable	Yes for Hierarchy, Merchant & MCC transaction defaults	Must be: Alphanumeric 20 characters max for organizations that do not use the duplicate hierarchy ID function 508 characters max for organizations that use the duplicate hierarchy ID function
D	Chart of Accounts	Chart of accounts name		Must be: Alphanumeric 20 characters max
E	Accounting Code	The segments defined for the specified chart of accounts. Segments must be concatenated into a single cell, with individual segments delimited by the pipe symbol (“\|”). Accounting Code must consist of segment values separated by pipe symbol (“\|”) as delimiters and concatenated in the ascending order of segment number.	Yes, if Chart of Accounts is specified	Must be: Alphanumeric. For example: “12\|1200\|1220”
F	Custom Field 1\| Custom Field 2\| Custom Field 3	Custom field names The header row needs to be updated with the names of the transaction default custom fields.	Yes, when the header row is defined and corresponding custom fields are configured in PaymentNet to be “Required”. If custom fields are not used, the column header row and each cell in the column must be left blank.	Must be: Pipe delimited Unlimited Note: If you are not providing values for the custom fields, you must enter a dash (-) for each blank value separated by the pipe character (\|). For example: -\|-\|-
G	Add/Update/Delete Flag	Indicates whether the record is for creating, updating, or deleting transaction defaults.	Yes	Valid values are: Add: For new rows Update: For existing rows to be updated Delete: For rows to be removed
H	Blank Override	Specifies whether or not to replace existing values with null values when import file columns are blank. Blank Override is used where Add/Update/Delete Flag is set to “Update” Best Practice: Set Blank Override to “0”.	Yes	Valid values are: 0: Retains the existing value if the column is left blank. 1: Overwrite the existing value with a null value if the column is left blank.