Transaction Accounting CSV Import is used to create a transaction batch by importing a CSV file of transactions. This is mostly used with direct payments report from clients formatted as CSV file so the user does not have to enter individual transactions manually.
In order for the Transaction Accounting CSV Import to function, the following must be setup:
1. Tables → Data Interface Tables → Data Interface Config Table
Set up a Data Interface config for the file you are importing. You may need to only set up one generic type interface for this, OR, you may need to set up a different Data Interface Config for each transaction file that you receive from a client that you want to import into IMPACT using this function. It will depend on if your clients have payment types in their files that equate to different transaction codes in IMPACT. (ie. CLIENTA has code TR17 and it indicates an NSF transaction while CLIENTB uses TR17 to indicate an adjustment to interest.) Each of these clients would need their own separate Data Interface Config.
Here is a sample screen filled out. Company ID is not needed for the Transaction Accounting CSV Import function, but you may need it if you use this same Data Interface Config for other import/export files for the same client. You can choose any alpha-numeric code for the CONFIG CODE field, and the CONFIG DESC can be whatever you would like.
You must choose a DEFAULT COMPANY and a DEFAULT CLIENT. The screen will not save unless you do. These codes are only used when loading certain files and the company and client code are not already specified in the file.
2. Tables → Data Interface Tables → Client's Transaction Code Import Table
You must then define for IMPACT the payment types that will be in the file and what Impact transaction code the payment type equates to. Here is a sample screen filled out. NOTE: The METHOD OF PAYMENT field on this screen is for a custom plugin. You can import the file a Method of payment. See the file layout information below. (reminder - the MOP field is only 1 character long. Values longer than that will be truncated to the first character in the field, values not in the MOP table will be accepted.)
You can also choose to have the funds applied based on the TRANSACTION POSTING SEQUENCE that pertains to the account - either at the commission rule level, client level or company level - by choosing CSS Transaction code = PSA Posting Sequence Company (CSV only) or PSB Posting Sequence Client (CSV only) - see sample below. You must still enter into the CLIENT'S TRANSACTION IMPORT CODE table all of the possible codes that will appear in the file and set each one to PSA or PSB.
FILE LAYOUT INFORMATION
Allowable CSV field headings are as follows:
dbt_no, company, client, clnt_acnt1, clnt_acnt2, pmt_type, trans_amt, dbt_fld_06, mop, post_date, check_no, ref_no, note, comm_amt, ignore. The file MUST contain field headings as the first row of the file in order to process. Use the ignore heading for any fields in the file that IMPACT should ignore. The post_date field MUST be of the format: CCYYMMDD or CCYY-MM-DD.
Not all fields are required. The file MUST contain (in any order) the following: pmt_type, trans_amt, AND either dbt_no OR company, client, clnt_acnt1 OR company, client, clnt_acnt2>
3322,999,1,100,B,ignore,,testref,note test 1
3330,888,17,55.55,C,ignore,20100815,testref2,note test 2
3419,666,1,23.1,1,ignore,20100831,testref4,note test 4
Things to note:
- The leading zeros on debtor numbers are not required.
- Every field DOES NOT have to have a value.
- MOP with more than 1 digit - only the first digit will be loaded.
- Dbt_no that is equal to a MASTER number will not load, they will error out as the funds need to be applied to links.
- Trans_Amt and Comm_Amt field - Please do some testing if you are going to use these fields to enter NSF's or POST CORRECTIONS:
- Transaction code in the row is defined as a PAYMENT - this will always reduce the money bucket it is for, regardless of being a positive or negative number in the file.
- Transaction code in row is defined as NSF - this will always increase the money bucket it is set for, regardless of being a positive or negative number
- Transaction code in the row is defined as POST CORRECTION - the value can be positive OR negative in the file, and each one will have a different result. A POSITIVE amt in the file will result in the money bucket amount being reduced. A NEGATIVE amt in the file will result in the money bucket being increased.
- If the comm_amt field is not used OR left empty, the commission will calculate as always based on the commission rule/rate on the account.
- If Transaction code is set up on the CLIENTS TRANSACTION IMPORT CODE to use PSA or PSB (Posting Sequence Company/Client (CSV only), the commission will be automatically calculated and any comm_amt in the comm_field will be completely ignored.
Transaction Accounting CSV Imports Navigation Menu
Transaction Accounting CSV Imports UI Navigation Window
Once the Transaction Accounting CSV Import option is selected, the following window is displayed
Transaction Accounting CSV Import Window
|Interface -||Data InterfaceConfiguration code pertaining to this specific import|
|File Path -||
The location of the CSV file
|Bank for Entries -||
The Bank for Entries combo box allows you to assign the transactions to a selected bank, including AUTO (Debtor Only) Clt--> St --> Cpy. This choice will automatically populate the Bank acct field on Debtor Transactions in the Transaction Detail Entry screen with the appropriate bank account as set up in the client code, state, or company (in that order).