(A) This rule describes the responsibilities of the child support enforcement agency (CSEA) to use the child support enforcement network (CSENet) in the processing of interstate cases to the greatest extent possible.
(B) CSENet is an electronic communications network developed by the federal office of child support enforcement (OCSE) that transmits and receives child support information to and from other states in a standardized format. A CSENet user is able to initiate and respond to case activities in other states for:
(1) Location of respondent;
(2) Establishment of paternity, and support establishment; and
(3) Enforcement, and collection activities as well as to transfer interstate case information between states.
(C) CSENet standard transactions consist of three parts:
(1) Function codes that identify the function being performed. The function codes are:
(a) COL (collection);
(b) CSI (case status information);
(c) ENF (enforcement);
(d) EST (establishment);
(e) LO1 (quick locate);
(f) MSC (managing state cases); and
(g) PAT (paternity).
(2) Action codes that identify the action being taken. The action codes are:
(a) A (acknowledgment);
(b) C (cancel);
(c) M (reminder);
(d) P (provide);
(e) R (request); and
(f) U (update).
(3) Reason codes, which are five-letter codes, define the specific reason for the transaction.
(D) The CSEA shall use CSENet to take the following actions:
(1) Request location information on a putative father or absent parent from a state that has CSENet quick locate capability with Ohio. A CSENet "Quick Locate" (LO1) transaction shall be used for this purpose.
(2) Request case information, including support order information, from a state that has CSENet case status information capability with Ohio. A CSENet "Case Status Information" (CSI) transaction shall be used for this purpose.
(3) Request the establishment of paternity from a state that has CSENet paternity capability with Ohio. A CSENet "Paternity" (PAT) transaction shall accompany a Uniform Interstate Family Support Act (UIFSA) petition for this purpose.
(4) Request the establishment of a support order from a state that has CSENet establishment capability with Ohio. A CSENet "Establishment" (EST) transaction shall accompany a UIFSA petition for this purpose.
(5) Request the enforcement of a support order from a state that has CSENet enforcement capability with Ohio. A CSENet "Enforcement" (ENF) transaction shall accompany a UIFSA petition for this purpose.
(6) Transmit case status and information to a state that has CSENet managing state cases capability with Ohio. A CSENet "Managing State Cases" (MSC) transaction shall be used for this purpose.
(E) When a CSEA receives an incoming CSENet transaction, it shall take the actions required by the transaction within thirty days.
R.C. 119.032 review dates: 11/01/2016
Promulgated Under: 119.03
Statutory Authority: 3125.25
Rule Amplifies: 3115.28, 3125.03, 3125.07, 3125.08
Prior Effective Dates: 1/1/98, 3/1/03, 9/1/05