US TikTok Shop Reimbursement Ops Playbook

A workable US TikTok Shop reimbursement playbook runs one repeatable loop: ingest orders and settlements, classify the event, search later offsets, calculate expected versus actual USD, assemble evidence, file through the correct channel, track the deadline, and verify the credit or payout before marking recovered.

A TikTok reimbursement playbook is most useful when every step leaves an auditable record: source rows, owner, next action, deadline, filing ID, and verified outcome.

Reimbursement operations fail when every exception becomes a spreadsheet note with no owner, deadline, or outcome. A good process keeps the raw data, the policy calculation, the evidence pack, and the filing history together for one order and one claim type.

This playbook is for US TikTok Shop sellers and operations teams handling fee mismatches, shipping discrepancies, missing logistics reimbursements, FBT issues, and lost or damaged shipment claims. Chargebacks are a separate bank-dispute workflow; do not merge them into the reimbursement queue.

What should a reimbursement operations playbook control?

The process should answer six questions for every candidate:

What order, shop, and settlement rows are involved?
Is this a reimbursement, a chargeback, a carrier dispute, or a valid adjustment?
What amount was expected, what amount posted, and what remains unexplained?
Which filing channel and current US policy apply?
What evidence is missing, and when does the filing window close?
Was the eventual credit or payout verified and recorded?

Use the US TikTok Shop payout reconciliation guide for the order-level math. This playbook turns that math into an owned queue with repeatable handoffs and outcome reporting.

What fields belong in the reimbursement queue?

Create one row per order-event, not one row per order. A single order can have a shipping discrepancy and a separate chargeback, each with a different channel and deadline.

Field	Operating rule
Shop ID and order ID	Keep identifiers as text; never merge shops in one work item
Claim type	Use a stable type such as fee, shipping, missing platform reimbursement, lost, damaged, DNR, or return protection
Detection rule	Record why the item entered the queue
Expected, actual, and requested USD	Preserve the formula inputs and round to cents
Fulfillment method	Distinguish TikTok Shipping, FBT, and Seller Shipping
Filing channel	Select Seller Center, U-PIC, FBT, carrier, or another verified path
Anchor date and deadline	Record the event date, waiting-period end, and hard cutoff
Confidence	High, medium, or low based on the evidence available
Owner and next action	Every open row needs a named owner and a dated follow-up
Status and claim ID	Keep the original ticket or claim ID through the outcome
Recovery verification	Settlement transaction, reimbursement record, insurance payout, or manual proof

The settlement CSV audit guide covers raw-file preservation, transaction IDs, sign normalization, and unlinked rows. Those controls matter because a duplicated export or a missing order join can create a false claim before an operator ever opens Seller Center.

How should daily intake work?

1. Preserve the source data

Save the original order and finance exports unchanged, or record the sync period and source when data is ingested through an integration. Note the shop, currency, statement period, export date, and filters. Work from a normalized copy while retaining the raw file for audit.

Do not compare a bank deposit directly with gross sales. Settlement timing, refunds, reserves, fees, shipping, and later adjustments can all separate an order date from the date money reaches the bank.

2. Deduplicate and join

Use order ID, statement ID, transaction ID, and adjustment ID to prevent double counting. Keep rows without an order ID in an unlinked bucket for separate review. If a later export contains a reversal, retain both the original and correcting rows.

3. Classify the event before filing

Use the event and fulfillment method to choose a path:

Signal	Likely workstream	First control
Seller Center shows a chargeback notice and reply-by date	Chargeback appeal	Respond in the chargeback flow; do not substitute a reimbursement ticket
Fee debit does not match the transaction-date formula	Fee review	Apply the policy basis and search for reversals
Shipping debit lacks a supported measurement or offset	Shipping discrepancy	Check carrier measurements, buyer contribution, and later credits
TikTok Shipping or FBT loss, damage, or DNR event	Logistics reimbursement	Confirm waiting period, tracking, and program channel
Seller Shipping carrier invoice	Carrier dispute	Use the carrier’s process unless current TikTok policy says otherwise
Matching credit already appears later	Reconciliation close	Link the offset and do not file a duplicate

The chargeback vs. reimbursement guide explains why a debit-defense workflow and a credit-recovery workflow need separate rows, evidence, and clocks.

How do you calculate the amount to review?

For each candidate, use a short formula that another operator can reproduce:

Unexplained amount = actual related deductions − expected amount − later offsets

