Update Payout Finance Settings
PUT/api/temu/:integrationInstance/payout-finance-settings
Changes how the store books Temu sales. Omitted fields are left unchanged. Changing the mode or the start date re-evaluates every payout and every per-order invoice and credit of the store; documents already sent to the accounting provider are not voided.
accounting:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token and the integrations.update permission. Open to API tokens with the accounting:write scope.
Body (all optional): accounting_sync_mode (per_order or per_payout), payout_accounting_start_date (nullable date, Y-m-d), fallback_revenue_nominal_code_id (nullable account ID), fallback_expense_nominal_code_id (nullable account ID), split_payouts_at_month_end (boolean, default true: a statement crossing a month end posts one part per month; applies to statements recorded afterwards).
- effective_from (optional, nullable, string, Y-m-d): payouts dated on or after this date (by payout date) use the change and are rebuilt; earlier ones keep the accounts they posted with. Defaults to today. Must be after the accounting lock date.
Mapping changes are dated. Each change applies to payouts dated on or after effective_from (by payout date), so payouts already in your books before that date keep the accounts they posted with. GET /api/ledger/payout-mapping-periods (List Payout Mapping Periods, kind temu_payout_type_mapping or temu_payout_fallback_setting) returns a row's dated history and scheduled changes, and GET /api/ledger/payout-mapping-periods/impact (Preview Payout Mapping Change) counts the payouts a change would rebuild.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
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.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Content
Response Headers
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.