# Authorizations and units: keeping shifts billable

> Service authorizations are the budget behind every billable shift. See how units track, how budget alerts warn you early, and why a row turns UNBILLABLE.

Canonical: https://enmantle.com/help/billing-authorizations-and-units · Section: Billing · Updated: 2026-09-20

Every billable shift draws down a service authorization — the units DODD has approved for a client. If those units run out or the authorization lapses, the claim denies. Enmantle tracks the budget behind each client so you can see what's left and fix problems before they cost you a payment.

## Where authorizations live

Each client's authorizations sit on their billing profile, under the `Authorizations` section — "DODD/PAWS authorizations and budget lines for this client." Use `Add authorization` to enter one. Every authorization carries a program — `Individual Options (IO)`, `Level One (LV1)`, `Level One Emergency`, or `SELF Waiver` — a date range, and a status such as `ACTIVE` or `EXPIRED`. Under each authorization sit one or more budget lines.

## Read a budget line

A budget line is where units actually track. It shows:

- `Line span` — the effective dates for the line.
- `Units used` — drawn down so far, shown as `used / authorized`.
- `Units remaining` — what's left to bill.
- `$ Remaining` and a `% Remaining` bar — the same picture in dollars and percent.

Chips on the line show the PAWS rollup code, the allowed billing codes (or `any code`), the frequency (`Weekly`, `Monthly`, `Quarterly`, `Annual`, or `Total`), and the source. A line synced from PAWS footers with `Synced: {date}`; one you keyed by hand reads `Entered: {date}`.

## Watch the budget alerts

You don't have to open every client to catch a problem. The `Budget Alerts` page lists "Active authorization lines that are expiring, low on units, or have stale data — across every client." The alerts read:

- `Authorization period has expired`
- `Authorization expires in {n} days`
- `No units remaining`
- `Only {x}% of units remaining ({n} units)`
- `Budget figures may be outdated`

Filter by `Severity` (`Critical` or `Warning`) and by `Alert type` (`Expired`, `Expiring soon`, `Low units`, `Stale data`) to work the urgent ones first.

> A low-units alert a week early is a phone call to the case manager. The same shortfall discovered at reconciliation is a denied claim. Watch the alerts.

## Why a row turns UNBILLABLE

On the `Setup` step, every derived row gets a status. A row with a hard error is `UNBILLABLE`, a row with something to check is `WARNING`, and a clean row is `PASS`. Authorizations are a common source of both:

- **No authorization on file** raises a `WARNING`: "Billing code {code} rolls up to PAWS code {rollup}, but no AuthorizationLine is configured for this client." The fix is to enter the client's PAWS authorization for that rollup code.
- **Billing past the units left** is flagged as a denial risk under DODD error `22`: "Billed {n} units for PAWS rollup {rollup}, but only {n} remain on the authorization." Reduce the billed units, split across authorizations, or request additional authorization from the case manager.

A row goes fully `UNBILLABLE` when it carries a hard error — for example, a rate or billing code that can't be resolved. Clear the issue, `Recalculate`, and promote the clean rows.

## Next steps

- Follow the full path: [From clock-ins to a clean eMBS invoice](/help/clock-ins-to-embs-invoice).
- When claims come back: [Importing remittance and reconciling payments](/help/import-remittance-and-reconcile).