DFIC Error 81 - Invalid Task Based Billing Code

Last reviewed: 12/15/2010
Article ID: R10621

The information in this article applies to:

• Tabs3 Billing Software Version 16, 15, 14 & 12
• Tabs3 Remote Entry Software Version 16, 15, 14 & 12

SUMMARY

An error 81 indicates a missing or invalid task based billing code was encountered. This error may be found in the Task Code file, the Client Task Code Budget file, the Fee file or the Cost file.

In Tabs3 Remote, an error 81 indicates a missing or invalid task based billing code can be found in the validation files or the Tabs3 Remote Fee or Cost files.

MORE INFORMATION

If the error is in the Fee file or the Cost file, it typically indicates a missing task based billing code for a task based billing client and may occur as a result of:

• Merging data capture transactions. Task based billing codes cannot be imported from some device interface programs for task based billing clients. Warnings regarding transactions imported for task based billing clients are generated immediately after the merge.
• Merging Tabs3 Remote data transactions. Although Tabs3 Remote supports task based billing, it is possible to enter non-task based billing transactions for a client if validation files are not used or the client is not present in the validation files. Warnings regarding invalid transactions imported for task based billing clients are generated immediately after the merge.
• Changing a client in Tabs3 to a task based billing client after fee and cost transactions have already been entered for the client.

RESOLUTION

In Tabs3:

• To correct the error, simply open the data entry program and edit the appropriate task code field (i.e., Phase/Task, Activity, Expense ID, Task Code ID) or change the client's Task Based Billing Client check box. The Client ID and reference number will be shown on the error report.
• The Change WIP Transactions program can also be used to convert transaction codes to task based billing codes for existing work-in-process transactions.

In Tabs3 Remote:

• If the error is in the validation files, simply recreate the Tabs3 validation files and transfer the new validation files to the remote terminal.
• If the error is in the remote data files, edit the transaction's Tcode field using the appropriate data entry program. If you cannot edit the transaction, you must restore from a backup. Or, you can attempt to merge the data into Tabs3. The merge program may or may not complete successfully (most likely it will not). However, by trying to merge the data that is not corrupted, you have the chance of salvaging at least part of the data.

REFERENCES

• KB Article R10167 - Data File Integrity Check Errors in Verification Files

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-2012 Software Technology, Inc.   All rights reserved. Terms of Use
The maker of Tabs3 and PracticeMaster
Tabs3, PracticeMaster, and the “pinwheel” symbol () are registered trademarks of Software Technology, Inc.
e-Mail Suggestions for the Knowledge Base to: kb@Tabs3.com
Technical Support via e-mail is not available.
Knowledge Base:   http://support.Tabs3.com
Web Site:   http://www.Tabs3.com