API · v1 · stabil
CODEMETA OSDeveloper Center
Konsole öffnen
Entity · expenses

Expense Schema

Schema-ID
expense
Collection
expenses
Permissions
  • Lesenexpense_view
  • Anlegenexpense_create
  • Ändernexpense_edit
  • Löschenexpense_delete
Beziehungen

Felder

Expense Schema

expenses4 Permissions

Schema for validating expense entities

userIduuiderforderlich

User ID who recorded this expense

datedateerforderlich

Date of the expense (ISO date format)

categorystringerforderlich

Expense category

TRAVELMATERIALLICENSINGACCOMMODATIONMEALSSHIPPINGOTHER
descriptionstringerforderlich

Expense description

1–1000 Zeichen
amountstringerforderlich

Gross amount in EUR as decimal string

Pattern
currencystringerforderlich

Currency code (ISO 4217)

PatternDefault: "EUR"
taxRatenumbererforderlich

VAT rate as percentage (e.g., 19 for 19%)

0 – 100Default: 19
netAmountstringerforderlich

Net amount (computed) in EUR as decimal string

Pattern
receiptAttachmentIduuidoptional

Receipt attachment UUID

nullable
ticketIduuidoptional→ ticket

Associated ticket UUID

nullable
projectIduuidoptional→ project

Associated project UUID

nullable
partyIduuidoptional

Associated party/customer UUID

nullable
contractIduuidoptional

Associated contract UUID

nullable
billablebooleanerforderlich

Whether this expense is billable to the customer

Default: true
billingStatusstringerforderlich

Current billing status

OPENAPPROVEDINVOICED
Default: "OPEN"
performanceRecordIduuidoptional

Leistungsnachweis this expense was billed on (per-project billing run, ADR 0416). Server-managed.

read-onlynullable
invoiceIduuidoptional

Invoice this expense was billed on (set when billingStatus flips to INVOICED). Server-managed.

read-onlynullable
approvalStatusstringerforderlich

Approval status

DRAFTSUBMITTEDAPPROVEDREJECTED
Default: "DRAFT"
approvedByIduuidoptional

User who approved this expense

nullable
approvedAtdatetimeoptional

Timestamp when approved (ISO datetime)

nullable
tagsstring[]optional

Expense tags

Default: []

Standard-Endpoints

Diese Resource folgt dem generischen CRUD-Vertrag der Plattform. Lesen Sie die Konventionen für Pagination, Idempotenz, Optimistic Locking und Audit. Die wichtigsten Endpoints:

  • GET /api/v1/expenses — Liste, paginiert + filterbar
  • GET /api/v1/expenses/<id> — Einzelne Entity
  • POST /api/v1/expenses — Anlegen
  • PATCH /api/v1/expenses/<id> — Teil-Update
  • DELETE /api/v1/expenses/<id> — Soft-Delete
  • GET /api/v1/expenses/<id>/timeline — Audit + Aktivitäten

Suche