> ## Documentation Index > Fetch the complete documentation index at: https://docs.go.aiinsurance.io/llms.txt > Use this file to discover all available pages before exploring further. # Policy Invoice Types > Configure the charge vocabulary a policy's pricing binds to Open **Admin → Financials → Policy Invoice Types**. This [Financials Configuration](/financials/pages/financials-configuration) area defines the policy-side billing vocabulary: the invoice types a policy's charges are grouped into, and the line item types that name the individual charges. The page is available before policy billing enforcement is enabled. Configure and verify this vocabulary first; the runtime policy-write and billing gates remain off until policy billing is enabled for your company. ## What This Page Configures A policy is priced as a list of charges. Every charge names the invoice type it belongs to and the line item type it is, and this page is where those names come from. A charge whose names are not configured here cannot be saved on a policy. There is one card, not two. Policy invoice types have no Loss/Recovery split — a billing vocabulary carries no reserves — so every policy invoice type behaves like an [Operating Invoice Type](/financials/pages/event-invoice-types#two-structural-kinds). ## Read and Edit States The card lists its invoice types and their nested line item types in read mode. Select **Edit** to change them, **Save** to commit the whole card, and **Cancel** to discard the pending edits. There is no page-level save control. Save stays unavailable until every invoice type has a name, at least one line item type, and a name and a **kind** on each of those line item types. ## Names, Directions, and Kinds | Item | What Can Change | What Is Permanent | | ------------------ | ------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------- | | **Invoice Type** | Its binding name, and its Expense/Income expected direction. | Nothing, but renaming requires a coordinated pricing or rater update. | | **Line Item Type** | Its binding name. | Its **Payable/Receivable** direction, and its **kind**. Renaming requires a coordinated pricing or rater update. | Policy invoice type names and line item type names are binding keys, not only display labels. Renaming one does not rewrite pricing already stored on policies or open quotes. Coordinate a rename with the pricing or rater update; otherwise records that still carry the old `` pair will be refused on their next write. Generated invoices already bound by id remain readable. A saved line item type's Payable/Receivable direction is permanent because its account balances are stored relative to it. A policy invoice type's Expense/Income expected direction is a label and remains editable. ### Kind Each line item type is one of six kinds: | Kind | Classification effect | | ---------------------- | ----------------------------------------------------------------------------------- | | **Premium** | Adds to the premium total and is eligible to earn. | | **Tax** | Adds to the taxes total and is eligible to earn. | | **Fee** | Adds to the fees total and is eligible to earn. | | **Broker commission** | Adds to the broker commission total and is eligible to earn. | | **Program commission** | Adds to the program commission total and is eligible to earn. | | **Other** | Feeds no pricing rollup and is not eligible to earn, though it can still be billed. | Kind selects a charge's classification, rollup, and earning eligibility. It does not select earning timing. The price component on the policy carries the **earning basis**, which controls whether an eligible charge earns pro rata or fully at inception. Kind is chosen when the line item type is created and cannot be edited afterwards. **A charge name always means the same kind, for good.** Within your company, a given invoice type and line item type name pair keeps the kind it was first created with — even after the line item type is renamed, deprecated, deleted, or its invoice type is replaced. Reusing that name for a different kind is rejected. This is deliberate. Financial history is recorded against the charge's name and kind. If a name could change kind, previously recognized amounts could move between classifications. **To correct a kind:** add a differently named line item type with the kind you want, point your rating at the new name, and deprecate the old one. Renaming the old one and reusing its name does not work — the old name stays claimed. ## Adding, Deprecating, and Restoring Use **Add invoice type** to add a type, then **Add line item** to add its line item types. Each new line item type needs a name, a direction, and a kind before the card can be saved. An unused type or line item type can be deleted outright. One that has been used by an invoice cannot be deleted; mark it deprecated instead. A deprecated entry remains visible for historical records but is unavailable for new activity, and **Restore** makes it available again. Deprecating a line item type that a live policy is still priced against will cause later transactions on that policy to be rejected until either the charge is restored or the policy's pricing is corrected. ## Before Policy Billing Is Turned On The **Policy Invoice Types** tab is available while policy billing is still off. Use it to cover every charge name and kind emitted by your pricing or rater, including the pricing already stored on policies and open quotes. Coordinate any required rater rename, verify that coverage, and only then enable policy billing. Enabling policy billing starts enforcing the vocabulary on every policy write. An uncovered existing policy or open quote is correctly refused on its next write until its pricing and the configured vocabulary agree. Configure the event-side categories and line items under [Event Invoice Types](/financials/pages/event-invoice-types). Kind is a policy-side concept only — event line item types do not have one.