BackOffice ERP icon

BackOffice ERP

BackOffice ERP API with Google-style smart search. IMPORTANT FOR AI: Use customer/project names instead of IDs (e.g., "VIGACA" not customer ID 123). Supports AI auto-fill from conversation context. Handles case-insensitive search across all business entities.

Invoices → Update

AI-generated

Summary

Update an existing invoice in the BackOffice ERP system by specifying the invoice ID along with required and optional invoice fields for modification.

Inputs

  • Invoice Id (required) — Exact invoice ID or use smart search with name, email, or keyword to identify the invoice to update.
  • Customer (required) — Customer id linked to the invoice; supports smart search by entering name, email, or keyword instead of the numeric ID.
  • Number (required) — Invoice number; can be left empty to auto-generate.
  • Date (required) — Invoice date formatted as YYYY-MM-DD; leave empty to use today's date.
  • Currency (required) — Numeric code for the currency used in the invoice.
  • Newitems (required) — Items to be added to the invoice.
  • Billing Street (required) — Billing street address.
  • Allowed payment modes (required) — Comma-separated string of allowed payment modes for this invoice.
  • Billing City — Billing city name.
  • Billing State — Billing state name.
  • Billing ZIP Code — Billing zip code.
  • Billing Country — Billing country code as a number.
  • Include shipping="no" — Boolean flag to indicate if shipping address should be added.
  • Show shipping on invoice — Boolean flag to show shipping details on the invoice.
  • Shipping street — Shipping street address.
  • Shipping city — Shipping city name.
  • Shipping state — Shipping state name.
  • Shipping zip — Shipping zip code.
  • Shipping country — Shipping country code.
  • Duedate — Due date for the invoice in date-time format.
  • Cancel overdue reminders — Boolean to prevent sending overdue reminders for the invoice.
  • Tags — Comma-separated tags associated with the invoice.
  • Sale agent — ID of the sales agent related to the invoice.
  • Recurring — Recurring frequency value from 1 to 12 or custom.
  • Discount type — Specifies if the discount is applied before_tax or after_tax.
  • Repeat every custom — Number gap if recurring is custom.
  • Repeat type custom — Gap option (day/week/month/year) if recurring is custom.
  • Cycles — Number of recurring cycles; 0 means infinite.
  • Adminnote — Administrative notes related to the invoice.
  • Items — Existing invoice items with their IDs.
  • Removed items — IDs of items to remove from the invoice.
  • Clientnote — Notes from the client.
  • Terms — Terms and conditions for the invoice.

Output shape

a list with a single JSON object containing the API response for the updated invoice or error details if update failed

If multiple matches occur in smart search, workflow output includes multiple_matches information with suggestions. Workflow continues on fail if enabled, returning error details per item.

Examples

Example 1: Update invoice 1234 for customer 'ACME Corp' with new items and payment info

Provide Invoice Id as '1234' or search term 'ACME Corp' for customer, specify required fields such as Customer, Number, Date, Currency, Newitems, Billing Street, and Allowed payment modes. Optionally include shipping details, tags, notes, recurring settings, and other invoice fields as needed.

Discussion