Why the same order appears on different days
A US business day and a China-based production team's workday do not end together. If one report groups a payment by Pacific Time and another by Beijing Time, the same event can land on different dates. Both totals can be internally consistent while describing different windows.
Start every comparison by naming the event and time zone. 'Yesterday' is not a complete reporting definition for a team operating across markets. Write the actual date and keep the date of the order separate from the time it was synced.
Understand Pacific Time and daylight saving time
Beijing is 16 hours ahead of Pacific Standard Time and 15 hours ahead of Pacific Daylight Time. Pacific midnight therefore corresponds to 4 p.m. or 3 p.m. in Beijing respectively. Use a time-zone-aware conversion rather than a fixed offset for all dates.
That means a morning report in Beijing may still include an unfinished US business day. Wait for the selected day to end and check data completeness before comparing it with a full prior day.
Check six common sources of disagreement
Differences can come from time zone, event type, account scope, included order statuses, synchronization delay, or later refund and cancellation changes. A newly authorized account may also still be filling historical records.
Write these definitions down before investigating individual orders. A missing record is not necessarily a calculation error, and a changing total is not automatically a new sale. Compare equivalent snapshots as well as equivalent dates.
Reconcile in the right order
Choose one completed date. Align the event type, time zone, accounts, and statuses. Compare total order count, GMV, and commission, then inspect the order IDs responsible for the difference. Orders near midnight are a useful place to start.
Save the explanation with the reconciliation record. For partner statements, confirm whether the partner uses creation, payment, or another date. Matching a platform date label does not prove that both parties selected the same underlying event.
Let sales dates and work dates serve different purposes
A cross-border team can use US business dates for orders, GMV, commission, and operating results, while using the staff's local workday for editing, publishing records, and attendance. Label both in a combined report.
An unfinished day should not be described as a decline against a completed day. If a progress comparison is useful, align the elapsed window and say it is partial. For routine reviews, completed and sufficiently synced periods are easier to interpret.
Understand Star Captain's business-date convention
The documented Star Captain workflow groups financial reporting around its US business-date convention, and the day changes at Pacific midnight with daylight-saving adjustment: 3 p.m. Beijing during daylight time and 4 p.m. in standard time. Order exports display Pacific Time. Those are related conventions, but they are not identical at every boundary.
If a single day differs by a few orders, check whether the other export uses order-created time or payment time before assuming an error. Check boundary orders and the exact export columns when reconciling. Performance analytics and Profit & cost need the same chosen range.
Inspect midnight, month-end, and daylight-saving boundaries
Check payments near the cutoff explicitly. At month-end, wait for the last US business day and the sync to complete before confirming commissions or partner statements. A one-hour boundary difference can cross a week or month too; do not assume a wider date range always cancels it out.
On daylight-saving transitions, verify actual timestamps rather than adding a constant number of hours. When historical backfill is incomplete, label the range as incomplete. A report with an honest coverage note is more useful than a falsely final total.
Write a short reporting standard for the team
Specify the financial business date, event field, display time zone, staff workday, report publication time, and reconciliation procedure. Include the cutoff convention in exports or the accompanying notes so a new colleague can reproduce a result.
For discrepancies, use the same sequence every time: dates, scope, totals, then order IDs. Record any definition change and its effective date. Avoid silently comparing a month calculated under one convention with another month calculated under a different one.
Agree on the date before debating the total
Most reconciliation work becomes easier once both sides can describe the exact window. Start with a completed day, retain original timestamps, and keep sync coverage visible. Then use the team performance checklist to connect orders to employee and team results.
A wider total can be a useful cross-check, but it is not a replacement for boundary testing. Preserve the old convention if the team changes reporting rules, and explain which periods can still be compared directly.
Frequently asked questions
Which time zone should we use for US TikTok Shop orders?
Use the time zone and event definition of the specific source report you are reconciling. This guide discusses Pacific Time and Star Captain's documented business-date convention; check the report labels explicitly.
Why does yesterday's total increase later in Beijing?
The corresponding US day may not have ended, or data may still be syncing. Refund and status updates can also change later snapshots.
What should we check first when totals differ?
Align date, time zone, event type, account scope, and status filters. Then compare order IDs and update times.
Does Star Captain match Pacific midnight exactly?
Yes. Business dates follow Pacific midnight and adjust for daylight saving time automatically. When a day still differs, compare the timestamp field each side used and review the first Pacific hour and period boundaries explicitly.
When should a China-based team publish its US daily report?
After the chosen US business day ends and coverage is sufficiently complete. The documented report schedule is around 3:30 p.m. Beijing in daylight time and 4:30 p.m. in standard time, with status notes when data is incomplete.
Should staff attendance also use the US business date?
Use the actual staff workday for attendance and production. Label it separately from the financial business date in combined reports.
Related guides
Put it into practice: Explore Orders & performance →
