> For the complete documentation index, see [llms.txt](https://docs.zipwire.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zipwire.io/zipwire-approve/unboxing-key-concepts/billing-plans.md).

# Billing Plans

A **Billing Plan** is a reusable template that defines the structure of how timesheets are filled in—what time units are allowed and how they're organized per day.

## What's Inside a Billing Plan

* **Time Units** — Hours (24 per day) or Half-Days (6 per day)
* **Tier Grid** — A week-long grid per day specifying which tier (A, B, or C) or NA (not available) applies to each time slot
* **Standard Hours** — Expected hours per day (typically 8) that defines the boundary between standard and overtime tiers
* **Billing Cycle** — Frequency (flexible, weekly, or monthly)

## Why It Matters

Senders record detailed work in a private Journal, but the final Timesheet is constrained by the Billing Plan.

**Example: UK Billing Plan**

* Uses **half-day units** (minimum work unit = 4 hours)
* Grid might show: A, A, B, B, NA, NA (4 half-days available Mon-Fri, weekends off)

**Example: US Billing Plan**

* Uses **hourly units**
* Grid shows 24 hours per day with tiers A-C for standard/overtime/premium

## Tiers for Rate Incentives

The grid uses **Tier codes (A, B, C)** to support different payment rates:

* **Tier A** — Standard hours (e.g., £75/hr)
* **Tier B** — Overtime (e.g., £100/hr)
* **Tier C** — Premium/night work (e.g., £150/hr)
* **NA** — Not available (off hours)

This allows you to incentivize or discourage long work days without forcing senders to lie about their hours.

## Reusability

A single Billing Plan can be used by multiple Rate Plans across different senders in an assignment or across assignments. For example, "BP1: 8-hour hourly UK" might be used by 10 different senders, each with their own rate plan and pay rates.