Integration Overview of STI Software

Last reviewed: 02/26/2003
Article ID: R10359

The information in this article applies to:

• All Version 10 Products

SUMMARY

This article defines the integration between the various STI software systems.

Note: This article includes basic integration information. For complete integration details, refer to the program's online Help or manual.

Types of Integration

Real-Time Integration

Information is sent from one program to another at the time of entry. For example, journal entries can be automatically posted to GLS when a cost or payment transaction is entered in TABS III.

Batch Integration

Information is sent from one program to another as a group or batch. The user controls this process, usually by selecting a specific menu option. For example, running the Post Checks program in APS sends a batch of journal entries to GLS.

TABS III

TAS to TABS III (Real-Time Integration)

Integration between the systems occurs as follows:

• When a client is added in TAS, the client is also added in TABS III and PracticeMaster, since TAS and TABS III share data files and PracticeMaster and TABS III use mirrored data files.
• A TABS III payment record is created when a TAS transaction with a type of check or EFT and a payee of FIRM is paid (i.e., assigned a check number greater than zero).

Integration Notes:

• TABS III can include a client's trust account balance on the Detail and Summary Work-In-Process Reports.
• TABS III can print either detail or summary trust account information at the end of a statement.
• TABS III can print a message on a billing statement indicating that the client should remit an amount to replenish the trust account.
• TAS Checks and EFTs with a payee other than "FIRM" do not integrate to TABS III.
• TAS deposits do not integrate to TABS III.
• Only trust transactions dated between the last statement date and the current statement date will show on TABS III statements.
• Trust accounts that have a balance of zero will not print on TABS III statements or work-in-process reports.
• When the Back Up Data Files program or the Restore Data Files program is used in either TABS III or TAS, the other program's data is backed up or restored, as well.
• Clients that have a TAS trust account cannot be deleted in PracticeMaster or TABS III; the trust account must first be deleted in TAS.

APS to TABS III (Real-Time Integration)

Integration between the systems occurs as follows:

• When creating an invoice or manual check entry in APS, a Cost data entry window will be displayed allowing you to create a cost transaction in TABS III.

Integration Note:

• Deleting or editing an invoice or manual check entry in APS does not delete or change any corresponding cost transaction that was created in TABS III when the APS entry was originally saved.

PracticeMaster to/from TABS III (Real-Time Integration)

Integration between the systems occurs as follows:

• When a client is added, changed or deleted in PracticeMaster or TABS III, the client is also added, changed or deleted in the other program, since PracticeMaster and TABS III have mirrored data files.
• When a fee or cost transaction is added, changed or deleted in PracticeMaster or TABS III, the fee or cost is also added, changed or deleted in the other program's mirrored data file.
• Client Notes added in TABS III are also added to PracticeMaster's Journal file.
• Converting time and phone tasks to fee records in PracticeMaster also creates fee records in TABS III.

Integration Notes:

• Clients that have a TAS trust account cannot be deleted in PracticeMaster or TABS III; the trust account must first be deleted in TAS.
• Changes to the Billing System Lookup Files can only be made in TABS III. The Billing System's Lookup Files include the following:
• Timekeeper file (T3EMPL)
• Category file (T3CAT)
• Transaction Code file (T3TCODE)
• Task Code file (T3TBCODE)
• Location file (T3LOC)
• When a fee or cost transaction is added in PracticeMaster, fields in the TABS III fee and cost files that are not used in PracticeMaster (e.g., sales tax) will be assigned the default values in TABS III.
• Only TABS III transactions that use a Type 0 or Type 5 transaction code are displayed in PracticeMaster.
• When TABS III is integrated with GLS, you cannot add cost transactions in PracticeMaster. Furthermore, cost transactions in PracticeMaster are "read only".
• Information added to the Journal file in PracticeMaster is not added to TABS III. Likewise, you cannot make changes to the TABS III Client Notes in PracticeMaster's Journal File.
• Although synchronization is automatic, certain situations can require that the mirrored data files be resynchronized using the Synchronize TABS III and PracticeMaster program (from the TABS III menu, select Maintenance | Integration | Synchronize TABS III and PracticeMaster). Examples of situations that may require resynchronization include when data is imported into PracticeMaster or when a Data File Integrity Check reports an error 500).

