The Support Order Tab in the E-IWO Import Feature

The Support Order tab shows a list of imported e-IWO XML files. Here, you can approve or reject selected and filtered files. This tab includes an Export button that you can use to export and populate the data from the grid in an employer-record CSV file. All of the visible fields in your chosen view are included in the export file.

You can click Problems to open the Problems panel to view potential errors or warnings that are related to the files. Like The Overview Tab in the E-IWO Import Feature, the Support Order tab includes filtering and view options. You can modify some fields before you save and publish your changes. For the fields that you can modify, see the descriptions in the following table.

When you are finished modifying any records, you can click Publish. If you click Publish but you don’t click Save, the application shows a message indicating the unsaved records and that the unsaved records won’t be included in publishing. Furthermore, you can publish entries that are approved. After you publish a record, you cannot modify that record.

Column descriptions in the Support Order tab
Label	Description
EIWO File Name	The file name of the XML file that you upload from the e-IWO system. Field can’t be modified.
FEIN (EIWO)	The Federal Employer ID Number that is included in the document batch header. Field can’t be modified.
Doc Type (EIWO)	The e-IWO file determines the doc type. The Doc Types are: ORG: Original or New. The file is a new record and doesn’t have a match in the database. Fees and disposable-income items aren’t part of e-IWO, and you must add these items manually. AMD: Amended. The file contains a change to an existing, active support order for that jurisdiction and case number. When the amended order is published, the E-IWO Import feature adds an end date to the existing order and create a new order with updated dates (Effective From, Court Order, and Court Order Received) as specified in the Support Order tab. TRM: Terminated or Stop. This indicates a termination of an existing, active Support order for that jurisdiction and case number. E-IWO Import adds an end date to the existing, matched record, using the date in the Effective to Date (stop) column. LUM: Lump Sum. This indicates that it is Lump Sum garnishment. This is only partially supported in the E-IWO Import feature. The e-IWO file is imported, but it is treated as a new Current Child Support order with `-LUM` added to the end of the case number, but only in Dayforce: it is stripped from the Acknowledgement File. This addition prevents any conflict with existing case numbers. The amount isn’t annualized and de-annualized but carries over directly from the e-IWO file. The Duration defaults to `Use for Single Payroll Deduction`. You must enter an Effective To date.
Employee SSN	This is the Social Security Number of the employee in the e-IWO file. This field is used to find the employee within the Dayforce database. This field can’t be modified.
Employee No.	The employee number is retrieved from the employee profile in People based on the Employee SSN. If the Employee No. column is blank, the Employee SSN wasn’t found in Dayforce. This field can’t be modified.
Employee Last Name	If the employee number is populated, the employee last name is pulled from the Dayforce database associated with the Employee SSN. If the employee number isn’t populated, the employee last name is pulled from the e-IWO file. This field can’t be modified.
Employee First Name	If the employee number is populated, the employee first name is pulled from the Dayforce database associated with the Employee SSN. If the employee number isn’t populated, the employee first name is pulled from the e-IWO file. This field can’t be modified.
Employee Middle Name	If the employee number is populated, the employee middle name is pulled from the Dayforce database associated with the Employee SSN. If the employee number isn’t populated, the employee middle name is pulled from the e-IWO file. This field can’t be modified.
DOB	Date of birth. If the employee number is populated, the employee’s date of birth is pulled from the Dayforce database associated with the Employee SSN. If the employee number isn’t populated, the employee date of birth is pulled from the e-IWO file. This field can’t be modified.
Publish Status	Defaults to `NOTPUBLISHED` until some action is taken on the record. Populated with `Accept` when the transaction is saved with no errors and is published, which writes the record to the Dayforce database. This field can’t be modified.
Accept / Reject	An indicator showing which of the following conditions, or states, that the file is in: Accept: You can save the record if no errors are present. Reject: You can save the record as rejected if errors are present. The required Reject Reason Code field is available. Pending: You can save the record as pending if errors are present or not. Blank or Null: You can save the record whether errors are present or not. When you save a record with the Accept condition, you can publish that record, which writes the record to the Dayforce database.
Reject Reason Code	If the Accept/Reject field is saved as Reject, this field is required (for blank, Accept, or Pending, this field cannot be changed). The Reject Reason Code is a drop-down with the following options as provided by the Federal OCSE: B: Name mismatch D: Duplicate IWO M: IWO received from multiple states N: NCP no longer at the employer O: Other reason S: Employee is in a suspended status at the employer U: NCP not known to employer W: Incorrect FEIN received for employee X: Employer couldn’t electronically process this record Z: Termination cannot be processed; no current IWO in place
Reject Reason Data	Data that corresponds with the Reject Reason Code. Keep the following two tips in mind: If the Reject Reason Code is M (IWO received from multiple states), the Reject Reason Data column must be a valid two-letter state or territory abbreviation. For example, `OR` for Oregon or `PR` for Puerto Rico. If the Reject Reason Code is W (Incorrect FEIN received for employee), the Reject Reason Data column must contain the FEIN number (entered in 9 digits).
Error / Warning	This will list the errors and warnings associated with each IWO after comparing to Dayforce for the applicable FEIN associated with the SSN identified. See E-IWO Feature Errors and Warnings.
Effective to Date (stop)	This is the date that the Income Withholding Order should be stopped. It is only populated if the Document Type for the order is TRM (termination).
Effective From Date (start)	This is the date that the Income Withholding Order should be started. It is only populated if the Document Type for the order is ORG (original or new) or AMD (amended).
Issuing Agency	This is the State or Territory that issued the order.
Case Number	This is the Case Number of the Income Withholding Order. In the XML file, this is called the `CaseIdentifier`.
Docket Number	This is the Docket Number of the Income Withholding Order. In the XML file, this is called the `OrderIdentifier`.
Court Order Date	This is the Date the Income Withholding Order was issued. In the XML file, this is called `Document Date`.
Court Order Receive Date	The date that the file is imported, transformed, or processed in Dayforce.
Payee	This is the State Disbursement Unit, or SDU, of the Payee. The SDU is the name of the individual, tribunal, court, or tribal child support enforcement agency that payments are required to be sent to. You can modify this field before saving and publishing.
FIPS	The `RemittanceFIPSCode` from the e-IWO file. This code is required for Illinois Support Orders.
12 Wks Arrears	Indicator of whether child support is in arrears for a period longer than 12 weeks. If the CCPA Withholding Rate is `45` or `35` in the imported XML file, this field is set to Y (true). If the CCPA Withholding Rate is `50` or `40` in the imported XML file, this field is set to N (false).
Support 2nd Fam	If the CCPA Withholding Rate is `50` or `45` in the imported XML file, this field is set to Y (true). If the CCPA Withholding Rate is `40` or `35` in the imported XML file, this field is set to N (false).
Curr Child Supp Amt	The Current Child Support Amount is calculated based on two factors – the Obligation Payment Frequency in the imported XML file and the Employee’s Pay Frequency. Obligation Payment Frequency and Employee’s Pay Frequency describes these options.
Child Support Name	The name is defaulted as Child Support. The field can be modified by the user.
Child Support Display Name	The name is defaulted as Child Support. The field can be modified by the user.
Child Supp Arrears Amt	The Child Support Arrears Amount is calculated based on two factors—the Obligation Payment Frequency in the imported XML file and the Employee’s Pay Frequency. Obligation Payment Frequency and Employee’s Pay Frequency describes these options.
Curr Spousal Supp Amt	The Current Spousal Support Amount is calculated based on two factors—the Obligation Payment Frequency in the imported XML file and the Employee’s Pay Frequency. Obligation Payment Frequency and Employee’s Pay Frequency describes these options.
Spousal Support Name	This field must not be blank. You can modify this field before saving and publishing.
Spousal Support Display Name	This field must not be blank. You can modify this field before saving and publishing.
Spousal Supp Arrears Amt	The Spousal Support Arrears Amount is calculated based on two factors—the Obligation Payment Frequency in the imported XML file and the Employee’s Pay Frequency. Obligation Payment Frequency and Employee’s Pay Frequency describes these options.
Curr Cash Med Supp Amt	This field isn’t supported in Dayforce. It should be added to Current or Arrears for either Child Support or Spousal Support at the discretion of the customer. The Current Cash Medical Support Amount is calculated based on two factors – the Obligation Payment Frequency in the imported XML file and the Employee’s Pay Frequency. Obligation Payment Frequency and Employee’s Pay Frequency describes these options.
Med Supp Arrears Amt	This field isn’t supported in Dayforce. It should be added to Current or Arrears for either Child Support or Spousal Support at the discretion of the customer. The Medical Support Arrears Amount is calculated based on two factors – the Obligation Payment Frequency in the imported XML file and the Employee’s Pay Frequency. Obligation Payment Frequency and Employee’s Pay Frequency describes these options.
Other Supp Amt	This field isn’t supported in Dayforce. It should be added to Current or Arrears for either Child Support or Spousal Support at the discretion of the customer. The Medical Support Arrears Amount is calculated based on two factors – the Obligation Payment Frequency in the imported XML file and the Employee’s Pay Frequency. Obligation Payment Frequency and Employee’s Pay Frequency describes these options.
Duration	The frequency with which the garnishment should be taken. This field must not be blank. You can modify this field before saving and publishing. See the following options: If the doc type is ORG or AMD, it should default to Ongoing Deduction. If the doc type is TRM, it should default to Court Order End Date Exists. If the doc type is LUM, it should default to Use For Single Payroll Deduction.
Total Calculated By Freq	This field shows the sum of the following amounts: Curr Child Supp Amt Child Supp Arrears Amt Curr Spousal Supp Amt Spousal Supp Arrears Amt Curr Cash Med Supp Amt Med Supp Arrears Amt Other Supp Amt If you modify any of these amounts, Dayforce recalculates them.
Calc Total On Order	The Calc Total On Order is output based on the Income Withholding Amount Frequency displayed for the Employee’s Pay Frequency. The Income Withholding Amount in the imported XML file is output for all four of the following: `B`: Bi-weekly (26 pay periods per year) `M`: Monthly (12 pay periods per year) `S`: Semi-monthly (24 pay periods per year) `W`: Weekly (52 pay periods per year) The amount for the Employee’s actual Pay Frequency is used on the Support Order tab for this field. Due to the calculation, the calculation might create a difference between the Total Calculated By Freq and the Calc Total On Order.
Custodial Parent Name	This is the combined first and last name of the Obligee on the XML Import File.
Last Modified User	This is the user that last updated and saved the record in the Support Order tab.
Last Modified Timestamp	This is the date and time that last updated and saved the record in the Support Order tab.

Obligation Payment Frequency and Employee’s Pay Frequency

The Obligation Payment Frequency in the imported XML file can be one of the following:

A: annually (1 pay period per year)
B: bi-weekly (26 pay periods per year)
M: monthly (12 pay periods per year)
Q: quarterly (4 pay periods per year)
S: semi-monthly (24 pay periods per year)
W: weekly (52 pay periods per year)
X: semi-annually (2 pay periods per year)

The Employee’s Pay Frequency in the imported XML file can be one of the following:

Weekly (52 pay periods per year)
Bi-weekly (26 pay periods per year)
Semi-monthly (24 pay periods per year)
Monthly (12 pay periods per year)

Support amounts are calculated using the Obligation Payment Frequency (the amount multiplied by the number of pay periods per year) then divided by the Employee’s Pay Frequency (number of pay periods per year) to arrive at the child or spousal support amount. The same calculation applies for child or spousal support arrears amounts.