This section is devoted to accounting software developers and other third-party developers (including end-users) who are looking to integrate Treasury Software applications into a seamless and automated process for their users.
Our Software Integration Kit (SIK), unlike most automation development kits, is included directly in the runtime edition and is available to both power users and software developers in a Graphical User Interface. Please note that the SIK requires a Corporate or Processor Enterprise license.
Treasury Software's SIK includes full automation tools to seamlessly:
--import any file
--import all files within a directory
--archive (move) the imported files
--preserve the audit trail of archived files (append the file name of each file with a date/time stamp to insure that each file is uniquely named in the archive directory)
--provide summary reporting
and, of course
--perform any Treasury Software core module process including:
----ACH and Positive Pay file creation
----ACH and Positive Pay file transmission
----Automated Transaction Matching (ATM) for bank reconciliation
Note: The Software Integration Kit is referenced as the 'Custom Import Menu Setup' in some documents and is used here interchangeably.
To access the Software Integration Kit, from the Automation tab select Software Integration Kit.
You can have up to 20 integration routines per account. Select one that is not being used and click 'Add/Edit'.
Settings pages - Basic, Advanced and Automation
Visible--Check this box if you want this process to be available to the user from the main menu (Import submenu). This checkbox only drives visibility--it does not activate or inactivate a process.
What do you want to import?
File - select the file
Folder - point to a folder. Note: Each of the files should have the same format.
Tip: If you only want to import one file, but the file name is dynamic (keeps changing), then use the folder option.
Each custom process has it's own custom import layout. For example, here in the first process, the system defaults to the Custom Menu #1 template in the drop down list. The second custom process will have a Custom Menu #2, and so on.
This enables each custom process to have its own file layout.
Bank Reconciliation only
There will be two Custom Menu layout drop down lists. One is for the G/L (on the left), the other is for the Bank data (on the right). If automating both Bank and G/L imports, create a separate process for each (and keep each set of files in a different folder if using the folder import).
Advanced - second page
Fields to include:
If you are importing a csv/Excel file (see above), at a minimum you will want to create a file with the following data:
--Name of the other party (employee, customer, vendor)
--Bank Account Number
--ABA Routing Number
Additional fields that are commonly included:
--ID Number (ie. employee or vendor number)
--Checking or Savings (C or S; CHK or SAV)
--Personal or Corporate (PPD or CCD)
For additional fields, see Mapping Fields.
This is used to preserve the audit trail and keep the original import file available for future research and review.
The file is moved to the archive directory after a successful import. We recommend appending the file name with a date/time stamp, as this will make the file name unique, and insure that when the file is copied into the archive directory it will not overwrite any existing files.
Note: Fixed width text files are not supported in the archive process.
Tip: Confirm that the user triggering the custom process will have rights/privileges to the archive directory as it will be performed under their security profile.
Tabular notes: Includes Excel, comma delimited (csv) and tab delimited files.
Fixed width file notes: Select tabular, and also click the hyperlink 'Unsupported file formats' to display the second row of mapping templates.
Automation - third page
Command line group
This enables the process to be triggered from the Command Line Interface.
Processes are triggered by the numeric value set here. Therefore, all twenty processes could be called from a single command line, assuming all have the same value.
The basic syntax for the trigger is:
[path]\BRCOM.exe /ACCT="sample" /MENU /AUTO=1
· Account (database) - /ACCT
· Include to activate (static to trigger) - /MENU
· Group to use (numeric value in the Command Line Group number box)- /AUTO
This example triggers the Custom Import Menu group #1 (AUTO=1) for the 'sample' account.
Chaining multiple processes
Select a numeric value in the Command Line Group number box. When passed to the program, it will trigger sequentially all custom menu selections with the same value.
You want to trigger three import processes and then create and transmit an ACH file.
Import process 1 - Import a single payroll file
Import process 2 - Import all trade payable files in a directory
Import process 3 - Import all customer collection files in a directory
Create three separate custom menus, with all having the same Command Line Group number (1). As the processes are sequenced based on the process order (from the list top to bottom), make sure they are in sequence, as the last one will contain the automation process.
On Import process 3 (only), select the 'Custom Action After Import' to 'ACH File - Create and Transmit'.
Custom action after import
This can be:
ACH File - Create and Transmit
Positive Pay File - Create and Transmit
Automated Transaction Matching
Select as needed.
Custom date formats
Enables you to import non-standard date formats.
Question - How do you know if the format is a custom format?
Try opening the source file in Excel. If Excel opens the file and the date looks appropriate, you do not need to enter any settings. However, if Excel has a a problem interpreting the date, so will Treasury Software.
You can generate an activity receipt at the file level, which can be displayed at the end of each automation.
It will list all files in that folder and whether they were successfully imported.
ACH Merge / ACH Import - The system will only import ACH files in text format (not Excel, etc...) and ACH files in conformity to NACHA standards.