TABS III Palm Application to TABS III (Batch Integration)

Integration between the systems occurs as follows:

• When a HotSync is performed on a handheld device, fee and cost transactions entered into the handheld device are passed to TABS III.

Integration Notes:

• If TABS III is set up to integrate with STI's General Ledger System (GLS), debits and credits for cost transactions will automatically be created and posted to GLS at the time you synchronize transactions from the handheld device.

TABS III Remote to TABS III (Batch Integration)

Integration between the systems occurs as follows:

• Once the TABS III Remote data files (RMT*.*) are copied to the TABS III working directory, the "Merge TABS III Remote Data" program is run to merge fee and cost transactions into TABS III.
• Validation files can be created in TABS III and then copied to the directory where the TABS III Remote program is located. This allows TABS III Remote users to select existing clients, transaction codes, etc., when adding or editing transactions.

Integration Notes:

• If errors occur during the merge process, an error list can be displayed, printed or saved.
• The RMT*.* files are deleted after the "Merge TABS III Remote Data" program is run provided no errors are encountered. If errors are encountered, the RMT*.* files are not deleted. The transactions that have already merged without error are flagged so the file can be corrected and remerged without duplicating already merged transactions.
• GLS integration for cost transactions created in TABS III Remote occurs if the following conditions are met:
• TABS III is configured to automatically create GLS journal entries.
• The cost transaction codes assigned to the merged transactions have GLS debit and credit account numbers specified in TABS III.
• The dates for the merged cost transactions are not beyond the GLS Current Fiscal Month.

Cost Recovery Interface to TABS III (Batch Integration)

Integration between the systems occurs as follows:

• Once the data from a cost recovery interface is converted to *.REM data files in the TABS III directory, the "Merge Data Capture Transactions" program is run to merge cost transactions into TABS III.
• Validation files can be created in TABS III, allowing users of a cost recovery device to select existing clients, transaction codes, etc., when adding transactions (provided the cost recovery system supports validation files).

Integration Notes:

• If errors occur during the merge process, an error list can be displayed, printed or saved.
• The *.REM files are deleted after the "Merge Data Capture Transactions" program is run provided no errors are encountered. If errors are encountered, the *.REM files are not deleted. The transactions that have already merged without error are flagged so the file can be corrected and remerged without duplicating already merged transactions.
• GLS integration for transactions created using a cost recovery device occurs if the following conditions are met:
• The Import Cost Totals Only check box is selected in the "Merge Data Capture Transactions" window.
• TABS III is configured to automatically create GLS journal entries.
• The cost transaction codes assigned to the merged transactions have GLS debit and credit account numbers specified in TABS III.
• The dates for the merged cost transactions are not beyond the GLS Current Fiscal Month.

TABS III to Taskbill (Batch Integration)

• The Taskbill program exports updated fee and cost transactions from TABS III to a disk file in one of a variety of formats. This disk file is created for transmission to companies that require billing data to be provided in a specific electronic format. The Taskbill program does not export information to a report format.

Integration Notes:

• Before you can export any data from TABS III, the desired format (e.g., LEDES 1998 B) must be configured in Taskbill.

General Ledger

STI programs pass information to GLS. GLS does not pass information to any STI Programs.

TABS III to GLS (Real-Time Integration)

Integration between the systems occurs as follows:

• Entering cost and payment transactions in TABS III creates journal entries in GLS. For example, a payment transaction can be configured to create a debit to a GLS cash account and a credit to an income account.
• Updating statements in TABS III can create journal entries in GLS if the TABS III statements contain client funds payment to firm transactions.

Integration Notes:

