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

# Audit Exports

> Scheduled CSV / JSON downloads of settled FXOrders for your accounting and reconciliation archive.

<Note>
  **Status:** the dedicated batch export endpoints described below (CSV, JSON) are **coming**. In the interim, per-intent records are retrievable one at a time via the existing order endpoints, which return the full signed FXOrder + settlement legs. Batch downloads are on the roadmap.
</Note>

Audit Exports is the default integration path for the settlement side of the workflow. Your accounting archive subscribes to scheduled downloads rather than to a real-time stream — matching how reconciliation systems typically consume data today.

For custodians with downstream systems that can't wait for scheduled exports (custom accounting reconciliation, real-time client-reporting dashboards, etc.), see [Programmatic Access](/custodian/integration/programmatic-access).

## Export formats

<Tabs>
  <Tab title="Daily / weekly reconciliation (CSV)">
    One row per settled intent over the date range. Columns match accounting needs:

    | Column                                     | Description                                                        |
    | ------------------------------------------ | ------------------------------------------------------------------ |
    | `intent_id`                                | FXOrder UUID                                                       |
    | `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 (sender) or what the sender paid (receiver) |
    | `target_currency` / `target_amount`        | What the receiver got                                              |
    | `fx_rate`                                  | Executed rate                                                      |
    | `sender_party_id` / `receiver_party_id`    | Canton identities                                                  |

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

  <Tab title="Monthly settlement archive (JSON)">
    Full settled FXOrder records for the period, including every settlement field + the linked settlement legs with `transaction_hash`.

    One JSON document, ND-JSON-per-intent, or ZIP per intent — format options TBD. This feeds your internal accounting archive for retention.

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

## Filtering

Planned filters:

* **Date range** — `from` / `to` on `settled_at`
* **Status** — filter to SETTLED, or include FAILED / EXPIRED for operational reviews
* **Institution** — limit to a specific `sender_party_id` or `receiver_party_id`
* **Currency pair** — limit to JPYSC0 → USDCx, etc.

## Consuming exports

Once exports land, your accounting archive picks them up via your existing ingestion — whatever you already use for ingesting daily reconciliation.

## Interim: per-intent retrieval

Until the batch endpoints ship, you can retrieve one intent at a time via the order endpoints. The response is the full signed FXOrder + settlement legs — structurally the same content that will appear in the monthly JSON export, just retrieved on demand instead of batched. If your team needs records now, scripting against the order endpoint is the path.

## Next steps

* Deploy the backend if you haven't — see [Deploy](/custodian/integration/deploy)
* Ops team workflow — see [Console](/custodian/integration/console)
* Need real-time, not scheduled? — see [Programmatic Access](/custodian/integration/programmatic-access)