Skip to main content
PUT
Update organisation invoice template

Authorizations

X-Auth-Token
string
header
required

Authentication token for API access

Body

application/json

Document (invoice or credit note) template: grouping, sort order, line description formula, attachment strategy. Same shape for org default and per-client override. Grouping is driven by booleans (subsection header, subtotal row, VAT and quantity total in subsection and in bottom subtotals).

showSubsectionHeader
boolean

When true, emit group header lines (e.g. "--- Pay Element ---") when client uses subtotal grouping.

showSubtotalInSubsection
boolean

When true (and showSubsectionHeader is true), emit a subtotal row after each group with amount and optionally VAT and quantity total.

showSubtotalVatInSubsection
boolean

When true, include VAT in each subsection subtotal row description.

showQuantitySumInSubsection
boolean

When true, include quantity total (sum of quantities/units in the group) in each subsection subtotal row description.

showBottomSubtotals
boolean

When true, emit a bottom block listing all group subtotals after the lines.

showVatInBottomSubtotals
boolean

When true, include VAT in each bottom subtotal line description.

showQuantitySumInBottomSubtotals
boolean

When true, include quantity total in each bottom subtotal line description.

lineItemSortOrder
enum<string>

Sort order for line items when subsection/grouping is not used (e.g. as stored, by employee A–Z, by pay element then employee).

Available options:
None,
ByEmployee,
ByPayElementThenEmployee
lineDescriptionFormula
string | null

Template string with placeholders (e.g. "{description} - {employeeName} - {poNumber}"). Use ids from GET /finance/line-item-description-fields in curly braces. When null, use line Description only.

lineDescriptionTagGroupId
string | null

Optional tag group key when formula uses {tagValue}. Required when a placeholder with requiresTagGroup is used. Stored as a normalised key.

attachmentStrategy
enum<string>

How to handle attachments when over provider limit (e.g. excess lost vs merge on integration).

Available options:
ExcessLost,
MergeOnIntegration
includeAttachmentsWithOnlineInvoice
boolean

When true, the customer can see the attached files on their own copy of the document rather than them being an internal record only.

Response

OK

Billing's response envelope: the platform's (message.text + message.token, content.data + content.metadata, validationIssues) plus the fields billing sent before it (PRODLAUNCH-416). Those are deprecated, removed on 31 December 2026, and are projections of their replacements so the two cannot disagree.

message
object
required

What happened, as English text and a stable snake_case token to translate from.

content
object
validationIssues
object[] | null
errors
object[] | null
deprecated
read-only

Deprecated: the same issues as validationIssues (reasonText is reason, reasonId is reasonToken, reasonParameters is reasonTokenArguments). Read validationIssues; this will be removed.

metadata
object
deprecated

Deprecated: the same values as content.metadata. Read that; this will be removed.