> ## 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. # The Chart of Accounts > The accounts your configuration mints, and the sections they read into Money in Financials sits in **accounts**. Nobody authors them: they are minted automatically from your [Invoice Types and Line Items](/financials/invoice-types). Configure an Invoice Type on the [Event Invoice Types page](/financials/pages/event-invoice-types) and its accounts appear with it, in the same transaction. This is the part of the model that most directly explains the product. When an invoice is created, paid, or voided, what actually happens is that money moves between the accounts below. [The Ledger](/financials/accounting-model/ledger) describes the balanced rows, and [What Each Action Posts](/financials/accounting-model/postings) maps product actions to those rows. ## The Account Roles Every account has a **role**, which says what it is for. | Role | One per | What it holds | | -------------------------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Cash** | Company | The single account every payment posts against. There is exactly one, and it has no Invoice Type behind it. | | **Line item** | Line Item Type | The income or expense account for that line — where the money is finally recognized. | | **Payable** / **Receivable** | Line Item Type | The balance twin of the line above: what is owed on it but not yet settled. A line expecting money out gets a Payable; one expecting money in gets a Receivable. | | **Reserves** | Loss/Recovery type | The reserve balance for that type. | | **Unpaid Losses** / **Unpaid Recoveries** | Loss/Recovery type | Money expected to move that has been reserved but not yet paid. Named for the type's expected direction. | | **Additional Incurred** / **Additional Recovered** | Loss/Recovery type | Relief for payments that deliberately do **not** draw down the reserve. | ## What Gets Minted, and When Cash is created lazily by whichever configuration change needs it first. Every company has exactly one for its whole life. Reserves, Unpaid Losses (or Unpaid Recoveries), and Additional Incurred (or Additional Recovered) — all three carrying the type's expected direction. An **Operating** type mints none of these: it has no reserves, so it has nothing to hold them in. Its line item account, plus its own balance twin — a Payable or a Receivable according to that line's direction. This happens for both kinds of Invoice Type. Two rules do all the work, and they read from **different** directions — a detail that matters as soon as a type owns a line item pointing the other way: * The **three core accounts** follow the *Invoice Type's* expected direction. * Each **line item pair** follows *that line item's own* direction. The balance twin is **per line item**, not per type. A type with four line items has four Payable/Receivable accounts, one each. This is what lets a multi-line invoice's outstanding balance split correctly across lines that point in different directions. ### Worked Examples Three types, each with two line items pointing in **opposite** directions. Cash is shared company-wide and is not counted in any of them. Each tab gives the same set twice: a table pairing every account with its provenance and its chart section, and a tree showing the shape a configuration mints. A dash in the **Line Item** column marks an account minted at the Invoice Type level, which belongs to no line item. **Hover any account name to see its machine key.** **Broker Fees** — an Operating type expecting money out, owning `Commission` (expense) and `Refund` (income). An Operating type mints **no** core accounts. Two line items × two accounts = **4 accounts**.
Invoice Type Line Item Account Section
Broker FeesCommissionBroker Fees CommissionExpenses
Broker FeesCommissionBroker Fees Commission PayableLiabilities
Broker FeesRefundBroker Fees RefundIncome
Broker FeesRefundBroker Fees Refund ReceivableAssets
``` Broker Fees ├─ Commission │ ├─ broker-fees-commission-1 │ └─ broker-fees-commission-payable-1 └─ Refund ├─ broker-fees-refund-1 └─ broker-fees-refund-receivable-1 ``` Note the two line items land in **different chart sections** — one an expense, one income — and their twins on opposite sides of the balance sheet, purely because their directions differ. **ALAE** — a Loss/Recovery type expecting money **out**, owning `Legal Fees` (expense) and `Expense Recovery` (income). Three core accounts + two line items × two = **7 accounts**.
Invoice Type Line Item Account Section
ALAE—ALAE ReservesLiabilities
ALAE—ALAE Unpaid LossesLiabilities
ALAE—ALAE Additional IncurredExpenses
ALAELegal FeesALAE Legal FeesExpenses
ALAELegal FeesALAE Legal Fees PayableLiabilities
ALAEExpense RecoveryALAE Expense RecoveryIncome
ALAEExpense RecoveryALAE Expense Recovery ReceivableAssets
``` ALAE ├─ ⟨type level⟩ │ ├─ alae-reserves-1 │ ├─ alae-unpaid-1 │ └─ alae-additional-1 ├─ Legal Fees │ ├─ alae-legal-fees-1 │ └─ alae-legal-fees-payable-1 └─ Expense Recovery ├─ alae-expense-recovery-1 └─ alae-expense-recovery-receivable-1 ``` The three core accounts are named and oriented for a **loss** — "Unpaid Losses", "Additional Incurred" — because the *type* expects money out. The `Expense Recovery` line item still gets an income leaf and a Receivable twin, because *it* expects money in. **Subrogation** — a Loss/Recovery type expecting money **in**, owning `Recovery` (income) and `Recovery Costs` (expense). Three core accounts + two line items × two = **7 accounts**.
Invoice Type Line Item Account Section
Subrogation—Subrogation ReservesAssets
Subrogation—Subrogation Unpaid RecoveriesAssets
Subrogation—Subrogation Additional RecoveredIncome
SubrogationRecoverySubrogation RecoveryIncome
SubrogationRecoverySubrogation Recovery ReceivableAssets
SubrogationRecovery CostsSubrogation Recovery CostsExpenses
SubrogationRecovery CostsSubrogation Recovery Costs PayableLiabilities
``` Subrogation ├─ ⟨type level⟩ │ ├─ subrogation-reserves-1 │ ├─ subrogation-unpaid-1 │ └─ subrogation-additional-1 ├─ Recovery │ ├─ subrogation-recovery-1 │ └─ subrogation-recovery-receivable-1 └─ Recovery Costs ├─ subrogation-recovery-costs-1 └─ subrogation-recovery-costs-payable-1 ``` This is the case that shows the two rules are genuinely independent. The core accounts flip to the **asset** side and take recovery names, because the type expects money in — while `Recovery Costs` still mints an expense leaf and a **Payable**, because that one line expects money out. The product exposes the same relationship on the [Event Invoice Types page](/financials/pages/event-invoice-types) and the read-only [Chart of Accounts page](/financials/pages/chart-of-accounts). The local fixture below uses `Comission` as its Invoice Type name and gives the two line items their full display names. Event Invoice Types page showing the Comission Operating Invoice Type with Broker Fees Commission marked Payable and Broker Fees Refund marked Receivable The outbound `Broker Fees Commission` line item creates an expense account and its matching payable. Chart of Accounts Expenses section showing the debit-normal Comission Broker Fees Commission account and its stable key Chart of Accounts Liabilities section showing the credit-normal Comission Broker Fees Commission Payable account and its stable key The inbound `Broker Fees Refund` line item creates an income account and its matching receivable. Chart of Accounts Income section showing the credit-normal Comission Broker Fees Refund account and its stable key Chart of Accounts Assets section showing the debit-normal Comission Broker Fees Refund Receivable account and its stable key #### Video walkthrough Watch the complete example, from configuring the two line items through inspecting all four generated accounts.