Page tree
Skip to end of metadata
Go to start of metadata

Title: AMEX/American Express: Automated Integration using the IMU

Brief description:

Many clients utilize Unanet's credit card transaction import feature. This feature allows a system admin to import company credit card expenses, after which end users can easily and quickly pull appropriate charges onto their expense reports. With Unanet's Integrated Management Utility (IMU), an inbound interface can be designed to automate the process of importing American Express - KR-1025 files into Unanet. For other credit card types, a similar interface can be developed.

NoteThis method of automated import is hosted and maintained on your own platform.

  • The CreditCardConnect offering, which requires a subscription fee, can be utilized if you wish the import platform to be hosted and maintained by Unanet. For more information, please visit this page:

KC - Quick Topic - CreditCardConnect (AMEX KR-1025 and VISA)

  • CreditCardConnect is currently offered for VISA cards or the AMEX KR-1025 file (it may expand to other files and credit card types in the future).

What’s covered in this document:

Interface Description

  • The interface expects the client to receive (via FTP or similar file transfer mechanism) their Amex KR-1025 files into a predefined file folder. It expects that the files all have the same file name prefix, which is configurable. For example, AMEX_201412150001.
  • The interface looks for files in the predefined folder to replace all commas with spaces and prepend a new line on top of all files (the preprocess to ensure that the CSV Translator functions properly, and it is triggered by pre-process.bat), and creates a new set of modified copies.
  • The interface renames the file and converts it to csv format, and translates the files using CSV Translator (replaces Charge Date with Business Process Date for New Member Fee transactions as KR-1025 does not include the value). The code that drives this step is located in the file imu_pre_build.xml.  
  • The interface processes one set (if one file per company and there is more than one company) of files in each scheduled run. That is, if two sets of AMEX files were placed in the directory, the interface would process the set of files that has the older date/time stamp. The processed files are then moved out of the directory, so that the newer files then become the oldest files, and will be processed in the next run. 

Download Template

  • Please contact Support or your consultant to access the XML file template.

Configure Interface

pre-process.bat

  • Change the directories to where the interface gets installed.

    set "MasterFolder=C:/AMEX DOWNLOAD FOLDER"

run_CSVtrans.bat

  • Change the file names to 

imu_pre_build.xml

  • To configure the IMU package, the following values need to be set in imu_pre_build.xml:

    • AMEX DOWNLOAD FOLDER - Replace this value in the code with the name of the folder to which AMEX transfers the credit card transaction files. This value appears once in the code. Note that if the folder is located on a mapped drive, the UNC path should be used here. The basic format of the UNC path is: \\server\share\file_path.
    • FILEPREFIX - Replace this value in the code with the prefix on the credit card transaction file received from AMEX. This value appears twice in the code. Note: the asterisk must not be removed from the code because the code is trying to match the beginning of the file name.

      <target name="AMEX_Process"
          description="Custom processing before running imports">

           <property name="temp.dir" value="${base.dir}/temp" /> 
            <move todir="${temp.dir}" flatten="true">
               <first>
                  <sort>
                     <date xmlns="antlib:org.apache.tools.ant.types.resources.comparators"/>
                        <resources>
                          <fileset dir="C:/AMEX DOWNLOAD FOLDER">
                             <include name="FILEPREFIX*" />
                          </fileset>
                      </resources>
                   </sort>
               </first>
            </move> 

            <foreach target="_IMUmove" param="AmexFile" inheritall="true">
               <path>
                  <fileset dir="${temp.dir}" casesensitive="yes">
                     <include name="FILEPREFIX*" />
                  </fileset>
               </path>
            </foreach> 

      </target>

      <target name="_IMUmove">

          <echo>File: >> ${AmexFile}</echo>
          <echo file="${basedir}/log.txt" message="${AmexFile} - ${run.timestamp} ${line.separator}" append="true"/>

          <echo>Moving the input files to ${run.input.dir}...</echo>

          <move file="${AmexFile}" tofile="${run.input.dir}/credit_card.csv"/>

      </target>

imu_config.properties

  • The standard settings in the imu_config.properties file including the URL for Unanet, the login and password and email configuration need to be set.

unanet_imu_AMEX_import.bat

  • Change the directories to where the interface gets installed.

    set ant_home=C:/unanet_imu_AMEX_import/bin/ant
    C:/unanet_imu_AMEX_import/bin/ant/bin/ant.bat -f C:/unanet_imu_AMEX_import/imu_build.xml import

Schedule the task to run

Use a scheduler such as Windows Task Scheduler or Unix CRON to schedule for unanet_imu_AMEX_import.bat to execute.

Log.txt

After the IMU moves and processes the AMEX file, the file will be renamed and stored under the IMU data directory. If the client needs to look at a specific AMEX file, a row is appended to the file C:\unanet_imu_AMEX_import\log.txt each time the interface runs. The new row lists the original file names along with the timestamp when it was imported by the IMU. Once the timestamp is identified in the log.txt file, the file can be found in the IMU input folder.










Additional Information

KC - Quick Topic - CreditCardConnect (AMEX KR-1025 and VISA)

KC - Quick Topic - Reconciling Credit Card Transactions in Unanet Financials

KC - Credit Card Integrations, Imports, and the IMU

AMEX Electronic Transmissions Getting Started guide.doc


  • No labels