Update Payout Statement
PUT/api/temu/:integrationInstance/payouts/:payout
Corrects a recorded statement: replaces its figures and lines and re-evaluates it (and the statement after it) for posting. Refused with 422 once the payout's documents are in the accounting provider; void them in the ledger first.
accounting:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Also refused (422) when it would change the reserve handed on to a later statement whose documents are already in the accounting provider.
Authentication: Requires Bearer token and the integrations.update permission. Open to API tokens with the accounting:write scope.
Body: period_start_date (required, Y-m-d), period_end_date (required, Y-m-d, on or after the start), payout_date (required, Y-m-d, the day Temu paid out; not before the period start), amount (required, the statement Payout amount), beginning_balance (optional, default 0), sales (optional, ≥ 0), refunds (optional, ≤ 0), others (optional, either sign), reserves (optional, ≤ 0), currency (optional 3-letter code, default the account currency), temu_payout_id (optional, max 64, unique per store), payout_status (optional, max 64), bank_account (optional, max 64), notes (optional, max 2000), month_parts (see below).
Every amount is in whole cents (at most two decimal places). Amounts are signed the way Temu Seller Center shows them (Finances → Payments → Statements). The five columns must add up to amount exactly, and the period must not overlap another statement of the store; otherwise the response is 422.
Month-end split: when the store's split_payouts_at_month_end setting is on (the default) and the period crosses a month end, send month_parts: one entry per month end the period crosses, [{"month_end_date": "2026-09-30", "sales": 120.00, "refunds": 0, "others": 0}], with that earlier month's own amounts (not a running total). The last month gets the rest. The statement then posts one document set per month, earlier months dated on their last day. Missing, extra or oversized parts are refused (422); a statement that does not split must send none. A correction keeps the split the statement was recorded with.
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
Response Headers
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.