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 → Create
AI-generatedSummary
Create a new expense record in the BackOffice ERP system with specified details such as category, amount, date, currency, and optional fields including expense name, note, customer, taxes, payment mode, reference number, and recurrence settings.
Inputs
- Category (required) — Numeric ID of the expense category to classify the expense.
- Amount (required) — Monetary amount of the expense.
- Date (required) — Date of the expense in YYYY-MM-DD format; can be left empty to default to today's date.
- Currency (required) — Numeric ID representing the currency used for the expense.
- Expense name — Optional descriptive name for the expense.
- Note — Optional note providing additional details about the expense.
- Customer (clientid) — Optional customer ID or searchable keyword (such as name or email) to link the expense to a customer.
- Tax — Optional Tax 1 amount or rate associated with the expense.
- Tax2 — Optional Tax 2 amount or rate associated with the expense.
- Paymentmode — Optional numeric ID representing the payment mode used.
- Reference no — Optional reference number string for the expense.
- Recurring — Optional string indicating recurrence frequency (values 1 to 12 or 'custom').
- Repeat every custom — Optional numeric gap number if recurrence is set to custom.
- Repeat type custom — Optional unit for custom recurrence gap: day, week, month, or year.
Output shape
A single JSON object representing the newly created expense record returned by the BackOffice ERP API.
Returns the full expense data as received from the API upon successful creation. If multiple matches occur during smart search (for example, customer identification), a message with possible matches is returned instead. Errors halt execution unless 'continue on fail' is enabled.
Examples
Example 1: Create an expense with mandatory details
Set category, amount, date, and currency; optionally include expense name and note.
Example 2: Create a recurring expense linked to a customer
Specify recurring fields and clientid with a searchable name.