Menu Help & How To Video Simulation Game Document & Resources Training Link Tag Search clock thumbs-up angle-up arrow-up

Incoming CSENet Messages: How to Help Your Office Keep up With Them

Start by pulling one month of incoming CSENet messages for your office using the NETOFF function in OSIS. It is suggested to begin with the first day of the month as shown below:

Image of an OSIS screen with the information entered to access the CSENet messages by office code.

Remember there are four ways to look up CSENet Messages:

  1. NETIR – by U Number NETIR [U#] [DIR FLAG] [MMDDYY]
  2. NETIRF – by FGN NETIRF [FGN] DIR FLAG] [MMDDYY]
  3. NETIRO – by the other state IV-D number NETIRO [CASE #] [DIR FLAG] [MMDDYY]
  4. NETOFF – by office NETOFF [OFFICE CODE] [DIR FLAG] [MMDDYY]

Using NETOFF, copy your incoming CSENet messages page by page into a blank Microsoft Excel spreadsheet. It is suggested to use one Microsoft Excel spreadsheet per month:

Image of the NETOFF screen in OSIS displaying Incoming CSENet transactions.

Once your messages are pasted into Excel, format your spreadsheet to make it easier to read. Insert a top row and add column headings. Highlight your first-row column headings. Select the “Data” tab. Select “Filter” from the ribbon. You will now be able to touch on the column heading arrows to sort:

Image of an Excel spreadsheet that has the information from the NETOFF screen copied to it.

Action Codes (AC)

CSENet Action Code
A Acknowledgement
C Cancel request
M Reminder
P Provision of information
R Request (These are requests from the other state. We must respond within 30 days unless it is a Function Code CSI.)
U Update previous

Sorting and filtering by Action Code is one way to make sure you don’t miss any REQUESTS from the other state. Not only is this good casework but can help boost your office audit performance.

Function Codes (FNC CDE)

CSENet Function Code
COL Collections
CSI Case Information (These are automated transactions. Manual response not required. OSIS takes care of these behind the scenes.)
ENF Enforcement
EST Order Establishment
LO1 Locate level 1 (Quick Locate)
LO2 Locate level 2 (Full Locate)
MSC Miscellaneous
PAT Paternity

Reason Codes

Use the Valid Transactions Table to interpret Reason Codes. Some of the most important are:

  • GRUPD – request status update. We must respond within 30 days.
  • GRPOC – request copies of documentation. We must respond within 30 days.

Other critical information the other state may be providing may come under these Reason Codes:

  • AADIN – Acknowledgment – additional information needed to proceed. The other state is asking us for information.
  • GSPUD – providing status update. These messages frequently contain critical case information.
  • CITAX – Tax intercept information. Customers frequently contact CARE or local offices confused about tax intercepts received in the other state. CITAX messages provide data regarding interstate tax intercepts. Tracking these will help keep case balances accurate and reduce customer confusion.
  • GSC## – Case closure. Tracking closures in the other state can alert you to review or even close your case.