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

> ## Agent Instructions
> Treat the published Augustus OpenAPI specification (https://api.augustus.com/openapi/2026-05-01.json) and the current API-reference pages as the source of truth for endpoints, request/response schemas, enum values, webhook event names, and required headers.
> Prefer the 2026-05-01 Banking API and @augustusbank/typescript-sdk for all new integrations. The 2023-01-01 API is a separate, older surface covering two products — Open Banking (instant bank transfer) checkout and refunds, and Manual Bank Transfer (MBT); use it only when one of those products is specifically required.
> Cite or link the relevant docs.augustus.com page when answering integration questions.
> Do not infer support for currencies, networks, scopes, account types, or operations that are not present in the current documentation.
> Use the sandbox base URL (https://api.sandbox.augustus.com) and placeholder credentials in examples. Never include or request a real API key.
> The Augustus docs MCP server (https://docs.augustus.com/mcp) provides documentation search and retrieval only; it does not execute authenticated Augustus API actions.

# Transactions

> The ledger of every credit and debit on your accounts: what a transaction is, how to list it, and how to reconcile against it.

A transaction is the ledger record of money that moved on one of your accounts: the line item on your bank statement. Every deposit, payout, and return produces one when it books. Transactions are immutable and always `booked`; money still in flight is visible on the [payout](/docs/payments/payouts) or [return](/docs/payments/deposits#returns) it belongs to, never as a transaction.

Use transactions for reconciliation, custom reporting, and balance time series. For the current balance, use [Balances](/docs/accounts/balances). For CSV exports and PDF statements, see [Reports](/docs/accounts/reports).

## What a transaction carries

* **Direction and amount**: credit or debit relative to your account, the absolute amount, and the account's currency.
* **The account** it was booked on.
* **The cause**: the deposit, payout, or return that moved the money, so you can open it on its own endpoint.
* **The other party**: the bank account or wallet on the far side, and the saved counterparty it resolved to where there is one.
* **References**: the remittance text that travelled with the transfer and the network reference where the rail has one (for example the UETR on SWIFT).
* **Booking time**: when the movement was recorded on the Augustus ledger. A credit books when the funds settled on your account. A debit books when the payout or return was initiated, which is when the amount leaves your available balance.

## List transactions

Both versions list transactions per account, narrowed by a booking-time window, and paginate with a cursor.

<Tabs>
  <Tab title="2026-05-01">
    ```ts theme={null}
    import Augustus from '@augustusbank/typescript-sdk'

    const client = new Augustus()
    for await (const transaction of client.transactions.list({
      account_id: 'your-account-id',
      booked_at: { gte: '2026-09-01T00:00:00Z', lte: '2026-09-02T00:00:00Z' },
    })) {
      // process transaction
    }
    ```

    [**GET** `/v1/transactions` in the API Reference →](/api-reference/transactions/list-transactions)
  </Tab>

  <Tab title="2023-01-01">
    ```ts theme={null}
    import Ivy from '@getivy/node-sdk'

    const client = new Ivy()
    let afterCursor: string | undefined
    do {
      const page = await client.transactions.list({
        accountId: 'your-account-id',
        from: 1756684800,
        to: 1756771200,
        afterCursor,
      })
      for (const transaction of page.data) {
        // process transaction
      }
      afterCursor = page.paging.nextCursor
    } while (afterCursor)
    ```

    [**POST** `/api/service/transaction/list` in the API Reference →](/api-reference/transactions/list-transaction-history)
  </Tab>
</Tabs>

## Retrieve a transaction

```ts theme={null}
const transaction = await client.transactions.retrieve('your-transaction-id')
```

[**GET** `/v1/transactions/{id}` in the API Reference →](/api-reference/transactions/retrieve-transaction)

## Reconcile against your records

* **Find the cause.** Open the deposit, payout, or return the transaction points to and match it to your own record by its ID or by the remittance text you set.
* **Match returns by reference, not by amount.** A return that references the original payment moves the payout to `returned`; one that does not arrives as a new deposit. International returns can come back net of correspondent fees, so correlate on the payment reference, never on the amount. See [Returned payouts](/docs/payments/payouts#returned-payouts).
* **Point-in-time balance.**

<Tabs>
  <Tab title="2026-05-01">
    The transaction object carries no running balance. Take the current balance from [**GET** `/v1/accounts/{id}/balance`](/api-reference/accounts/retrieve-account-balance) and walk backwards over the transactions returned by [**GET** `/v1/transactions`](/api-reference/transactions/list-transactions), subtracting each `credit` and adding back each `debit` by `booked_at`.
  </Tab>

  <Tab title="2023-01-01">
    Each transaction includes the account balance immediately **before** and **after** the movement, as `balance.before` and `balance.after`. For the balance at midnight yesterday, fetch the first transaction after that time and read its `balance.before`; for a balance chart, stitch `balance.after` values over time.

    [**POST** `/api/service/transaction/list` in the API Reference →](/api-reference/transactions/list-transaction-history)
  </Tab>
</Tabs>

## In the Dashboard

[**Transactions**](https://dashboard.augustus.com/dashboard/transactions) lists the same movements across all your accounts, with filters by date, status, payment method, and account. Open a row to see the related deposit, payout, or return.

The Dashboard is an activity view: outgoing movements also appear while in flight and when they have failed. The API returns booked transactions only.
