5.  SAMPLE FILES
AND TRANSMITTER IDENTIFIERS

(Last review or update:  February 1, 2006)
 

A.    Transmitter Identifiers. 

AKSYS no longer processes and posts acknowledgements by transmitter identifier, nor will AKSYS cross reference to the EFIN in an acknowledgement in an effort to identify the transmitter of an acknowledgement. Instead, AKSYS uses the transmitter's ETIN that is in the RSN of each acknowledgement. If AKSYS cannot identify the transmitter it will not post the acknowledgement. It will place the acknowledgement in its Master Data System, and the transmitter can obtain it by requesting a reposting.

If you are not getting acknowledgements, but you know that you should be receiving some, call AKSYS for technical assistance. The AKSYS technician will ask for your ETIN.  He might ask for a few sample primary social security numbers in returns for which you should have received acknowledgements.

The technician can scan the Master Data System and extract the acknowledgements that you have not received.  He will examine the data in the ETIN position in the  RSN of each acknowledgement, and he will tell you why the acknowledgements were not posted to your current file. With your concurrence, the technician will add the new ETINs to AKSYS's cross-reference system.  Thereafter, acknowledgements with those ETINs that arrive at AKSYS will be posted to your current file. 

The following are examples of files produced by AKSYS. Appendix 1 contains more information on the structure of acknowledgement records. 

B.   An Example of a Transmitter's Current File. 

                       0120****THIS IS AKSYS.(spaces to the 119th byte)#
           (one or more 120-byte acknowledgement records)
           0120****$$001660000000000000000000265.60000(zeros to the 119th byte)#

The information record is the last record.  The information record in the example shows that AKSYS already has posted 1660 acknowledgement units. for which the transmitter owes AKSYS $265.60.

C.   The Dummy Acknowledgement File.

After a transmitter has downloaded his current file, the new current file, assuming that no more acknowledgements were received during the cycle, will look like this if the file is reset by a Main Processing Unit (MPU).

        0120****THIS IS AKSYS.(spaces to the 119th byte)#
        0120****THERE ARE NO STATE ACKNOWLEDGEMENTS. (spaces to the 119th byte)#
        0120****$$001660000000000000000000265.60000(zeros to the 119th byte)#

Or like this if reset by a dialup system terminal.

        0120****THIS IS AKSYS.(spaces to the 119th byte)#
        0120****THERE ARE NO STATE ACKNOWLEDGEMENTS. (spaces to the 119th byte)#
        0120****$$This is a dummy acknowledgement file.(zeros to the 119th byte)#

If a transmitter does not download his current acknowledgement file it will remain available to him indefinitely -- until he calls for it.  New acknowledgements received for him from state revenue departments will be added to the current file.