Notice desk → qualify & cover. An administrator uploads the notice, reviews the read and creates the order; three engines score it; the administrator passes or fails pre-check; the approver qualifies; the enrollment engine covers the child — every stamp on one record.
A court, a state child-support agency or the federal NMSN process sends a medical support notice to the employer. In most organizations it is photocopied to payroll and benefits and tracked on a spreadsheet until somebody remembers the forty-day clock. Benefits Reimagined gives it two rooms that stay in sync: an administrator-only notice desk where the PDF becomes an order with its checks, its clock and its pre-check decision, and the platform's own Workflow and Enrollment, where the order is qualified and the child is covered — never out of sequence, never without a name and a date on the stamp.
"A court, state agency or NMSN process sends a medical support notice to the employer. An administrator uploads the PDF, reviews the read and creates a Medical Support Order. Engines score document validity and fraud; the administrator then passes or fails pre-check. A pass creates a benefit life event and usually a workflow instance. When the approver approves, the order becomes Qualified. Enrollment — the NMSN reason, matching dates and verified children — can then mark it Enrolled. The agency registry stores endpoints; the electronic send to the state is on the roadmap."
Nine steps from set-up to a covered child. Steps 1–6 and 9 live on the administrator-only notice desk; steps 7 and 8 happen in the platform's Workflow and Enrollment. Rows shaded amber are the two screens that store connections and lists rather than send anything — the page says so, and so does the product.
| # | Screen / room | Who | What they do |
|---|---|---|---|
| 1 | Set-up (before the first notice) | Implementation consultant | Seed the regions and child relationship codes; two benefit adjustment reasons flagged QMCSO and NMSN; the QMCSO child type with its age, student and disability rules; the federal SLA row; the legal-document type in the Document Center; an active workflow template for the life event; module access. Then pilot one order end to end. |
| 2 | Config · State Rules | Config consultant | One active rule per operating state for orders (and terminations) with the service-level days; the seeded federal NMSN row is read by the engines and protected from create, edit and delete on the screen. |
| 3 | Config · eSERV Config | Integration admin | Register each child-support agency: name, state, endpoint and port, real-time or batch, authentication method, PGP key, remote directory. A connection inventory — it sends nothing to the state. |
| 4 | Dashboard | Benefits leadership · operations | Read the four live tiles — total, validation pending, deficient, SLA breach — recent orders with the same view, pre-check and delete actions as intake, quick actions and Essential Insights. Not a decision screen. |
| 5 | Order Intake · upload & create | Intake admin | Pick the employee, one to four QMCSO children from the dependent record (or add the child in Employee Management first), type and subtype, the PDF; review the OCR read of Part A and Part B; save. The system stores the document once, writes the three check rows and sets the first status. |
| 6 | Order Intake · Pre-check | Qualification admin (same desk) | Open a pending or deficient order and PASS or FAIL pre-check. Fail closes the order. Pass on a Medical Support Order creates a benefit life event flagged for the order and, where a template applies, a workflow instance — the order shows Under Review. |
| 7 | Workflow (outside the desk) | Workflow approver | Approve the life event → the order becomes Qualified with the qualified date and flag. Reject → Not Qualified. The approver never sits in the notice desk. |
| 8 | Enrollment (outside the desk) | Employee · HR on their behalf | Enroll under the NMSN event: qualified order, federal subtype, event dates equal to the order's start and end, at least one verified child on the order → the engine marks the order Enrolled. |
| 9 | eSERV Transmit | Operations (planned) | Lists enrolled orders and reuses view, pre-check and delete. The send of Part B or an acknowledgment to the state is on the roadmap — not a go-live desk. |
These are the numbers a benefits administrator is held to. In Benefits Reimagined the service-level days live in a state-rules catalog — one row per operating state plus a seeded federal row for the NMSN — and every order carries its notice date, received date and clock from the moment it is saved.
Sources: 45 CFR 303.32, ERISA §609(a), 29 CFR 2590.609-2, DOL EBSA QMCSO guidance, DOL WHD Fact Sheet #30, OCSS e-NMSN program pages and 2025 Federal Register notices, as of September 2026. Informational only — confirm your procedures with counsel.
Follow a National Medical Support Notice from the Texas Office of the Attorney General for an hourly employee with two children — from the catalogs a consultant seeds, through intake, the engines and the administrator's pre-check on the notice desk, to the approver's stamp in Workflow and the enrollment that covers the children — then the two config screens, and the same desk serving a plant on another HRIS.
The order desk reads from configuration that other parts of the platform already own. Two benefit adjustment reasons — one flagged for court and agency orders, one for the federal notice — decide which life event a pass creates. A QMCSO child type on the dependent catalog carries the age, student and disability rules a named child must satisfy. A state-rules table holds the service-level days for each state's orders and terminations, with a seeded federal row for the NMSN that the interface protects from edits. The Document Center has a type for the legal PDF, the workflow engine has a template for the event, and the agency registry holds each child-support agency's connection details.
A notice that arrives before the federal row is seeded has no clock — the seed is part of go-live, not an option.
State rules are unique per state and rule type; the federal row cannot be created, edited or deleted from the screen, so the NMSN clock cannot be changed by accident.
The intake administrator selects the employee, picks one to four children from that employee's dependent record — or opens Employee Management in a new tab to add the child first — chooses the order type and subtype, and uploads the PDF. The document lands in the Document Center once, under its own type, and can never be attached to a second order. Optical character recognition reads Part A and Part B into a review screen: agency, case number, court or notice dates, custodial parent, each child, coverage types. The administrator corrects what the scan misread and saves; the start date must equal the notice date, the court order ID must be unique across the tenant, and a federal notice may not carry an issuing state.
Everything the engines will test is captured at intake — nobody re-keys the notice for payroll or the plan later.
The order list filters by employee, type and status; view, pre-check and delete sit on each row, and only pending or deficient orders can be deleted.
Saving an order writes three check rows. The document-validity engine confirms the notice names an agency and a case, that the dates are in order, that the employee and children are present, that the document level and format match the subtype, and that coverage is described. The fraud-detection engine compares each child's name, Social Security number and date of birth to the HR record, flags a subtype that contradicts the document, and searches for the same court order ID or the same case-and-children pair on another order. The pre-check engine confirms the employee was active and enrolled on the notice date, that the custodial parent's address is usable, and that the notice-to-received interval is inside the service level. Age failures set Not Qualified; fraud or document failures set Deficient; a past end date closes the order; otherwise it waits as Validation Pending for a person.
An order is never qualified by a clean scan. The engines score; the administrator passes or fails; the approver qualifies.
Athena on this desk explains why a check failed and which record to fix, and drafts the note — it does not pass or fail an order.
A pass creates a benefit life event flagged for the order and, where the template applies, a workflow instance; the order shows Under Review until the approver acts. Approval writes Qualified, the qualified date and the flag the plan relies on; rejection writes Not Qualified. Neither enrolls anyone. Enrollment is its own step with its own conditions: the adjustment reason must be the NMSN reason, the order must be Qualified with the federal subtype, the event's start and end dates must equal the order's, and at least one selected child must be on the order's dependent-verification record. Only then does the enrollment engine mark the order Enrolled — and the premium becomes a permitted mid-year deduction beside the rest of the employee's elections.
The child is covered exactly once, under exactly the dates the order states — and the record shows who allowed it.
Because payroll and enrollment share the platform, the withholding test and the pre-tax deduction use the same election the plan sees.
State Rules is the per-state service-level registry: one active row per state for orders and, where used, terminations, chosen from the platform's region list and unique per state and rule type. Create uses the days to cap an NMSN end date; pre-check and the dashboard's breach tile use them to count the clock. The federal NMSN row is seeded at implementation and the screen refuses to create, edit or delete it, so the federal clock cannot change by accident. eSERV Config is the agency connection registry — enabled flag, agency name and state, endpoint and port, real-time or batch, authentication method, token or credentials, PGP key and remote directory. It persists the connection and nothing more: the transmit desk lists enrolled orders, and the send itself is on the roadmap.
A client hears 'connection inventory', not 'live state feed' — and the clock the auditor asks about is the one the engines actually read.
Due-date notification fields exist on the state rule and are not yet consumed; the dashboard's breach tile is the live signal.
Child-support agencies find employers through new-hire reporting, so a notice can name an employee at any entity on any payroll. The order desk reads the employee, the employment status, the dependents and the elections from the Benefits Reimagined data model. On SAP SuccessFactors Employee Central those fields are live; for an acquired plant on Workday, a division on UKG, or payroll on ADP, Dayforce or Paycom, the HRIS Sync control plane fills the same canonical fields and IntelliMap shortens the mapping — so the fraud engine compares the notice to the same record regardless of the system behind it.
A merger or a payroll change should not mean a second mailroom for court orders.
The agency registry is per state, not per HRIS — an Oregon notice for a Workday employee and a Texas notice for a SuccessFactors employee follow the same path.
Nine rules a benefits administrator should know before the first notice. Each is enforced by the engines, the server or the gate — not by a checklist — and each says plainly what the platform does and does not do.
| Rule | What the system does | What it means for you |
|---|---|---|
| An administrator's app | The desk admits platform administrators and users with header access; everyone else is routed to Employee Home. | No employee self-intake — do not promise it. |
| Type is Medical Support Order | Orders persist as a Medical Support Order or a Terminated order; QMCSO is the qualified outcome — a status and a flag with a date. | The record shows when, and by whom, a notice became qualified. |
| NMSN is federal | A federal notice carries no issuing state and the federal document format; a court or agency order needs a state and the state format. | The wrong document level fails create — before the clock starts. |
| Start date = notice date | The server validates it; the end date cannot precede it and an NMSN end date is capped by the federal service level. | The coverage window on the order is the window the notice states. |
| One PDF, one court order ID | A document is bound to one order; a court order ID is unique across the tenant. | Duplicate paper is caught at save, not at enrollment. |
| Pre-check waits for a person | The three engines write their rows and leave pre-check Pending; only an administrator's PASS or FAIL moves it. | A clean scan never qualifies an order on its own. |
| PASS starts a life event, not coverage | Pass creates the event and usually a workflow instance; approve writes Qualified; reject writes Not Qualified. | Coverage comes later, after Qualified — never from the pre-check click. |
| Enrollment dates must match exactly | The gate needs the NMSN reason, a qualified federal order, event dates equal to the order's, and a verified child. | A one-day slip blocks plan create — fix the order or the event, not the rule. |
| Config is not a send | The agency registry stores connections; the transmit desk lists enrolled orders; the electronic send is on the roadmap. | Part B and acknowledgments go through the agency's portal or by mail today. |
Seven screens on the notice desk — Dashboard, Order Intake, the order view, State Rules, eSERV Config, eSERV Transmit — and two rooms outside it that act on the same order. The amber tags mark what is on the roadmap rather than in the release.
Leadership's daily view: four live tiles — total, validation pending, deficient, SLA breach — a welcome banner, quick actions to intake, state rules and the transmit list, Essential Insights, and recent orders with view, pre-check and delete.
The inbox and the factory: employee, one to four QMCSO children from the dependent record, type and subtype, the PDF into the Document Center under its own type, OCR review of Part A and Part B, then create — with intake insights from BR Intelligence beside it.
The orders table filtered by employee, type and status; view, pre-check and delete per row. Pre-check is PASS or FAIL on a pending or deficient order; delete only on those two statuses.
One order, six tabs: details, the document (opens in Document Management), pre-check with the three engine rows, dependent verification, benefits (read-only once enrolled) and the full history with notes.
Per-state service-level registry for orders and terminations, unique per state and rule type, with the seeded federal NMSN row protected from edits; insights from BR Intelligence.
The agency connection registry — name, state, endpoint, port, real-time or batch, authentication, PGP key, remote directory — persisted for the day the send is wired.
Lists every enrolled order and reuses view, pre-check and delete. The Part B and acknowledgment send is on the roadmap; the screen is not a go-live send desk.
Outside the desk but on the same order: add or edit the QMCSO child on the dependent record in a new tab; open the legal PDF where the plan can find it.
Outside the desk, on the same order: the approver's decision writes Qualified or Not Qualified; the enrollment gate writes Enrolled only when reason, subtype, dates and a verified child agree.
Payroll vendors treat a medical support notice as a garnishment; benefits outsourcers treat it as a service ticket. Here is what changes when it is a record in the platform that enrolls the child.
| Moment | Mailroom, payroll vendor or outsourcer | Benefits Reimagined QMCSO |
|---|---|---|
| A notice arrives | Mailroom → photocopy → payroll and benefits inboxes. | Uploaded once; OCR reads it; the order exists with its clock before lunch. |
| Is it the right child? | Someone eyeballs the name against the census. | Fraud engine compares name, SSN and date of birth to the HR record and flags duplicates. |
| Is it qualified? | A judgment call in an e-mail thread. | Validity engine checks §609(a) elements; an administrator passes; an approver qualifies — all recorded. |
| The forty-day clock | A calendar reminder, if one was set. | Service-level days per state on the order; pending, deficient and breach counts on the dashboard. |
| Enrolling the child | Benefits keys it in and hopes the dates match payroll. | Enrollment gate: qualified order, matching dates, verified child — or it does not enroll. |
| The deduction | Payroll estimates disposable earnings from a second system. | Same platform: withholding tested on the real earnings; premium is a permitted mid-year change. |
| The employee leaves | Someone remembers to tell the agency. | Termination blocks new orders and sits on the record with the continuation choice. |
| An auditor asks | Which folder? Which year? | The order history: intake, engine rows, decisions, approval, enrollment, closure. |
Order Intake, State Rules and eSERV Config each carry insights from BR Intelligence, and the platform's Athena for administrators sits beside them. It reads the engine rows, the state rules and the order history, explains a deficiency in plain language, points to the record that fixes it, and drafts the note — while the pass, the approval and the enrollment stay with people.
A notice becomes an order with an employee, children, dates and a clock the moment it is saved — not a photocopy in two inboxes.
Document validity, fraud detection and pre-check run on every order and leave their evidence on it.
An administrator passes, an approver qualifies, the enrollment engine covers — three people, three stamps, one history.
Twenty and forty business days from the notice date, per state, counted on the dashboard.
The premium is a permitted mid-year change on the same platform that tests the withholding limit.
Intake, checks, decisions, approval, enrollment and closure on the order — for the agency, the plan and the auditor.
The same two rooms, told the way administrators live them. Consultants seed the desk, intake administrators run it, approvers qualify in Workflow, employees enroll — the same roles whether the employer is one company or a shared-services center handling notices from every county court and state agency.
Bring one redacted NMSN or court order. We'll upload it, review the OCR read, show you the three engines' rows, pass pre-check, approve the life event, and walk the enrollment gate — with the clock counting the whole way.
Medical child support orders handled where the child's coverage and the employee's deduction already live — on SAP SuccessFactors today and on whichever HRIS your next entity brings.