ACR 60294 – TINS Dropped Transactions and Relationship Table
July 17, 2020

Introduction

Effective July 17, 2020, TINS Application Change Request (ACR) 60294 implemented a process where TINS automatically drops invalid transactions submitted via batch as well as a TINS Relationship Table that maintains a list of agencies authorized to submit batch files on behalf of other state agencies.

Issue 1

Currently, TINS receives erroneous batch files or erroneous transactions that include:

• Invalid data in fields not intended for the values being submitted in the TINS file layout
• Submission of USAS INREC file layout with the TINS dataset name
• Files with blank records or records with blank fields

File submissions to TINS with such errors result in TINS generating error messages on the TINS84104A: Non-Processed / Warning Payee Maintenance Transactions report for the agency submitting the erroneous file and/or data as well as for all agencies that submit a TINS batch file the same day the invalid file or data is received.

Issue 2

TINS batch files are received with agency numbers in the file’s INPUT SOURCE field for which the submitting agency is not authorized.

Solution 1

Implement a system change that automatically drops invalid and blank transactions if:

• Transactions in a TINS file include invalid data, are formatted incorrectly or are blank
• The file is submitted to TINS with an invalid file layout

Include the dropped transactions in the new agency’s daily Comma Separated Values (CSV) file via ACR 60105 of TINS processed and non-processed transactions. Transactions with blank data are not included in the CSV file. (TINS processing is not attempted on dropped transactions.)

Solution 2

Implement a TINS Relationship Table that maintains a list of agencies authorized to submit transactions on behalf of other state agencies to ensure the appropriate TINS security access is maintained.

For questions contact Payment Services.