The sign convention can be reversed if the workbook documents it. The important controls are consistency, order-level grouping, transaction-date policy, and an explicit offset search.

The expected amount may include:

the applicable fee rate and basis;
approved refund or replacement amount;
supported carrier cost;
buyer-paid shipping contribution;
platform or logistics credits;
reserves or other valid deductions; and
the amount already paid in a later adjustment.

Use the fee mismatch examples by claim type for referral, refund admin-fee, shipping, and promotion edge cases. A non-zero delta is a review signal, not proof that TikTok owes the full amount.

How should the queue be prioritized?

Prioritize by deadline and evidence readiness, not only by dollar value:

Chargeback notices with a near reply-by date, handled in their own workflow.
Reimbursement candidates whose waiting period has ended and filing window is closing.
High-confidence fee or settlement mismatches with complete math.
Medium-confidence logistics candidates that need a policy or timing check.
Low-confidence items missing tracking, photos, delivery proof, or other required documents.

Use the application’s claim statuses consistently:

Status	Meaning	Required next action
Detected	A rule found a possible discrepancy	Validate the event and source rows
Needs review	Eligibility, timing, or evidence is incomplete	Assign an owner and resolve the missing check
Ready	The amount, channel, and evidence are sufficient to file	Submit before the deadline
Filed	A claim or ticket was submitted	Save the ID and schedule follow-up
Recovered	The credit or payout was verified	Record amount, date, and verification source
Rejected	The channel or reviewer denied the request	Save the reason and decide whether a valid escalation exists
Expired	The filing window ended without a valid filing	Record the cause and improve intake
Dismissed	Review found no recoverable discrepancy	Preserve the explanation; do not recreate it on the next sync

Never overwrite a filed, recovered, rejected, expired, or dismissed decision simply because a new reconciliation run sees the same order. An idempotent queue keeps the audit trail intact.

What should an evidence pack contain?

Build the pack before the ticket is opened. The reviewer should be able to reproduce the request without searching across a shared drive:

order ID, SKU, shop, and fulfillment method;
expected, actual, and unexplained USD amounts;
order and settlement export rows;
transaction and adjustment IDs;
refund or delivery status when relevant;
tracking history, acceptance scan, POD, or damage photos for logistics events;
the policy or program reference for the transaction date;
proof that later statements were searched for an offset;
deadline math and the filing channel; and
prior ticket or claim history.

The Seller Center evidence pack template provides a reusable folder structure and request wording. Keep one pack per claim type. Combining a shipping fee dispute with a lost-parcel claim makes the request harder to review and can send it to the wrong channel.

How do you file and manage deadlines?

Before submitting, run this short gate:

The event is classified as a reimbursement, not a chargeback or carrier-only dispute.
The order and shop IDs match every attachment.
The expected-versus-actual calculation uses the policy effective on the event date.
Later statements were searched for a matching credit.
The fulfillment method and filing channel are correct.
Required tracking, delivery, refund, or photo evidence is attached.
The deadline and waiting period are recorded.
The claim ID or ticket ID will be saved immediately after submission.

File through the current US TikTok Seller Center path, FBT process, U-PIC process, carrier, or other applicable channel. Do not open duplicate tickets in several channels to increase the chance of a response. If the wrong channel was used and a valid window remains, document the handoff and close the duplicate.

The claim deadline escalation guide covers deadline fields, near-cutoff triage, same-thread escalation, and the difference between a correct ineligibility decision and a stalled review.

What is a sensible escalation process?

Escalation should add evidence or correct a factual error, not restart the same case:

Situation	Response
Missing document that was attached	Reply on the original claim ID with the labeled attachment
Incorrect amount, tracking, or fulfillment fact	Quote the disputed line and attach the correcting record
No decision after the stated review period	Send a status request on the original ID, then use the named support path
Wrong channel and window still open	Refile in the correct channel, record the handoff, and close the duplicate
Correctly ineligible event	Record the reason and do not escalate
Chargeback lost at the bank	Record the outcome as a chargeback result; do not relabel it as a reimbursement

Keep the original request, attachments, denial text, and timestamps together. A short factual rebuttal is easier to review than a new narrative with no link to the first submission.

How do you verify a recovery?

Verification is the step that turns a filed request into a recovery metric:

