---
title: "Create a new transaction"
method: POST
path: "/CheckAccountTransaction"
tags: ["CheckAccountTransaction"]
---

# Create a new transaction

`POST /CheckAccountTransaction`

Creates a new transaction on a check account. This should only be used with check account type online, preferably for csv import accounts.

## Request body

- ModelCheckAccountTransaction — CheckAccountTransaction model. Responsible for the transactions on payment accounts.
  - `id` integer — The check account transaction id
  - `objectName` string — The check account transaction object name
  - `create` string, date-time — Date of check account transaction creation
  - `update` string, date-time — Date of last check account transaction update
  - `sevClient` object — Client to which check account transaction belongs. Will be filled automatically
    - `id` integer, required — Unique identifier of the client
    - `objectName` string, required — Model name, which is 'SevClient'
  - `valueDate` string, date-time, required — Date the check account transaction was booked
  - `entryDate` string, date-time, nullable — Date the check account transaction was imported
  - `paymtPurpose` string, nullable — The purpose of the transaction
  - `amount` number, float, required — Amount of the transaction
  - `payeePayerName` string, nullable, required — Name of the other party
  - `payeePayerAcctNo` string, nullable — IBAN or account number of the other party
  - `payeePayerBankCode` string, nullable — BIC or bank code of the other party
  - `checkAccount` object, required — The check account to which the transaction belongs
    - `id` integer, required — Unique identifier of the check account
    - `objectName` string, required — Model name, which is 'CheckAccount'
  - `status` 100 | 200 | 300 | 400, required — Status of the check account transaction.<br> 100 <-> Created<br> 200 <-> Linked<br> 300 <-> Private<br> 400 <-> Booked
  - `sourceTransaction` object, nullable — The check account transaction serving as the source of the rebooking
    - `id` integer, required — Unique identifier of the check account transaction
    - `objectName` string, required — Model name, which is 'CheckAccountTransaction'
  - `targetTransaction` object, nullable — The check account transaction serving as the target of the rebooking
    - `id` integer, required — Unique identifier of the check account transaction
    - `objectName` string, required — Model name, which is 'CheckAccountTransaction'

## Response `201`

Created - Returns created transaction

- ModelCheckAccountTransactionResponse — CheckAccountTransaction model. Responsible for the transactions on payment accounts.
  - `id` string — The check account transaction id
  - `objectName` string — The check account transaction object name
  - `create` string, date-time — Date of check account transaction creation
  - `update` string, date-time — Date of last check account transaction update
  - `sevClient` object — Client to which check account transaction belongs. Will be filled automatically
    - `id` string, required — Unique identifier of the client
    - `objectName` string, required — Model name, which is 'SevClient'
  - `valueDate` string, date-time — Date the check account transaction was imported
  - `entryDate` string, date-time, nullable — Date the check account transaction was booked
  - `paymtPurpose` string, nullable — The purpose of the transaction
  - `amount` string — Amount of the transaction
  - `payeePayerName` string, nullable — Name of the other party
  - `payeePayerAcctNo` string, nullable — IBAN or account number of the other party
  - `payeePayerBankCode` string, nullable — BIC or bank code of the other party
  - `gvCode` string, nullable — ZKA business transaction code. This can be given for finAPI accounts.
  - `entryText` string, nullable — Transaction type, according to the bank. This can be given for finAPI accounts.
  - `primaNotaNo` string, nullable — Transaction primanota. This can be given for finAPI accounts.
  - `checkAccount` object — The check account to which the transaction belongs
    - `id` string, required — Unique identifier of the check account
    - `objectName` string, required — Model name, which is 'CheckAccount'
  - `status` '100' | '200' | '300' | '350' | '400' — Status of the check account transaction.<br> 100 <-> Created<br> 200 <-> Linked<br> 300 <-> Private<br> 350 <-> Auto-booked without user confirmation<br>400 <-> Booked
  - `sourceTransaction` object — The check account transaction serving as the source of a money transit
    - `id` string, required — Unique identifier of the check account transaction
    - `objectName` string, required — Model name, which is 'CheckAccountTransaction'
  - `targetTransaction` object — The check account transaction serving as the target of a money transit
    - `id` string, required — Unique identifier of the check account transaction
    - `objectName` string, required — Model name, which is 'CheckAccountTransaction'
  - `enshrined` string, date-time — Timepoint when the transaction was enshrined.

## Other responses

- `400` — Bad request
- `401` — Authentication required
- `500` — Server error

---

[API](https://skmtc.net/sevdesk/apis/sevdesk-api.md) · [All operations](https://skmtc.net/sevdesk/apis/sevdesk-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/sevdesk/sevdesk-api/revisions/a32cec0fecea/schema)