Expense Update
Edit the data of an expense while it is still in the created status. After submission or after creation with documents (status pending_adm_approval), the expense can no longer be changed.
info
Only expenses with the created status can be updated.
Request
ENDPOINT
/expense_submission/fund_class/{fund_class_key}/contract/{contract_key}/expense/{expense_key}METHOD
PUTPath params
| Parameter | Type | Description |
|---|---|---|
fund_class_key | string | Unique key of the fund (UUID) |
contract_key | string | Unique key of the contract |
expense_key | string | Unique key of the expense (UUID) |
Request Body
{
"payment_method": "transfer",
"start_deferral_date": "2026-06-02",
"end_deferral_date": "2026-06-30",
"description": "Honorários de auditoria - 1º semestre 2026 (corrigido)",
"payment_value": 16000.00,
"payment_date": "2026-07-01",
"payment": {
"target": {
"name": "AUDITORES EXEMPLO S.A.",
"document_number": "12.345.678/0001-90"
},
"target_account": {
"account_number": "123456",
"account_branch": "0001",
"account_digit": "0",
"financial_institution_code": "341"
},
"transfer_type": "wire_transfer",
"source_account": {
"account_key": "5e621ba2-b4ac-4ddd-9893-82d220e1577e"
}
}
}
Body attributes
| Field | Type | Required | Description |
|---|---|---|---|
payment_method | string | optional | Payment method: transfer, automatic_debit or bank_slip. |
start_deferral_date | string | optional | Accrual start date in the YYYY-MM-DD format. Must be a business day. |
end_deferral_date | string | optional | Accrual end date in the YYYY-MM-DD format. Must be a business day. |
description | string | optional | New expense description. Maximum of 200 characters. |
payment_value | number | optional | New expense value. Minimum: 0. |
payment_date | string | optional | New payment date in the YYYY-MM-DD format. Must be a business day. |
payment | object | optional | New payment data. Same structure as in the expense creation. |
Response
STATUS
200The response follows the same structure as the expense creation, with the updated fields.
Possible errors
STATUS
404Expense not found
The fund_class_key + contract_key + expense_key set does not correspond to any registered expense.
{
"title": "Expense Not Found",
"description": "Expense with key {expense_key} was not found.",
"translation": "A despesa com chave {expense_key} não foi encontrada.",
"code": "ESB000016"
}
STATUS
400Expense cannot be edited in this status
The expense is not in the created status and cannot be edited.
{
"title": "Cannot Update Expense In This Status",
"description": "Expense {expense_key} cannot be updated with status {current_status}.",
"translation": "A despesa {expense_key} não pode ser atualizada com o status {current_status}.",
"code": "ESB000023"
}
Next steps
- Submit the expense — forward it for analysis when it is ready.
- Cancel the expense — cancel it if it is no longer needed.