---
title: "Update transaction"
method: POST
path: "/transactions/{id}"
tags: ["transactions"]
---

# Update transaction

`POST /transactions/{id}`

Update a transaction.

## Path parameters

- `id` string, required

## Request body

- object
  - `custom_fields` CommonCustomFields — Custom fields in JSON `key:value` format. See [Custom fields](https://docs.numeral.io/reference/custom-fields).

## Response `200`

200

- TransactionDetails — Debit or credit transaction on a connected account.
  - `id` string, required — The UUID of the transaction.
  - `object` 'transaction', required — Label used to identify this kind of object.
  - `connected_account_id` string, required — The ID of the connected account.
  - `booking_date` string, date, required — The date when a transaction is registered on the account.
  - `value_date` string, date, required — The date when a transaction is effectively credited or debited on the account.
  - `category` 'credit_transfer' | 'cash_concentration' | 'direct_debit' | 'cheque' | 'card' | 'lockbox' | 'counter_operation' | 'bill_of_order' | 'instant_credit_transfer' | 'other_payment' | 'cash_pooling' | 'account_balancing' | 'other_cash_management' | 'derivative' | 'loan' | 'fx' | 'precious_metals' | 'commodities' | 'trade_services' | 'securities' | 'account_management' | 'unavailable', required — The category of the transaction.
  - `description` string, required — The description of the transaction.
  - `direction` 'debit' | 'credit', required — The direction of the transaction, either `debit` or `credit`.
  - `amount` integer, required — The absolute value of the transaction, in the specified currency's smallest unit. For euro transactions, the smallest unit is cents. €20 is represented as `2000`.
  - `currency` 'EUR', required — Currency in which an amount is expressed
  - `counterparty_account` TransactionCounterpartyAccount, required — The account of the counterparty, which is either the debitor or the creditor depending on the transaction's `direction`.
    - `account_number` string, required — The account number of the counterparty, which can be the IBAN or any other identification provided by the bank.
    - `holder_name` string, required — The name of the counterparty.
  - `external_account` TransactionExternalAccount, required — The external account, which is either the debtor or the creditor depending on the transaction's `direction`.
    - `account_number` string, required — The external account number, which can be the IBAN or any other identification provided by the bank.
    - `bank_code` string — The bank code of the external account.
    - `holder_name` string, required — The name of the external account holder.
    - `holder_address` TransactionExternalAccountHolderAddress — The address of the account holder, as an address object.
      - `line_1` string — Line 1.
      - `line_2` string — Line 2.
      - `building_number` string — Building number.
      - `street_name` string — Street name.
      - `postal_code` string — Postal / zip code.
      - `region_state` string — Region or state.
      - `city` string — City.
      - `country` string — ISO 3166 alpha-2 country code.
  - `virtual_account_number` string, required — The number of the virtual account linked to the transaction.
  - `internal_account` TransactionInternalAccount, required — The internal account, which is either the debtor or the creditor depending on the transaction's `direction`.
    - `account_number` string, required — The account number of the internal account, which is a virtual account number.
    - `holder_name` string — The name of the internal account holder.
  - `internal_account_id` string — The ID of the internal account linked to the transaction.
  - `external_account_id` string — The ID of the external account linked to the transaction.
  - `uetr` string, uuid — Unique End-to-end Transaction Reference (UETR).
  - `bank_data` TransactionBankData, required
    - `file_id` string, required — Identifier of the file in which this transaction has been described
    - `statement_id` string — ISO20022 | Unique identification, as assigned by the account servicer, to unambiguously identify this transaction.
    - `end_to_end_id` string — ISO20022 | Unique identification, as assigned by the initiating party, to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. Usage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. It can be included in several messages related to the transaction.
  - `custom_fields` CommonCustomFields, required — Custom fields in JSON `key:value` format. See [Custom fields](https://docs.numeral.io/reference/custom-fields).
  - `reconciliation_status` 'partially_reconciled' | 'reconciled' | 'excluded' | 'unreconciled', required — The reconciliation status of the transaction, which is either `unreconciled`, `reconciled`, `excluded` or `partially_reconciled`.
  - `reconciled_amount` integer, required — The amount of the transaction that is already reconciled. It is the sum of the `amount` of the reconciliations related to this transaction.
  - `created_at` string, date-time, required — The UTC timestamp of the creation of this transaction.

## Other responses

- `400` — Validation error.
- `404` — The specified resource was not found.
- `409` — Conflict.
- `415` — Unsupported Media Type.

---

[API](https://skmtc.net/numeral/apis/payments.md) · [All operations](https://skmtc.net/numeral/apis/payments/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/numeral/payments/versions/220f101cc2ef/schema)