> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pylon.mortgage/llms.txt
> Use this file to discover all available pages before exploring further.

# Title order-out

> For title companies integrating into Pylon: write fees directly to the loan file so the Closing Disclosure is accurate. Pylon absorbs tolerance cures.

<Warning>
  **Audience**: This page is for **title companies that integrate directly with Pylon** to write fees to loan files. If you are a lender or building a general integration, see the [Order-Outs Overview](/guides/getting-started/order-outs-and-integrations/overview) and [Complete integration guide](/guides/getting-started/e2e-build) instead.
</Warning>

You **write your final title and settlement fees to the loan file** via the API; those values flow into the Closing Disclosure (CD). There is no separate “balancing” step—writing the fees is how the CD gets the correct numbers. **[Pylon is responsible for all tolerance cures](/entity-models/key-concepts/tolerance-cure)** and represents and warrants the file; fees should have been disclosed within [TRID](/entity-models/key-concepts/trid) tolerance bands at initial disclosure, so you only need to send final amounts.

## How to write fees

**1. Get the loan’s fees** — Query so you have fee IDs and can match your figures to the right line items:

```graphql theme={null}
query GetLoanFees($loanId: ID!) {
  loan(id: $loanId) {
    id
    fees {
      id
      feeType
      feeDescription
      feeSpecifiedFixedAmount
      feeTotalPercent
      integratedDisclosureSectionType
    }
  }
}
```

* `feeSpecifiedFixedAmount` is in **cents** (e.g. 50000 = \$500.00).
* Use `feeType`, `feeDescription`, and `integratedDisclosureSectionType` to map to your title/settlement fees. For percent units, see the [GraphQL API Reference](https://pylon.mortgage/documentation/graphql/index.html) for `Fee` and `UpdateFeeInput`.

**2. Update each fee** — Call the `fee` mutation with `UpdateFeeInput`: required `id`, and either `feeSpecifiedFixedAmount` (cents) or `feeTotalPercent`. Only send the field you’re updating so you don’t switch a fixed fee to percent (or vice versa).

```graphql theme={null}
mutation UpdateFee($input: UpdateFeeInput!) {
  fee {
    update(input: $input) {
      fee {
        id
        feeSpecifiedFixedAmount
        feeTotalPercent
      }
    }
  }
}
```

Example variables for a \$750 fixed amount:

```json theme={null}
{
  "input": {
    "id": "fee_abc123",
    "feeSpecifiedFixedAmount": 75000
  }
}
```

Call the mutation once per fee you need to update. The CD will reflect the new amounts.

## Related resources

* [Tolerance cure](/entity-models/key-concepts/tolerance-cure) — Fee tolerance bands and who is responsible for cures
* [TRID (TILA-RESPA Integrated Disclosure)](/entity-models/key-concepts/trid) — Disclosure timing and requirements
* [Order-Outs Overview](/guides/getting-started/order-outs-and-integrations/overview) — When order-outs are triggered (after [ITP](/entity-models/key-concepts/itp))
* [GraphQL API Reference](https://pylon.mortgage/documentation/graphql/index.html) — `Fee`, `FeeMutations`, `UpdateFeeInput`, `UpdateFeeResponse`