Actions103
- Calendar Actions
- Common Data Actions
- Contacts Actions
- Contracts Actions
- Credit Notes Actions
- Customers Actions
- Custom Fields Actions
- Estimates Actions
- Expenses Actions
- Invoices Actions
- Items Actions
- API Keys Actions
- Leads Actions
- Milestones Actions
- Payments Actions
- Projects Actions
- Property Actions
- Proposals Actions
- Staff Actions
- Subscriptions Actions
- Tasks Actions
- Tickets Actions
- Timesheets Actions
Expenses → Update
AI-generatedSummary
Update an existing expense in BackOffice ERP by specifying its Expense Id along with mandatory and optional fields to modify its details.
Inputs
- Expense Id (required) — Specify the exact Expense Id or use a search keyword (name, email, or keyword) to locate the expense to update.
- Category (required) — Provide the numeric identifier for the Expense Category.
- Amount (required) — Enter the numeric amount for the expense.
- Date (required) — Set the date of the expense in YYYY-MM-DD format or leave empty to default to today.
- Currency (required) — Provide the numeric code for the currency of the expense.
- Expense name — Optionally name or rename the expense.
- Note — Add or update a note for the expense.
- Customer — Optionally specify the customer by numeric id or smart search using name, email, or keyword.
- Tax — Optionally provide the first tax value.
- Tax2 — Optionally provide the second tax value.
- Paymentmode — Optionally specify the payment mode by numeric code.
- Reference no — Optionally provide a reference number.
- Recurring — Optionally mark the expense as recurring using predefined values (1 to 12) or 'custom'.
- Repeat every custom — If recurring is custom, define the numeric interval between repeats.
- Repeat type custom — If recurring is custom, specify the repeat interval unit (day, week, month, year).
Output shape
a single JSON object representing the updated expense or error details if the update failed.
The operation matches the Expense Id to an existing expense using exact ID or smart search mechanisms. If multiple matches are found, the node outputs multiple matches for user disambiguation. The returned JSON contains the updated expense data from BackOffice ERP API response. If there is a failure and 'continue on fail' is enabled, the error is included in the output.
Examples
Example 1: Update an expense by Expense Id with new amount, category, and date
Set Expense Id to '12345', Category to '10', Amount to 250.00, and Date to '2024-06-05' to update these fields on the expense.