Behind every billing row is a small set of reference data that turns a shift into a priced, coded claim. It lives under Billing settings. You mostly maintain cost centers; the rest is platform-managed reference data you read and rely on. This guide walks each piece and how they fit together.

Cost centers: your funding sources

A cost center is a funding source that scopes billing — "payer kind, contract number, and DODD handling." Open Cost Centers to see them, listed by Name, Payer, Exclude DODD, and Status.

Click Create Cost Center.
Give it a Name and, optionally, a Description.
Set the Payer kind — MEDICAID_WAIVER, COUNTY_BOARD, PRIVATE_PAY, MRC, or OTHER.
Enter the Contract number (a 7-digit DODD contract number); leave it blank to fall back to your tenant default.
Tick Exclude from DODD for funding that shouldn't flow to DODD, keep Active on, and Save.

Each cost center can also carry Custom Codes — per-client billing-code or rate overrides for the cases that don't fit the standard tables.

Rate tables set the price

Rate Tables are Platform-managed · view only — Enmantle keeps them in sync with DODD rates, so there's nothing to edit. There's one table per service family: HPC, HPC Transport, ADS / VocHab, NMT, LPS, PDP, RAL, AFL, Foster, and Shared Living. Each row has an ID, a rate (stored in cents), and an Effective date range, plus the dimensions that service uses (staff and group size, ODDP range, vehicle type, and so on).

The service crosswalk picks the code

The Service Crosswalk maps "each ServiceType to one or more BillingCodes. Add conditions (program, group size) to disambiguate." Use Add mapping to link a service type to a DODD billing code, with Program and Group Size conditions and a Priority to break ties. This is what lets a single service resolve to the right code for the client's waiver and shift size.

The code library validates the code

The Code Library is the Platform-managed · view only catalog of DODD billing codes. Each entry lists the Code, Title, Program, Category, Unit Type, Effective window, and whether EVV is required. Alongside it, Counties (CODB) maps each county to its CODB number for pricing.

How they fit together

When a shift derives into a billing row on the Setup step, these pieces work in order: the crosswalk picks the billing code, the code library validates it, the county's CODB plus the matching rate table price it, and the cost center scopes the funding source and contract number. Set them up once and every row prices and codes itself.

Because rate tables, the code library, and county CODB numbers are platform-managed, you never chase a rate update — Enmantle keeps HPC and the rest current for you.

Next steps

Keep shifts within budget: Authorizations and units.
See the full flow: From clock-ins to a clean eMBS invoice.