Create invoice

Authentication

Bearer token authentication. Pass your DayZero API token in the Authorization header and the target business UUID in x-business-id.

Request body

Schema: InvoiceCreateRequest

customer_idstringrequired

UUID of the customer to invoice.

currencystring

Currency for the invoice (USD, CAD, AUD, EUR, or GBP). Defaults to business default.

line_itemsarray · LineItemRequestrequiredLineItemRequest

Line items (at least one required). Can be variant-linked or custom.

9 fields

variant_idstring

UUID of product variant. Omit or use 'custom' for manual line items.

catalog_item_idstring

UUID of a Products & Services catalog item (Books). Mutually exclusive with a real variant_id. When set, description and unit_price default from the catalog item; provide unit_price to override the catalog price for this invoice.

quantityinteger

Quantity ordered. Defaults to 1 for custom items.

descriptionstring

Line item description (required for custom items).

unit_priceinteger

Price per unit in cents. Required for custom items. For variant-linked items this is an OPTIONAL override - if omitted, the current catalog price is used; if provided, the catalog price is ignored for this invoice. The override is snapshotted onto the invoice line item. Negative only on a custom item, for a discount or credit (e.g. -12000 for a $120.00 discount); variant and catalog lines must be 0 or more, and the invoice's lines may not add up to less than 0.

amountinteger

Total amount in cents. Deprecated for custom items - use unit_price instead. For backward compatibility, if unit_price is not set, amount is treated as unit_price.

location_idstring

Optional warehouse UUID to deduct this line from. Overrides the invoice's fulfillment_location_id and the business default. Ignored for custom (non-variant) lines.

notestring

Optional free-text note for this line item, shown alongside the description (e.g. internal context or a customer-facing clarification). Not used in pricing calculations.

deferredboolean

Tag this line's revenue as deferred. Drives the default amount suggested when a deferral is created for the invoice (see suggested_deferred_amount_cents on the deferral-status response) - it does not defer anything by itself and has no effect once a deferral already exists.

due_datestringrequired

Payment due date in YYYY-MM-DD format.

issue_datestring

Optional 'Date of issue' in YYYY-MM-DD format — the date the invoice is dated and reported under. Backdates the invoice: it becomes the invoice's date in the app, the date its finalization journal entry posts on, and the issue date on the PDF and receipt in place of the system-generated one. Also accepted as 'invoice_date', which is what the update endpoint calls it.

invoice_numberstring

Optional invoice number to use instead of the next one from the business's auto-numbering — e.g. the number this invoice already carries in the system it is being migrated from. Must be unique within the business.

descriptionstring

Optional invoice description or notes.

fulfillment_location_idstring

Default warehouse UUID for inventory deductions when the invoice is delivered. Per-line location_id overrides this.

project_idstring

Optional UUID of a project (job) to link this invoice to. When the invoice is finalized, its revenue and COGS are attributed to this project for profitability reporting.

payment_term_idstring

Optional UUID of the payment term this invoice was issued under (Net 30, Due on Receipt ...). It is recorded for reference and reporting; due_date is still the date the invoice is actually due, so a due date you set yourself always wins over the term.

tax_exemptboolean

True to charge no sales tax on this invoice even though the business has a default tax rate. Sales tax is worked out when the invoice is finalized.

recurringInvoiceRecurringConfig

If provided, creates a recurring template for this invoice.

historicalboolean

Record an invoice that was already issued somewhere else, for backfilling books, rather than issuing a new one. The invoice is written locally as a draft and never reaches Stripe, so it cannot be sent to or charged to the customer, and no Stripe account is required. It also lifts the rule that a due date must be in the future — a historical invoice normally came due in the past. Pair it with issue_date and invoice_number to preserve the date and number the invoice carried in the old system.

Responses