National Interstate Case Reconciliation Project
Technical Data Guide for Extract File and
Matching Results
SECTION 3: ICR GUIDE TO RECONCILIATION MATCHING RESULTS
The purpose of the ICR Guide to Reconciliation Matching Results is to provide state child support enforcement agencies steps to utilizing the national ICR matching results to reconcile interstate case discrepancies. This document describes the ICR data exchange process and provides a guide for using the Reason Codes returned to the states after completion of the national ICR.
The Guide addresses case and participant-level discrepancies.
Section 3.0 is organized as follows:
- A Technical Approach includes the step-by-step technical process of the extract matching approach and data elements of the extract file layout
- Working with Reconciliation Matching Results, provides the State CSE staff workers with suggestions on how to utilize the Reason Codes and reconcile cases after receiving the extract matching results
- Frequently Asked Questions
- Common Terms and Definitions used throughout this document.
3.1 Technical Approach
The purpose of the ICR project is to inform states about mismatches that may arise with interstate cases, and to provide assistance with reconciling those cases. The process outlined here will inform states of data discrepancies in cases shared with another state. The outcome of this process will be to allow states to load the correct Other State Case ID and verified SSNs into their systems in an automated fashion with a high level of confidence.
There are several steps involved within the process, and this section of the document outlines these steps, their purpose and their structure.
The Extract File Matching approach, which is the ICR methodology selected after consultation with the state partners, centers on the submission by states of extracts of their interstate cases. These extracts contain basic data for every open or closed interstate case (action) in their system that fits the definition of an ICR interstate case as provided in section 2.3.
Upon receipt of state extracts from participating states (and a parallel methodology to obtain Federal Case Registry [FCR] data for non-participating states), OCSE will run an extract file matching routine and process the extracts. OCSE will then return to each participating state a formatted response dataset that clearly defines:
- Cases that exactly match a case in another state,
- Cases that essentially match another state's case but contain data discrepancies between the cases,
- Open cases that match closed cases in another state, and
- Cases that a state presumed were interstate cases which could not be found in the other state's extract file.
Figure 1, ICR Extract File Matching, on the following page, illustrates the ICR matching approach for both participating states and
non-participating states
Table of Contents
3.1.1 Use of State Data
The basis of the ICR is matching, at the federal level, of state interstate case data. There are two manners in which this data is acquired, either through an extract file that participating states develop, or through FCR-derived data from non-participating states. This section details both circumstances.
States that have chosen to participate in the ICR program write an extract program containing basic case and participant data for each case that meets the definition of an interstate case for ICR purposes. This basic case data includes:
- Your state Case ID,
- Your state Interstate Case (action) Status (i.e., 'open' or 'closed'),
- Your state Initiating/Responding Indicator,
- Your state FIPS Code,
- Other State Case ID,
- Other State FIPS Code, and
- Your state caseworker contact information.
Each participant in a case is submitted in a separate record.
The basic data for each active participant on each submitted interstate case includes:
- SSN,
- Member ID,
- Participant Type,
- Name,
- DOB, and
- Sex.
State extracts are submitted in a file format provided by OCSE via CONNECT:Direct, the secure transmission line
currently in use for transmission of case and participant data to the FCR.
Appendix A, ICR State Extract File Record Format, displays the names and specifications for the extract file for participating states. Please refer to section 2.0 for more technical information regarding the creation of the extract file.
Figure 1. ICR Extract File Matching
Those states that do not participate in the ICR program do not develop an extract. However,
an 'extract' will be derived by OCSE from those states' cases already resident on the FCR. FCR-derived extracts will
be compared against the ICR extracts provided by participating states. These participating states will receive response data containing matches and discrepancies between their ICR extract cases and the FCR-derived cases from non-participating states. Due to the lack of interstate identifiers in the FCR, non-participating states will not receive any ICR response data.
These FCR-derived extracts will contain information similar to the extracts submitted by participating states. However, there are problems inherent with using FCR data for interstate matches. There may be a significant number of interstate cases missing from the
FCR-derived extracts, including:
- Cases not submitted by states with their initial loads onto the FCR in 1998
because the cases were already closed, since closed cases were specifically excluded from initial loads,
- Cases rejected by the FCR due to missing critical data elements (e.g., an SSN was not submitted nor identified for either the CP, NCP, or PF), and
- Cases not submitted by states because state staff knew the cases would be rejected for lacking necessary data.
Furthermore, since the FCR does not designate cases as 'interstate,' matches using FCR-derived data may contain non-interstate cases, and the extract matching routine would therefore be returning case matches that are not interstate cases.
For these reasons, you should be aware that FCR case matches provide a lower level of confidence for automating updates as compared to the level of confidence of the matches found from state extract files. The extract matching routine sets the FCR-Supplied Indicator to "Y" whenever a case from your ICR extract matches an FCR-derived case from another state.
Table of Contents
3.1.2 ICR Matching Routine
The matching routine developed for the ICR processes each state's interstate extract against all other state extracts, including FCR-derived extracts for non-participating states.
The matching routine first searches for a corresponding case in another state's extract by using the state code from the Other State FIPS Code and Other State Case ID as keys to finding that case. If the other state's case is found, your state's case and the other state's case are compared to determine the extent to which the case data and participants match.
If the other state's case is not found based on the combination of the state code from the Other State FIPS Code and Other State Case ID, the program searches the other state's file for each child from your state's case by SSN. If the SSN search reveals a corresponding case for that child in the other state, then the program compares case data and participants between the two cases to determine the extent to which they match.
If a matching case is not found by matching on a child SSN, the match routine then attempts to match on an adult SSN/participant type and child name to find a matching case in the other state. If the adult SSN/participant type and child name search identifies a corresponding case in the other state, the program compares case data and participants between the two cases to determine the extent to which they match.
If no corresponding case is found in the other state, your state's case is flagged as a case mismatch. This designation means that your state presumes it has a case in common with another state, but that the other state does not appear to have a corresponding case on its extract file.
For cases that match, the program compares the participants to determine the number of participants that match between the two cases. The program determines the number of adults that your state submitted, the number of children that your state submitted, the number of adults that the other state submitted, the number of children that the other state submitted, the number of adults that matched between the two cases and the number of children that matched between the two cases. The program compares the participant data for the NCP and the CP on both cases to determine if the NCPs and CPs match. If the CPs on both cases match, the CP Match Indicator in the reconciliation response file is set to "Y", otherwise it is set to "N". If the NCPs on both cases match, the NP Indicator is set to "Y", otherwise it is set to "N".
When the program finishes the comparison of case data and participants for matching cases, it will write a response record to the reconciliation response file for your state. This response record transmits all data from the extract matching program to your state. Each state will only receive one reconciliation response file which will include data from both the regular ICR match routine and the Reason Code 01 rematch routine. The data includes, if applicable, a series of Reason Codes categorizing the extent of the match and any critical data discrepancies identified by the matching program, and the number of participants that matched between the two cases.
Section 3.2 provides an explanation of each of the Reason Codes returned in the response record. The Reason Codes clearly define the following conditions:
- All data match between the two cases,
- The matching program failed to find any case in the other state's extract file based on a search using your state's Other State Case ID and based on a search for a child in common, or an adult participant SSN/participant type and child name in common between the two states,
- A case with a child and/or adult in common was found in the other state, but the Other State Case ID from your state does not match the Case ID in the other state. The number of adults and children that match can be checked to determine the extent to which all the participants matched between the two cases,
- Data discrepancies exist between the two cases involving case and participant data elements.
The information from the match is loaded into the output record and returned to the your state via CONNECT:Direct. The record format for the reconciliation matching results being returned to your state is shown in Appendix C, ICR Reconciliation Matching Results File Record Format.
Table of Contents
3.2 Working with Reconciliation Matching Results
This section provides an explanation of the Reason Codes associated with the reconciliation matching results and the suggested next action for reconciling interstate cases.
Upon receipt of the response file from the ICR match routine, state staff from participating states can evaluate discrepancies indicated by the associated Reason Codes to determine what the appropriate next actions should be. The information returned to participating states should allow your systems to update some of the information that is not consistent between the two states. Full use of other available tools such as CSENet could be utilized for those instances in which an action needs to be taken by another state, such as providing closure reasons or case initiation.
Figure 2 shows high-level courses of action for states to reconcile their interstate cases, based on different match-mismatch scenarios in Initiating and Responding States.
Figure 2. ICR Response File Processing
As the figure shows, there are four possibilities for case matching/mismatching.
- The case is known to both the initiating and responding state and the data is identical. This scenario will appear as Reason Code 00 in the response file, as explained in section 3.2.1 below,
- The case is known to both the Initiating and Responding State and the data is mismatched,
- The case is known in the Initiating State, but unknown or closed in the Responding State, or
- The case is unknown or closed in the Initiating State, but known to the Responding State.
The ICR matching routine will match each participating state's extract of interstate cases against the extract of all other participating states and the FCR-derived extracts for non-participating states. As detailed in section 3.1.2, the matching process runs through several routines to determine the extent to which the case data and participants in your state match the case data and participants in the other state.
When the matching routine is completed, it writes a response record to the reconciliation response file for your state (See Appendix C, ICR Reconciliation Matching Results File Record Format). The data also includes the number of participants that matched between cases and a series of Reason Codes that categorize the extent of the match and any critical data discrepancies. (The response Reason Codes are presented in chart form in Appendix B).
Data discrepancies between matched cases involve the following data elements. A specific Reason Code will be assigned to each data discrepancy:
- Case ID (Reason Codes 01-02),
- FIPS Code (Reason Code 03),
- Case Status (Reason Codes 04-05),
- Case Match, Participant Mismatch (Reason Code 06), and/or
- Participant SSN Mismatch (Reason Codes 07 - 08).
It is important to understand that:
- Reason Codes will be returned in association with each participant on the submitted case,
- Multiple Reason Codes will be returned on each individual participant record when multiple discrepancies have been identified on a single case, and
- Case data will be redundantly displayed in each participant record associated with the case in question.
Following are descriptions and suggested next actions for the case and participant-level discrepancy Reason Codes to be returned by OCSE for the Interstate Case Reconciliation project. The issue of keeping interstate cases synchronized after a national ICR has not yet been resolved. However, the current recommendation for keeping interstate cases synchronized would require the reconciliation process to be run again.
The suggested next actions represent basic guidelines for automated processing of reconciliation response data, and suggestions for worker intervention as required. These are only suggestions; each participating state will determine the extent to which reconciliation response data is automatically processed in your state. For the purposes of suggesting automated actions, the suggested next action text refers to the Reconciliation Response program as a generic term covering any automated program(s) developed by states to process the ICR reconciliation matching results.
States should consider developing programs to automatically update corrected Other State Case IDs and SSNs in your systems. Correcting these discrepancies in an automated manner provides states with the immediate benefits of enabling the exchange of data through CSENet and the processing of payments through EFT/EDI, as well as getting the participant registered on the FCR.
Table of Contents
3.2.1 Reason Code 00 - Case Data Matches and This Participant Matched
Your Other State Case ID, Other State FIPS Code, and Case Status match the Case ID, FIPS code, and case status of the other state's case. Also, the participant in this record was found in the other state's case.
Note: If Reason Code 00 is returned from an FCR-derived match, you should keep in mind that the FCR does not maintain interstate data. If you receive back a "Y" in the FCR-Supplied Indicator field, this indicates that the other state's FCR data was used for matching. You should assign a lower confidence level to the other state's case actually being an interstate case because the FCR does not maintain interstate identifiers. Therefore, it is possible that an interstate case from your ICR extract could match to an in-state case from the FCR for a non-participating state.
Suggested Next Action: As Initiating State or as Responding State:
Step 1: The Reconciliation Response program checks the number of your case participants that matched participants in the other state's case when processing a Reason Code 00 record.
When the Number of Adults from Your State equals the Number of Adults Matched and the Number of Children from Your State equals the Number of Children Matched, then no further action is required, since the case data and participants are synchronized between the two states. The Reconciliation Response program can skip to the first participant record for the next case in the response file.
If the above sets of fields do not equal each other, then the case data are still synchronized between the two states, but a participant from your case did not match to the participants from the other state's case. The Reconciliation Response program continues to process the response file records for your case until it finds the Reason Code 06 record associated with the non-matching participant. See section 3.2.7 for Reason Code 06, Suggested Next Action.
It is also important to remember that Reason Codes 07 and 08 are participant-level discrepancies and may be received for a participant in the case even though Reason Code 00 is received at the case level. See sections 3.2.8 and 3.2.9 for Reason Codes 07 and 08.
Keep in mind that case structures may vary from state to state, so the number of mismatched participants may not necessarily mean there is a case discrepancy. You also receive a Y/N indicator that tells you whether the CP and NCP matched between the two states. If all case participants match, but the CP Match Indicator or the NP Match Indicator are set to 'N', use caution here since this may reflect that the wrong case was matched. The match may be with a change of custody case for the child(ren).
Table of Contents
3.2.2 Reason Code 01 - Could Not Find a Matching Case in the Other State
The ICR matching process could not find a matching case in the other state file. The ICR matching process attempts to find a case in the other state file by matching on Other State Case ID. If the Other State Case ID match fails to find a case in the other state's file, then the ICR matching process attempts to find a child in common between your case and a case in the other state's file by matching the child's SSN. If no child in common is found in the other state's file, the ICR matching process then attempts to find a matching case by matching the adult's SSN and participant type and Child Name in common. If a matching case cannot be found, the response file returns this Reason Code indicating that the other state did not submit a case that matches the case in your state.
Note: If the FCR-Supplied Indicator on this record = Y, then the ICR matching process attempted to match your state's case against an FCR-derived extract for the other state. The other state may have a matching case, but it may not be registered on the FCR.
Suggested Next Action:
As Initiating State:
Step 1: The worker analyzes the case to determine whether it should remain an interstate case, or whether a one-state action should be pursued on the case.
Step 2: If the case is to remain an interstate case, re-send the CSENet transaction/UIFSA forms to have the other state initiate a new case. Or, if a one-state action is to be pursued, close out interstate activity on the case and make it an in-state case.
As Responding State:
Step 1: If the family no longer requires child support services from your state, initiate the case closure procedure in accordance with Federal case closure criteria.
Table of Contents
3.2.3 Reason Code 02 – Case ID Mismatch, Case Found by Matching a Child and/or Adult Participant in Common
The ICR matching process found a case in the other state's file by matching on an adult and/or a child in common between your state's case and the other state's case. However, there is a discrepancy between the Other State Case ID that your state submitted and the case ID for the other state's case. The case ID submitted by the other state for its case can be found in the Case ID (From Other State) field, and the number of the case participants that matched can be found in the Number of Adults Matched and Number of Children Matched fields.
Suggested Next Action: As Initiating or as Responding State:
Step 1: Determine the threshold of matching participants necessary to support automated update of Other State Case ID (e.g., perform an automated update only if both adult participants in your case matched to adult participants in the other state's case, and at least 75% of the children on your case matched to children on the other state's case). States should also consider whether their case was matched against an FCR-derived extract file (FCR-Supplied Indicator = Y) before performing an automated update within their system.
Step 2: The Reconciliation Response program interrogates the Number of Adults Matched and the Number of Children Matched fields. If the matching participant threshold is met, then the Reconciliation Response program automatically updates the Other State Case ID in your state's case with the Case ID (from Other State).
You also receive a Y/N indicator that tells you whether the CP and NCP matched between the two states. If all case participants match, but the CP Match Indicator or the NP Match Indicator are set to 'N', use caution here since this may reflect that the wrong case was matched. The match may be with a change of custody case for the child(ren).
If the matching participant threshold is not met, the Reconciliation Response program automatically generates a CSENet CSI R FRINF request transaction to request all available data on the other state's case and participants.
Step 3: Upon receipt of the CSI P FSINF provide transaction, the worker analyzes the other state's case data to determine if the two cases matched. If so, the worker updates Other State Case ID in your state's case.
Table of Contents
3.2.4 Reason Code 03 – Your Other State FIPS Code Does Not Match Code from Other State
Positions 3 - 5 (FIPS county code) of the FIPS code for the other state's case do not match positions 3 - 5 of the Other State FIPS Code that your state submitted. The FIPS code submitted by the other state can be found in the FIPS Code (from Other State) field. A verification indicator for the Other State FIPS Code submitted by your state can be found in the Other State FIPS Code Verification Indicator. A second verification indicator for the FIPS Code (from Other State) field submitted by the other state for its case can be found in the FIPS Code Verification Indicator (from Other State).
Suggested Next Action: As Initiating State or as Responding State:
Step 1: Automatic updates of the FIPS County Codes for other states are not recommended. FIPS County Code discrepancies, because of ongoing problems with county FIPS Codes, should be addressed as a lesser priority in reconciling ICR discrepancies. Automation may be used to:
- Sort cases with FIPS County Codes returned from the other state as '000'. These cases need to be reviewed as to how they should be reconciled. Note: Several states work all interstate cases in a central office and request that other states use '000' as the local code.
- Identify cases in your state's system where no FIPS County Code is recorded for the other state. The FIPS County Code obtained on the ICR results file may help you work the case in the other state.
Table of Contents
3.2.5 Reason Code 04 – Your Case is Open, Matches to Closed Case in the Other State
The Case Status in your state indicates that your state's case is open; however, the matching case submitted by the other state is closed.
Suggested Next Action:
As Initiating State:
Step 1: The worker analyzes the case to determine whether it should remain an interstate case or whether a one-state action can be pursued.
Step 2: If the case is to remain interstate, send CSENet transaction/UIFSA forms to have the other state initiate the appropriate interstate action on the case. Or, if a one-state action is to be pursued, close out interstate activity on the case and make it an in-state case.
As Responding State:
Step 1: If the family no longer requires child support services, initiate the case closure procedure, in accordance with Federal case closure criteria (e.g., by generating an MSC P GSC14 case closure notice provide transaction to the Initiating State through CSENet.
Table of Contents
3.2.6 Reason Code 05 - Your Case is Closed, Matches to Open Case in the Other State
The Case Status in your state indicates that your state's case is closed; however, the matching case submitted by the other state is open.
Suggested Next Action: As Initiating State or as Responding State:
None required. It is up to the state with the open case to determine the next appropriate action to take on their case.
Table of Contents
3.2.7 Reason Code 06 - This Participant Was Not Found in the Other State Case
The participant was not found in the other state's case. Your state's case was matched against the other state's case; however, this participant on your case did not match any of the participants on the other state's case.
Suggested Next Action: As Initiating State or as Responding State:
Step 1: Determine participant criteria supporting the automated generation of a CSI request to receive more case/participant data from the other state (e.g., it may be more important to resolve this discrepancy when your CP or NCP was not found on the other state's case as opposed to a child not being found, particularly a child over the age of majority).
Step 2: Based on meeting the above criteria, the Reconciliation Response program generates a CSENet CSI R FRINF request transaction to the other state to request all available data on the other state's case and participants.
Step 3: Upon receipt of the CSI P FSINF provide transaction, have the worker analyze the provided data to determine if this participant in your state's case requires correction or update in your state system.
Table of Contents
3.2.8 Reason Code 07 - An SSN was Provided for this Participant by the Other State
Your state's case was matched against the other state's case, but you did not provide an SSN for this participant. An SSN for this participant in your state was provided on the corresponding interstate case in the other state. A verification code is also provided for this SSN.
The Social Security Administration provides verification of SSN/Name combinations. The verification process used for FCR is the same process used for ICR. The difference is that with the FCR, name, SSN, Date of Birth and Sex Code are passed to the verification process, but with the ICR, only the name and SSN are passed to the verification process. The verification process will determine whether the combination is verified based on the information provided to the process.
Suggested Next Action: As Initiating State or as Responding State:
Step 1: If the provided SSN is for a CP or an NCP, check to make sure the CP and NCP indicators are set to 'Y'.
Step 2: If the Other State SSN Verification Indicator is set to "Y", automatically update your system with this participant's SSN.
Table of Contents
3.2.9 Reason Code 08 – A Different SSN was Provided for this Participant by the Other State
Your state's case was matched against the other state's case, but the SSN you provided for this participant did not match the SSN provided for this participant in the other state. The different SSN known to the other state can be found in the SSN (from Other State) field. A verification indicator is provided for the SSN you submitted and for the SSN provided by the other state.
The Social Security Administration provides verification of SSN/Name combinations. The verification process used for FCR is the same process used for ICR. The difference is that with the FCR, name, SSN, Date of Birth and Sex Code are passed to the verification process, but with the ICR, only the name and SSN are passed to the verification process. The verification process will determine whether the combination is verified based on the information provided to the process.
Suggested Next Action: As Initiating State or as Responding State:
Step 1: Check to make sure the CP and NCP indicators are set to 'Y' if you are considering automatically updating a different SSN for a CP or NCP.
Step 2: If the Submitting State's SSN Verification Indicator is set to "N" and the Other State SSN Verification Indicator is set to "Y", either update the SSN in your system or add the Other State SSN as an Alias/Additional SSN and submit to the FCR as an Additional to obtain a full verification for that SSN.
Table of Contents
3.3 Frequently Asked Questions
How will case ID formatting discrepancies be handled? Some states use leading zeroes in the case ID field and other states do not.
States should supply their case ID and the Other State Case ID in the same manner as sent to the FCR and on CSENet transactions. The ICR matching process will identify case ID discrepancies when a state stores Other State Case ID in a format that is different from the format used by the other state for their own case ID. It is necessary to correct this discrepancy because the other state may reject CSENet transactions where the Other State Case ID is not formatted according to their standards. As a general rule, a state should always store Other State Case ID in the same format that was received from the other state.
What is the format for case IDs?
All case ID fields should be alphanumeric and left-justified with trailing spaces.
Will it be possible to receive more than one Reason Code per case?
Yes. For example, you could receive a Reason Code 02 and a Reason Code 03 where you had both an incorrect Other State Case ID and an incorrect Other State FIPS Code for that case in your state system.
How will name consistency problems (e.g., Jr. vs. Junior) be handled?
The other state's participant name is supplied, but it should be considered for informational purposes only. There is no hierarchy between the states as to whose name or convention is preferred - your state's or the other state's. The name or convention verified by the FCR should be the accepted name.
Will the ICR program automatically close cases?
No
Will the FCR extract include closed cases?
Yes, these cases are not physically deleted from the FCR and will be included in the FCR extract of any non-participating states.
Will the FCR extract contain rejected cases?
No.
How will the ICR deal with Family Violence cases?
Family Violence (FV) is not a factor in populating state ICR extract files. States can include interstate FV cases in their ICR extracts. However, Family Violence is a factor in the FCR and disclosure of FCR case data is prohibited for FV cases. Therefore, when the ICR extracts data from the FCR for states that are not participating in the ICR program, those FCR-derived extracts will not include FV cases.
How far back should we populate our ICR extract?
As far back as you can go in your current, active database. States should not include archived cases or pre-conversion cases.
Does Member ID refer to the participant number or to the case ID?
Member ID refers to participant number.
Is there a difference between a closed IV-D case and a closed interstate case?
Yes. As interstate activity may be recorded as a part of a case, the interstate portion of a case may be closed while the IV-D case remains open as an intrastate case. Closed interstate cases refer to the cases where the interstate action or activity is closed, whether or not the IV-D case remains open. Normally if the IV-D case is closed, the interstate portion of the case is also closed.
Table of Contents
3.4 Common Terms and Definitions
This section provides a list of definitions of common terms used throughout this document.
Closed Interstate Case
For purposes of Interstate Case Reconciliation, a closed interstate case can occur when a case remains open in the Initiating State as an in-state case, but it no longer has an interstate connection to the other state. When the Initiating State has closed out all interstate activity on a case that remains an open in-state case on their system, it should be reported to the ICR as a closed interstate case. This holds true as long as all interstate data concerning the other state is still retained on the Initiating State’s system. Likewise, when the Responding State has closed out all interstate activity on a case that remains open as an in-state case due to a request for IV-D services, it should be reported to the ICR as a closed interstate case.
The ICR match process will not return matches between closed interstate cases in two different states. The ICR will not return mismatches where a closed case in one state could not be found in the other state.
Case ID
The Case ID is the identifier assigned to a case for reporting purposes to the Federal Case Registry.
Initiating State
The Initiating State is the State or county court, or administrative agency, which sends a request for action to another jurisdiction in interstate child support cases. The requested action can include a request for wage withholding or for review and adjustment of existing child support obligations. In cases where a State is trying to establish an initial child support order on behalf of a resident custodial parent, and they do not have Long Arm Jurisdiction (i.e., they cannot legally claim personal jurisdiction over a person who is not a resident), they must file a two-state action under the UIFSA guidelines.
Interstate Case for ICR Purposes
The following are definitional elements to assist in determining which cases should be submitted as interstate cases for ICR purposes:
- A case requested by one state for another state to open and maintain for purposes of paternity or order establishment, and/or enforcement.
- The state requesting this action is the Initiating State. The other state is the Responding State.
- Both states maintain identical cases on their systems, and both states would submit the interstate case for ICR purposes.
- Both interstate open and closed cases are submitted for ICR purposes. Neither long-arm nor limited services cases are submitted for ICR purposes.
- Neither international cases nor tribal cases are submitted for ICR purposes.
Other State
The Other State is the state with which your state believes it shares an interstate case.
Responding State
The court or administrative agency with jurisdiction over a noncustodial parent or child support order on which an Initiating State has requested action. The Responding State receives pleadings or an electronic or form request from the Initiating State to take an action in a case. The Responding State may provide a single service for the Initiating State, such as service of process, or it may provide all the services needed, from establishing an order to enforcing it, using the Responding State’s child support laws and procedures.
Submitting State
Each state that submits an extract file is known as the Submitting State.