• TABS III tcodes set up with a Trans. Type of Expense or Advance and with a Type of 0 - Normal or 5 - Miscellaneous can be individually configured to integrate with GLS. Furthermore, all tcodes with a Type of Payment (i.e., Type 1, 2 & 3) can be configured to integrate with GLS.
• For each tcode that is configured to integrate with GLS, the following GLS settings can be configured:
• GLS account to be credited
• GLS journal to be used by the credit entry
• GLS account to be debited
• GLS journal to be used by the debit entry
• TABS III fee transactions do not integrate.
• The following transaction-related activities in TABS III do not affect GLS:
• Reversing or adjusting a payment
• Writing-up or writing-down cost transactions
• Editing or deleting an existing cost or payment transaction

TAS to GLS (Real-Time Integration)

Integration between the systems occurs as follows:

• When a trust transaction with a type of Check or EFT and a payee of FIRM is paid (i.e., the transaction is assigned a check number greater than zero), journal entries are created in GLS. The GLS accounts to be affected by such journal entries are specified on the Bank Account tab of the TAS Miscellaneous window (from the TAS menu, select File | Open | Miscellaneous). For example, a bank account may be configured to create a debit journal entry to a cash account and a credit entry to an income account when an eligible transaction is paid.

Integration Notes:

• Checks and EFTs with a payee other than FIRM do not integrate.
• TAS deposits do not integrate.
• When a check with a payee of FIRM is voided using the "Void Checks" program in TAS, reversing journal entries will automatically be created in GLS.
• TAS will only integrate with the GLS client selected in TAS Customization.

APS to GLS (Batch Integration)

Integration between the systems occurs as follows:

• Running the "Post Checks" program in APS creates journal entries in GLS. The debit entries specified in each invoice are created, and a credit entry is created for the account indicated on the Bank Account tab of the Miscellaneous window in APS (File | Open | Miscellaneous).
• Running the "Post Unpaid Invoices" or "Unpost Unpaid Invoices" program in APS creates or reverses journal entries in GLS. The accounts affected by these programs depend on the accounting method specified on the General Ledger tab of the Customization program in APS (Utilities | Customization).
• Running the "Void Posted Checks" program in APS creates reversing journal entries in GLS, based on the original journal entries created when the Post Checks program was run.
• GLS balance information can be included when running the Cash Requirements Report or the Pre-Check Register in APS.

Integration Notes:

• The bank account balance is not stored in APS.
• APS will only integrate with one GLS client.
• If errors are encountered during the process of posting checks, posting unpaid invoices, or unposting unpaid invoices, an error list can be displayed, printed, or saved to a file upon completion of the process.

Payroll to GLS (Batch Integration)

There are three payroll systems that integrate with GLS. The following table provides integration information for each payroll system.

Integration between PenSoft Payroll or Great Plains Payroll and GLS occurs as follows:

• The payroll integration data file is created in the payroll system, and the appropriate posting program is run to create journal entries in GLS.

Integration between System/II Payroll and GLS occurs as follows:

1. The "System/II Payroll Interface Configuration" program is run in GLS to map System/II account numbers to the corresponding GLS account numbers.
2. The JORPAY.IN integration file is created in the System/II Payroll program.
3. The "Post System/II Payroll" program is run to create journal entries in GLS.

Integration Notes:

• Records that do not have valid GLS account numbers in the integration file are not merged.
• Records that have a date beyond the Current Fiscal Month in GLS are not merged.
• After the posting process has completed, an error list can be displayed or printed (if errors were encountered).
• After the process of posting PenSoft Payroll data or Great Plains Payroll data has completed, GLS deletes the GLSPEND.DTA or GLSPAY.DTA file, even if errors were encountered during the posting process.
• After the process of posting System/II Payroll data has completed, GLS deletes the contents of the JORPAY.IN file, even if errors were encountered during the posting process. A zero byte JORPAY.IN file remains.

Third Party Software Journal Entries to GLS (Batch Integration)

The Post ASCII Data program allows you to import GLS journal entries from any other software package, provided that the data is in an ASCII text file named GLSASCII.DTA, and in the correct format.

Integration Notes:

