Generate Sales Order Accounting Transaction

POST 
/api/sales-orders/:salesOrder/generate-accounting-transaction

Generates — or regenerates — the accounting transaction (invoice journal) for a sales order from its current lines and financial data. Use this after correcting an order to refresh the journal without waiting for the next scheduled accounting sync.

Required scope: orders:write

Grant this scope to your token under Settings → Developer → Personal Access Tokens.

Authentication: Requires Bearer token.

Behavior:

• No request body is required.
• The response returns the generated transaction with its lines and nominal codes. Tax rate details, parent/children, and accounting-integration sync metadata are not expanded on this response — fetch GET /api/sales-orders/{salesOrder}/accounting for the fully expanded transaction.
• Regeneration replaces the transaction's lines to match the order's current state.

Path parameters:

• salesOrder (required): Sales order ID.

Requires permission: sales_orders.update

Request

Responses

200

OK

Response Headers

Content-Type

401

Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.

403

Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.

404

Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.

422

Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.

429

Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.