<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>FBTops</title>
	<atom:link href="https://fbtops.com/feed/" rel="self" type="application/rss+xml" />
	<link>https://fbtops.com/</link>
	<description>TikTok Shop reimbursement &amp; FBT recovery service (US)</description>
	<lastBuildDate>Tue, 14 Jul 2026 14:02:39 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.1</generator>
	<item>
		<title>How to Identify Duplicate TikTok Shop Refunds in Settlement Reports</title>
		<link>https://fbtops.com/identify-duplicate-tiktok-shop-refunds-settlement-reports/</link>
		
		<dc:creator><![CDATA[Oleksandr Bondar]]></dc:creator>
		<pubDate>Mon, 13 Jul 2026 10:55:43 +0000</pubDate>
				<category><![CDATA[Reconciliation]]></category>
		<guid isPermaLink="false">https://fbtops.com/?p=24</guid>

					<description><![CDATA[A sourced workflow for finding duplicate-looking TikTok Shop refund rows, ruling out false positives, proving net payout impact, and preparing a settlement evidence packet.]]></description>
										<content:encoded><![CDATA[
<p><strong>Direct answer:</strong> a duplicate TikTok Shop refund is not simply two rows with the same order ID and amount. It is a repeated net deduction for one underlying refund event, with no separate quantity, shipping, tax, fee, reversal, reserve movement or adjustment explaining the second impact. To prove it, match the order/SKU, statement lines, signed amounts, reserve activity, Payment ID and bank deposit before opening a support case.</p>

<div class="guide-verified"><strong>Last verified: July 13, 2026.</strong> This US guide uses TikTok Shop settlement, finance, refund and Finance API documentation. Settlement report labels, fee schedules, reserve levels and refund workflows can vary by seller, program and effective date. Use the seller&#8217;s current report and account record as the final source for a specific case.</div>

<nav class="guide-toc" aria-label="Duplicate TikTok Shop refunds guide contents">
<p>In this guide</p>
<ul>
<li><a href="#definition">What counts as duplicate-looking</a></li>
<li><a href="#records">Records to collect</a></li>
<li><a href="#workflow">Step-by-step review</a></li>
<li><a href="#false-positives">False positives</a></li>
<li><a href="#api">API and export checks</a></li>
<li><a href="#evidence">Evidence packet</a></li>
<li><a href="#faq">FAQ</a></li>
<li><a href="#sources">Official sources</a></li>
</ul>
</nav>

<h2 id="definition">What counts as a duplicate-looking TikTok Shop refund?</h2>
<p>A duplicate-looking refund is a pair or group of settlement entries connected to the same order, SKU, refund amount, date range or transaction description. Similarity makes the rows worth reviewing. It does not prove an error.</p>

<p>A stronger duplicate-refund case exists when all three conditions are true:</p>

<ul>
<li>One underlying refund event is tied to the same order/SKU or item quantity.</li>
<li>Two or more settled rows reduce the seller&#8217;s payable balance for that same event.</li>
<li>No valid second refund, tax/shipping component, fee impact, adjustment, reserve movement, reversal or later correction explains the extra deduction.</li>
</ul>

<div class="guide-answer"><strong>Important distinction:</strong> TikTok&#8217;s settlement report is statement-based, not order-creation-based. A refund may appear in a later statement than the original order, and an order still in <em>On hold</em> is not final settlement evidence.</div>

<figure class="svg-fig">
<img decoding="async" src="/wp-content/themes/fbtops-child/assets/img/duplicate-refund-scan.svg?v=1" alt="Duplicate TikTok Shop refund review workflow from candidate rows to net effect and case classification" loading="lazy" width="440" height="280">
<figcaption>Start with candidate rows, but confirm the signed net effect before calling a refund duplicate.</figcaption>
</figure>

<h2 id="records">Records to collect before you test duplicates</h2>
<p>Do not work from a screenshot of two similar refund rows. Export the source records and keep raw files unchanged. The goal is to reconstruct the financial path from refund event to statement and payout.</p>

<div class="guide-table">
<table>
<thead><tr><th>Record</th><th>Why it matters</th><th>Key fields to preserve</th></tr></thead>
<tbody>
<tr><td>Settlement report detail</td><td>Final settled lines and signed amounts</td><td>Statement ID, Statement Date, Payment ID, Status, Type, Order/adjustment ID, SKU ID, quantity, transaction label, signed amount</td></tr>
<tr><td>Order/refund record</td><td>Underlying refund event and status timeline</td><td>Order ID, refund/return ID, SKU, quantity, reason, approval/completion timestamps</td></tr>
<tr><td>Preceding and following statements</td><td>Later corrections, reversals or cross-period timing</td><td>Same order/SKU/refund references across adjacent statement periods</td></tr>
<tr><td>Reserve and payout record</td><td>Explains why statement amount and payout amount differ</td><td>Payment ID, reserve collection/release, payout status, bank-posting date</td></tr>
<tr><td>Bank deposit</td><td>Proves cash impact</td><td>Amount, posting date, descriptor and matched Payment ID context</td></tr>
<tr><td>Support history</td><td>Shows any prior adjustment or explanation</td><td>Case number, response, correction promise, affected statement</td></tr>
</tbody>
</table>
</div>

<p>The broader order-to-bank process is covered in <a href="/how-to-reconcile-tiktok-shop-payments/">how to reconcile TikTok Shop payments</a>. Use that workflow first if statements and payouts have not been matched end to end.</p>

<h2 id="workflow">Step-by-step duplicate refund review</h2>

<h3>1. Freeze the source files</h3>
<p>Save the original settlement export, payout/reserve export, order/refund export and bank record. Record market, shop, currency, date range, timezone and export timestamp. Work in a copy so the original evidence remains intact.</p>

<h3>2. Normalize signs without changing labels</h3>
<p>Keep TikTok&#8217;s original `Type` or transaction label. Add a working column for signed amount if needed, but do not rename refund, shipping, tax, fee, commission, FBT or adjustment rows into one generic &#8220;refund&#8221; bucket.</p>

<h3>3. Generate duplicate candidates</h3>
<p>Group rows by Order ID, SKU ID, amount, currency and nearby statement dates. Flag repeated negative refund-related amounts, but keep the candidate status as <strong>unresolved</strong> until the net effect is tested.</p>

<div class="guide-template">
<div class="guide-template-head"><strong>Candidate review columns</strong><button type="button" class="guide-copy-btn js-copy-template" data-copy-target="#duplicate-refund-columns">Copy columns</button></div>
<pre id="duplicate-refund-columns">case_id,statement_id,statement_date,payment_id,order_id,sku_id,refund_or_return_id,transaction_type,signed_amount,currency,quantity,event_date,candidate_reason,false_positive_check,net_effect,classification,next_action</pre>
<p class="guide-template-note">Use these as working columns. Preserve the original TikTok export separately.</p>
</div>

<h3>4. Compare the transaction type, not only the amount</h3>
<p>A product refund, seller discount refund, customer-paid shipping refund, TikTok shipping incentive refund, return shipping fee, sales tax refund, retail delivery fee refund, refund administration fee, affiliate commission effect or adjustment can share similar amounts. Similar amount does not mean duplicate deduction.</p>

<h3>5. Rebuild the refund timeline</h3>
<p>Place the refund request, approval, completion, posting, reversal, adjustment and payout events in order. A row in a later statement may be a correction, not a repeated refund. A row in <em>On hold</em> or unsettled API data is provisional and can change before final settlement.</p>

<h3>6. Trace the net payout effect</h3>
<p>Use TikTok&#8217;s settlement formula first, then bridge to payout. The official report guide defines total settlement amount as net sales plus shipping plus fees plus adjustment amount. The payout bridge also needs reserve activity: payout amount equals statement amount plus reserve amount.</p>

<div class="guide-formula">Duplicate test = same underlying refund event + repeated settled deduction &#8211; valid offset or explanation<small>Do not use this as an accounting formula; use it as a review rule for classifying candidates.</small></div>

<h3>7. Classify each candidate</h3>
<div class="guide-table">
<table>
<thead><tr><th>Classification</th><th>Use when</th><th>Next action</th></tr></thead>
<tbody>
<tr><td>Explained</td><td>Rows represent separate items, components, fees, taxes, reversals, reserves or corrections</td><td>Document the explanation and close the candidate</td></tr>
<tr><td>Timing difference</td><td>The same event appears across statement periods but only one final net deduction remains</td><td>Monitor the next payout or reserve release</td></tr>
<tr><td>Unresolved</td><td>The rows cannot be explained from exports alone</td><td>Gather support history or request transaction-level explanation</td></tr>
<tr><td>Supported duplicate</td><td>One refund event reduced payable balance twice without offset or valid second event</td><td>Prepare an evidence packet and open/follow up in Seller Center</td></tr>
</tbody>
</table>
</div>

<h2 id="false-positives">Common false positives</h2>
<p>Most candidate pairs are not true duplicate refunds. Rule these out before opening a support case.</p>

<div class="guide-table">
<table>
<thead><tr><th>False positive</th><th>Why it looks duplicated</th><th>How to rule it out</th></tr></thead>
<tbody>
<tr><td>Two units refunded separately</td><td>Same SKU and same amount repeats</td><td>Compare quantity, item-level refund IDs and refund timestamps</td></tr>
<tr><td>Product refund plus seller discount refund</td><td>Both rows are refund-related</td><td>Check transaction type and net sales components</td></tr>
<tr><td>Shipping or tax refund component</td><td>Amount is close to another refund row</td><td>Separate shipping, sales tax and retail delivery fee fields</td></tr>
<tr><td>Refund administration or commission impact</td><td>Fee line appears near refund lines</td><td>Keep fee/commission labels and signed amounts intact</td></tr>
<tr><td>Reserve collection or release</td><td>Payout differs from statement total</td><td>Bridge statement amount to payout amount with reserve records</td></tr>
<tr><td>Cross-period correction</td><td>Same order appears in adjacent statement</td><td>Check reversal/adjustment lines before and after the candidate period</td></tr>
<tr><td>Unsettled estimate</td><td>On-hold value resembles final refund</td><td>Wait for final statement or mark as provisional monitoring</td></tr>
</tbody>
</table>
</div>

<div class="guide-warning"><strong>Do not prove duplication from order ID and absolute amount alone.</strong> Settlement signs, transaction type, statement status, reserve movement and Payment ID determine whether the seller was actually charged twice.</div>

<h2 id="api">API and export checks for higher-volume sellers</h2>
<p>Manual exports are enough for a first review. At higher volume, use Finance API records to reproduce the same logic with versioned endpoints and authorized access. API data still needs source preservation and final-settlement controls.</p>

<div class="guide-table">
<table>
<thead><tr><th>Official record</th><th>Use in duplicate-refund review</th><th>Limit</th></tr></thead>
<tbody>
<tr><td><code>GET /finance/202309/statements</code></td><td>Enumerate Statement IDs and payment statuses before drilling down</td><td>Does not prove refund duplication by itself</td></tr>
<tr><td><code>GET /finance/202501/statements/{statement_id}/statement_transactions</code></td><td>Review all transaction lines inside a statement, including adjustments and reserve-related entries</td><td>Use order-level endpoint for SKU detail</td></tr>
<tr><td><code>GET /finance/202501/orders/{order_id}/statement_transactions</code></td><td>Primary API path for order/SKU-level refund, fee, commission, shipping and tax lines</td><td>Do not invent JSON fields beyond the official docs</td></tr>
<tr><td><code>GET /finance/202507/orders/unsettled</code></td><td>Early monitoring for candidate refunds not yet finalized</td><td>Estimated and subject to change; not final proof</td></tr>
<tr><td><code>GET /finance/202605/payments</code> or withdrawals endpoint</td><td>Bridge statement/payout movement to bank reconciliation</td><td>Not the source for underlying refund cause</td></tr>
</tbody>
</table>
</div>

<p>API access should use TikTok&#8217;s OAuth authorization model and the documented `seller.finance.info` scope where required. For access and authorization controls, see the current <a href="/fbt-lost-package-claim/#lpoa">third-party authorization guidance</a> in our FBT claim guide.</p>

<h2 id="evidence">Build the evidence packet</h2>
<p>When the candidate remains unresolved or is supported as a duplicate, prepare the case so support can trace the exact ledger effect without guessing.</p>

<ul>
<li>Seller account, market, statement period, currency and timezone.</li>
<li>Statement ID, Statement Date, Payment ID and payout status.</li>
<li>Order ID, SKU ID, quantity, refund/return ID where available.</li>
<li>Original export filenames and row numbers for every candidate line.</li>
<li>Signed calculation showing expected versus reported net effect.</li>
<li>Reserve bridge and bank deposit match, if the issue affected payout.</li>
<li>Timeline of refund, posting, reversal, adjustment and payout events.</li>
<li>Prior support case numbers and responses, with customer PII redacted.</li>
</ul>

<div class="guide-template">
<div class="guide-template-head"><strong>Support request wording</strong><button type="button" class="guide-copy-btn js-copy-template" data-copy-target="#duplicate-refund-ticket">Copy template</button></div>
<pre id="duplicate-refund-ticket">Subject: Request for transaction-level explanation - possible duplicate refund deduction

Hello TikTok Shop Support,

We are reviewing settlement statement [Statement ID] / payment [Payment ID] for [shop name]. The attached rows appear to show more than one settled deduction tied to the same refund event:

- Order ID: [order]
- SKU / Goods ID: [sku]
- Refund or return ID: [if available]
- Statement row(s): [row numbers / transaction labels]
- Signed amount(s): [amounts and currency]
- Payout impact reviewed: [yes/no]

Please confirm whether these rows represent separate valid transaction components, a correction/reversal sequence, reserve movement, or a repeated deduction. If this is a repeated deduction, please advise the correction path and expected statement or adjustment reference.

Thank you.</pre>
<p class="guide-template-note">Attach source rows and calculations. Do not include buyer personal data unless support specifically requires it through the secure Seller Center workflow.</p>
</div>

<h2 id="faq">FAQ</h2>
<details><summary>Is the same refund amount appearing twice always an error?</summary><p>No. Equal amounts can come from separate units, separate refund components, shipping or tax lines, fee effects, adjustments, reserve activity or timing differences. Treat it as a candidate until the net effect is tested.</p></details>
<details><summary>Should I use On hold data to prove a duplicate refund?</summary><p>No. On-hold and unsettled API values are provisional and can change. Use them for early monitoring, then confirm with final statement records.</p></details>
<details><summary>What is the best key for detecting duplicate refunds?</summary><p>Use a combined key: Statement ID, Order ID, SKU ID, refund or return ID when available, transaction type, signed amount, currency, quantity and event date. Order ID plus amount alone is too weak.</p></details>
<details><summary>How do reserves affect duplicate refund review?</summary><p>Reserves can make payout amount differ from statement amount without any duplicate refund. Use the reserve export to bridge statement amount to payout amount before claiming a cash impact.</p></details>
<details><summary>When should I contact support?</summary><p>Contact support when the candidate remains unresolved after transaction-type, timeline, reserve and payout checks, or when the evidence shows a repeated net deduction for one refund event.</p></details>

<section class="guide-sources" id="sources">
<h2>Official sources</h2>
<ol>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=2336057241700098&amp;default_language=en" target="_blank" rel="noopener">How to Access Your Settlement Report</a>, September 11, 2025. Settlement-based reporting, SKU/order fields, formulas, refund/shipping/tax/FBT lines and payout bridge.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=2470273945257771&amp;lang=en" target="_blank" rel="noopener">Finances Page FAQ</a>, August 11, 2025. On hold, Processing, Paid, Failed, Pending, bank posting and negative settlement behavior.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=754576121693998" target="_blank" rel="noopener">How to View Your Reserve Record</a>, September 11, 2025. Reserve records and final payout amount formula.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=3995852763531009&amp;default_language=en" target="_blank" rel="noopener">Dynamic Settlement and Reserve Policy</a>, June 30, 2026. Account-specific settlement tiers and reserves.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=3253210454181634" target="_blank" rel="noopener">Customer Order Cancellation, Return, and Refund Policy</a>, July 8, 2026. Refund workflows, seller cost default and FBT logistics-related requests.</li>
<li><a href="https://partner.tiktokshop.com/docv2/page/get-statements-202309" target="_blank" rel="noopener">Get Statements</a>; <a href="https://partner.tiktokshop.com/docv2/page/get-transactions-by-statement-202501" target="_blank" rel="noopener">Get Transactions by Statement</a>; <a href="https://partner.tiktokshop.com/docv2/page/get-transactions-by-order-202501" target="_blank" rel="noopener">Get Transactions by Order</a>; <a href="https://partner.tiktokshop.com/docv2/page/get-unsettled-transactions-202507" target="_blank" rel="noopener">Get Unsettled Transactions</a>; <a href="https://partner.tiktokshop.com/docv2/page/get-payments-202605" target="_blank" rel="noopener">Get Payments</a>; <a href="https://partner.tiktokshop.com/docv2/page/get-withdrawals-202309" target="_blank" rel="noopener">Get Withdrawals</a>.</li>
</ol>
</section>

<div class="guide-change-log"><strong>Change log.</strong> July 13, 2026: rebuilt as a sourced duplicate-refund review workflow; added statement/payout/reserve controls, Finance API checks, false-positive table, evidence packet, support wording and visual workflow. Removed unsupported assumptions that matching amount/order alone proves duplication.</div>

<div class="guide-cta">
<p class="guide-cta-title">Need a refund variance reviewed before it becomes noise?</p>
<p>FBTops traces refund candidates through statements, reserves, payouts and bank records, then separates explained entries from possible duplicate deductions and other reimbursement opportunities.</p>
<a class="guide-cta-btn" href="/free-audit/">Request a free 14-day audit</a>
<small>Independent service. Not affiliated with TikTok. Outcomes depend on account records and applicable policy.</small>
</div>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>What Evidence Supports an FBT Reimbursement Claim?</title>
		<link>https://fbtops.com/what-evidence-supports-fbt-reimbursement-claim/</link>
		
		<dc:creator><![CDATA[Oleksandr Bondar]]></dc:creator>
		<pubDate>Mon, 13 Jul 2026 10:54:43 +0000</pubDate>
				<category><![CDATA[FBT Claims]]></category>
		<guid isPermaLink="false">https://fbtops.com/?p=25</guid>

					<description><![CDATA[A scenario-based evidence checklist for FBT reimbursement claims, including outbound orders, IBR, WOP/WOT, OBC removal, U-PIC, settlement proof and Finance API records.]]></description>
										<content:encoded><![CDATA[
<p><strong>Direct answer:</strong> the best FBT reimbursement evidence packet connects five things: the affected order or Goods ID, the event that created the loss, the eligibility scenario, the value being requested, and proof that the reimbursement has not already posted. Evidence helps TikTok Shop evaluate a claim, but it does not make an ineligible scenario payable.</p>

<div class="guide-verified"><strong>Last verified: July 13, 2026.</strong> This US guide uses official TikTok Shop FBT, refund, settlement, shipping-insurance and Finance API documentation. Evidence requirements are scenario-specific. Recheck the live Seller Center ticket form and current policy before submitting a claim.</div>

<nav class="guide-toc" aria-label="FBT reimbursement evidence guide contents">
<p>In this guide</p>
<ul>
<li><a href="#framework">The five-part evidence framework</a></li>
<li><a href="#scenario-table">Evidence by claim scenario</a></li>
<li><a href="#outbound">Consumer-order FBT evidence</a></li>
<li><a href="#warehouse">IBR, WOP/WOT and OBC evidence</a></li>
<li><a href="#returns">Return/refund appeal evidence</a></li>
<li><a href="#settlement">Settlement and payout proof</a></li>
<li><a href="#packet">Build the packet</a></li>
<li><a href="#faq">FAQ</a></li>
<li><a href="#sources">Official sources</a></li>
</ul>
</nav>

<h2 id="framework">The five-part evidence framework</h2>
<p>A reimbursement reviewer should be able to open your packet and answer five questions without guessing:</p>

<ul>
<li><strong>Identity:</strong> Which order, Goods ID, SKU, IBR, WOP, WOT, OBC, package or tracking number is affected?</li>
<li><strong>Event:</strong> What official record shows the loss, damage, shortage, refund, return, adjustment or logistics issue?</li>
<li><strong>Eligibility:</strong> Which fulfillment route and policy scenario applies, and what exclusions must be ruled out?</li>
<li><strong>Value:</strong> What quantity and amount are being requested, and what invoice or statement record supports it?</li>
<li><strong>Settlement status:</strong> Did the credit already post in Seller Center Finance, FBT Billing, the statement report or payout?</li>
</ul>

<figure class="svg-fig">
<img decoding="async" src="/wp-content/themes/fbtops-child/assets/img/evidence-packet-map.svg?v=1" alt="FBT reimbursement evidence packet map: identity, event, eligibility, value and settlement proof" loading="lazy" width="440" height="286">
<figcaption>A strong packet maps every sentence in the claim to a source record, not to seller memory.</figcaption>
</figure>

<div class="guide-warning"><strong>Do not use one universal checklist.</strong> IBR, WOP, WOT, OBC, consumer-order logistics claims, refund appeals and U-PIC shipping insurance have different evidence needs. A document that matters in one route can be irrelevant or misleading in another.</div>

<h2 id="scenario-table">Evidence by FBT and reimbursement scenario</h2>
<div class="guide-table">
<table>
<thead><tr><th>Scenario</th><th>Core references</th><th>Evidence officially supported</th><th>Common mistake</th></tr></thead>
<tbody>
<tr><td>Consumer-order FBT logistics issue</td><td>Order ID, Goods ID, package/tracking, refund or return reason</td><td>Order/Goods ID, problem description, product photos where the scenario requires them, Seller Center ticket and Finance/FBT Billing confirmation</td><td>Assuming an automatic reimbursement posted without checking statements or FBT Billing</td></tr>
<tr><td>IBR inbound missing/extra/incorrect units</td><td>IBR, Goods ID, discrepancy quantity</td><td>Signed BOL for freight, carrier tracking/POD for small parcel, discrepancy record, commercial invoice if reimbursement is due</td><td>Treating every planned-versus-received shortage as automatically payable</td></tr>
<tr><td>IBR inbound damaged units</td><td>IBR, Goods ID, damaged quantity</td><td>Inbound damaged-unit ticket context, carrier/warehouse record, commercial invoice if reimbursement is due</td><td>Mixing inbound damage with in-warehouse WOT damage</td></tr>
<tr><td>WOP in-warehouse inventory lost</td><td>WOP, Goods ID, quantity</td><td>WOP reference, inventory event, Goods ID/quantity and commercial invoice if reimbursement is due</td><td>Using buyer order date instead of warehouse adjustment date</td></tr>
<tr><td>WOT in-warehouse inventory damaged</td><td>WOT, Goods ID, quantity</td><td>WOT reference, damaged inventory event, Goods ID/quantity and commercial invoice if reimbursement is due</td><td>Attaching photos that cannot be tied to the WOT event</td></tr>
<tr><td>OBC removal full package lost</td><td>OBC, Goods ID, quantity, handover/actual outbound time</td><td>OBC reference, Goods ID/quantity, tracking or handover record, commercial invoice if reimbursement is due</td><td>Filing a seller-arranged pickup under a TikTok-arranged transport route</td></tr>
<tr><td>OBC less items, wrong item or damage</td><td>OBC, requested/actual Goods ID, discrepancy or damaged quantity</td><td>Pictures for wrong/damaged items, signed BOL if available, received quantity record, commercial invoice if reimbursement is due</td><td>Filing a partial shortage as Package Lost</td></tr>
<tr><td>Legacy TikTok Shipping/U-PIC</td><td>Order, tracking, U-PIC claim, affidavit where required</td><td>Claim form, invoice, consignee statement/affidavit for listed scenarios, damage photos, carrier communication and additional requested docs</td><td>Applying U-PIC rules to FBT warehouse claims</td></tr>
<tr><td>Return/refund appeal</td><td>Order, return/refund ID, tracking, appeal reason</td><td>Photos or videos of product condition where relevant, return tracking, comments, CS requests and appeal decision</td><td>Calling an operational unboxing video a universal TikTok requirement</td></tr>
</tbody>
</table>
</div>

<p>The warehouse-claim timeframe matrix from TikTok&#8217;s inbound/warehouse/removal guide is future-effective from July 20, 2026. This article cites its evidence and path details, but filing-window language should still be checked against the rule active on the filing date.</p>

<h2 id="outbound">Consumer-order FBT evidence</h2>
<p>Consumer-order FBT logistics claims begin from the order and buyer-facing logistics event, not from a warehouse inventory adjustment. Official FBT materials point sellers to related order IDs or Goods IDs, a detailed problem description, required documents and product photos where the scenario calls for them.</p>

<h3>Collect these records</h3>
<ul>
<li>Order ID, Goods ID/SKU, quantity and package/tracking number.</li>
<li>Refund or return reason and whether TikTok Customer Service approved a logistics-related request.</li>
<li>Product photos for damaged, wrong or missing-item return scenarios where requested.</li>
<li>Seller Center support ticket ID and complete response history.</li>
<li>Seller Center Finance or FBT Billing evidence showing whether reimbursement is processing or settled.</li>
</ul>

<p>The outbound claims guide distinguishes automatic reimbursement scenarios from missed reimbursements that may need a ticket. Even when a scenario is designed to be automatic, reconcile the credit in Settled Statements or FBT Billing before closing the case. See the <a href="/fbt-lost-package-claim/">FBT lost package claim guide</a> for path selection and deadlines.</p>

<h2 id="warehouse">IBR, WOP/WOT and OBC evidence</h2>
<p>Warehouse claims use operational references. The packet should make it obvious whether the case is inbound, in-warehouse or product removal.</p>

<h3>IBR inbound cases</h3>
<p>For inbound missing, extra, incorrect, delayed or damaged-unit issues, use the IBR as the anchor. Official guidance names Goods ID and discrepancy quantity, with signed BOL for freight and carrier tracking/POD for small parcel where applicable. A commercial invoice is required if reimbursement is determined to be due.</p>

<div class="guide-answer"><strong>Eligibility note:</strong> an inbound discrepancy is not automatically reimbursable just because planned quantity is higher than received quantity. The evidence must support a covered warehouse/network issue or applicable exception.</div>

<h3>WOP/WOT in-warehouse cases</h3>
<p>Lost inventory uses WOP; damaged inventory uses WOT. Preserve the reference, inventory event date, Goods ID, quantity and commercial invoice. Do not replace the warehouse event with a buyer-order timeline.</p>

<h3>OBC removal cases</h3>
<p>Removal claims use OBC. A full shipment loss, partial shortage, wrong item and damaged item are different scenarios. Wrong or damaged items require pictures of the received or damaged units; a signed BOL is used where available. The announced compensation route applies only when TikTok arranged the return transportation.</p>

<div class="guide-table">
<table>
<thead><tr><th>Reference</th><th>Use it for</th><th>Do not confuse with</th></tr></thead>
<tbody>
<tr><td>IBR</td><td>Inbound order issue: missing, extra, incorrect, delayed or damaged receiving</td><td>Warehouse loss after receipt</td></tr>
<tr><td>WOP</td><td>Product in Warehouse: Inventory Lost</td><td>Consumer-order lost package</td></tr>
<tr><td>WOT</td><td>Product in Warehouse: Inventory Damaged</td><td>Inbound damaged units or buyer return damage</td></tr>
<tr><td>OBC</td><td>Product Removal: package lost, less items received, incorrect item or damaged product</td><td>Inbound IBR or seller-arranged pickup claim</td></tr>
</tbody>
</table>
</div>

<h2 id="returns">Return/refund appeal and shipping-insurance evidence</h2>
<p>Official return/refund policy supports photos or videos of products, comments about item condition, and delivery evidence such as shipping labels, receipts, photos or videos of delivery where relevant. It does not make an &#8220;unboxing video&#8221; a universal public requirement. A continuous unboxing video can be a useful operational control, but publish it as a best practice, not a guaranteed or universal TikTok rule.</p>

<p>Legacy TikTok Shipping/U-PIC is a separate evidence route. U-PIC-related pages support claim forms, invoices, consignee statements or affidavits in listed scenarios, damage photos, carrier proof and additional documentation requested by the insurer. Do not apply U-PIC affidavit or 90-day insurance rules to FBT warehouse claims.</p>

<h2 id="settlement">Settlement and payout proof</h2>
<p>Claim evidence is not complete until the financial record is checked. A reimbursement is not recovered cash until it appears in Seller Center Finance, FBT Billing, a statement adjustment, payout record or bank-matched deposit.</p>

<div class="guide-table">
<table>
<thead><tr><th>Financial record</th><th>What it proves</th><th>How to use it</th></tr></thead>
<tbody>
<tr><td>Settlement report</td><td>Statement Date, Statement ID, Payment ID, Status, Type and order/adjustment ID</td><td>Verify adjustment reasons such as logistics reimbursement or TikTok Shop reimbursement</td></tr>
<tr><td>FBT Billing / Billing Details</td><td>FBT-specific reimbursement or charge posting where applicable</td><td>Confirm whether an approved FBT reimbursement has posted</td></tr>
<tr><td>Finance status</td><td>On hold, Processing, Paid, Failed or Pending state</td><td>Do not treat On hold estimates as final payment proof</td></tr>
<tr><td>Payout or payment record</td><td>Whether money was sent toward the bank</td><td>Paid means sent, not necessarily bank-posted</td></tr>
<tr><td>Bank statement</td><td>Cash received</td><td>Match amount, posting date and descriptor to Payment ID context</td></tr>
<tr><td>Finance API records</td><td>Repeatable statement, transaction, order and payment data under authorized access</td><td>Use `seller.finance.info` endpoints for reconciliation; do not expose tokens or PII</td></tr>
</tbody>
</table>
</div>

<p>For duplicate or missing settlement entries, use <a href="/identify-duplicate-tiktok-shop-refunds-settlement-reports/">the duplicate refund review workflow</a> before opening a support case. For a full order-to-bank process, use <a href="/how-to-reconcile-tiktok-shop-payments/">the TikTok Shop payment reconciliation guide</a>.</p>

<h2 id="packet">Build the final evidence packet</h2>
<p>Use a short index so the reviewer can move from the narrative to the exact attachment.</p>

<div class="guide-template">
<div class="guide-template-head"><strong>Evidence packet index</strong><button type="button" class="guide-copy-btn js-copy-template" data-copy-target="#evidence-packet-index">Copy index</button></div>
<pre id="evidence-packet-index">Case name: [scenario] - [reference ID] - [Goods ID / SKU]
Seller / shop: [legal name and shop]
Market: US
Scenario: [consumer-order FBT / IBR / WOP / WOT / OBC / refund appeal / U-PIC]
Primary reference: [Order ID / IBR / WOP / WOT / OBC / tracking]
Affected item and quantity: [Goods ID, SKU, quantity]
Trigger event and date: [order placed / first receive / inventory adjustment / handover / refund approval]
Eligibility note: [why this scenario is covered; exclusions ruled out]
Value requested: [amount, currency, valuation source]
Prior credit check: [statement / FBT Billing / payout result]
Attachments:
1. [source record with IDs]
2. [tracking / BOL / POD / warehouse event]
3. [photos/videos if scenario requires]
4. [commercial invoice or valuation record]
5. [settlement / payout / billing proof]
Open question for support: [exact question]</pre>
<p class="guide-template-note">Keep attachment filenames descriptive and preserve originals. Redact buyer personal data unless Seller Center specifically requests it through a secure workflow.</p>
</div>

<h3>Weak evidence patterns to avoid</h3>
<ul>
<li>Cropped screenshots that remove IDs, dates, account context or URLs.</li>
<li>One generic folder with mixed IBR, WOP/WOT, OBC and order evidence.</li>
<li>Requested amount with no commercial invoice, statement line or calculation.</li>
<li>Photos or videos that do not show the relevant item, package, label or condition.</li>
<li>Speculative narrative such as &#8220;warehouse lost it&#8221; without the warehouse or carrier record.</li>
<li>On-hold or unsettled data presented as final payout proof.</li>
<li>U-PIC affidavit requirements copied into unrelated FBT warehouse claims.</li>
</ul>

<h2 id="faq">FAQ</h2>
<details><summary>Does evidence guarantee an FBT reimbursement?</summary><p>No. Evidence helps TikTok Shop evaluate a claim, but eligibility depends on the scenario, fulfillment route, transport responsibility, timing and current policy.</p></details>
<details><summary>Is an unboxing video required for every claim?</summary><p>No official public source reviewed here states that an unboxing video is required for every FBT claim. Photos or videos can be relevant for product-condition and return/refund issues, and a continuous unboxing video can be a useful operational best practice.</p></details>
<details><summary>What is the most important evidence for an inbound shortage?</summary><p>The IBR, Goods ID, discrepancy quantity, signed BOL for freight or carrier tracking/POD for small parcel, and a commercial invoice if reimbursement is due. Eligibility still depends on whether the discrepancy is covered.</p></details>
<details><summary>What evidence proves the reimbursement was paid?</summary><p>Use Seller Center Finance, FBT Billing, statement adjustments, payout/payment status and bank reconciliation. A ticket approval alone is not final cash proof.</p></details>
<details><summary>Can Finance API data support evidence packets?</summary><p>Yes, when accessed through authorized seller tokens and documented scopes. Statement, order transaction and payment endpoints can support reconciliation, but API records should be archived safely and should not expose tokens, PII or bank data.</p></details>

<section class="guide-sources" id="sources">
<h2>Official sources</h2>
<ol>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=1347196964587277" target="_blank" rel="noopener">US FBT Seller Reimbursement Operation Manual</a>, June 5, 2026. FBT ticket basics, order/Goods ID, product photos where specified and Finance/FBT Billing posting references.</li>
<li><a href="https://scm-us.tiktok.com/merchant-university/course-details/26903053318" target="_blank" rel="noopener">Guide to Claims: Outbound Order Claims for Logistics-Related Issues</a>, July 2, 2026. Consumer-order FBT logistics claim handling and settlement verification.</li>
<li><a href="https://scm-us.tiktok.com/merchant-university/course-details/26935332358" target="_blank" rel="noopener">Guide to Claims: Product Inbound, In Warehouse, and Product Removal</a>, June 19, 2026. IBR/WOP/WOT/OBC references, scenario evidence, commercial invoice and July 20 future-effective timing matrix.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=3253210454181634" target="_blank" rel="noopener">Customer Order Cancellation, Return, and Refund Policy</a>, July 8, 2026. Photos/videos and delivery evidence for relevant refund/return scenarios.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=8338237340780289" target="_blank" rel="noopener">Appeal Return/Refund Orders in Seller Center</a>, October 7, 2024. Appeal reasons, evidence upload and CS requests.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=8280381640656683" target="_blank" rel="noopener">How to File a Reimbursement Claim for Legacy TikTok Shipping Logistics Issues</a>, April 24, 2026. Legacy TikTok Shipping evidence, affidavit and damage-photo scenarios.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=6626878837311275" target="_blank" rel="noopener">Shipping Insurance</a>, May 14, 2026, and <a href="https://u-pic.com/tiktok-coverage" target="_blank" rel="noopener">U-PIC TikTok Coverage Terms</a>. U-PIC claim form, invoice, package receipt, affidavit/consignee statement and carrier proof where applicable.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=2336057241700098&amp;default_language=en" target="_blank" rel="noopener">How to Access Your Settlement Report</a>, September 11, 2025. Statement ID, Payment ID, adjustment reasons and reimbursement/settlement verification.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=2470273945257771&amp;lang=en" target="_blank" rel="noopener">Finances Page FAQ</a>, August 11, 2025. On hold, Processing, Paid, Failed and payout-to-bank reconciliation.</li>
<li><a href="https://partner.tiktokshop.com/docv2/page/get-statements-202309" target="_blank" rel="noopener">Get Statements</a>; <a href="https://partner.tiktokshop.com/docv2/page/get-transactions-by-statement-202501" target="_blank" rel="noopener">Get Transactions by Statement</a>; <a href="https://partner.tiktokshop.com/docv2/page/get-transactions-by-order-202501" target="_blank" rel="noopener">Get Transactions by Order</a>; <a href="https://partner.tiktokshop.com/docv2/page/get-payments-202309" target="_blank" rel="noopener">Get Payments</a>. Finance API records for authorized reconciliation support.</li>
</ol>
</section>

<div class="guide-change-log"><strong>Change log.</strong> July 13, 2026: rebuilt from a generic evidence checklist into a scenario-based evidence guide; added IBR/WOP/WOT/OBC distinctions, settlement and payout proof, U-PIC separation, API support, visible sources, FAQ and evidence packet template. Clarified that an unboxing video is a best practice, not a universal official requirement found in reviewed sources.</div>

<div class="guide-cta">
<p class="guide-cta-title">Need a claim packet checked before filing?</p>
<p>FBTops reviews FBT reimbursement evidence, settlement proof and eligibility gaps, then turns scattered exports into a case-ready packet with clear references and unresolved questions.</p>
<a class="guide-cta-btn" href="/free-audit/">Request a free 14-day audit</a>
<small>Independent service. Not affiliated with TikTok. TikTok determines eligibility and payment.</small>
</div>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>TikTok Shop Creator Commission Clawbacks: What Sellers Should Reconcile</title>
		<link>https://fbtops.com/tiktok-shop-creator-commission-clawbacks/</link>
		
		<dc:creator><![CDATA[Oleksandr Bondar]]></dc:creator>
		<pubDate>Mon, 13 Jul 2026 10:53:43 +0000</pubDate>
				<category><![CDATA[Fees & Payouts]]></category>
		<guid isPermaLink="false">https://fbtops.com/?p=26</guid>

					<description><![CDATA[A sourced reconciliation guide for TikTok Shop creator and affiliate commission adjustments after refunds, returns, settlement timing, and Finance API records.]]></description>
										<content:encoded><![CDATA[
<p><strong>Direct answer:</strong> TikTok Shop creator commission &#8220;clawbacks&#8221; should be reconciled as commission adjustments, reversals or final-settlement changes tied to an attributed order. A full refund can reduce actual standard affiliate commission to $0 before creator payment, but commissions are not universally recoverable after every refund. Use settled statement transactions, not estimated on-hold values, to confirm whether the commission, refund administration fee, affiliate partner commission or shop ads commission posted correctly.</p>

<div class="guide-verified"><strong>Last verified: July 13, 2026.</strong> This US guide uses official TikTok Shop settlement, affiliate, refund and Finance API documentation. Commission rates, collaboration terms, aftersales status and settlement timing can vary by seller and order. Verify the seller&#8217;s current account records before escalating a variance.</div>

<nav class="guide-toc" aria-label="Creator commission clawback guide contents">
<p>In this guide</p>
<ul>
<li><a href="#definition">What a commission clawback means</a></li>
<li><a href="#lifecycle">Commission lifecycle and 15-day timing</a></li>
<li><a href="#fields">Settlement fields to reconcile</a></li>
<li><a href="#refunds">Refund and return scenarios</a></li>
<li><a href="#workflow">Step-by-step reconciliation</a></li>
<li><a href="#api">Finance API checks</a></li>
<li><a href="#exceptions">Exception register and support packet</a></li>
<li><a href="#faq">FAQ</a></li>
<li><a href="#sources">Official sources</a></li>
</ul>
</nav>

<h2 id="definition">What does &#8220;creator commission clawback&#8221; mean?</h2>
<p>&#8220;Clawback&#8221; is common seller shorthand, not always TikTok&#8217;s report label. In settlement data, the same economic event may appear as a commission refund, negative commission, adjustment, canceled estimate, fee reversal or changed final commission. The reconciliation question is narrower: did the commission cost match the final eligible sale after refunds and returns?</p>

<p>For FBTops analysis, a creator commission clawback candidate exists when:</p>

<ul>
<li>An attributed order generated estimated or accrued affiliate/creator commission.</li>
<li>A cancellation, return, refund or partial refund changed the sale value or quantity.</li>
<li>The final settlement does not show the expected commission reduction, or shows an excessive commission reversal.</li>
</ul>

<div class="guide-answer"><strong>Safe framing:</strong> this article identifies reconciliation exceptions. It does not claim every refund should claw back creator commission or that every commission is recoverable after creator payment.</div>

<h2 id="lifecycle">Commission lifecycle and the 15-day timing issue</h2>
<p>Official affiliate guidance says estimated standard commission is not final. It can change if returns or refunds occur. TikTok describes standard affiliate commission as:</p>

<div class="guide-formula">Commission = (Revenue &#8211; Refunds) x commission rate<small>For full refund examples, actual commission can become $0. Partial refunds require order-line and quantity matching.</small></div>

<p>The commonly cited 15-day timing rule needs careful wording. Creators typically receive commission 15 days after delivery, but only after the seller order is settled. Unresolved aftersales, returns or refunds can delay creator payment and keep the commission estimate adjustable.</p>

<figure class="svg-fig">
<img decoding="async" src="/wp-content/themes/fbtops-child/assets/img/commission-lifecycle.svg?v=1" alt="TikTok Shop creator commission lifecycle from attributed order to estimated commission, settlement, refund adjustment and creator payment" loading="lazy" width="440" height="286">
<figcaption>Estimated commission should not be treated as final until aftersales and settlement status are resolved.</figcaption>
</figure>

<div class="guide-warning"><strong>Do not publish the old shortcut &#8220;non-recoverable after exactly 15 days.&#8221;</strong> The safer statement is: creators typically receive commission 15 days after delivery, but payment depends on seller settlement and unresolved aftersales. Final treatment must be checked in the settled statement records.</div>

<h2 id="fields">Settlement fields to reconcile</h2>
<p>TikTok&#8217;s settlement report guide groups several commission-like costs inside fees. A creator-commission review should not look only for one field called &#8220;creator commission.&#8221; Preserve the original report labels.</p>

<div class="guide-table">
<table>
<thead><tr><th>Settlement field</th><th>Why it matters</th><th>Review control</th></tr></thead>
<tbody>
<tr><td>Affiliate commission</td><td>Standard creator commission for attributed sales</td><td>Match to order/SKU, revenue/refund outcome and rate</td></tr>
<tr><td>Affiliate partner commission</td><td>Additional partner-related commission field in settlement reporting</td><td>Do not merge with standard affiliate commission without label mapping</td></tr>
<tr><td>Affiliate shop ads commission</td><td>Commission associated with shop ads</td><td>Separate from organic/open/target collaboration assumptions</td></tr>
<tr><td>Refund administration fee</td><td>Referral-fee-related refund cost, not creator commission</td><td>Current public referral-fee article supports 20% of refunded referral fee, capped at $5 per SKU from May 15, 2025</td></tr>
<tr><td>Referral fee and transaction fee</td><td>Fee lines can move near refund lines</td><td>Rule out false positives before calling a commission error</td></tr>
<tr><td>Adjustments</td><td>Later corrections or settlement changes</td><td>Review adjacent statements and adjustment reason</td></tr>
<tr><td>Reserve and payment status</td><td>Explains payout timing</td><td>Do not confuse unpaid reserve movement with a missing commission reversal</td></tr>
</tbody>
</table>
</div>

<h3>Commission rates are not universal</h3>
<p>Do not write that TikTok Shop creator commissions are normally 10%, 20% or 30% as a platform rule. Current official collaboration documentation says sellers can set affiliate commission rates from 1% to 80%. Target collaboration commission overrides Open collaboration commission, and edits become effective on different timelines depending on the collaboration type.</p>

<div class="guide-answer"><strong>Safe wording:</strong> Sellers may set affiliate commission rates within TikTok&#8217;s documented 1%-80% range, but the rate to reconcile is the rate stored with the specific order or collaboration, not a generic benchmark.</div>

<h2 id="refunds">Refund and return scenarios that change commission</h2>
<p>Refunds can affect sales value, seller discounts, shipping, referral fees, refund administration fees and affiliate commissions. The final commission result depends on the order&#8217;s settlement status, refund completion, quantity retained and collaboration rules.</p>

<div class="guide-table">
<table>
<thead><tr><th>Scenario</th><th>Likely review question</th><th>Evidence needed</th></tr></thead>
<tbody>
<tr><td>Full refund before creator payment</td><td>Did actual affiliate commission recalculate to $0?</td><td>Order/SKU, refund completion, statement transaction, commission field</td></tr>
<tr><td>Partial return</td><td>Did commission remain only on retained eligible value or quantity?</td><td>Refund quantity, retained quantity, SKU-level transaction detail</td></tr>
<tr><td>Refund after estimated commission appears</td><td>Was the estimate later canceled or adjusted?</td><td>On-hold record, final statement, adjacent statement periods</td></tr>
<tr><td>Commission appears after refund</td><td>Is it a late settlement, separate line, or unsupported cost?</td><td>Statement ID, transaction type, adjustment reason and Payment ID</td></tr>
<tr><td>Excess negative commission</td><td>Did a reversal exceed the original commission basis?</td><td>Original rate/basis, refund amount, signed commission lines</td></tr>
<tr><td>Refund administration fee confusion</td><td>Is the row a referral-fee refund admin cost rather than creator commission?</td><td>Report label, refunded referral fee basis and SKU cap context</td></tr>
</tbody>
</table>
</div>

<p>Customer refund responsibility is separate from commission reconciliation. The return/refund policy states customer refunds are at seller cost unless specified otherwise, but the commission and fee fields still need to be read from settlement transactions. For refund row analysis, see <a href="/identify-duplicate-tiktok-shop-refunds-settlement-reports/">the duplicate refund review workflow</a>.</p>

<h2 id="workflow">Step-by-step creator commission reconciliation</h2>

<h3>1. Preserve raw exports</h3>
<p>Save order, affiliate/collaboration, refund, statement, payout and bank records with export timestamps. Do not overwrite prior versions; estimated and final values can differ.</p>

<h3>2. Build an order-line key</h3>
<p>Match by Order ID, SKU ID, quantity, creator/collaboration reference when available, statement ID and transaction type. For partial returns, reconcile at SKU and quantity level, not only at order total.</p>

<h3>3. Establish the original commission basis</h3>
<p>Use the rate and basis recorded for that transaction. Target rates can override Open rates, and collaboration edits have effective dates. Do not use a generic category benchmark.</p>

<h3>4. Map the final refund outcome</h3>
<p>Separate requested, approved, completed, rejected and canceled refunds. Estimated commission can remain pending while aftersales are unresolved.</p>

<h3>5. Compare expected and posted commission</h3>
<p>Use the official commission logic and the settled statement lines. For a full refund before creator payment, actual standard commission may be $0. For partial refunds, calculate the retained eligible amount or quantity and compare to signed statement transactions.</p>

<h3>6. Bridge to payout and bank only after statement matching</h3>
<p>A payout difference can result from reserves, multiple statements, negative balances, failed/reversed payments or unrelated fees. Use <a href="/how-to-reconcile-tiktok-shop-payments/">the full payment reconciliation workflow</a> before escalating a payout-level complaint.</p>

<h2 id="api">Finance API checks for commission exceptions</h2>
<p>Finance API records can support repeatable reconciliation when accessed through authorized seller tokens and documented scopes. They should not replace final statement review.</p>

<div class="guide-table">
<table>
<thead><tr><th>Record</th><th>Use</th><th>Limit</th></tr></thead>
<tbody>
<tr><td><code>GET /finance/202309/statements</code></td><td>Find Statement IDs, payment status and settlement amounts</td><td>Not SKU-level detail</td></tr>
<tr><td><code>GET /finance/202501/statements/{statement_id}/statement_transactions</code></td><td>Review fee, commission, refund, shipping, tax, adjustment and reserve fields inside a statement</td><td>Use order endpoint for SKU-level analysis</td></tr>
<tr><td><code>GET /finance/202501/orders/{order_id}/statement_transactions</code></td><td>Trace SKU-level sales, fees, commissions, shipping, taxes and refunds</td><td>Historic availability limitations can apply</td></tr>
<tr><td><code>GET /finance/202507/orders/unsettled</code></td><td>Monitor estimated pre-settlement commission and refund changes</td><td>Estimated and subject to change; not final proof</td></tr>
<tr><td>Payments / withdrawals endpoints</td><td>Bridge statement totals to payout and bank records</td><td>Not proof of underlying commission cause</td></tr>
</tbody>
</table>
</div>

<h2 id="exceptions">Exception register and support packet</h2>
<p>Do not open a ticket that says only &#8220;commission not clawed back.&#8221; Give support a transaction-level question.</p>

<div class="guide-template">
<div class="guide-template-head"><strong>Commission exception columns</strong><button type="button" class="guide-copy-btn js-copy-template" data-copy-target="#commission-exception-columns">Copy columns</button></div>
<pre id="commission-exception-columns">case_id,status,order_id,sku_id,creator_or_collaboration,statement_id,payment_id,original_commission_rate,original_commission_amount,refund_amount,refund_quantity,expected_commission_after_refund,posted_commission,variance,transaction_type,evidence_status,next_action</pre>
<p class="guide-template-note">Use actual statement labels and signed amounts. Keep raw exports unchanged.</p>
</div>

<h3>Support request wording</h3>
<div class="guide-template">
<div class="guide-template-head"><strong>Copy-ready support question</strong><button type="button" class="guide-copy-btn js-copy-template" data-copy-target="#commission-support-template">Copy template</button></div>
<pre id="commission-support-template">Subject: Request for transaction-level explanation - affiliate commission after refund

Hello TikTok Shop Support,

We are reviewing order [Order ID] / SKU [SKU ID] in statement [Statement ID]. The order had a refund or return event on [date]. Based on the settled statement lines, the posted affiliate commission appears to differ from the expected commission after refund.

Attached records:
1. Order and SKU detail
2. Refund/return status and quantity
3. Original commission rate or collaboration record
4. Statement transaction rows for affiliate commission / affiliate partner commission / affiliate shop ads commission
5. Payout or payment record if relevant

Question:
Please confirm whether the commission lines represent the final settled commission, a pending timing difference, a separate affiliate/partner/shop ads component, or an adjustment that should appear in a later statement.

Thank you.</pre>
<p class="guide-template-note">Redact buyer personal data. Do not include API tokens, unmasked bank information or unrelated seller records.</p>
</div>

<h2 id="faq">FAQ</h2>
<details><summary>Do TikTok Shop creator commissions always claw back after refunds?</summary><p>No. Official sources support commission recalculation before final payment and show that full refunds can make actual standard commission $0, but final treatment depends on settlement status, aftersales, refund timing and the specific commission field.</p></details>
<details><summary>Is creator commission always 10%, 20% or 30%?</summary><p>No. Current official seller collaboration documentation says sellers can set affiliate commission rates from 1% to 80%. The rate to reconcile is the rate stored with the specific order or collaboration.</p></details>
<details><summary>What does the 15-day creator payment rule mean?</summary><p>Creators typically receive commission 15 days after delivery, but only after the seller&#8217;s order is settled. Unresolved aftersales, returns or refunds can delay payment, so estimated commission is not final until settlement.</p></details>
<details><summary>Is the refund administration fee a creator commission clawback?</summary><p>No. It is a referral-fee-related refund administration cost. Current public referral-fee guidance supports 20% of the refunded referral fee, capped at $5 per SKU from May 15, 2025.</p></details>
<details><summary>Which report should I use as final proof?</summary><p>Use settled statement transactions and payout/payment records. On-hold and unsettled API values are useful for monitoring but are estimated and can change.</p></details>

<section class="guide-sources" id="sources">
<h2>Official sources</h2>
<ol>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=2336057241700098&amp;default_language=en" target="_blank" rel="noopener">How to Access Your Settlement Report</a>, September 11, 2025. Affiliate commission, affiliate partner commission, affiliate shop ads commission, refund administration fee and settlement fields.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=5982454398175018" target="_blank" rel="noopener">TikTok Shop Referral Fee Updates &#8211; 2024</a>, May 8, 2025. Refund administration fee wording and $5 per SKU cap from May 15, 2025.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=6837873164896001" target="_blank" rel="noopener">Setting Up Affiliate Collaborations</a>, May 13, 2026. Open/Target collaboration setup, 1%-80% commission range and edit effective dates.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=6077860360177451" target="_blank" rel="noopener">How Standard Affiliate Commission Works</a>, June 3, 2026. Commission formula, estimated versus actual commission, full refund example and creator payment timing.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=2470273945257771&amp;lang=en" target="_blank" rel="noopener">Finances Page FAQ</a>, August 11, 2025. Estimated standard commission, On hold values, statement/payout statuses and bank-posting caveat.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=3253210454181634" target="_blank" rel="noopener">Customer Order Cancellation, Return, and Refund Policy</a>, July 8, 2026. Refund responsibility and FBT logistics-related return/refund context.</li>
<li><a href="https://partner.tiktokshop.com/docv2/page/get-statements-202309" target="_blank" rel="noopener">Get Statements</a>; <a href="https://partner.tiktokshop.com/docv2/page/get-transactions-by-statement-202501" target="_blank" rel="noopener">Get Transactions by Statement</a>; <a href="https://partner.tiktokshop.com/docv2/page/get-transactions-by-order-202501" target="_blank" rel="noopener">Get Transactions by Order</a>; <a href="https://partner.tiktokshop.com/docv2/page/get-unsettled-transactions-202507" target="_blank" rel="noopener">Get Unsettled Transactions</a>; <a href="https://partner.tiktokshop.com/docv2/page/get-payments-202605" target="_blank" rel="noopener">Get Payments</a>; <a href="https://partner.tiktokshop.com/docv2/page/get-withdrawals-202309" target="_blank" rel="noopener">Get Withdrawals</a>.</li>
</ol>
</section>

<div class="guide-change-log"><strong>Change log.</strong> July 13, 2026: rebuilt from a short checklist into a sourced commission reconciliation guide; added official settlement fields, safe 15-day wording, 1%-80% commission-rate context, refund administration fee cap, Finance API checks, false-positive controls, copy-ready exception register and FAQ. Removed unsupported universal 10%-30% commission and exact 15-day non-recoverability claims.</div>

<div class="guide-cta">
<p class="guide-cta-title">Need commission exceptions matched to refunds and statements?</p>
<p>FBTops traces creator commission, refund, fee and payout entries at order-line level, then separates timing differences from possible missing or excessive adjustments.</p>
<a class="guide-cta-btn" href="/free-audit/">Request a free 14-day audit</a>
<small>Independent service. Not affiliated with TikTok. TikTok determines seller account records and settlement outcomes.</small>
</div>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>How to Reconcile TikTok Shop Payments: Statements, Payouts, and Bank Deposits</title>
		<link>https://fbtops.com/how-to-reconcile-tiktok-shop-payments/</link>
		
		<dc:creator><![CDATA[Oleksandr Bondar]]></dc:creator>
		<pubDate>Sun, 12 Jul 2026 17:29:02 +0000</pubDate>
				<category><![CDATA[Reconciliation]]></category>
		<guid isPermaLink="false">https://fbtops.com/how-to-reconcile-tiktok-shop-payments/</guid>

					<description><![CDATA[A sourced, order-to-bank TikTok Shop payment reconciliation workflow covering statements, reserves, payouts, refunds, FBT charges, exceptions, and Finance API records.]]></description>
										<content:encoded><![CDATA[
<p><strong>Direct answer:</strong> reconcile TikTok Shop payments by connecting four records with stable identifiers: the order and SKU, the settlement statement and line-item transactions, the payout plus reserve activity, and the deposit posted by the bank. Do not compare dashboard GMV directly to the bank. A settlement report is statement-based, not order-creation-based, and one payout can include later adjustments, reserves, refunds, fees, commissions and FBT charges from different orders.</p>

<div class="guide-verified"><strong>Last verified: July 13, 2026.</strong> This US guide uses current public TikTok Shop Academy and Partner API documentation. Settlement tier, reserve level, fee schedule, report labels and payout controls can vary by seller and can change. Confirm account-specific values in Seller Center before closing the books.</div>

<nav class="guide-toc" aria-label="TikTok Shop payment reconciliation table of contents">
<p>In this guide</p>
<ul>
<li><a href="#chain">The order-to-bank chain</a></li>
<li><a href="#records">Records to collect</a></li>
<li><a href="#statement">Read the settlement statement</a></li>
<li><a href="#workflow">Step-by-step reconciliation</a></li>
<li><a href="#holds">Reserves, holds and negative balances</a></li>
<li><a href="#exceptions">Build an exception queue</a></li>
<li><a href="#api">Manual exports vs Finance API</a></li>
<li><a href="#example">Worked example</a></li>
<li><a href="#faq">FAQ</a></li>
<li><a href="#sources">Official sources and change log</a></li>
</ul>
</nav>

<h2 id="chain">The order-to-bank reconciliation chain</h2>
<p>A useful reconciliation does not ask only whether the payout total looks reasonable. It proves how each statement amount became a payout and how that payout reached the bank. Every unresolved difference receives an owner, evidence status and next action.</p>

<figure class="svg-fig">
<img decoding="async" src="/wp-content/themes/fbtops-child/assets/img/reconciliation-chain.svg?v=1" alt="TikTok Shop order-to-bank reconciliation chain linking orders, statements, payouts, reserves, bank deposits and an exception queue" loading="lazy" width="440" height="270">
<figcaption>Match Order ID and SKU to Statement ID, then Payment ID and reserve activity to the bank deposit.</figcaption>
</figure>

<div class="guide-answer"><strong>The control objective:</strong> every order, refund, adjustment and FBT event should end in one of three states: correctly settled, legitimately pending, or documented as an exception requiring investigation or a claim.</div>

<h2 id="records">Collect the source records before calculating</h2>
<p>Seller Center reports answer different questions. Combining them into one undifferentiated spreadsheet removes the status and timing information needed to explain a difference.</p>

<div class="guide-table">
<table>
<thead><tr><th>Record</th><th>What it proves</th><th>Primary identifiers</th><th>Where to obtain it</th></tr></thead>
<tbody>
<tr><td>Order and SKU export</td><td>What was sold, quantity, discounts, fulfillment route and order event dates</td><td>Order ID, SKU, Goods ID</td><td>Seller Center order exports or authorized Order API</td></tr>
<tr><td>Settlement report</td><td>Final statement line items for sales, refunds, shipping, fees, commissions, adjustments, taxes and FBT charges</td><td>Statement ID, Order ID, SKU</td><td>Finances &gt; Statements or Payouts &gt; Export</td></tr>
<tr><td>On-hold/unsettled record</td><td>Orders and estimated entries not yet in a final statement</td><td>Order ID, transaction type, estimated amount</td><td>Finance &gt; On hold or authorized Finance API</td></tr>
<tr><td>Payout and reserve record</td><td>How statement amount, reserve collection/release and other activity became a payout</td><td>Payment ID, Statement ID, expected release date</td><td>Finance/Payouts and reserve exports</td></tr>
<tr><td>Bank statement</td><td>Amount and date actually posted by the bank</td><td>Deposit amount, ACH descriptor, posting date</td><td>Seller-controlled bank record</td></tr>
<tr><td>Return/refund and tracking events</td><td>Why a sale changed and which party funded the refund or shipping event</td><td>Order ID, return ID, tracking number</td><td>Orders, Returns/Refunds and logistics records</td></tr>
<tr><td>FBT operational records</td><td>Inbound, inventory and removal events behind FBT charges or claims</td><td>IBR, WOP/WOT, OBC, Goods ID</td><td>FBT Merchant Portal and claim records</td></tr>
</tbody>
</table>
</div>

<p>TikTok&#8217;s official settlement guide says reports are generated daily and provide a <em>settlement-based perspective</em>, not an order-creation-based view. An order can therefore appear later than its creation date, and unsettled orders should remain in a pending population rather than being forced into the current payout.</p>

<h2 id="statement">Read the settlement statement as a ledger</h2>
<p>The statement is not one fee calculation. It is a line-item ledger whose labels can change with report versions and seller programs. Preserve TikTok&#8217;s original transaction type, then map it to your accounting category.</p>

<div class="guide-formula">Total settlement = Net sales + Shipping + Fees + Adjustment amount<small>Official high-level formula from TikTok&#8217;s settlement report guide. The signed values inside each category determine whether the line adds or subtracts.</small></div>

<div class="guide-formula">Payout amount = Statement amount + Reserve amount<small>Reserve amount can represent collection or release activity. Use the signed amount and the seller&#8217;s reserve export.</small></div>

<figure class="svg-fig">
<img decoding="async" src="/wp-content/themes/fbtops-child/assets/img/statement-stack.svg?v=2" alt="TikTok Shop settlement line-item stack showing sales, refunds, shipping, fees, commissions, FBT charges, adjustments, reserves and payout" loading="lazy" width="440" height="282">
<figcaption>Use the current report labels and signed values. There is no universal fee percentage for every seller, category or date.</figcaption>
</figure>

<h3>Fields worth preserving at import</h3>
<div class="guide-table">
<table>
<thead><tr><th>Field group</th><th>Keep at minimum</th><th>Why it matters</th></tr></thead>
<tbody>
<tr><td>Statement identity</td><td>Statement ID, statement date, statement/payment status</td><td>Defines the accounting batch and whether payment processing is complete</td></tr>
<tr><td>Order identity</td><td>Order ID, SKU, Goods ID, quantity</td><td>Prevents totals from hiding duplicate or missing line items</td></tr>
<tr><td>Sales and discount</td><td>Gross/net sales, seller discount, platform discount</td><td>Separates seller-funded economics from platform-funded incentives</td></tr>
<tr><td>Refund</td><td>Refund amount, shipping refund, commission refund, adjustment reason</td><td>Shows which components reversed and which remained</td></tr>
<tr><td>Fees and commissions</td><td>Original transaction label and signed amount</td><td>Avoids applying a guessed universal percentage</td></tr>
<tr><td>FBT</td><td>Fulfillment fee, warehouse service fee, shipping offset and related adjustment</td><td>Connects financial entries to fulfillment operations</td></tr>
<tr><td>Payout bridge</td><td>Payment ID, reserve collection/release, withdrawal or payment status</td><td>Explains why statement amount and bank deposit differ</td></tr>
</tbody>
</table>
</div>

<div class="guide-warning"><strong>Do not hard-code old fee examples as policy.</strong> Referral fees, transaction fees, creator commissions, FBT charges, refund effects and settlement tiers can vary by category, campaign, seller status and effective date. Reconcile the actual signed statement lines to the fee schedule applicable to that transaction.</div>

<h2 id="workflow">Step-by-step TikTok Shop payment reconciliation</h2>

<h3>1. Freeze the reporting period and timezone</h3>
<p>Record the Seller Center market, export timestamp, timezone, currency and period. A bank posting date can trail the platform&#8217;s paid date, so keep transaction date, statement date, payout date and bank date as separate fields.</p>

<h3>2. Import without changing source labels</h3>
<p>Keep a raw tab or immutable table for each export. Normalize IDs and dates in a separate working model. This makes it possible to reproduce every transformation after TikTok changes a report column.</p>

<h3>3. Build the order-to-statement bridge</h3>
<p>Match each settled transaction to Order ID and SKU. Group statement lines only after the detailed match. Orders missing from statements should be checked against On hold or unsettled records before they are treated as missing payments.</p>

<h3>4. Recalculate the statement from signed line items</h3>
<p>Sum each statement&#8217;s sales, shipping, fees and adjustments using the signs in the export. Compare your calculated statement total to TikTok&#8217;s statement amount. Keep taxes and informational fields separate when they are not part of the payable formula for that report version.</p>

<h3>5. Bridge statement to payout</h3>
<p>Join Statement ID to the payout or payment record. Add reserve collection/release and any documented payout-level movement. A payout can contain more than one statement or later activity, so Payment ID is the stronger bridge than a date-only match.</p>

<h3>6. Match payout to the bank</h3>
<p>Match amount, currency, ACH descriptor and posting date. TikTok&#8217;s Finance FAQ says a Paid status means TikTok sent the payout; bank posting typically takes 1-3 business days. Treat that as an operating expectation, not a guaranteed bank deadline.</p>

<h3>7. Reconcile refunds and FBT operations</h3>
<p>For every refund, compare the order event to the gross-sales reversal, discount reversal, shipping, commission and adjustment lines. For FBT, connect charges and credits to the Goods ID and relevant IBR, WOP/WOT or OBC record. Operational inventory records prove what happened; the settlement proves what was financially recognized.</p>

<h3>8. Move unresolved differences to a case queue</h3>
<p>Do not overwrite a variance with a note such as &#8220;timing.&#8221; Give it a category, amount, owner, next check date, evidence status and applicable claim deadline. This is where reconciliation becomes reimbursement recovery.</p>

<h2 id="holds">Reserves, holds, payout statuses and negative balances</h2>

<h3>On hold is not the same as missing</h3>
<p>Orders can remain unsettled while return, delivery, risk or other conditions are unresolved. Keep an aging report for On hold transactions, but do not add estimated unsettled API amounts to a final statement. TikTok states that unsettled amounts may change and final values come from statement APIs.</p>

<h3>Paid is not the same as bank-posted</h3>
<p>Finance statuses include On hold, Processing, Paid and Failed, while a statement can be Pending. A Paid payout still needs a bank match. A Failed payout needs its failure reason, corrected bank/control action and subsequent payment record.</p>

<h3>Reserve activity changes payout timing</h3>
<p>TikTok&#8217;s June 30, 2026 Dynamic Settlement and Reserve Policy describes introductory, standard, accelerated, express and deferred settlement tiers plus three reserve levels. It does not publish one universal period or reserve percentage for every seller. The policy states that a portion of earnings for each delivered order can be retained in reserve for 30 days from delivery, with assignment subject to evaluation and account conditions.</p>

<h3>Payout scheduling is not universal</h3>
<p>Daily, business-day, weekly and monthly payout scheduling is documented as a feature in testing for selected sellers. Changing a payout schedule does not change whether an order has settled.</p>

<h3>Negative balances can absorb future sales</h3>
<p>Refunds or platform expenses can exceed revenue and produce a negative balance. TikTok documents that it can be offset by future sales or paid separately; a balance-offset transaction does not necessarily create a bank payout. Reconcile the negative-balance payment or carryforward as its own ledger event.</p>

<h2 id="exceptions">Build an exception queue that can become a claim</h2>
<div class="guide-table">
<table>
<thead><tr><th>Exception</th><th>First checks</th><th>Evidence to preserve</th><th>Disposition</th></tr></thead>
<tbody>
<tr><td>Order absent from final statements</td><td>On hold/unsettled status, cancellation, delivery and return events</td><td>Order export, status history, unsettled record</td><td>Pending, corrected, or investigate missing settlement</td></tr>
<tr><td>Statement does not recalculate</td><td>Signs, duplicated rows, report version and adjustment lines</td><td>Original export and calculation log</td><td>Data issue, mapping correction, or support ticket</td></tr>
<tr><td>Payout differs from statements</td><td>Reserve collection/release, multiple statements, failed/reversed payment</td><td>Payment ID, reserve export, payout status</td><td>Explained bridge or payout investigation</td></tr>
<tr><td>Bank deposit missing</td><td>Paid timestamp, bank posting lag, beneficiary/account status</td><td>Payout record and bank statement</td><td>Wait within normal posting range or escalate failed/missing ACH</td></tr>
<tr><td>Refund economics look wrong</td><td>Who funded refund, discount and shipping; commission/refund lines</td><td>Return/refund timeline and statement detail</td><td>Correct, explain, or claim a discrepancy</td></tr>
<tr><td>FBT fee or credit mismatch</td><td>Goods ID, fulfillment route, IBR/WOP/WOT/OBC and applicable fee schedule</td><td>FBT operation, invoice, statement and claim record</td><td>Accept, dispute, or prepare reimbursement claim</td></tr>
<tr><td>Creator commission remains after refund</td><td>Commission and refund transaction lines, campaign terms, dates</td><td>Order, creator attribution and statement entries</td><td>Explain timing/terms or investigate a missing reversal</td></tr>
</tbody>
</table>
</div>

<div class="guide-template">
<div class="guide-template-head"><strong>Case queue header</strong><button type="button" class="guide-copy-btn js-copy-template" data-copy-target="#reconciliation-case-header">Copy columns</button></div>
<pre id="reconciliation-case-header">case_id,status,market,order_id,sku,goods_id,event_type,statement_id,payment_id,expected_amount,actual_amount,variance,trigger_date,claim_deadline,evidence_status,owner,next_action,next_check_date,outcome</pre>
<p class="guide-template-note">Keep source files immutable. The case queue records conclusions and actions, not replacements for the original exports.</p>
</div>

<p>Potential refund duplication deserves its own test. See <a href="/identify-duplicate-tiktok-shop-refunds-settlement-reports/">how to identify duplicate TikTok Shop refunds in settlement reports</a>. For evidence requirements, use the <a href="/tiktok-shop-reimbursement-policy/">reimbursement policy guide</a> and <a href="/what-evidence-supports-fbt-reimbursement-claim/">FBT evidence checklist</a>.</p>

<h2 id="api">Manual exports vs TikTok Shop Finance API</h2>
<p>A spreadsheet is sufficient for a controlled first reconciliation. The Finance API helps when volume, repeatability or aging analysis makes manual downloads unreliable. API access must use TikTok&#8217;s OAuth-based authorization and the documented `seller.finance.info` scope where required.</p>

<div class="guide-table">
<table>
<thead><tr><th>Method</th><th>Best for</th><th>Main control</th><th>Limitation</th></tr></thead>
<tbody>
<tr><td>Seller Center exports</td><td>First audit, monthly close, human review</td><td>Save original file and export timestamp</td><td>Manual repetition, changing report columns, limited automation</td></tr>
<tr><td>Finance API</td><td>Daily ingestion, transaction-level joins, aging and monitoring</td><td>OAuth authorization, versioned endpoint, pagination and raw response archive</td><td>API data windows and fields do not necessarily match Excel exports</td></tr>
</tbody>
</table>
</div>

<h3>Verified Finance API endpoints</h3>
<div class="guide-table">
<table>
<thead><tr><th>Purpose</th><th>Official endpoint</th><th>Important limitation</th></tr></thead>
<tbody>
<tr><td>List statements</td><td><code>GET /finance/202309/statements</code></td><td>Filter by statement time and payment status; preserve pagination.</td></tr>
<tr><td>Transactions by statement</td><td><code>GET /finance/202501/statements/{statement_id}/statement_transactions</code></td><td>Order, adjustment and reserve-related transactions; `seller.finance.info`.</td></tr>
<tr><td>Transactions by order</td><td><code>GET /finance/202501/orders/{order_id}/statement_transactions</code></td><td>Covers sales, fees, commissions, shipping, taxes and refunds.</td></tr>
<tr><td>Unsettled transactions</td><td><code>GET /finance/202507/orders/unsettled</code></td><td>Estimated, changeable amounts; final values come from statement APIs.</td></tr>
<tr><td>Withdrawals</td><td><code>GET /finance/202309/withdrawals</code></td><td>Types include withdrawal, settlement, transfer and reverse.</td></tr>
</tbody>
</table>
</div>

<p>The transaction endpoints document data from July 1, 2023, with a separate limitation for some US cross-border data before April 30, 2025. Check the current endpoint page before implementation; version dates in the path are part of the contract.</p>

<div class="guide-warning"><strong>Unverified endpoint warning:</strong> Partner Center currently lists a Get Payments entry, but the public extraction reviewed for this guide did not expose a reliable method, path and response schema. Do not infer an endpoint from a page slug; navigate the official documentation and capture the actual API contract.</div>

<h2 id="example">Worked reconciliation example</h2>
<p>The following numbers are illustrative and are not a TikTok fee schedule.</p>

<div class="guide-table">
<table>
<thead><tr><th>Bridge line</th><th>Illustrative amount</th><th>Control</th></tr></thead>
<tbody>
<tr><td>Net sales</td><td>$95.00</td><td>Matched to detailed order/SKU lines</td></tr>
<tr><td>Shipping</td><td>+$4.00</td><td>Matched to statement shipping entries</td></tr>
<tr><td>Fees</td><td>-$8.00</td><td>Actual signed statement lines, not a guessed percentage</td></tr>
<tr><td>Adjustments</td><td>+$2.00</td><td>Reason and source transaction preserved</td></tr>
<tr><td><strong>Statement amount</strong></td><td><strong>$93.00</strong></td><td>$95 + $4 &#8211; $8 + $2</td></tr>
<tr><td>Reserve activity</td><td>-$10.00</td><td>Matched to reserve collection and expected release</td></tr>
<tr><td><strong>Expected payout</strong></td><td><strong>$83.00</strong></td><td>Statement amount plus signed reserve amount</td></tr>
<tr><td>Bank deposit</td><td>$83.00</td><td>Matched by Payment ID context, amount and posting date</td></tr>
</tbody>
</table>
</div>

<p>If the bank posted $75 instead, the $8 variance would remain open. The next checks would be another reserve movement, a failed/reversed payment, multiple statements in one payout, a negative-balance offset or a bank posting split. It should not be assigned to &#8220;fees&#8221; without a line-level record.</p>

<h3>Month-end close checklist</h3>
<ul>
<li>Every final statement recalculates from signed line items.</li>
<li>Every statement is assigned to a payout/payment or a documented pending status.</li>
<li>Every paid payout is matched to a bank deposit or failed/reversed event.</li>
<li>Reserve collections and releases are aged to their expected dates.</li>
<li>Negative balances and manual balance payments are separately identified.</li>
<li>Refund, commission and FBT exceptions are connected to the original order and event.</li>
<li>Open cases include evidence, owner, next action and claim deadline.</li>
</ul>

<h2 id="faq">TikTok Shop payment reconciliation FAQ</h2>

<details><summary>Why does my TikTok Shop payout not match GMV?</summary><p>GMV is not a bank-reconciliation figure. Settlement statements can include sales, discounts, refunds, shipping, fees, commissions, FBT charges, taxes and adjustments, while payout amount also reflects reserve activity and timing.</p></details>

<details><summary>What is the most important reconciliation key?</summary><p>No single ID connects every layer. Use Order ID and SKU for order-to-transaction matching, Statement ID for settlement batching, and Payment ID plus amount/date for the payout-to-bank bridge.</p></details>

<details><summary>Does Paid mean the money is in my bank?</summary><p>No. Paid means TikTok sent the payout. The official Finance FAQ says bank posting typically takes 1-3 business days, so the payout still needs a bank match.</p></details>

<details><summary>Should unsettled API amounts be treated as final revenue?</summary><p>No. TikTok says unsettled transactions are estimates that may change. Use final statement APIs or statement exports for settled values.</p></details>

<details><summary>Is there one standard TikTok Shop fee percentage?</summary><p>No. Fees and commissions can vary by category, campaign, seller status, fulfillment program and effective date. Reconcile the actual statement line and verify it against the schedule applicable to that transaction.</p></details>

<details><summary>How often should TikTok Shop payments be reconciled?</summary><p>Import statements and payout changes daily for active monitoring, then complete a controlled monthly close. Time-sensitive reimbursement cases should enter the claim queue as soon as the variance is verified.</p></details>

<section class="guide-sources" id="sources">
<h2>Official sources</h2>
<ol>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=2336057241700098&amp;default_language=en" target="_blank" rel="noopener">How to Access Your Settlement Report</a>, September 11, 2025. Daily reports, settlement perspective, fields and formulas.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=2470273945257771&amp;lang=en" target="_blank" rel="noopener">Finances Page FAQ</a>, August 11, 2025. Finance statuses, bank reconciliation, minimum payout and negative carryforward.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=3995852763531009&amp;default_language=en" target="_blank" rel="noopener">Dynamic Settlement and Reserve Policy</a>, June 30, 2026. Current tier/reserve framework and account-specific evaluation.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=754576121693998" target="_blank" rel="noopener">How to View Your Reserve Record</a>, September 11, 2025. Reserve exports and payout bridge.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=8205104048391950" target="_blank" rel="noopener">Scheduling your payouts</a>, August 20, 2025. Selected-seller payout scheduling test.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=2380042835445547" target="_blank" rel="noopener">How to Pay Off Negative Balances</a>, September 12, 2025. Carryforward and separate balance payment.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=3253210454181634" target="_blank" rel="noopener">Customer Order Cancellation, Return, and Refund Policy</a>, July 8, 2026. Current refund and return context.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=8644984183162670" target="_blank" rel="noopener">Fulfilled by TikTok (FBT)</a>, July 9, 2026. Current FBT overview.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=6355939885090574" target="_blank" rel="noopener">FBT Inbound Request Creation and Management Process</a>, April 8, 2026. IBR operations and fees/events to reconcile.</li>
<li><a href="https://partner.tiktokshop.com/docv2/page/finance-api-overview" target="_blank" rel="noopener">Finance API overview</a> and linked official endpoint references.</li>
<li><a href="https://partner.tiktokshop.com/docv2/page/get-statements-202309" target="_blank" rel="noopener">Get Statements</a>; <a href="https://partner.tiktokshop.com/docv2/page/get-transactions-by-statement-202501" target="_blank" rel="noopener">Get Transactions by Statement</a>; <a href="https://partner.tiktokshop.com/docv2/page/get-transactions-by-order-202501" target="_blank" rel="noopener">Get Transactions by Order</a>; <a href="https://partner.tiktokshop.com/docv2/page/get-unsettled-transactions-202507" target="_blank" rel="noopener">Get Unsettled Transactions</a>; <a href="https://partner.tiktokshop.com/docv2/page/get-withdrawals-202309" target="_blank" rel="noopener">Get Withdrawals</a>.</li>
</ol>
</section>

<div class="guide-change-log"><strong>Change log.</strong> July 13, 2026: replaced the short checklist with a sourced order-to-bank workflow; added statement and reserve formulas, status logic, exception queue, illustrative example, verified Finance API endpoints, citations and FAQ. Removed unsupported universal settlement periods and fee percentages from the source draft.</div>

<div class="guide-cta">
<p class="guide-cta-title">Turn unexplained payout differences into a controlled case queue</p>
<p>FBTops traces orders through statements, reserves, payouts and FBT records, then separates correctly settled amounts from potential refund, fee, inventory and reimbursement exceptions.</p>
<a class="guide-cta-btn" href="/free-audit/">Request a free 14-day audit</a>
<small>Independent service. Not affiliated with TikTok. Results depend on available account records and applicable policy.</small>
</div>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>FBT Lost Package Claim: How to File, Evidence, and Deadlines</title>
		<link>https://fbtops.com/fbt-lost-package-claim/</link>
		
		<dc:creator><![CDATA[Oleksandr Bondar]]></dc:creator>
		<pubDate>Sun, 12 Jul 2026 17:29:02 +0000</pubDate>
				<category><![CDATA[FBT Claims]]></category>
		<guid isPermaLink="false">https://fbtops.com/fbt-lost-package-claim/</guid>

					<description><![CDATA[How to classify, document and file an FBT lost package claim, including current and future deadlines, eligibility, ticket paths, evidence, authorization and LPOA guidance.]]></description>
										<content:encoded><![CDATA[
<p><strong>Direct answer:</strong> an FBT lost package claim starts by identifying where the loss occurred and whether that scenario is eligible: consumer delivery, inbound receipt, in-warehouse adjustment, or product removal. Then match the case to the current Seller Center path and attach the reference ID, quantity, trigger date, value and scenario-specific evidence. A count difference or missing scan does not automatically create a payable reimbursement.</p>

<div class="guide-verified"><strong>Last verified: July 13, 2026.</strong> The 60-day consumer-order rule was active on the review date. The IBR day-14-to-180 window and WOP/WOT/OBC 60-day warehouse windows below are announced rules <strong>effective July 20, 2026</strong>. Before that date, follow the timeframe displayed in your Seller Center account.</div>

<nav class="guide-toc" aria-label="FBT lost package claim table of contents">
<p>In this guide</p>
<ul>
<li><a href="#what-counts">What counts as an FBT lost package claim</a></li>
<li><a href="#decision-tree">Which claim path to use</a></li>
<li><a href="#deadlines">Current and future deadlines</a></li>
<li><a href="#evidence">Evidence and eligibility</a></li>
<li><a href="#lpoa">Third-party authorization and LPOA</a></li>
<li><a href="#template">Copy-ready claim template</a></li>
<li><a href="#after-filing">After you file</a></li>
<li><a href="#faq">FAQ</a></li>
<li><a href="#sources">Official sources and change log</a></li>
</ul>
</nav>
<h2 id="what-counts">What counts as an FBT lost package claim?</h2>
<p>An FBT lost package claim is a practical label for a reimbursement request involving Fulfilled by TikTok inventory that cannot be reconciled to the expected consumer-order, inbound, warehouse, or removal record. Seller Center evaluates the exact scenario, transport responsibility and evidence rather than the generic label.</p>
<ul>
<li><strong>Consumer-order lost package:</strong> a buyer-facing FBT order enters a qualifying logistics-related refund or return scenario.</li>
<li><strong>Inbound discrepancy:</strong> planned quantity and warehouse receipt differ. This can be investigated, but the difference alone may be ineligible when it occurred before the units entered the FBT network.</li>
<li><strong>In-warehouse inventory lost or damaged:</strong> inventory was received, then a WOP/WOT adjustment records a covered warehouse event.</li>
<li><strong>Removal-order loss:</strong> an OBC exit shipment is lost or short after inventory leaves FBT. The announced compensation route applies only when TikTok arranged return transportation.</li>
</ul>
<div class="guide-warning"><strong>Timing does not prove eligibility.</strong> A request can be inside the filing window and still be denied because FBT did not receive the units, TikTok did not arrange the removal transport, the wrong category was used, or the reference and evidence do not match.</div>
<h2 id="decision-tree">Choose the correct claim path before filing</h2>
<p>Classify the loss by its operational source and use the corresponding reference. The labels below come from the official warehouse guide; verify the live dropdown because Seller Center wording can change.</p>
<figure class="svg-fig"><img decoding="async" src="/wp-content/themes/fbtops-child/assets/img/fbt-claim-decision.svg?v=1" alt="Decision tree showing inbound, in-warehouse, and removal paths for FBT lost package claims" loading="lazy" width="440" height="286"><figcaption>Use the event and reference ID to choose the path. A discrepancy is not automatically an eligible loss.</figcaption></figure>
<div class="guide-table">
<table>
<thead><tr><th>Scenario</th><th>Primary Seller Center path</th><th>Reference</th><th>Eligibility or routing control</th></tr></thead>
<tbody>
<tr><td>Inbound missing, extra or incorrect units</td><td>FBT Issues &gt; Inbound Order Issues &gt; Inbound Exception &#8211; Missing, Extra, Incorrect Units</td><td>IBR, Goods ID, discrepancy quantity</td><td>Planned-versus-received difference alone may be ineligible; establish a warehouse/network issue or eligible First Mile exception.</td></tr>
<tr><td>Inventory lost after warehouse receipt</td><td>FBT Warehouse Reimbursement Claim &gt; Product in Warehouse &gt; Inventory Lost</td><td>WOP, Goods ID, quantity</td><td>Use the lost-in-warehouse adjustment, not a buyer order date.</td></tr>
<tr><td>Inventory damaged after warehouse receipt</td><td>FBT Warehouse Reimbursement Claim &gt; Product in Warehouse &gt; Inventory Damaged</td><td>WOT, Goods ID, quantity</td><td>Tie damage evidence to the adjustment and exact units.</td></tr>
<tr><td>Full removal shipment lost</td><td>FBT Warehouse Reimbursement Claim &gt; Product Removal &gt; Package Lost</td><td>OBC, Goods ID, quantity</td><td>All goods lost; TikTok-arranged return transport required under the announced compensation route.</td></tr>
<tr><td>Removal shipment received short</td><td>FBT Warehouse Reimbursement Claim &gt; Product Removal &gt; Less Items Received</td><td>OBC, Goods ID, discrepancy quantity</td><td>Do not file a partial shortage as Package Lost.</td></tr>
<tr><td>Consumer-order FBT logistics loss</td><td>FBT Issue &gt; Logistics-Related Reimbursement Claims</td><td>Impacted order and tracking</td><td>Use the outbound-order workflow, not IBR/WOP/WOT/OBC warehouse categories.</td></tr>
</tbody>
</table>
</div>
<p>Fallback warehouse-stock or inventory-removal support categories are useful when the primary claim form fails or a posting problem needs troubleshooting. They should not be presented as interchangeable with the primary reimbursement paths.</p>
<h2 id="deadlines">Current and future deadline triggers</h2>
<p>The filing status matters as much as the number. The July 20 warehouse schedule was future-dated on this page&#8217;s July 13 review date.</p>
<div class="guide-table">
<table>
<thead><tr><th>Scenario</th><th>Policy status</th><th>Window and trigger</th><th>Eligibility check</th></tr></thead>
<tbody>
<tr><td>Consumer-order FBT logistics claim</td><td>Active on July 13 review date</td><td>Within 60 calendar days from order placed date</td><td>Confirm a qualifying buyer/refund logistics scenario and whether an expected automatic credit was missed.</td></tr>
<tr><td>Inbound IBR missing units</td><td><strong>Effective July 20, 2026</strong></td><td>Submit from day 14 through day 180 after first receipt at hub or direct fulfillment center</td><td>Count difference alone is not enough; confirm network responsibility or an eligible exception.</td></tr>
<tr><td>In-warehouse WOP/WOT loss or damage</td><td><strong>Effective July 20, 2026</strong></td><td>Within 60 days from the inventory-adjustment/order-create date</td><td>Match Goods ID, quantity and valuation to the warehouse event.</td></tr>
<tr><td>Removal OBC loss or damage</td><td><strong>Effective July 20, 2026</strong></td><td>Within 60 days from handover or actual outbound time</td><td>TikTok-arranged return transportation; use the exact full-loss, shortage, wrong-item or damage path.</td></tr>
<tr><td>Warehouse case filed before July 20</td><td>Transition period</td><td>Use the window shown in the seller&#8217;s account</td><td>Save a dated screenshot; the public future-rule announcement does not define every transition case.</td></tr>
</tbody>
</table>
</div>
<p>The 7-day, 10-day and 20-business-day thresholds found in other TikTok logistics documents are scenario-specific. The 20-business-day and recipient-affidavit route belongs to legacy TikTok Shipping/U-PIC cases, not the general IBR/WOP/WOT/OBC warehouse workflow.</p>
<figure class="svg-fig"><img decoding="async" src="/wp-content/themes/fbtops-child/assets/img/claim-flow.svg?v=1" alt="Four-step FBT reimbursement claim workflow from classification to filing" loading="lazy" width="440" height="250"><figcaption>Classify first, then confirm the rule version, eligibility, trigger date and evidence.</figcaption></figure>
<h2 id="evidence">Evidence and eligibility checklist</h2>
<p>Evidence should prove the item, quantity, trigger event, transport responsibility and value. It supports an eligible scenario; it does not convert an excluded discrepancy into a covered loss.</p>
<h3>Core records</h3>
<ul>
<li>Seller legal name, shop name and market.</li>
<li>Goods ID, SKU, product name and affected quantity.</li>
<li>Order ID, IBR, WOP, WOT, OBC, shipment ID or tracking number for the exact scenario.</li>
<li>Order placed, first receipt, inventory adjustment, handover or actual outbound timestamp.</li>
<li>Commercial invoice supporting ownership, item identity and unit cost.</li>
<li>Settlement/reimbursement record showing whether a credit already posted.</li>
</ul>
<h3>Inbound IBR cases</h3>
<p>A planned-versus-received gap is not automatically reimbursable. The official guide says units may be ineligible when the discrepancy occurred before receipt into the FBT network, although TikTok may investigate or locate units. Strong records help establish an eligible hub-to-warehouse or other covered network issue.</p>
<ul>
<li>IBR page with expected, received and discrepancy quantities.</li>
<li>Signed BOL for freight or carrier tracking/POD for small parcel.</li>
<li>Carton, pallet and packing records tied to the Goods ID.</li>
<li>Warehouse/hub scan history and any network exception message.</li>
</ul>
<h3>In-warehouse WOP/WOT cases</h3>
<ul>
<li>Inventory-adjustment screenshot and event date.</li>
<li>WOP for lost inventory or WOT for damaged inventory.</li>
<li>Before/after stock records, Goods ID and affected quantity.</li>
<li>Commercial invoice and damage records where applicable.</li>
</ul>
<h3>Removal OBC cases</h3>
<p>Under the announced warehouse guide, compensation applies only when TikTok arranged the return transportation. Seller-arranged freight pickup or a seller-provided small-parcel label is excluded from that route. A full shipment loss uses Package Lost; a partial shortage uses Less Items Received.</p>
<ul>
<li>OBC, Goods ID, requested and received quantity.</li>
<li>Handover/actual outbound timestamp and carrier tracking.</li>
<li>Signed BOL/POD where applicable.</li>
<li>Receiving photos for partial shortage, wrong item or damage.</li>
</ul>
<div class="guide-warning"><strong>Keep original evidence unchanged.</strong> Work from copies, but preserve timestamps, account names, IDs, URLs and the complete carrier or warehouse record.</div>
<h2 id="lpoa">Third-party authorization and LPOA requirements</h2>
<p><strong>&#8220;LPOA requirements&#8221; is common shorthand for a third-party authorization process, not a statement that TikTok requires an LPOA for every reimbursement claim.</strong> If a seller asks FBTops or another provider to prepare, submit or follow up on claims, use written authorization and platform-supported, least-privilege access. Depending on the seller&#8217;s counsel, contract and workflow, the document may be a limited authorization letter or a narrowly scoped Limited Power of Attorney (LPOA).</p>
<p>If a third party will <strong>process reimbursement claims</strong>, define &#8220;process&#8221; narrowly as administrative preparation, submission, evidence follow-up and reconciliation. TikTok determines claim eligibility and payment.</p>
<p>A seller authorization or optional LPOA should identify:</p>
<ul>
<li><strong>Seller and representative:</strong> legal entities, shop/market and authorized signers.</li>
<li><strong>Scope:</strong> records the representative may review and the claims/tickets they may prepare, submit or follow up.</li>
<li><strong>Access method:</strong> invited sub-account, Partner authorization or approved OAuth/API workflow where available.</li>
<li><strong>Limits:</strong> no shared owner credentials, ownership changes, payout destination changes or unrelated account administration.</li>
<li><strong>Term, revocation and confidentiality:</strong> dates, termination method and handling of account/order data.</li>
</ul>
<div class="guide-security"><strong>Official access distinction:</strong> TikTok&#8217;s Partner terms require lawful written seller approval for account access, while the US Seller Terms restrict sharing the seller&#8217;s username/password combination. Written authorization or an LPOA is a seller-provider control; it is not verified here as a TikTok-mandated claim document and does not override credential restrictions.</div>
<p>This is operational guidance, not legal advice. Have counsel approve legal language used with a seller.</p>
<h2 id="template">Template A: FBT lost package claim wording</h2>
<p>Use this as a claim-writing framework. Replace every bracketed value with case-specific data and attach the evidence packet before submitting.</p>

<div class="guide-template">
  <div class="guide-template-head">
    <strong>Copy-ready Seller Center ticket draft</strong>
    <button type="button" class="guide-copy-btn js-copy-template" data-copy-target="#fbt-claim-template">Copy template</button>
  </div>
  <pre id="fbt-claim-template">Subject: FBT lost package claim - [IBR / WOP-WOT / OBC / Order ID] - [Goods ID] - [Quantity]

Hello TikTok Shop Support,

We are submitting this FBT lost package claim for [seller legal name] / [shop name]. [Representative name or FBTops] is acting under the seller's written authorization or, if the seller elected to use one, a limited LPOA. For this ticket, process reimbursement claims means prepare, submit and follow up administratively; TikTok determines eligibility and payment. We are not requesting any change to account ownership, payout destination, or seller credentials.

Claim scenario:
- Scenario type: [Inbound missing units / Product in Warehouse Inventory Lost / Product Removal Package Lost / Consumer-order FBT package loss]
- Reference ID: [IBR, WOP/WOT, OBC, Order ID, shipment ID, tracking number]
- Goods ID / SKU: [Goods ID and SKU]
- Affected quantity: [quantity]
- Trigger date: [first receive date, adjustment date, handover date, actual outbound time, or order generated date]
- Claim window checked in Seller Center: [yes/no and date checked]

Evidence attached:
1. [Seller Center screenshot or export showing the reference ID and affected quantity]
2. [Invoice or purchase record supporting unit cost and ownership]
3. [Carrier, BOL, POD, tracking, inventory adjustment, or removal record]
4. [Settlement/reimbursement ledger screenshot showing no duplicate credit]
5. [Additional photos or receiving records if applicable]

Request:
Please review this case under the applicable FBT reimbursement policy and process the reimbursement claim if the loss is eligible. If any document or reference is missing, please advise exactly what is required so we can provide it in the same ticket thread.

Thank you.</pre>
  <p class="guide-template-note">Use factual language. Do not imply a guaranteed reimbursement, and do not attach seller passwords or unrelated personal data.</p>
</div>

<h2 id="after-filing">What to do after you file</h2>
<p>After submission, track the claim like a receivable. A support ticket is not recovered cash until the reimbursement appears in the settlement or transaction report.</p>

<ol>
  <li><strong>Save the ticket ID and timestamp.</strong> Add the ticket link to your reconciliation worksheet.</li>
  <li><strong>Mirror the exact support category.</strong> If support moves the ticket to a different path, update your case type so future claims follow the same logic.</li>
  <li><strong>Respond in the same thread.</strong> Opening duplicate tickets can split evidence and slow review.</li>
  <li><strong>Track every evidence request.</strong> Record what was requested, who supplied it, and when it was uploaded.</li>
  <li><strong>Reconcile the final credit.</strong> Match the approved amount to the settlement report, transaction date, order or Goods ID, and reimbursement reason.</li>
</ol>

<p>If a claim is denied, read the denial reason literally. Many denials are not final policy decisions; they are evidence or routing failures. Correct the missing document, reference ID, or deadline explanation before escalating.</p>

<h2 id="faq">FAQ</h2>
<details><summary>What is an FBT lost package claim?</summary><p>It is a practical label for a reimbursement request involving FBT inventory that cannot be reconciled to a qualifying consumer-order, inbound, in-warehouse or removal event. Eligibility depends on the exact scenario and transport responsibility.</p></details>
<details><summary>Which Seller Center category should I use?</summary><p>Use the event-specific category and reference: impacted order for outbound consumer claims, IBR for inbound, WOP/WOT for in-warehouse loss or damage, and OBC for removal. Verify the live labels before filing.</p></details>
<details><summary>Does an inbound shortage automatically qualify?</summary><p>No. A planned-versus-received difference may be investigated, but it can be ineligible when the discrepancy occurred before receipt into the FBT network. Establish a covered warehouse issue or eligible First Mile exception.</p></details>
<details><summary>Do I need an LPOA to have FBTops process reimbursement claims?</summary><p>No official TikTok source reviewed here says every claim requires an LPOA. FBTops uses written authorization as an onboarding control; depending on the seller&#8217;s counsel and workflow, this may be a limited authorization letter or narrowly scoped LPOA. Access should use a sub-account, Partner authorization or approved OAuth/API workflow rather than shared owner credentials.</p></details>
<details><summary>Can I use the same deadline for every FBT reimbursement claim?</summary><p>No. The active consumer-order rule uses 60 days from order placement. The IBR/WOP/WOT/OBC warehouse schedule becomes effective July 20, 2026 and uses different trigger events. Before that date, use the rule displayed in the seller&#8217;s account.</p></details>
<details><summary>How do I know whether the claim was paid?</summary><p>Match the approved ticket to the settlement and payout records. Confirm amount, reason, transaction date and related order or Goods ID before marking the case recovered.</p></details>

<section class="guide-sources" id="sources">
<h2>Official sources</h2>
<ol>
<li><a href="https://scm-us.tiktok.com/merchant-university/course-details/26935332358" target="_blank" rel="noopener">Guide to Claims: Product Inbound, In Warehouse, and Product Removal</a>, June 19, 2026. July 20 effective date, eligibility, paths, identifiers, evidence and transport exclusions.</li>
<li><a href="https://scm-us.tiktok.com/merchant-university/course-details/26903053318" target="_blank" rel="noopener">Guide to Claims: Outbound Order Claims for Logistics-Related Issues</a>, July 2, 2026. Consumer-order scenarios and 60-day request window.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=1331308753078058" target="_blank" rel="noopener">Seller Terms of Service for TikTok Shop (US)</a>, effective January 22, 2026. Third-party/API use and credential restriction.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=3005954397357832" target="_blank" rel="noopener">Access Management on Seller Center</a>, May 26, 2026. Invited sub-accounts and roles.</li>
<li><a href="https://partner.tiktokshop.com/docv2/page/66063c677be39902c7774b24" target="_blank" rel="noopener">TikTok Shop Partner Center Terms of Service</a>, January 22, 2026. Written seller approval for account access.</li>
<li><a href="https://partner.tiktokshop.com/docv2/page/authorization-overview-202407" target="_blank" rel="noopener">Authorization overview</a>. OAuth-based seller authorization for approved applications.</li>
</ol>
</section>
<div class="guide-change-log"><strong>Change log.</strong> July 13, 2026: labelled July 20 warehouse rules as future-effective; separated timing from eligibility; added inbound network-responsibility and removal-transport exclusions; split WOP/WOT/OBC paths; clarified that LPOA is an optional seller-provider authorization control, not a verified TikTok claim requirement; added primary sources.</div>
<div class="guide-cta">
  <strong>Need FBT claims processed without handing over your owner password?</strong>
  <p>FBTops audits FBT lost package claims, inbound shortages, damaged inventory, refund exceptions, and settlement discrepancies. We work from Seller Center evidence, signed authorization/LPOA where needed, and least-privilege access.</p>
  <a href="/free-audit/">Request a free 14-day audit</a>
  <small>Independent service. Not affiliated with TikTok. Reimbursement outcomes depend on Seller Center records and applicable policy.</small>
</div>

<p><strong>Related guides:</strong> <a href="/tiktok-shop-reimbursement-policy/">TikTok Shop reimbursement policy</a>, <a href="/what-evidence-supports-fbt-reimbursement-claim/">what evidence supports an FBT reimbursement claim</a>, and <a href="/how-to-reconcile-tiktok-shop-payments/">how to reconcile TikTok Shop payments</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>TikTok Shop Reimbursement Policy: Deadlines, Evidence, and Claim Rules</title>
		<link>https://fbtops.com/tiktok-shop-reimbursement-policy/</link>
		
		<dc:creator><![CDATA[Oleksandr Bondar]]></dc:creator>
		<pubDate>Sun, 12 Jul 2026 17:29:02 +0000</pubDate>
				<category><![CDATA[Policy & Deadlines]]></category>
		<guid isPermaLink="false">https://fbtops.com/tiktok-shop-reimbursement-policy/</guid>

					<description><![CDATA[Current TikTok Shop reimbursement deadlines, future-effective FBT warehouse claim windows, eligibility rules, evidence, and official sources for US sellers.]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">TikTok Shop does <strong>not</strong> use one universal reimbursement deadline. On the July 13, 2026 review date, manual FBT consumer-order logistics claims use a <strong>60-calendar-day window from the order placed date</strong>. TikTok has also announced a separate warehouse schedule that becomes effective <strong>July 20, 2026</strong>: inbound IBR requests can be submitted from day 14 through day 180 after first receipt, WOP/WOT in-warehouse claims use 60 days from the inventory-adjustment date, and eligible OBC removal claims use 60 days from handover or actual outbound time.</p>


<p class="wp-block-paragraph">This guide separates rules in effect on the review date from announced future rules, identifies the event that starts each clock, and distinguishes official policy from seller-reported operating practices. A claim can still fail inside the filing window when the scenario is ineligible, routed incorrectly, or unsupported by the required records.</p>


<div class="guide-verified"><strong>Last verified: July 13, 2026.</strong> Warehouse windows marked &#8220;effective July 20&#8221; were announced but were not yet in force on the review date. Until then, use the timeframe displayed in your Seller Center account. Recheck the linked official source and your account before filing.</div>


<nav class="guide-toc" aria-label="On this page">
<p>On this page</p>
<ul>
<li><a href="#deadline-matrix">The deadline matrix</a></li>
<li><a href="#evidence-protocol">The evidence protocol</a></li>
<li><a href="#golden-rule">Refund decisions and eligibility</a></li>
<li><a href="#auto-vs-manual">Automatic vs manual reimbursements</a></li>
<li><a href="#community">What sellers report in practice</a></li>
<li><a href="#checklist">Operations checklist</a></li>
<li><a href="#faq">FAQ</a></li>
<li><a href="#sources">Official sources and change log</a></li>
<li><a href="#related">Related guides</a></li>
</ul>
</nav>


<h2 class="wp-block-heading" id="deadline-matrix">The deadline matrix: match the clock to the scenario</h2>


<p class="wp-block-paragraph">Several clocks can exist around one order, but they do not all control the seller&#8217;s reimbursement request. Buyer refund-response timers, shipping-insurance deadlines, consumer-order FBT claims, and warehouse inventory claims have different triggers. Late requests may be rejected under the applicable policy, so record the source event rather than the day the discrepancy was discovered.</p>


<div class="guide-table">
<table>
<thead><tr><th>Claim or action</th><th>Window</th><th>Clock starts</th><th>Status and source</th></tr></thead>
<tbody>
<tr><td>FBT consumer-order logistics claim</td><td>60 calendar days</td><td>Order placed date</td><td>Active on review date. <a href="https://scm-us.tiktok.com/merchant-university/course-details/26903053318" target="_blank" rel="noopener">Official outbound claims guide</a>.</td></tr>
<tr><td>Inbound missing units (IBR)</td><td>Day 14 through day 180</td><td>First receipt at hub or direct fulfillment center</td><td><strong>Effective July 20, 2026.</strong> Eligibility is separate from timing. <a href="https://scm-us.tiktok.com/merchant-university/course-details/26935332358" target="_blank" rel="noopener">Official warehouse claims guide</a>.</td></tr>
<tr><td>In-warehouse lost or damaged (WOP/WOT)</td><td>60 calendar days</td><td>Inventory-adjustment/order-create date</td><td><strong>Effective July 20, 2026.</strong> Not the buyer order date. <a href="https://scm-us.tiktok.com/merchant-university/course-details/26935332358" target="_blank" rel="noopener">Official warehouse claims guide</a>.</td></tr>
<tr><td>Removal package lost or damaged (OBC)</td><td>60 calendar days</td><td>Handover or actual outbound time</td><td><strong>Effective July 20, 2026.</strong> TikTok-arranged return transportation only. <a href="https://scm-us.tiktok.com/merchant-university/course-details/26935332358" target="_blank" rel="noopener">Official warehouse claims guide</a>.</td></tr>
<tr><td>TikTok Shipping insurance</td><td>90 days</td><td>Ship date</td><td>Excludes FBT and seller shipping. <a href="https://seller-us.tiktok.com/university/essay?knowledge_id=6626878837311275" target="_blank" rel="noopener">Official Shipping Insurance guide</a>.</td></tr>
<tr><td>Buyer return/refund action</td><td>Varies by request and scenario</td><td>Buyer request or logistics event</td><td>Buyer-facing workflow, not a universal seller claim clock. <a href="https://seller-us.tiktok.com/university/essay?knowledge_id=3253210454181634" target="_blank" rel="noopener">Current return and refund policy</a>.</td></tr>
<tr><td>7-, 10-, or 20-day logistics thresholds</td><td>Scenario-specific</td><td>Tracking or carrier event</td><td>Do not apply universally. The 20-business-day/affidavit route belongs to legacy TikTok Shipping scenarios.</td></tr>
</tbody>
</table>
</div>


<figure class="figure svg-fig"><img decoding="async" src="/wp-content/themes/fbtops-child/assets/img/deadline-matrix.svg?v=3" alt="Scenario-specific TikTok Shop claim clocks for consumer orders, inbound inventory, warehouse adjustments, removal orders and shipping insurance" width="440" height="270" loading="lazy"><figcaption>The policy, trigger event and effective date must all match the claim scenario.</figcaption></figure>


<p class="wp-block-paragraph">The 60-day consumer-order rule cannot be copied onto every FBT warehouse case. The announced IBR, WOP/WOT and OBC clocks begin July 20, 2026; the public guide reviewed here does not define the complete pre-July-20 transition rule. For cases filed before that date, use the instruction shown in the seller&#8217;s account and preserve a dated screenshot. If payouts already look inconsistent, start with our guide to <a href="/how-to-reconcile-tiktok-shop-payments/">reconciling TikTok Shop payments</a>.</p>


<h2 class="wp-block-heading" id="evidence-protocol">The evidence protocol: what actually wins claims</h2>


<p class="wp-block-paragraph">Reimbursement decisions are evidentiary, not sympathetic. Sellers who win appeals do not write better complaints &#8212; they attach better records. Three types of evidence carry the most weight, and all three must be captured <em>before</em> you need them.</p>


<h3 class="wp-block-heading">1. The unboxing video</h3>


<p class="wp-block-paragraph">When a customer return arrives, a continuous unboxing video is the strongest defense against return fraud &#8212; the buyer who returns a brick, a used item, or a different product entirely. To be usable in an appeal, the video should be one uninterrupted take that shows:</p>


<ul class="wp-block-list"><li>The return order information &#8212; tracking number or QR code &#8212; clearly on camera.</li><li>All six sides of the unopened package.</li><li>The complete opening process, with no cuts.</li><li>The specific issue: the damage, the missing part, or the wrong item.</li></ul>


<h3 class="wp-block-heading">2. Photo documentation for damage</h3>


<p class="wp-block-paragraph">Damage claims need two sets of photos, not one: the damaged inner item <em>and</em> the damaged outer packaging. A photo of a broken product without the packaging leaves open the argument that the item was packed damaged &#8212; which shifts the loss back to you.</p>


<h3 class="wp-block-heading">3. Weight verification</h3>


<p class="wp-block-paragraph">For missing-component and shortage disputes, the carrier receipt showing the package weight is decisive &#8212; when it matches the weight listed on your Product Detail Page. Keep PDP weights accurate and file carrier receipts systematically; the comparison proves the package left complete.</p>


<figure class="figure svg-fig"><img decoding="async" src="/wp-content/themes/fbtops-child/assets/img/evidence-stack.svg?v=1" alt="Three evidence types for TikTok Shop appeals: a continuous unboxing video, photos of the damaged item and packaging, and a carrier weight receipt matching the product page weight" width="440" height="250" loading="lazy"><figcaption>Weak documentation &#8212; not weak cases &#8212; is the most common reason claims are rejected.</figcaption></figure>


<p class="wp-block-paragraph">For a deeper breakdown of how to organize identifiers, tracking history and settlement records into a claim packet, see <a href="/what-evidence-supports-fbt-reimbursement-claim/">what evidence supports an FBT reimbursement claim</a>.</p>



<h2 class="wp-block-heading" id="golden-rule">Before issuing a seller-funded logistics refund</h2>


<div class="guide-warning"><strong>Check the current FBT or TikTok Shipping workflow before approving a logistics-related refund.</strong> In some scenarios, proactive seller approval can affect reimbursement eligibility; in others, current outbound guidance allows a seller to file after issuing a logistics-related refund. The correct action depends on the order&#8217;s fulfillment route and claim type.</div>


<p class="wp-block-paragraph">Do not turn a scenario-specific operating rule into a universal prohibition. Record who funded the refund, why it was approved, which logistics route handled the order, and whether TikTok already created an automatic credit. When the buyer should contact TikTok Customer Service, direct them there; when Seller Center permits a seller-filed claim, preserve the buyer request, refund event and carrier history in the same case packet.</p>


<h2 class="wp-block-heading" id="auto-vs-manual">Automatic vs manual reimbursements</h2>


<p class="wp-block-paragraph">Some qualifying outbound scenarios are designed for automatic reimbursement after TikTok approves the buyer&#8217;s logistics-related request. Warehouse inventory and removal cases use separate manual workflows. In every case, verify the final credit in the settlement report.</p>


<div class="guide-table">
<table>
<thead><tr><th>Scenario</th><th>Typical handling</th><th>Seller control</th></tr></thead>
<tbody>
<tr><td>Delivered Not Received after an approved buyer request</td><td>Often automatic under the qualifying outbound workflow</td><td>Check the order and settlement for the expected credit; file within 60 days if a qualifying reimbursement was missed.</td></tr>
<tr><td>Buyer return or Return to Seller logistics issue</td><td>Scenario-dependent</td><td>Use the current outbound-order guidance; do not assume every return loss is automatic.</td></tr>
<tr><td>Damaged, wrong, or missing customer return</td><td>Usually manual review</td><td>Use the outbound-order reimbursement path and attach inspection evidence. Do not misroute it as an in-warehouse WOP/WOT claim.</td></tr>
<tr><td>Inbound planned quantity exceeds received quantity</td><td>Investigation first; not automatically reimbursable</td><td>The count difference alone does not prove an FBT warehouse loss. Establish a network issue or an eligible First Mile exception.</td></tr>
<tr><td>Inventory lost or damaged after warehouse receipt</td><td>Manual WOP/WOT claim</td><td>Use the inventory-adjustment reference and the rule applicable on the filing date.</td></tr>
<tr><td>Full removal shipment lost</td><td>Manual OBC claim when eligible</td><td>The announced compensation route applies only when TikTok arranged return transportation; partial shortages use Less Items Received.</td></tr>
</tbody>
</table>
</div>


<p class="wp-block-paragraph">&#8220;Automatic&#8221; is not the same as &#8220;reconciled&#8221;. Credits can be delayed, partial, netted against other entries or absent from the expected payout. The step-by-step manual workflow and exact IBR/WOP/WOT/OBC categories are covered in our <a href="/fbt-lost-package-claim/">FBT lost package claim guide</a>.</p>


<h2 class="wp-block-heading" id="community">What sellers report in practice</h2>


<p class="wp-block-paragraph">Seller communities can reveal recurring operational problems, but they are discovery sources, not policy authority. Verify every reported rule against the current US Seller Center or an official source before publishing or filing.</p>


<p class="wp-block-paragraph"><strong>Return-fraud reports are common.</strong> Sellers frequently recommend continuous unboxing video, package photos and weight records. These records can make an appeal easier to evaluate, but no community tactic guarantees reimbursement.</p>


<p class="wp-block-paragraph"><strong>An inbound count difference is not automatically a payable FBT loss.</strong> If the fulfillment network receives fewer units than the seller planned, TikTok may investigate or locate the inventory, but the difference alone may be ineligible because it occurred before the units entered the warehouse network. Photographing cartons, retaining signed BOL/POD records and matching SKUs helps establish what happened; eligibility still depends on the official scenario.</p>


<p class="wp-block-paragraph"><strong>Organized follow-up is more useful than duplicate tickets.</strong> Seller reports suggest that some evidence-related rejections can be reconsidered after the missing reference or document is supplied. Keep one case history where possible and distinguish a corrected submission from an unsupported repeat request.</p>


<h2 class="wp-block-heading" id="checklist">Your policy operations checklist</h2>


<ul class="wp-block-list">
<li><strong>Record the correct trigger:</strong> order placed, first receive, inventory adjustment, handover, or ship date.</li>
<li><strong>Label future rules:</strong> do not apply the July 20 warehouse schedule before its effective date without account-specific instruction.</li>
<li><strong>Separate timing from eligibility:</strong> an inbound discrepancy inside the filing window can still be ineligible.</li>
<li><strong>Check the refund workflow before acting:</strong> seller-funded approval can affect some logistics claims, but the rule is scenario-specific.</li>
<li><strong>Preserve original evidence:</strong> IDs, timestamps, URLs, tracking, invoices, BOL/POD and inventory adjustments.</li>
<li><strong>Reconcile automatic credits:</strong> approval is not recovered cash until the statement and payout match.</li>
<li><strong>Recheck the official source:</strong> save the title, URL, effective date and access date used for each decision.</li>
</ul>


<h2 class="wp-block-heading" id="faq">TikTok Shop reimbursement policy FAQ</h2>


<details><summary>Is every FBT claim subject to the same 60-day deadline?</summary><p>No. The active consumer-order outbound guide uses 60 calendar days from the order placed date. A separate warehouse schedule announced for July 20, 2026 uses day 14 through day 180 from first receipt for IBR cases and 60 days from the relevant adjustment or handover event for WOP/WOT and eligible OBC cases.</p></details>
<details><summary>What happens if I miss a claim window?</summary><p>A late request may be rejected under the policy for that scenario. Confirm the exact trigger and applicable version before concluding that recovery is unavailable, because buyer, insurance, consumer-order and warehouse clocks are different.</p></details>
<details><summary>Does an inbound receiving shortage automatically qualify for reimbursement?</summary><p>No. A difference between planned and received quantity can trigger investigation, but the difference alone may be ineligible when it occurred before the units entered the FBT network. Reimbursement depends on establishing a covered warehouse issue or an eligible First Mile exception.</p></details>
<details><summary>Does TikTok Shop reimburse sellers automatically?</summary><p>Some qualifying outbound buyer-request scenarios can be reimbursed automatically. Inbound, in-warehouse and removal claims use separate workflows, and every expected credit should be matched to the settlement and payout records.</p></details>
<details><summary>What evidence helps with a disputed return?</summary><p>Preserve the return label, tracking, sealed-package views, continuous opening, product condition, packaging, relevant weights and Seller Center records. Evidence requirements vary; an unboxing video is an operational control, not a guarantee of approval.</p></details>
<details><summary>Can FBTops prepare and follow up on claims?</summary><p>Yes. FBTops can reconcile records, identify potential cases, organize evidence and prepare, submit or follow up on claims under written authorization and platform-supported access. We do not require shared owner credentials, and TikTok determines eligibility and payment.</p></details>



<section class="guide-sources" id="sources">
<h2>Official sources</h2>
<ol>
<li><a href="https://scm-us.tiktok.com/merchant-university/course-details/26903053318" target="_blank" rel="noopener">Guide to Claims: Outbound Order Claims for Logistics-Related Issues</a>, published July 2, 2026. Consumer-order reimbursement scenarios and 60-day filing rule.</li>
<li><a href="https://scm-us.tiktok.com/merchant-university/course-details/26935332358" target="_blank" rel="noopener">Guide to Claims: Product Inbound, In Warehouse, and Product Removal</a>, published June 19, 2026. Warehouse schedule effective July 20, eligibility, IBR/WOP/WOT/OBC paths and evidence.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=6626878837311275" target="_blank" rel="noopener">Shipping Insurance</a>, updated May 14, 2026. TikTok Shipping/U-PIC scope and 90-day deadline; excludes FBT and seller shipping.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=3253210454181634" target="_blank" rel="noopener">Customer Order Cancellation, Return, and Refund Policy</a>, updated July 8, 2026. Buyer-facing refund and reverse-logistics rules.</li>
<li><a href="https://seller-us.tiktok.com/university/essay?knowledge_id=8280381640656683" target="_blank" rel="noopener">How to File a Reimbursement Claim for Legacy TikTok Shipping Logistics Issues</a>, updated April 24, 2026. Legacy 20-business-day and affidavit scenarios; not the FBT warehouse rule.</li>
</ol>
</section>
<div class="guide-change-log"><strong>Change log.</strong> July 13, 2026: separated active consumer-order rules from the warehouse schedule effective July 20; corrected inbound eligibility, removal exclusions, refund wording and legacy shipping distinctions; added primary-source links. Next scheduled review: July 20, 2026, or earlier if Seller Center issues a transition notice.</div>


<h2 class="wp-block-heading" id="related">Related guides and insights</h2>


<ul class="wp-block-list"><li><a href="/fbt-lost-package-claim/">FBT lost package claim: how to document and file the case</a> &#8212; the manual claim process, including exact ticket categories.</li><li><a href="/how-to-reconcile-tiktok-shop-payments/">How to reconcile TikTok Shop payments</a> &#8212; the workflow that surfaces claimable cases in time.</li><li><a href="/what-evidence-supports-fbt-reimbursement-claim/">What evidence supports an FBT reimbursement claim?</a> &#8212; building an appeal-ready packet.</li><li><a href="/identify-duplicate-tiktok-shop-refunds-settlement-reports/">How to identify duplicate TikTok Shop refunds</a> &#8212; one of the most common settlement discrepancies.</li></ul>


<div class="guide-cta"><p class="guide-cta-title">Deadlines are the whole game &#8212; let us watch them for you</p><p>A free 14-day audit of one seller account maps every claimable case against its remaining window: what is recoverable, what evidence supports it, and what expires next. No upfront cost, no admin access.</p><a class="guide-cta-btn" href="/free-audit/">Get my free 14-day audit</a><small>Independent service &#183; Not affiliated with TikTok &#183; Success fee only, after funds are recovered</small></div>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
