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

# Statements

> Settlement confirmations, FX execution reports, and reconciliation exports for your accounting team.

<Note>
  **Status:** the dedicated statement endpoints described below (CSV, JSON) are **coming**. In the interim, settled-order details are retrievable per-intent via `GET /api/v1/orders/{intent_id}` (full settled record). Scheduled batch statements are on the roadmap.
</Note>

Statements is the default integration path for the accounting side of the workflow. Your GL ingests settlement confirmations on a daily or weekly cadence; your treasury archive takes a monthly record set. For institutions wiring real-time accounting or TMS-driven reconciliation, see [Programmatic Access](/institution/integration/programmatic-access).

## Statement types

<Tabs>
  <Tab title="Settlement confirmations (CSV)">
    One row per settled intent, over a date range. Columns match the general ledger handoff:

    | Column                                     | Description                                                   |
    | ------------------------------------------ | ------------------------------------------------------------- |
    | `intent_id`                                | FXOrder UUID — correlate with your internal payment reference |
    | `transaction_hash`                         | Atomic DvP settlement proof — one hash covers all four legs   |
    | `settled_at`                               | ISO 8601 timestamp                                            |
    | `source_currency` / `source_amount_actual` | What left your custody                                        |
    | `target_currency` / `target_amount`        | What the receiver got                                         |
    | `fx_rate`                                  | Executed rate                                                 |
    | `counterparty_party_id`                    | Receiver institution                                          |
    | `counterparty_custodian_party_id`          | Receiver's custodian                                          |

    **Status: coming.** Interim: the per-intent endpoint returns the same data one order at a time.
  </Tab>

  <Tab title="FX execution report (CSV)">
    Best-ex and TCA-style documentation — one row per settled intent:

    | Column                          | Description                                                   |
    | ------------------------------- | ------------------------------------------------------------- |
    | `intent_id`, `settled_at`       | As above                                                      |
    | `quoted_rate` / `executed_rate` | Quote acceptance vs. final executed                           |
    | `mid_market_rate_at_quote`      | Mid captured at quote time (rate-source attribution)          |
    | `rate_source`                   | Where the mid came from (INTERNAL\_OBSERVED, BLOOMBERG, etc.) |
    | `slippage_bps`                  | Executed vs. quoted in basis points                           |
    | `num_competing_quotes`          | How many market makers bid                                    |
    | `spread_to_best`                | Difference between accepted and next-best quote               |

    Feeds your TCA (transaction cost analysis) process and satisfies best-execution documentation.

    **Status: coming.**
  </Tab>

  <Tab title="Month-end reconciliation (JSON)">
    Full settled FXOrder records for the period — party ids, executed rate, amounts, and settlement details. One document per month, suitable for your treasury archive.

    **Status: coming.**
  </Tab>
</Tabs>

## Filtering

Planned filters across all statement types:

* **Date range** — `from` / `to` on `settled_at`
* **Status** — SETTLED by default; include FAILED / EXPIRED for operational reviews
* **Counterparty** — limit to a specific receiver institution
* **Currency pair** — limit to JPYSC0 → USDCx, etc.

## Consuming statements

Once statements land, your accounting systems ingest them via your existing pipelines — whatever you use today to ingest daily settlement files from banks or other counterparties. Most institutions schedule a daily CSV pull into their GL and a monthly JSON dump into their treasury archive.

## Interim: per-intent retrieval

Until batch endpoints ship, settled-order details are retrievable one at a time:

```bash theme={null}
GET /api/v1/orders/{intent_id}
```

Returns the full settled FXOrder record — structurally the same content that will appear in batch statements, just retrieved on demand. If your accounting team needs records now, scripting against this endpoint is the path; when batch endpoints ship, switch the scheduled job from a per-intent loop to a single batch call.

## Next steps

* Daily operation — see [Console](/institution/integration/console)
* Real-time reconciliation — see [Programmatic Access](/institution/integration/programmatic-access)