Search later settlement statements by order ID, transaction ID, adjustment ID, amount, and date.
Match the credit to the claim type; do not use an unrelated order or shop credit.
For U-PIC or other insurance paths, save the payout notice and receipt evidence if no settlement row exists.
Record the recovered amount separately from the amount requested; partial recovery is still partial.
Mark the claim recovered only after the money or payout is verified.
Keep the original requested amount, filed date, and evidence so time-to-recovery remains measurable.

If a credit appears before filing, close the candidate as reconciled or dismissed with the offset attached. Filing after payment creates duplicate work and can distort the recovery-rate benchmark.

What cadence should an ops team run?

Cadence	Core actions	Output
Daily or each sync	Ingest new data, deduplicate, classify candidates, check near deadlines	Clean queue with owner and next action
Weekly	Review ready and aging filed items, search later statements, sample dismissals, escalate stalled claims	Filing and recovery worklist
Monthly	Close a cohort, calculate claim and dollar recovery, inspect outcomes by issue type	Benchmark report with pending and rejected counts
After policy changes	Recheck formulas, labels, evidence requirements, and open candidates	Versioned rule and process note

High-volume shops should not wait for a monthly close to find a lost-package deadline or a missing logistics credit. A monthly report is for measurement; intake and deadline review need to run more frequently.

Which KPIs should the playbook report?

Keep the operating dashboard small:

valid candidates detected;
candidate-to-filed rate;
filed USD and recovered USD;
claim-count and dollar recovery rates;
open filed USD by age;
median days from filed to recovered;
rejection, expiry, and dismissal reasons;
later-offset rate;
evidence completeness at filing; and
recovery by claim type, fulfillment method, and channel.

Do not collapse these into one “money found” number. Potential recoverable amount, filed amount, and verified recovered amount describe different stages. RecoverPayout’s dashboard and claims workflow is designed around that distinction: detected discrepancies become reviewable claims, and recovered amounts are tracked separately from open candidates.

How does RecoverPayout fit this playbook?

RecoverPayout connects to US TikTok Shop data or accepts supported order and settlement files, applies deterministic reconciliation rules, and creates claims with expected-versus-actual amounts and evidence fields. It can help an operator keep a repeatable queue instead of rebuilding the same spreadsheet each week.

The seller remains responsible for checking current eligibility, supplying missing documents, filing in TikTok Seller Center (US), FBT, carrier, or U-PIC channels, and confirming that a credit or payout arrived. Use the shipping fee discrepancy checklist, lost-in-transit reimbursement guide, and refund admin fee overcharge guide when a candidate needs a claim-type-specific review.

Frequently asked questions

What is a TikTok reimbursement ops playbook?

It is the documented process for detecting, classifying, calculating, filing, following up, and verifying US TikTok Shop reimbursement cases. It defines the queue fields, statuses, owners, evidence requirements, deadlines, and recovery metrics.

Should chargebacks be in the reimbursement queue?

No. Chargebacks are bank disputes that require a response to a Seller Center notice by its reply-by date. Reimbursements are credits or payouts for covered fee, shipping, logistics, platform, or insurance events. Track them separately even when they involve the same order.

What is the minimum evidence for a reimbursement claim?

Start with the order ID, fulfillment method, expected-versus-actual USD calculation, related settlement rows, transaction IDs, later-offset search, applicable policy reference, and the program-specific proof. Logistics cases may also need tracking, acceptance scans, delivery proof, or damage photos.

How often should a TikTok Shop seller review reimbursement candidates?

Review new candidates and near deadlines at least weekly; high-volume shops should process new data more often. A monthly close is useful for benchmarks and bank reconciliation, but it is too slow as the only deadline-control mechanism.

What should happen when a reimbursement credit appears later?

Match it to the original order and claim, record the recovered amount and posting date, and close the claim as recovered. If it appeared before filing, mark the candidate as offset or dismissed with the matching transaction attached instead of filing a duplicate.

How do I handle a denied reimbursement?

Save the denial text, claim ID, submitted evidence, and timestamps. Escalate on the same thread only when the denial contains a factual error, a document was overlooked, or the review is stalled. Accept correct ineligibility decisions and record the process lesson.

Does RecoverPayout file claims automatically?

No. RecoverPayout surfaces potential discrepancies and prepares evidence for seller review. The seller decides whether a case is eligible, files through the correct current channel, supplies seller-owned documents, and verifies the final credit or payout.

Sources and policy note

This guide addresses the US market. Confirm current TikTok Seller Center (US), FBT, U-PIC, and carrier requirements, deadlines, labels, and evidence rules for the specific order before filing. This is operational guidance only—not legal, tax, or financial advice.