• Records with an invalid GLS account number or a date beyond the GLS Current Fiscal Month will not be merged.
• After the posting process has completed, an error list can be displayed or printed (if errors were encountered).
• A warning will be displayed if unequal debits and credits were posted. Unequal journal entry totals might be posted due to rejected journal entries. Any rejected entries will need to be entered manually using the GLS "Journal Entries" program.
• If journal entries are successfully posted, you will be prompted to print a Journal Entry Verification List.
• All journal entries created by the "Post ASCII Data" program will have a "P" (Payroll) in the Source field on the General Ledger Report, the Journal Report and the Journal Entry Verification List.
• If you want to use the Check Reconciliation program for a bank account that will have journal entries posted by the "Post ASCII Data" program using the Summary option, you must edit the posted journal entries by adding the check number.

Trust Accounting

TABS III to TAS (Both Real-Time and Batch Integration)

Integration between the systems occurs as follows:

• When a client is added, changed or deleted in TABS III, the client is also added, changed or deleted in TAS and PracticeMaster, since TABS III and TAS share data files and TABS III and PracticeMaster use mirrored data files.
• When a change is made to the timekeeper file in TABS III, the change is also made to the attorney information in TAS.

Integration Notes:

• Clients that have a TAS trust account cannot be deleted in PracticeMaster or TABS III; the trust account must first be deleted in TAS.
• When TAS is integrated with TABS III, you cannot add, change, or delete attorneys in TAS.
• When the Back Up Data Files program or the Restore Data Files program is used in either TABS III or TAS, the other program's data is backed up or restored, as well.

Third Party Software Trust Transactions to TAS (Batch Integration)

The Import Transactions program allows you to import trust transactions from other software packages if the data is in an ASCII text file named T4IMPORT.DAT and in the correct format.

Integration Notes:

• The T4IMPORT.DAT file must be located in the current working directory.
• When transactions are successfully imported, you will be prompted to print a Transaction Entry Verification List.
• Upon completion of the import process, the T4IMPORT.DAT file is deleted (even if errors are encountered).
• An imported transaction will integrate to TABS III and GLS only if the following conditions are met:
• In TAS Customization, integration is selected for TABS III, GLS or both.
• The transaction is either type "C" (check) with a check number greater than zero, or type "E" (EFT).
• The Payee Name is FIRM.
• At least one of the GLS or TABS III payment amounts indicated in the record must not equal zero.
• The bank account must have GLS debit and credit accounts and/or TABS III transaction codes for payments set up.

Accounts Payable

TAS to APS (Batch Integration)

Integration between the systems occurs as follows:

• The 1099 information for trust accounts that are set up to use the firm as the payer (i.e., trust accounts that have the same Federal ID # as the firm) can be sent to a merge file using the "Create APS 1099 Merge File" program in TAS.

Integration Notes:

• The paid information for APS vendors is not affected when TAS information is included.
• If the APS vendor and the TAS payee are to be combined on the 1099-MISC Form, the Federal ID # and the 1099 box number must match.
• If a 1099-MISC Form includes combined information from TAS and APS, the address from the APS Vendor file will be used on the 1099-MISC Form.

Third Party Software Invoices to APS (Batch Integration)

The Import Invoices program allows you to import invoices and manual checks along with optional GLS information from other software packages if the data is in an ASCII text file named A3IMPORT.DTA and in the correct format.

Integration Notes:

• The A3IMPORT.DTA file must be located in the current working directory.
• When invoices are successfully imported, you will be prompted to print an Invoice/Manual Check Verification List.
• Upon completion of the posting process, the A3IMPORT.DTA file is deleted (even if errors are encountered).

References

• STI Article R10663 - Comparing Programs that Integrate with a Handheld

THE INFORMATION PROVIDED IN THE SOFTWARE TECHNOLOGY, INC. KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SOFTWARE TECHNOLOGY, INC. DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SOFTWARE TECHNOLOGY, INC. OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF SOFTWARE TECHNOLOGY, INC. OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

© 1999-2003 Software Technology, Inc.   All rights reserved.
Knowledge Base:   http://support.Tabs3.com
Web Site:   http://www.Tabs3.com