CheckAccountTransaction

Update an existing check account transaction

Changed on Jul 13, 2026

Update a check account transaction

put/CheckAccountTransaction/{checkAccountTransactionId}

Request

Base URL
https://my.sevdesk.de/api/v1
Auth
API key in header Authorization

Path parameters

checkAccountTransactionIdinteger required

ID of check account to update transaction

Request body

valueDatestring date-time

Date the check account transaction was booked

entryDatestring date-time nullable

Date the check account transaction was imported

paymtPurposestring

the purpose of the transaction

amountnumber float nullable

Amount of the transaction

payeePayerNamestring nullable

Name of the payee/payer

status100 | 200 | 300 | 400

Status of the check account transaction. 100 <-> Created 200 <-> Linked 300 <-> Private 400 <-> Booked

Example request

{
  "valueDate": "2024-05-10T00:00:00+02:00",
  "entryDate": "2024-05-10T00:00:00+02:00",
  "paymtPurpose": "salary",
  "amount": 100,
  "payeePayerName": "Cercei Lannister"
}

Response

Successful operation - Returns changed check account resource

idstring

The check account transaction id

objectNamestring

The check account transaction object name

createstring date-time

Date of check account transaction creation

updatestring date-time

Date of last check account transaction update

valueDatestring date-time

Date the check account transaction was imported

entryDatestring date-time nullable

Date the check account transaction was booked

paymtPurposestring nullable

The purpose of the transaction

amountstring

Amount of the transaction

payeePayerNamestring nullable

Name of the other party

payeePayerAcctNostring nullable

IBAN or account number of the other party

payeePayerBankCodestring nullable

BIC or bank code of the other party

gvCodestring nullable

ZKA business transaction code. This can be given for finAPI accounts.

entryTextstring nullable

Transaction type, according to the bank. This can be given for finAPI accounts.

primaNotaNostring nullable

Transaction primanota. This can be given for finAPI accounts.

status'100' | '200' | '300' | '350' | '400'

Status of the check account transaction. 100 <-> Created 200 <-> Linked 300 <-> Private 350 <-> Auto-booked without user confirmation 400 <-> Booked

enshrinedstring date-time

Timepoint when the transaction was enshrined.

Example response

{
  "id": "1",
  "objectName": "CheckAccountTransaction",
  "sevClient": {
    "id": "0",
    "objectName": "SevClient"
  },
  "valueDate": "2024-05-10T00:00:00+02:00",
  "entryDate": "2024-05-10T00:00:00+02:00",
  "paymtPurpose": "salary",
  "amount": "-100.32",
  "payeePayerName": "Cercei Lannister",
  "checkAccount": {
    "id": "0",
    "objectName": "CheckAccount"
  },
  "sourceTransaction": {
    "id": "0",
    "objectName": "CheckAccountTransaction"
  },
  "targetTransaction": {
    "id": "0"
  }
}

Changes

Jul 13, 2026a32cec0fecea Revision changes
- warning
  added the new 350 enum value to the response property for the response status
- info
  added the optional property to the response with the status
- info
  added the optional property to the response with the status
- info
  added the optional property to the response with the status
Aug 6, 2024a12897a73d08 Revision changes
- breaking
  the response property became nullable for the status
- breaking
  the response property became nullable for the status
- breaking
  the response property became nullable for the status
- warning
  removed the request property
- info
  the endpoint scheme security api_key was added to the API
- info
  the request property became nullable
- info
  added the optional property to the response with the status
- info
  added the optional property to the response with the status
- info
  the response optional property became not read-only for the status
- info
  the response optional property became not read-only for the status
- info
  the response optional property became not read-only for the status
- info
  the response optional property became not read-only for the status
- info
  the response optional property became not read-only for the status

Operation history