Direct answer: A supplier mortgage/pledge security page is not a line saying "the supplier will provide security". The page should state: the security type (movable-property mortgage, receivables pledge, IP pledge, account/deposit pledge, equity pledge, real-property mortgage, third-party guarantee); the collateral/right description; the scope of secured debt; registration and searches; insurance/custody/use restrictions; priority; default and enforcement; release and discharge; cross-border and tax issues; and what must not be published. Legally, the Civil Code provides for mortgage (Article 394), mortgageable property (Article 395), creation of real-property mortgage by registration (Article 402), creation of movable-property mortgage on contract effectiveness but no opposition to good-faith third parties without registration (Article 403), pledge (Article 425), rights that may be pledged including receivables, equity and IP property rights (Article 440), creation of IP/receivables pledges by registration (Articles 444 and 445), and the purchase-money super-priority (Article 416); the Supreme People's Court interpretation on the security system addresses security contracts, registration, priority and enforcement; the Civil Procedure Law provides the procedure for enforcing security interests and preservation. This article is current to 2026-11-08 and is a summary of public rules and page method, not legal, security or financial advice; the law, contract, registration and court findings control.
This article is for procurement, finance, legal, internal-control, supply-chain and website teams at equipment, electronics, automotive-parts, medical-device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby. It covers how to write and accept a supplier mortgage/pledge security page. The usual gap is "collateral description, registration/search, priority, insurance/custody, enforcement/discharge, cross-border", ending with a page that only says "the supplier provides security".
First, fix the type: movable-property mortgage, receivables/IP/account/equity pledge, real-property mortgage or third-party guarantee have different registration and priority rules. Then fix the text: collateral description, debt scope, registration/search, insurance/custody, use restrictions and priority. Finally fix the exit: default/enforcement, release/discharge, cross-border/tax. The page should state type, registration, priority and enforcement — not "provides security".
How does this page relate to guarantees, retention of title, liquidated damages/deposits, supplier financial risk and contract-signing pages?
A mortgage/pledge security page answers "which asset/right secures the debt, how is it registered, and how is priority/enforcement handled"; the guarantee page answers "bank/insurer/guarantor credit plus documentary claims"; the retention-of-title page answers "ownership of the goods until payment plus registration/repossession"; the liquidated-damages/deposit page answers "remedies and the deposit penalty"; the supplier financial-risk page answers "early warning/exposure/security/contingency"; the contract-signing page answers "document priority/signature". Mortgage/pledge is a property/right security and cannot be replaced by a guarantee or retention of title.
Common breaks: only "provides security"; unclear collateral description; movable mortgage not registered; receivables/IP pledge not registered; prior mortgages/seizures not searched; insurance beneficiary unclear; collateral sold or moved; no enforcement path; no discharge on payment; cross-border not registered or assessed. The page separates "type—due diligence—contract—registration—priority—enforcement—exit" so procurement, finance and legal share one vocabulary.
| Page | Question it answers | Key content | Cannot replace |
|---|---|---|---|
| Mortgage/pledge security | Which asset secures/how registered/how enforced | Type, due diligence, contract, registration, priority, enforcement, exit | Guarantee/retention/deposit |
| Guarantee | Third-party credit/documentary claims | Bank/insurer/guarantor, text, expiry | Property security |
| Retention of title | Ownership until payment | Registration opposition, repossession, redemption | Mortgage/pledge |
| Liquidated damages/deposit | Breach remedies | Ratio, adjustment, deposit penalty | Priority over collateral |
| Supplier financial risk | Warning/exposure/contingency | Security, substitution, exit | Registration/enforcement procedure |
| Contract signing | Documents/signature/version | Priority, deviations, seals | Security registration |
Page relationships are editorial; the law, contract, registration and court findings control.
How should the security type be chosen?
Common types: movable-property mortgage (equipment, inventory, vehicles); receivables pledge (existing/future receivables); IP pledge (trademark/patent/copyright property rights); account/deposit pledge; equity pledge; real-property mortgage; third-party guarantee. Choose by collateral value/disposability/registration/priority/monitoring/cross-border/tax; equipment and inventory need depreciation, resale and seizure analysis; receivables need debtor dispersion, confirmation and collection accounts; IP needs validity, licences and valuation; real property needs registration, leases and seizure; a third-party guarantee needs the guarantor's credit, guarantee type and period. Do not just write "mortgage" — state the type and registration.
Acceptance checks: type; collateral; value; disposability; registration; priority; monitoring; cross-border/tax; guarantor. Common gaps: mixed types; collateral not disposable; inflated value; no registration; unclear priority; no monitoring; no cross-border assessment; weak guarantor.
| Type | Suitable/key points | Registration/evidence | Common gap |
|---|---|---|---|
| Movable mortgage | Equipment/inventory/vehicles; registration opposes third parties | Movable-property financing registration/search | Not registered |
| Receivables pledge | Existing/future; confirmation/collection account | Receivables pledge registration | No registration/confirmation |
| IP pledge | Trademark/patent/copyright property rights; validity | IP pledge registration | No registration/overvalued |
| Account/deposit pledge | Dedicated account/control/priority | Account agreement/registration | No control |
| Equity pledge | Equity value/corporate governance | Equity pledge registration | Not registered |
| Real-property mortgage | Plant/land; created by registration | Real-property registration | Not registered/lease |
| Third-party guarantee | Guarantor credit/type/period | Guarantee contract | General guarantee |
Type selection is editorial; decide by collateral, registration, priority, disposal and transaction risk.
What should due diligence check?
At least: title/authenticity of the collateral (invoice/registration/contract/possession); prior mortgages/pledges/seizures/leases/retention of title; registry searches; valuation/depreciation/disposal market; insurance/beneficiary; custody/use/transfer restrictions; guarantor credit/litigation/dishonesty; cross-border law/registration/tax; release/discharge path. For equipment, check nameplate/serial number/location; for inventory, warehouse/stock count/flow; for receivables, contract/invoice/debtor confirmation/collection account; for IP, certificates/annuities/licences/invalidity/litigation. Record the search date, screenshots and reports.
Acceptance checks: title; prior rights; registry search; valuation; insurance; custody; credit; cross-border; discharge; evidence. Common gaps: no prior search; invoice only; no valuation; no insurance; unclear custody; weak credit; no cross-border check; unclear discharge path.
| Due-diligence item | What to confirm | Evidence | Common gap |
|---|---|---|---|
| Title | Invoice/registration/contract/possession | Title documents | Invoice only |
| Prior rights | Mortgage/pledge/seizure/lease/retention | Search/registration | Not searched |
| Valuation | Market/depreciation/disposal | Appraisal/quotes | Overvalued |
| Insurance | Cover/beneficiary/sum insured | Policy | Missing |
| Custody/use | Location/conditions/transfer limits | Agreement/stock count | Unclear |
| Credit | Litigation/dishonesty/financials | Search/statements | Not checked |
| Cross-border | Law/registration/tax | Opinion | Not assessed |
| Discharge | Release/discharge path | Process | Unclear |
The due-diligence list is editorial; the collateral/right, registry system and transaction risk control.
Which security clauses should the contract contain?
At least: security type; collateral/right description (name/number/quantity/location/registration number); secured debt scope (purchase price/liquidated damages/compensation/expenses); registration obligation/timing/cost; insurance/beneficiary/sum insured; custody/use/maintenance/transfer/re-mortgage restrictions; priority/no hindrance; default/enforcement; release/discharge; representations (title/no prior rights/no seizure); cross-default; cross-border law/tax/enforcement; dispute resolution. Clauses must be enforceable; "the supplier provides a mortgage" is not enough.
Acceptance checks: type; description; debt scope; registration; insurance; custody; restrictions; priority; enforcement; discharge; representations; default; cross-border. Common gaps: just "mortgage"; unclear description; narrow debt scope; no registration; no insurance; free transfer; unclear priority; no enforcement procedure; no discharge; missing representations.
| Clause | What to write | Evidence | Common gap |
|---|---|---|---|
| Type | Mortgage/pledge/guarantee | Contract | Vague |
| Description | Name/number/quantity/location/registration number | List/registration | Unclear |
| Debt scope | Price/liquidated damages/compensation/expenses | Contract | Too narrow |
| Registration | Who/when/cost/change/discharge | Registration record | Not registered |
| Insurance | Cover/beneficiary/sum insured/renewal | Policy | Missing |
| Custody/use | Location/conditions/maintenance/stock count | Agreement | Unclear |
| Restrictions | Transfer/re-mortgage/lease/disposal | Clause | No restriction |
| Priority | Ranking/no hindrance | Registration/clause | Unclear |
| Enforcement | Default/procedure/auction/deficiency | Clause | None |
| Release/discharge | Payment/release/discharge | Record | No discharge |
| Representations/default | Title/no prior/cross-default | Clause | Missing |
| Cross-border | Law/tax/enforcement | Opinion | Undecided |
The clause list is editorial and is not a contract template or legal advice; legal/finance review before signing.
How should registration and priority be checked?
A real-property mortgage is created by registration; a movable-property mortgage is created when the contract takes effect but, without registration, cannot oppose a good-faith third party; IP and receivables pledges are created by registration; account/deposit/equity pledges follow their registration/control rules. Registration should describe the collateral/right, secured scope, term and parties; changes/extensions/discharges must be timely; the buyer should search registrations/prior rights/seizures. Priority depends on registration time/rules and the purchase-money super-priority (Civil Code Article 416: where a movable-property mortgage secures a principal debt that is the price of the mortgaged property and is registered within 10 days of delivery, it ranks ahead of other security holders except a lienholder); signing first does not mean priority.
Acceptance checks: registration type; timing; description; secured scope; term; change/discharge; search; priority; purchase-money super-priority; evidence. Common gaps: no registration where required; too-generic description; unclear scope/term; no prior search; assuming signing first gives priority; no discharge; no cross-border registration.
| Item | What to confirm | Evidence | Common gap |
|---|---|---|---|
| Registration type | Mortgage/pledge/guarantee | Registration | Not registered |
| Timing | Contract/delivery/registration | Timestamp | Signed first |
| Description | Collateral/right/registration number | Registration content | Too generic |
| Scope/term | Debt/term | Registration | Unclear |
| Change/discharge | Extension/release/discharge | Record | Not discharged |
| Search | Prior rights/seizure | Search result | Not searched |
| Priority | Ranking/super-priority | Registration/rules | Misjudged |
| Cross-border | Local registration/enforcement | Opinion | Not done |
Registration/priority is editorial; the Civil Code, the security-system interpretation, registration rules and court findings control.
How should default and enforcement of the security interest proceed?
First check the contract/security type: a movable mortgage/pledge may be enforced by agreed valuation/auction/sale; if agreement fails, use the Civil Procedure Law procedure for enforcing a security interest or litigation; real property/right pledges follow registration/enforcement rules; receivables require notice to the debtor and control of collections; IP requires realising licence/transfer value; a third-party guarantee follows the guarantee type/period. Before enforcement, confirm the debt is due/defaulted, the collateral/right exists, priority, and seizures/leases/third-party rights; after enforcement, pursue any deficiency and return any surplus. Do not self-help seize or dispose of collateral — it risks infringement and procedural defects.
Acceptance checks: default; maturity; negotiation; enforcement procedure; auction/sale; priority; third-party rights; deficiency/surplus; cross-border; evidence. Common gaps: disposing before maturity; self-help seizure; no notice; misjudged priority; third-party rights; no pursuit of deficiency; no return of surplus.
| Step | What to do | Evidence | Common gap |
|---|---|---|---|
| Default/maturity | Confirm debt/default | Contract/reconciliation | Not due |
| Negotiation | Valuation/auction/sale | Minutes | No record |
| Enforcement procedure | Security-interest procedure/litigation | Ruling/judgment | Self-help |
| Auction/sale | Public/reasonable price | Transaction/invoice | Low price |
| Priority/third parties | Ranking/lease/seizure | Search/registration | Misjudged |
| Deficiency/surplus | Pursue/return | Reconciliation | Not handled |
| Cross-border | Local procedure/enforcement | Opinion | Not assessed |
Enforcement procedure is editorial; the Civil Code, Civil Procedure Law and court procedure control.
How should release, discharge and discharge be managed?
After the debt is paid, the contract ends or the security is replaced, release the security, discharge the registration, return the collateral/right and notify the insurer/registry/third parties; keep payment/reconciliation/release agreements/discharge receipts/return confirmations. Failing to discharge leaves an encumbrance that affects the supplier's financing/resale/cooperation and may expose the buyer to claims. When replacing security, "register the new before releasing the old" or do both simultaneously to avoid a gap; cross-border releases follow local registration/discharge procedures.
Acceptance checks: payment; release agreement; discharge; return; notice; replacement; evidence; cross-border. Common gaps: paid but not discharged; no release agreement; collateral not returned; insurer not notified; replacement gap; no cross-border discharge.
| Item | What to confirm | Evidence | Common gap |
|---|---|---|---|
| Payment | Debt settled/reconciled | Reconciliation/payment | Unclear |
| Release agreement | Release/return | Agreement | None |
| Discharge | Registration discharged | Receipt | Not discharged |
| Return | Collateral/right | Handover/confirmation | Not returned |
| Notice | Insurer/registry/third parties | Notice record | None |
| Replacement | New before old/simultaneous | New registration | Gap |
| Cross-border | Local discharge | Opinion/receipt | Not done |
Release/discharge is editorial; registration rules, the contract and local law control.
What are the common pitfalls?
High risk: only "provides security"; unclear collateral description; movable mortgage not registered; receivables/IP not registered; no search for prior mortgages/seizures; unclear insurance beneficiary; collateral sold or re-mortgaged; misjudged priority; self-help enforcement; no discharge after payment; no cross-border registration/assessment; overvaluation; no monitoring/stock count. Check each in the contract/registration/due diligence/ledger.
Acceptance checks: type; description; registration; prior rights; insurance; disposal; priority; enforcement; discharge; cross-border; valuation; monitoring. Common gap: any of the above missing.
| Pitfall | Consequence | Evidence | Common gap |
|---|---|---|---|
| Only "security" | Type/registration unclear | Contract | Vague |
| Not registered | Cannot oppose/priority | Registration | Unregistered |
| No prior search | Ranking/seizure | Search | Not searched |
| No insurance | Uncovered loss | Policy | None |
| Free disposal | Collateral lost | Clause | No restriction |
| Priority misjudged | Insufficient recovery | Registration/rules | Misjudged |
| Self-help disposal | Infringement/procedural defect | Procedure | Self-help |
| No discharge | Encumbrance | Receipt | None |
| Cross-border not assessed | Unenforceable | Opinion | None |
The risk list is editorial; the law, contract, registration and court findings control.
How should the website page be written, and what must not be published?
Suggested sections: (1) security types/use cases; (2) due diligence/registration/priority principles; (3) contract points; (4) default/enforcement/release process; (5) contact/version/update date. The public page explains "principles and process" and does not publish specific collateral/serial numbers/valuations/registration numbers/supplier financials/litigation/seizures/contract prices; after login, collateral materials/status can be submitted/checked.
The English page should use consistent terms (mortgage, pledge, receivable pledge, IP pledge, account pledge, equity pledge, registration, priority, security interest, enforcement, release, perfection) and state the search date. It can link to the guarantee, retention-of-title and supplier financial-risk pages, but must not become a guarantee page.
| Section | What to write | Evidence | Avoid |
|---|---|---|---|
| Type/use case | Mortgage/pledge/guarantee | Policy | Only "security" |
| Due diligence/registration | Title/prior/registration/priority | Search/registration | No registration |
| Contract points | Description/scope/insurance/disposal/enforcement | Template | No clauses |
| Enforcement/release | Procedure/auction/discharge | Process | Self-help |
| Public boundary | No collateral/valuation/registration numbers | Access control | Publish all |
| Contact | Finance/legal window | Page | Personal mobile |
| Version | Update date/owner | Page | No owner |
The page structure is editorial; public statements must be true and verifiable, and the law, contract, registration and company policy control.
What should not be written?
High-risk statements: "the supplier providing security is enough" (type/registration/priority unclear); "a signed mortgage contract gives priority" (unregistered movable mortgage cannot oppose; real-property mortgage is created by registration); "receivables/IP need no registration" (pledge created by registration); "the collateral can be sold freely" (disposal restrictions/third parties); "on default we can tow the equipment" (procedure required; no self-help); "payment automatically discharges" (discharge/release must be done); "publish collateral/valuation/registration numbers" (sensitive).
A safer wording: "This contract requires [security type], collateral/right [description], securing [scope], registered in [registry] on [timing], insurance [who/beneficiary/sum insured], no [transfer/re-mortgage/lease] without consent, default handled by [negotiation/enforcement procedure/litigation], and on payment [release/discharge/return]; the law, contract, registration and court findings control."
Go-live acceptance checklist
Ten checks: type/use case; due diligence/title; contract clauses; registration/search; priority/super-priority; insurance/custody; default/enforcement; release/discharge; cross-border; public boundary/version. Each needs an owner, evidence and review date. The pass standard is not "the page says security is provided" but that procurement, finance and legal can use the page to choose a type, check title/prior rights, register, verify priority, enforce and discharge.
Before go-live, run one real (redacted) security through: type → due diligence → contract → registration → search → priority → default/enforcement → payment/discharge. Then simulate a collateral resale/seizure and a cross-border security to see whether registration/priority/enforcement work. Any step that fails is a gap in the page or the policy.
| Check | Pass standard | Evidence | If failed |
|---|---|---|---|
| Type/use case | Mortgage/pledge/guarantee | Policy | Add type |
| Due diligence/title | Title/prior/seizure | Search/documents | Add diligence |
| Contract clauses | Description/scope/insurance/disposal/enforcement | Contract | Amend contract |
| Registration/search | Registration/timing/description/change | Registration | Register |
| Priority | Ranking/super-priority | Registration/rules | Recheck |
| Insurance/custody | Cover/beneficiary/stock count | Policy/record | Add insurance |
| Default/enforcement | Procedure/auction/deficiency | Process | Add process |
| Release/discharge | Payment/discharge/return | Receipt | Discharge |
| Cross-border | Law/registration/enforcement | Opinion | Assess |
| Public boundary | No collateral/valuation/registration numbers | Access control | Take down |
The acceptance list is editorial; the law, contract, registration and company policy control.
Who should read it, who should not, and what decisions does it support?
For procurement, finance, legal, internal-control, supply-chain and website teams at equipment, electronics, automotive-parts, medical-device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby; also for companies whose suppliers offer equipment/receivables/IP/equity/real-property security, or that face "security not registered, priority misjudged, collateral lost, discharge unclear". Not for teams that do not use security or sign procurement contracts, or that want one page to replace legal/security/financial advice.
Read it if: building a security page; only writing "provides security"; not registering; not searching prior rights; no insurance; free disposal; misjudged priority; self-help enforcement; no discharge after payment; no cross-border assessment. Not suitable if: treating "signed contract" as "priority"; treating "security" as "guarantee"; treating "payment" as "automatic discharge"; publishing collateral/valuation/registration numbers. Supports: type, due diligence, contract, registration, priority, enforcement, discharge and page wording self-checks.
FAQ
How is a supplier mortgage/pledge different from a guarantee or retention of title?
A mortgage/pledge is where the supplier provides equipment, receivables, IP, equity or real property as security for a debt, and the buyer has priority over the collateral/right; a guarantee is third-party credit from a bank/insurer/guarantor, claimed against documents; retention of title keeps ownership with the seller until payment, with registration opposition and repossession. They can be combined but cannot replace each other.
Is an unregistered movable-property mortgage valid?
A movable-property mortgage is created when the contract takes effect, but Civil Code Article 403 provides that without registration it cannot oppose a good-faith third party; it may be defeated by a good-faith buyer/security holder/seizing creditor. A real-property mortgage is created by registration; IP/receivables pledges are created by registration. To have priority/opposition, register by type.
Where are receivables/IP pledges registered?
Receivables pledges are generally registered with the unified movable-property financing registration and publication system / the credit-reference centre receivables pledge registration system; IP (trademark/patent/copyright property rights) pledges follow the rules of the National Intellectual Property Administration / copyright registration bodies; local rules control. The registration should describe the right/registration number/secured scope/term, and prior rights should be searched.
What if the collateral is resold or seized?
Look at the contract/registration/whether the third party is in good faith: a registered movable mortgage can oppose a good-faith third party; an unregistered one may not. On discovery of resale/seizure, search/preserve/notify/demand immediately and assess enforcement/litigation; the contract should restrict transfer/re-mortgage/lease and provide for default. Do not seize or dispose of it yourself — it risks infringement and procedural defects.
How does the supplier's default lead to enforcement?
First confirm the debt is due/defaulted, the collateral exists and priority; negotiate valuation/auction/sale; if that fails, use the Civil Procedure Law security-interest enforcement procedure or litigation; for receivables, notify the debtor and control collections; for IP, realise licence/transfer value; pursue any deficiency and return any surplus. Cross-border matters follow local procedure/lawyers.
Should the website publish collateral/registration information?
Usually not specific collateral/serial numbers/valuations/registration numbers, supplier financials/litigation/seizures, contract prices or pending cases. The public page can explain security types, due-diligence/registration principles, enforcement/discharge process and a contact window; detailed materials are provided after login/under control.
One-sentence takeaway
The supplier mortgage/pledge security page on a Changzhou manufacturer's website is not about "providing security"; it is about turning type, due diligence/title, contract, registration/search, priority/super-priority, insurance/custody, default/enforcement, release/discharge and cross-border into a checkable list, so procurement, finance and legal can choose a type, check title/prior rights, register, verify priority, enforce and discharge.
Research method and limitations
This article is a summary of public rules and page method, not legal, security or financial advice. It uses no unpublished collateral, valuation, registration, supplier financial or litigation data; the types, tables and acceptance items are editorial and not legal conclusions. Civil Code Articles 394 (mortgage), 395 (mortgageable property), 402 (real-property mortgage registration), 403 (movable mortgage registration opposition), 425 (pledge), 440 (pledgeable rights), 444/445 (IP/receivables pledge registration) and 416 (purchase-money super-priority); the Supreme People's Court interpretation on the security system; the Civil Procedure Law security-interest enforcement procedure/preservation; the law, contract, registration and court findings control. This article does not decide whether any specific security/priority/enforcement is valid; companies should review item by item.
Sources and basis
Current to 2026-11-08; the official pages below control.
- Civil Code of the People's Republic of China: Supreme People's Court. Mortgage (Article 394, 395), real-property mortgage registration (Article 402), movable mortgage registration opposition (Article 403), pledge (Article 425), pledgeable rights (Article 440), IP/receivables pledge registration (Articles 444, 445), purchase-money super-priority (Article 416).
- Supreme People's Court interpretation on applying the security system of the Civil Code (Fa Shi [2020] No. 28, effective 1 January 2021): National Laws and Regulations Database. Security contracts, registration, priority and enforcement.
- Civil Procedure Law of the People's Republic of China (amended 1 September 2023, effective 1 January 2024): National Laws and Regulations Database. Security-interest enforcement procedure/preservation.