China Company Verification Before a Supplier Deposit

A deposit turns a name check into a payment decision

A buyer can lose leverage as soon as a deposit leaves the account. The review before payment should answer a narrow question: is the company asking for money the same business the buyer intends to contract with?

The useful file starts with the Chinese legal name, unified social credit code, registered address, legal representative, business scope and operating status. Then it compares those records with the invoice, bank beneficiary, email domain, website and sales contact.

The file should start with the live commercial record. Name the SKU, account, supplier, route, claim or customer promise that creates the exposure. Then name the evidence owner and the next event that should reopen the review. This keeps the work close to operations instead of turning it into a detached compliance memo.

Case pattern: the right factory name, wrong beneficiary

A buyer verifies a factory name and feels comfortable. The proforma invoice then asks for payment to a trading company with a similar English name. The sales contact says the companies are related but gives no ownership record.

The buyer should pause the deposit until the supplier explains the payment structure and the file shows who signs, invoices and receives funds.

The team should write the corrective note while the facts are fresh. The note should say what changed, which file now supports the decision and what the business will stop claiming until stronger evidence exists. That sentence prevents a private fix from turning into another public promise.

Build the pre-deposit file

The file should hold the registration record, license image, invoice, bank instruction, website screenshot and contact note in one folder. A reviewer should be able to read it without searching chat history.

For small test orders, the file can stay short. For tooling, private-label goods, credit terms or regulated products, add ownership, litigation and qualification checks before payment.

• Confirm Chinese legal name and credit code.
• Match invoice issuer and bank beneficiary.
• Compare business scope with ordered product.
• Save screenshots and dated source notes.
• Record any accepted mismatch before payment.

Review rhythm

Use one small sample each month while the issue remains active. Pull one recent order, one public page, one internal note and one customer or platform message. If those records tell the same story, record the sample date and move on. If they conflict, fix the specific field and ask whether other products, suppliers or routes share the same weakness.

The review should stay practical. A seller does not need a meeting for every small discrepancy. It needs a habit that catches drift before the drift reaches a customer, a platform reviewer, a customs desk or a payment partner.

Ask finance to read the file before payment. If finance cannot tell who receives the deposit and why, the commercial team has not finished the check.

The sample should include one negative example when possible. A complaint, rejected shipment, failed document request or confused customer message often shows the gap faster than a clean order. The reviewer should not treat the negative example as proof of failure. It is a stress test for the file.

If the sample exposes a gap, the team should fix the live record first and the policy note second. Customers, carriers and platforms see the live record. A polished internal rule does not help if the product page, invoice, support script or supplier instruction still says something else.

The review note should also record what the business will not expand yet. Do not add a new market, claim, bundle, route, supplier or campaign while the evidence for the current scope remains unresolved. This limit keeps a small file gap from becoming a wider operating problem.

That restraint is part of the control, not a delay tactic.

Handoff note

The handoff should be readable in ten minutes. It should name the business owner, file owner, missing evidence, accepted limit and next review trigger. If the answer depends on a chat thread or one employee memory, the record is too fragile.

Keep the handoff beside the working file. Product issues belong with listing, label, sample and complaint records. Supplier issues belong with purchase and due diligence records. Account and payment issues belong with access logs, finance approvals and platform notices.

Add an expiry trigger: a product version change, supplier change, new market, policy update, route change, complaint pattern or certificate date. Evidence that lacks a trigger can look complete long after it stops matching the live business.

Closing note

A pre-deposit check does not promise that a supplier will perform. It removes preventable identity and payment confusion before the buyer loses leverage.

That is the right level of ambition for the first review.

Reference links

• China National Enterprise Credit Information Publicity System