From clock-ins to a clean eMBS invoice

Billing on Enmantle isn't a separate data-entry job. It's built directly on the clock data your staff already create every shift. This guide walks the whole path — from clock-ins to a clean eMBS invoice and the remittance that comes back — so you can see how the pieces connect.

Billing rows derive from clock data

You don't build billing lines by hand. When your staff clock in and out, Enmantle derives the billing rows automatically from that clock data. Accurate shifts in means accurate billing out — which is exactly why the clock-in and clock-out steps matter so much. See Clocking in and out with GPS for how that data is captured.

Because the rows come straight from real clock events, there's no re-keying and no separate spreadsheet to reconcile against your schedule.

Setup flags each row before you promote it

On the Setup step ("Recalculate & create rows"), Enmantle shows every derived row with a status — PASS, WARNING, or UNBILLABLE — and spells out the reason on any row that needs attention. The filter chips (ALL, PASS, WARNING, UNBILLABLE) let you work the problems first.

• PASS — the row looks good to promote.
• WARNING — something to check. Common reasons include a missing daily note (No submitted ClientDailyNote for client on this service date), a note with no linked ISP goal status, an EVV visit that is not verified, or no authorization on file for the client's PAWS code.
• UNBILLABLE — a hard error you must fix first, such as a rate or billing code that can't be resolved, or units that exceed the client's authorization.

Work the issues, then hit Recalculate to re-check and Create Billing Data to promote the clean rows. When a reason points back to a bad time, correct it at the source — see Fixing a time entry.

Setup is your safety net. It's the difference between finding a problem at your desk and finding it after a claim bounces. Clear the issues, then promote.

Generate the eMBS invoice

Once your rows pass, move to the Invoice step ("Generate eMBS file"). Enmantle assembles the DODD/Medicaid flat file from the billing data you just reviewed, so what you submit matches what your staff actually worked.

1. On the Invoice step, click Create invoice.
2. Scope the period and, if you like, filter by client, service category, or cost center, then Generate invoice.
3. Before you submit, run the Preflight step ("Validate before submit") to audit the generated file, then review the totals and submit.

Different service types flow through the same path — for example, transportation is handled alongside your other billing. See HPC and non-medical transportation.

Import remittance and reconcile

Billing isn't done when the invoice goes out — it's done when the money is accounted for. When DODD reports back, use Import remittance on the Reconcile step to bring the remittance in and reconcile it against what you billed.

1. On the Reconcile step, click Import remittance and upload the DODD file (an INVCFLAT or ERROR_DETAIL .txt).
2. Enmantle matches each claim line to your submitted rows and updates the Billed, Paid, Variance, and Open cases tiles.
3. Work the Open cases — denials, short pays, and mismatches — and follow up.

That closing loop is how you know a billing cycle is truly finished, not just submitted. For the full workflow, see Importing remittance and reconciling payments.

Payroll, from the same clock data

The same clock data that drives billing also drives pay. Timesheets export to any payroll system, so you run payroll from the same source of truth — no second round of data entry. Staff can also see their own pay period and paycheck info in Enmantle.

The whole loop

Clock in, derive rows, preflight, generate the eMBS invoice, import and reconcile the remittance. Get the clock data right at the start and the rest of the path stays clean.

Next steps

• Make sure the source data is solid: Clocking in and out with GPS.
• Billing transportation? See HPC and non-medical transportation.
• Questions about data, migration, and support? See the FAQ.