A PI lands in your inbox as a supplier-formatted PDF and it wins by fatigue: twelve dense fields, a chop, and a payment deadline, arriving exactly when you're tired of comparing quotes. But read it wrong once and the failure mode is quiet until arrival day — spec disputes reference "quality per sample" with no AQL, the lead-time clock started at "PI date" you never confirmed, and the bank account on the deposit request belongs to an entity you never verified. The PI is not paperwork between you and the supplier; it's the contract you'll be read aloud in a Shenzhen arbitration room. Autopsy it like one.
The 14 Fields That Actually Bind
Everything on a PI is either load-bearing or furniture. Fourteen fields are load-bearing — they carry legal identity, clearance weight or payment triggers:
| # | Field | What it binds | Your verification move |
|---|---|---|---|
| 1 | Seller legal name + license number | Who owes performance | Match against National Enterprise Credit Information lookup; the trading company vs factory distinction changes the verification checklist you ran |
| 2 | Buyer entity name | Who owns the goods at every boundary | Consistent with your bond/IOR identity — the importer setup discipline (entity-name match) starts here |
| 3 | PI number + date | Version anchor for all amendments | Log it; the amendment discipline below lives and dies on numbering |
| 4 | Description lines (plain language) | The spec promise customs reads | Your words, not supplier marketing copy — vague descriptions are the top examination trigger |
| 5 | Per-line HS codes | Duty rate + clearance path | Run your own duty math; wrong codes surface as post-clearance audit exposure |
| 6 | Unit price + currency | The money promise | USD fixed-30-days language kills the FX re-open game |
| 7 | Order total (numbers + words) | Reconciliation anchor | Matches your landed-cost sheet; the teardown model prices everything around it |
| 8 | Incoterm + named port | Where risk and cost change hands | Convert multi-quote comparisons to FOB-equivalents before signing |
| 9 | Payment terms + trigger events | When money owes | Balance trigger bound to inspection pass + copy B/L — not to calendar dates the factory controls |
| 10 | Lead-time formula | The production clock | "25 days" becomes "25 days from deposit receipt AND golden-sample approval" |
| 11 | Packaging spec | The arrival condition | Carton spec by reference — the packing SOP's board-grade language goes in-line here |
| 12 | Sample reference serial | What the goods match | Sealed golden-sample ref; the clause that gives it teeth is below |
| 13 | Bank beneficiary details | Where your money goes | Character-by-character vs license name — the bank-name trap has its own section below |
| 14 | Stamp + signature block | Who executed | Company chop + legal-rep signature; a personal-name stamp authorizes nothing |
Fields 1, 2, 13 and 14 are the identity cluster — get any one wrong and the document's enforceability depends on events nobody planned. Fields 4-8 are the clearance cluster; customs reads your commercial invoice against them. Fields 9-12 are the performance cluster — the four dispute generators.
The Four-Clause Block Worth Arguing For
The payment terms guide introduced the four-clause block; this is the paste-ready layer with field-level placement:
- Beneficiary line (goes under field 13): "Payment beneficiary must match the business-license holder named above. Alternate accounts invalid; any account change requires a new PI countersigned by both parties." — kills the mid-order account-switch phishing in one sentence.
- Balance trigger (goes in field 9): "70% balance payable within 3 working days of (a) PASS third-party inspection at 80%+ ready quantity, and (b) receipt of copy B/L." — binds money to evidence events, the AQL protocol's enforcement window.
- Spec-warranty (goes in field 4/12): "Goods conform to Annex A spec and sealed sample ref [serial]; in conflict the sealed sample prevails. Non-conforming goods replaced or refunded at supplier cost including freight." — this is the golden-sample clause made global for the order.
- Dispute venue (goes above field 14): "Disputes resolved by CIETAC arbitration (Shenzhen) or [your neutral]; English prevails." — the enforceability clause most buyers forget; without it, "legal binding" is a conversation, not a venue.
Print these on the first PI and factories negotiate around them — the block's existence signals professional buyer and pre-empts the sloppy-dispute path. The tooling-specific fifth clause family lives separately: tooling ownership injects its own five-clause block when molds are involved.
The Bank-Name Trap: Legitimate Structure vs Deposit Drain
The single most recurring PI terror for first-time buyers: beneficiary bank account name doesn't match the PI-issuing company. Two worlds share this symptom:
| Signal | Legitimate: export-agency structure | Fraud pattern: deposit redirection |
|---|---|---|
| Relationship stated | PI issued by licensed factory; names the trade company as "export agent of [factory]" ON the PI | No relationship language; or "use this account, company paper coming later" |
| Documentation | Agency agreement copy provided as annex on request | Verbal assurances; documents promised after payment |
| Pressure vector | None — explains structure calmly at first ask | Production-slot urgency appears exactly when you question the account |
| Your move | Accept, keep annex logged under the PI number | Walk; the scam-defense checklist's beneficiary-mismatch instant-walk rule applies |
The distinction is documentary posture, not confidence — the fraud version is always more fluent than the legitimate one. Search-verify the agency structure once and it re-checks for years; the payment clause list carries the account-change protocol that keeps it re-verified every order.
Amendment Version Control: How Negotiated Clauses Un-Happen
The quiet killer. Production realities force PI re-issues — deposit arrives late, the sample run needs a spec tweak, the container count changes. Each re-issued PDF is a chance for the clause you negotiated to quietly vanish, because the supplier's admin re-types the template from memory, not from the negotiated copy. Real pattern from our tracked orders: the version that came back had the AQL clause (field 9's trigger) restored to the factory's default "quality per sample" — discovered only because the version log existed.
The discipline that makes amendments addressable:
- Version log line per PI: number + date + total + one-line red-line diff vs previous (a spreadsheet row, nothing fancier).
- Field-change = full re-sign: any change to the fourteen means a fresh countersign round; chat confirmations re-nothing a clause in arbitration.
- Amendment-PI naming: PI-001-A1, PI-001-A2 — the suffix links the family; a payment against PI-001-A2 cites that exact version in the wire memo.
- The deposit-anchor rule: wire only against the version in your log; a wire memo referencing a dead version is money with a memory.
Frequently Asked Questions
Is a proforma invoice legally binding in China?
Countersigned by both parties with quantity/spec/price/delivery stated, a PI reads as a contract in substance under Chinese arbitration practice — the document's title ("proforma") matters less than its fields and signatures. It is weaker than a full sales contract mainly in dispute mechanics, which is why the venue clause is the one worth typing. Unsigned PDF floating in chat is a quotation, not a contract.
What is the difference between a PI and a commercial invoice?
PI precedes payment and states deal terms; the commercial invoice issues at shipment and drives customs valuation. Customs reconciles the two line by line — mismatches (description wording, totals, HS codes) trigger the post-clearance audit pattern that ends in penalty exposure. PI is the promise, CI is its execution record.
What PI fields actually matter?
Fourteen: seller legal name + license number, buyer entity, PI number + date, plain-language description lines, per-line HS codes, unit price + currency (USD fixed-30-days), order total, Incoterm + port, payment trigger events, lead-time formula, packaging spec, sample reference serial, bank beneficiary, stamp + signature. The four clusters: identity (1/2/13/14), clearance (4-8), performance (9-12, plus 12's clause). Everything else is furniture.
The PI bank account differs from the company name — walk away?
Test the documentary posture, not the fluency. Legitimate export-agency structure: PI issued by the licensed factory naming the trade company as "export agent of" that factory on the PI itself, agency agreement available as annex. Fraud: no relationship language, documents promised post-payment, urgency appearing when you question the account. Anything looser than the documented structure earns your walk-away — beneficiary mismatch is the instant-walk red flag for a reason.
What do I do when the supplier re-issues the PI?
Diff line by line against your version log before countersigning — silent re-issuance is how negotiated clauses quietly un-happen. Field-change demands a full re-sign round, numbering follows PI-001-A1/A2 so wires cite the exact version, and the deposit-anchor rule keeps every payment tied to a logged version. Real tracked-order pattern: the re-issue restored the factory's default spec clause; only the version log caught it.
Can I edit the supplier's PI template?
Yes — margin-strike edits with both parties initialing before PDF signature are the professional standard, and suppliers expect them from buyers who will not be managed. What you cannot do: let the PI float unsigned through chat windows. Arbitration reads the signed artifact; unstamped edits are fiction in that room.
Want your PI reviewed before you sign it?
Send the draft PI (numbers can be blanked). We'll reply within 24-48h with the fourteen-field check, the clause block formatted for your template, and the exact re-draft language on any soft spot before your first deposit moves.
Request PI Review →📍 Make this the next step, not the last