Indicates whether the invoice should be automatically processed after creation/import.

When set to true and the invoice passes validations:

• For sending transports (non-download), the invoice is queued to be sent asynchronously.
• For download transport, the invoice is not sent. Instead, if tax report generation is enabled and required for this invoice, the invoice will be issued and the tax report generated
  (invoice ends in state=issued and exposes tax_report_ids). Otherwise, the invoice may end in state=error.

Note: This option is incompatible with the custom signature configuration.

Indicates whether the invoice should be issued synchronously after creation/import, without going through the transport send flow.

When set to true and the invoice passes validations:

• The invoice transitions to state=issued (c1 corner) inline.
• If the account has a before_send tax report setting enabled with auto_generate on and the invoice qualifies, the tax report is generated inline and exposed via tax_report_ids. When auto_generate is off the invoice is still issued but no report is created, consistent with the send flow — those reports are managed through the Tax Reports API.
• Authorities that report after sending (for example SII or SDI) are not triggered by issuing; their reports are created when the invoice is sent or marked as sent.
• No background send job is enqueued; the transport-level state (c2) remains untouched.
• While in state=issued the invoice becomes read-only: it cannot be updated, deleted, or reverted to new until it is sent or downloaded.

If both send_after_import and issue_after_import are true, send_after_import wins (sending already issues the invoice). Ignored for non-invoice documents.

When true, merges the descriptive data (address, city, etc.) of the invoice's contact hash into the matched contact. Routing and tax identifiers (cin_value, pin_value, routing_codes, tin_value) are only filled in when blank on the contact — a value already present is never overwritten. When false (default), a difference in the descriptive data or the routing identifiers leaves the matched contact unchanged and creates an office under it instead.

Ignored for received documents: an inbound invoice never rewrites an existing contact's data.

Mark the invoice as acknowledged.