Actions69
- Additional Information Category Actions
- Case File Actions
- Client Fee Actions
- Collision Actions
- Contact Actions
- Deadline Actions
- Department Actions
- Document Actions
- Document Template Actions
- Expenditure Actions
- Expense Actions
- Folder Actions
- Invoice Actions
- Note Actions
- Resubmission Actions
- RVG Fee Actions
- Task Actions
- Third Party Cost Actions
- User Actions
Expense → Update
AI-generatedSummary
Update an Actaport expense, addressing it by its ID and the case’s sequential number and reference year. Send any populated expense fields as updates; blank or unset fields are omitted from the request body.
Inputs
- Sequential Number (required) — Sequential number of the case containing the expense.
- Reference Year (required) — Reference year of the case containing the expense.
- ID (required) — ID of the expense to update.
- Reason (Grundlage) — Optional reason or basis for the expense.
- Expenditure Type (Art) — Optional expenditure type.
- Comment — Optional comment.
- Expense Type — Optional expense category: Aufwendung, Fremdleistung Inland, Fremdleistung Ausland, or Fremdleistung EU. Defaults to Aufwendung.
- VAT Rate — Optional VAT rate.
- Net Amount (Cent) — Optional net amount in cents.
- Gross Amount (Cent) — Optional gross amount in cents.
- Quantity — Optional quantity.
- Date — Optional date; sent as an ISO timestamp.
- User — Optional user associated with the expense, selected by ID or from the user list.
- Client — Optional client associated with the expense, selected by ID or from the client list.
- Linked Case Documents — Optional document IDs to link to the expense. Available document choices depend on the case number and reference year.
- Case File Number — Optional case file number.
- Request Options — Optional request settings for batching, SSL certificate validation, proxy, and timeout.
Output shape
A single response item containing the API response to the expense update.
The source pack provides only a signature-level view of the request implementation, so it does not expose the endpoint’s precise response fields.