The rejection notice simply reads “legal entity document information is inconsistent with the registered entity.” You check every character—the name, document number, issue date—all matching. You resubmit, and three days later it's rejected again. Within the same 48-hour window, SPS on 4 other stores drops from 180 to 95, AHR falls below the 150-point threshold, and Black Friday promotional registration eligibility is voided simultaneously. This is not 6 independent incidents—once the shared payment entity breaks, the platform flags all stores in the group under the same controlling entity; a single store's SPS anomaly triggers a re-review of associated stores, and secondary review materials get pulled back into the review queue.Item-by-Item Troubleshooting for Repeated Secondary Review RejectionsIn [the preceding section], the gap between standard rejection wording and the actual cause has already been broken down. This article focuses on the reverse-tracing method to use when “the stated wording and the root cause don't match.”
Three-Layer Causal Diagnostic Tree: Registered Entity → Payment Entity → Logistics Entity
Secondary review rejection, SPS score drop, and document review failure may seem like three independent symptoms, but they all trace back to the same diagnostic tree. Broken down by layer:
- Registered Entity Layer: legal entity document validity period is under 12 months (the backend does not flag this separately; it is lumped into “information inconsistency”); the registered entity name and the business license name differ in spacing, capitalization, or traditional vs. simplified Chinese characters; when local stores under the same business license in Thailand / Vietnam / Malaysia each reach the 3rd store, a cross-validation is triggered against the quota of 1–2 cross-border stores + 1–3 local stores.The maximum number of stores per business licenseA complete quota table is available.
- Payment entity layerThe payment account's owning entity does not match the store's registered entity (e.g., a local store registered under Company A but receiving payments through Company B's corporate account); when multiple stores share the same payment entity, if one store is flagged, the entire group's payments are frozen; a sub-account operator changed the payment entity but did not sync the change to the logistics contract.
- Logistics entity layerThe signing party of the logistics contract does not match the store's entity (cross-border stores must use the platform's 3PL whitelist, while local stores may use local logistics but the contract header must align); shipping tracking does not match the store's country (a Thailand-based local store showing shipment from a domestic warehouse); multiple stores sharing one logistics contract resulting in a fake-shipment determination.
Distribution of high-frequency secondary-review rejection reasons and their correlation with SPS
In Southeast Asian multi-store operations, secondary-review rejection reasons are not evenly distributed. The following is sorted by relative frequency (indicative relative metrics, not actual statistics):
When SPS falls below 150, the platform flags the store's AHR as "Needs Review," the Black Friday application channel is closed, and secondary review materials are subject to enhanced scrutiny (the standard 48-hour review cycle is extended to 72 hours or longer). This means: if you resubmit your secondary review materials while your SPS is already below 150, the rejection rate is significantly higher than when your SPS is healthy. The correct remediation order is to first stop the ongoing SPS score decline (suspend non-compliant operations and clear fake shipping records), and then resubmit the secondary review.
Mandatory Differences in Secondary Review Documents for Thailand, Vietnam, and Malaysia: Cross-Border Stores vs. Local Stores
The table below lists only the incremental hard thresholds at the secondary review stage. For a complete reference on registration document requirements, please refer toitem-by-item differences between cross-border and local stores:
| Dimension | Thai Local Store | Vietnamese Local Store | Malaysian Cross-Border Store |
|---|---|---|---|
| Legal Entity Documents | Passport remaining validity ≥ 12 months; Thai-national legal representatives must submit front and back copies of their national ID | The legal representative must be a Vietnamese citizen or a DRC joint-venture entity; foreign legal representatives must attach a work visa. | A passport valid for at least 6 months is sufficient; no local citizenship requirement. |
| Tax ID / entity registration proof | A Thai Tax Identification Number (TIN) + Certificate of Business Registration are required. | A Vietnamese tax number + a copy of the business establishment license is required. | Chinese business license + a dedicated cross-border store tax ID (platform withholds tax on behalf). |
| Logistics contract | Local 3PL contract; the contracting party must match the store entity. | Warehouses within Vietnam or platform-certified logistics providers must be used. | The TikTok-designated cross-border logistics whitelist must be used; the contract header must be in the store entity's name. |
| Payout attribution | Thai corporate bank account or the platform-designated receiving channel. | Vietnamese local bank account, account name = store entity name | A Chinese corporate bank account can be linked, but the account name must exactly match the registered entity. |
High-frequency pitfall: When a 3rd Thailand local store is rejected, 90% of cases are due to the legal representative's passport having fewer than 12 months of validity remaining at the time of submission, not a name spelling error. For Vietnam local stores, the issue is a mismatch between the legal representative's nationality and work visa type (an H1 visa cannot be used for business registration). For Malaysia cross-border stores, the most commonly overlooked problem is that the logistics contract letterhead lists the group parent company name instead of the store's registered entity.
Layer-by-layer remediation checklist before resubmission
- Registration entity layer remediation: Confirm that the legal representative's ID validity period covers the next 12 months; verify that the business license name matches the platform entry character by character (including spaces and punctuation); ensure the total number of stores under the same license has not exceeded the quota (cross-border 1–2 + each local 1–3).
- Payout entity layer remediation: Log in to the store backend under 'Finance Settings' and confirm that the receiving account name exactly matches the store's registered entity; if multiple stores share a payout entity, separate the store being resubmitted as an independent payout channel; check whether any sub-accounts have pending entity change tickets.
- Logistics entity layer remediation: Download the current logistics contract and verify the contracting party's letterhead; for cross-border stores, confirm that platform whitelist logistics providers are used; for local stores, confirm that local warehouse/3PL contract letterheads are aligned; clear all shipping records within the past 30 days marked as 'no tracking' or 'tracking inconsistent with destination country.'
- Sub-account and permissions layer remediation: In Business Center Role and Permission SettingsIn , confirm that operational sub-accounts do not have the 'Modify Payment Entity' or 'Change Logistics Contract' permissions; sub-accounts of departed employees must be deactivated immediately rather than transferred.
- SPS Recovery and Resubmission: After completing the fixes above, wait 7–14 days without any new violation records, confirm that SPS has recovered above 150 points before submitting the second-review materials; when resubmitting, attach a handwritten note (indicating which layer was fixed) to avoid the system flagging it as a duplicate submission and rejecting it outright.
Cascading Second-Review Risks in Multi-Store and Store-Cluster Contexts
When the same business license is used to set up multiple stores across Thailand, Vietnam, and Malaysia, the platform's risk-control layer groups stores that share a payment entity, shared IP ranges, or shared logistics contracts into the same controlling-entity group. If one store's SPS drops below 150, the second-review materials for the entire group are pulled into an intensified review queue; if the payment entity is flagged as anomalous, the withdrawal channels of associated stores are frozen simultaneously. The minimum remediation requirements are: name multi-store groups following the 'Country-StoreType-Sequence' format (e.g., TH-L-01, VN-L-02, MY-C-01), assign sub-accounts by operational unit rather than by individual, and for details on isolating 4–6 Profiles on a single workstation, seeDay-to-Day Store-Cluster Operations. Here, only 3 isolation items that must be verified during the second-review stage are highlighted: ① The account holder name on the payment account must be unique to each store; ② The contracting party on the logistics contract must be unique to each store; ③ Sub-accounts must not have cross-store operational permissions.
If your matrix already covers Thailand, Vietnam, and Malaysia with more than 5 stores, it is recommended to first completeBuilding a Southeast Asia Local-Store Matrixthe grouping and naming conventions within, then move on to store-by-store secondary review repairs to avoid a chain reaction where fixing one store breaks another. On the ad account side, TikTok's requirements for advertiser conduct and authenticity are detailed inTikTok Advertiser Account Policy, if the ad account is restricted due to entity irregularities during the secondary review period, address it in parallel to avoid funds being held up.
Frequently Asked Questions
How long after fixing the three-tier entity structure can I reapply for the Black Friday promotion?
SPS requires 7 consecutive days with no violations and a score back above 150, at which point AHR automatically removes the "requires review" flag. Typically, the registration channel reopens on day 8, but the actual timing depends on the real-time status shown on the "Event Registration" page in the seller dashboard. No fixed number of days is guaranteed.
After a sub-account employee departs, are SPS deduction points from their operational period recalculated?
No. SPS deductions are tied to the store entity, not the sub-account. Employee departure only triggers a permission revocation; existing violation records remain with the store. If a departing employee made false shipments or modified the payment-receiving entity during their active permission period, the deductions will not be cleared simply by deactivating the account.
The legal representative of a Vietnam local store is a foreign national, and the secondary review keeps getting rejected. What is required besides a work visa?
Besides a valid work visa, the legal representative name registered on the DRC (Certificate of Enterprise Registration) must exactly match the passport, and the passport validity must cover 12 months. If the legal representative on the DRC is a company (not an individual), an additional power of attorney plus the authorized person's Vietnamese citizenship proof or DRC registration record is required.
Is logging into 6 stores on separate computers safer than using multiple profiles on a single computer?
The number of devices is not itself a factor in the secondary review decision. The platform focuses on whether the three layers—payment-receiving entity, logistics contracts, and business license quota—are aligned. Spreading across multiple devices cannot substitute for entity-level isolation; if 6 stores share the same payment-receiving entity, no matter how many computers are used, a flag on one store will cascade. The core of isolation is at the entity level, not the device level.
