Direct answer: A procurement fraud and bid-rigging detection page is not a "catch the mole/catch the cartel" slogan. The page should state: fraud types (bid rigging/cover bidding, bid information leakage, kickbacks/conflicts of interest, fake suppliers, order splitting, quantity/invoice fraud); red flags (same author/IP/MAC, unusual similarity, price patterns, deposit from the same account, overlapping contacts/addresses/accounts, same winner, frequent changes/splitting); how to analyse data (supplier master, bid metadata, pricing patterns, orders/invoices, employee links); how to investigate (intake, evidence preservation, confidentiality, interviews, supplier response, legal/HR); how to dispose (bid rejection, termination, claims, debarment, referral, control remediation); governance (segregation, rotation, recusal, whistleblowing, training); public boundary. On the rules: the Tendering and Bidding Law Article 32 prohibits bidder collusion, collusion with the tenderee and bribery; Article 53 provides invalid award, fines and disqualification; the Implementing Regulations Articles 39–41 list collusion and deemed-collusion situations (same preparer, same bid handler, same project member, unusually identical documents/price patterns, mixed documents, deposit from the same account); MOF Internal Control Application Guideline No. 7 (Procurement) requires segregation of duties, authorisation/approval, supplier selection and records. This article is current to 2026-11-10 and is a summary of public rules and page method, not legal/audit/discipline advice; the company's policy, applicable project and legal judgment control.
This article is for procurement, tendering, legal, internal audit, finance, quality 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 procurement fraud and bid-rigging detection page. The usual gap is "only a whistleblowing hotline, no red flags, no data, no investigation procedure, red flags treated as conclusions, no closed-loop disposition, public accusations against suppliers", ending with a page that only says "clean procurement, transparent tendering", while abnormal bids/audits/litigation still disagree.
A red flag is not a conclusion: same author/IP, price patterns and same deposit account are investigation leads, not guilt. Investigations need confidentiality, evidence preservation and supplier response. Disposition needs bid rejection/contract/claims/debarment/referral/remediation closed-loop, and the public page explains method without naming names.
How does this page relate to supplier onboarding/debarment, related-party, tendering, negotiation, internal audit and contract-claim pages?
The fraud/bid-rigging page answers "how to identify red flags, investigate and dispose"; the supplier debarment/sanctions screening page answers "how to screen lists before/during cooperation"; the related-party page answers "how related suppliers are disclosed/approved"; the tendering/e-tendering page answers "process/platform/bid opening and evaluation"; the negotiation page answers "pre-deal preparation/concessions"; the procurement internal audit page answers "audit plan/evidence/remediation"; the contract/claim page answers "breach/compensation". The fraud page is the main page for "risk identification and investigation/disposition" and cannot be replaced by a debarment or audit page.
Common breaks: hotline only; no red-flag list; no data analysis; leads treated as conclusions; no procedure/confidentiality; supplier has no response; disposition not closed; public naming; controls not remediated. The page separates "types—red flags—data—investigation—disposition—governance—boundary" so procurement/tendering/legal/audit/finance/HR share one vocabulary.
| Page | Question it answers | Key content | Cannot replace |
|---|---|---|---|
| Fraud/bid-rigging | How to identify/investigate/dispose | Red flags, data, evidence, disposition | Debarment/audit |
| Debarment/sanctions | How to screen lists before/during | Lists, screening, hits | Behaviour analysis |
| Related party | How related suppliers are disclosed/approved | Relationship, pricing, approval | Collusion investigation |
| Tendering/e-tendering | Process/platform/opening/evaluation | Notice, bids, evaluation | Fraud investigation |
| Negotiation | Preparation/concessions/contract | BATNA, cost, concessions | Compliance investigation |
| Internal audit | Audit plan/evidence/remediation | Sampling, testing, remediation | Special investigation |
| Contract/claims | Breach/compensation/disputes | Terms, claims, arbitration | Fraud detection |
Page relationships are editorial; the company's policy, applicable project and legal judgment control.
What fraud types exist, and how should red flags be listed?
At minimum: bid rigging/cover bidding, tenderee-bidder collusion/information leakage, kickbacks/gifts/conflicts of interest, fake suppliers/shell companies, order splitting to avoid approval/tendering, price/quantity/invoice fraud, acceptance/warranty fraud, supplier bank-account change fraud. Red flags at minimum: bid documents by the same author/IP/MAC/printer, unusually identical typos/formatting, regular price differences, deposit from the same account, overlapping contacts/addresses/phones/emails/accounts, same person handling bids, same project members, same winner/cover bidders, frequent withdrawal after bidding, single bidder, frequent changes/splitting, last-minute bank-account change, employee-supplier links. Classify strong/medium/weak and state verification methods; a red flag is not automatically illegal.
Acceptance checks: type list; red-flag grading; verification; tender/non-tender applicability; false-positive handling; records. Common gaps: kickbacks only; no grading; leads as conclusions; no tender/non-tender distinction; no verification.
| Type | Red flag/signal | Verification | Common gap |
|---|---|---|---|
| Bid rigging | Same author/IP, unusual similarity, price patterns | Metadata/comparison | Price only |
| Cover bidding | Fixed cover bidders, rotating winners, withdrawal | History pattern | No history |
| Tenderee collusion | Leaking base/evaluators, hinting price | Access/communications | No internal check |
| Kickbacks/conflicts | Gifts, relatives, investments, part-time | Declaration/interview | No declaration |
| Fake supplier | Address/account/licence anomalies, shell | Due diligence/site visit | Licence only |
| Order splitting | Splitting near thresholds, frequent small orders | Order/budget | No split check |
| Price/invoice | Abnormal price/invoice/quantity | Three-way/benchmark | Amount only |
| Account change | Last-minute change, payment urgency | Callback/verification | Change directly |
Types/red flags are editorial; tendered projects follow the Tendering and Bidding Law and regulations, and whether commercial RFQ conduct is illegal is for legal judgment.
How should data analysis be done and accepted?
Data at minimum: supplier master (name/credit code/address/phone/email/account/contact/shareholders/beneficiaries), bid metadata (author/created/modified/IP/MAC/device/printer), pricing (unit/total/discount/patterns), bid history (win/cover/withdraw/abandon), orders/invoices/payment (splitting/price/quantity/account), employees/related parties (relatives/investments/part-time). Analysis at minimum: duplicate/similarity, address/phone/email/account clustering, price correlation/patterns, win concentration, splitting thresholds, account changes, timing anomalies. Article 40 "deemed" situations are key rules for tendered projects; commercial RFQs may use the same signals for internal control, but statistical correlation is not evidence.
Acceptance checks: data sources; fields; clustering/similarity; price analysis; win concentration; splitting; account changes; false positives; access/trail. Common gaps: Excel only; no metadata; no clustering; correlation as causation; no trail; stale data.
| Data | What to check | Evidence | Common gap |
|---|---|---|---|
| Supplier master | Name/credit code/address/phone/email/account | System | Incomplete fields |
| Shareholders/beneficiaries | Equity, controller, affiliates | Registry/declaration | No look-through |
| Bid metadata | Author/created/modified/IP/MAC/device | File/log | Not retained |
| Pricing patterns | Unit/total/discount/regular differences | Quotes | Total only |
| Bid history | Win/cover/withdraw/abandon | Register | Not analysed |
| Orders/invoices | Splitting/price/quantity/account | ERP | Amount only |
| Employee links | Relatives/investments/part-time/former employer | Declaration | No declaration |
| Clustering/similarity | Address/phone/email/account/file | Analysis | Manual review |
Data analysis is editorial; the company's systems, data access and applicable rules control.
How should a suspected fraud be investigated and evidence preserved?
Investigation at minimum: intake/registration (source/time/project/supplier/person), triage (red-flag strength/value/risk), case opening/authority (legal/internal audit/discipline/HR), confidentiality (need-to-know/documents/system access), evidence preservation (originals/emails/logs/metadata/lawful recording/witness), interviews (sequence/records/response), supplier communication/response, legal assessment (tendering law/contract/criminal/competition), conclusion (facts/evidence/responsibility/recommendations), archive. Investigation is not "suspend/expose first"; avoid tipping off, evidence loss, false accusations and defamation. Tendered projects may follow bid-rejection/review rules; commercial contracts follow terms/law.
Acceptance checks: intake/registration; triage; opening/authority; confidentiality; evidence preservation; interviews/response; legal assessment; conclusion; archive; timeline. Common gaps: no registration; no authority; leaks; evidence loss; no response; prejudgment; no legal assessment.
| Step | What to write | Evidence | Common gap |
|---|---|---|---|
| Intake/registration | Source/time/project/supplier/person | Register | No registration |
| Triage | Red-flag strength/value/risk/priority | Triage form | Investigate directly |
| Opening/authority | Legal/audit/discipline/HR, scope | Authority | No authority |
| Confidentiality | Need-to-know/documents/access | Undertaking/log | Leak |
| Evidence preservation | Originals/emails/logs/metadata/witness | List | Loss |
| Interviews/response | Sequence, records, supplier response | Notes | No response |
| Legal assessment | Tendering/contract/criminal/competition | Opinion | Prejudgment |
| Conclusion/archive | Facts/evidence/responsibility/recommendations | Report | No conclusion |
Investigation procedure is editorial; the company's policy, law and applicable rules control, and it is not legal advice.
How should disposition and remediation be accepted?
Disposition at minimum: tendered projects follow rules for bid rejection/re-tendering/deposit handling/referral; contracts follow terms for termination/payment suspension/claims/chargeback; supplier debarment/restricted cooperation/remediation acceptance; internal personnel discipline/legal action; loss recovery; criminal/regulatory referral where suspected. Remediation at minimum: root-cause analysis, control deficiency, process/authority/system changes, owner/deadline, validation, review. Disposition must be "facts—rules—proportionality—approval—records", not emotional or selective enforcement; state the supplier response/appeal channel. Article 53 provides invalid award, fines and disqualification; company-side disposition still follows applicable rules/contracts/legal advice.
Acceptance checks: disposition options; rule basis; proportionality/approval; supplier response/appeal; debarment; internal action; recovery; referral; remediation; validation. Common gaps: debarment only; no recovery; no remediation; selective enforcement; no response; no records.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| Tender disposition | Rejection/re-tender/deposit/referral | Decision | Not per rules |
| Contract disposition | Termination/payment hold/claims/chargeback | Contract/letter | Debarment only |
| Supplier | Debarment/restriction/remediation acceptance | Record | No remediation |
| Internal personnel | Discipline/legal/role | Decision | No action |
| Recovery | Loss calculation/claim/litigation | Finance/legal | No recovery |
| Referral | Criminal/regulatory/materials | Record | No referral |
| Remediation | Control deficiency/process/system/owner | Plan | No remediation |
| Response/appeal | Channel/timeline/records | Record | No response |
Disposition/remediation are editorial; applicable rules, contracts, company policy and legal advice control.
How should governance, whistleblowing and prevention be accepted?
Governance at minimum: segregation of duties (requirement/procurement/tendering/evaluation/payment), authorisation/approval, rotation/mandatory leave, conflict-of-interest declaration, supplier contact records, access/system logs, tender document/base confidentiality, evaluator management, contract/payment review. Whistleblowing at minimum: multiple channels (phone/email/platform/box), anonymity, protection/anti-retaliation, intake/feedback, records, training. Prevention at minimum: supplier due diligence, related-party look-through, price benchmarks, splitting monitoring, bank-account change verification, periodic audit, case review. Guideline No. 7 requires segregation of incompatible duties, authorisation/approval and records; governance should close the loop from detection to investigation, disposition, remediation and review.
Acceptance checks: segregation; authority; rotation; conflict declaration; confidentiality; whistleblowing channels/protection; training; monitoring; audit; review. Common gaps: one person end-to-end; no rotation; no protection; no training; no monitoring; no review.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| Segregation | Requirement/procurement/tendering/evaluation/payment | Policy | One person |
| Authorisation | Thresholds/sign-off/overreach | Approval | Beyond authority |
| Rotation/leave | Key-role rotation/mandatory leave | Record | No rotation |
| Conflict declaration | Relatives/investments/part-time/gifts | Declaration | No declaration |
| Confidentiality | Base/evaluators/quotes/access | Policy | Leak |
| Whistleblowing | Channels/anonymity/protection/feedback | Record | No protection |
| Monitoring/audit | Splitting/accounts/price/concentration | Report | No monitoring |
| Training/review | Annual training/cases/remediation | Record | No training |
Governance/whistleblowing are editorial; the company's integrity policy, applicable law and authority control.
How should the website page be written, and what must not be published?
Suggested sections: (1) fraud types/red-flag grading; (2) data/analysis; (3) investigation procedure/evidence/response; (4) disposition/remediation; (5) governance/whistleblowing/prevention; (6) contact window/update date. The public page explains "types, red flags, investigation principles, disposition framework, whistleblowing channels, boundary" and does not publish specific suppliers/projects/people, investigation details, evidence, penalties, contracts/prices, system screenshots or undisclosed allegations. The English page should use consistent terms (procurement fraud, bid rigging, collusion, red flags, whistleblowing, conflict of interest, investigation, evidence preservation, debarment, remediation) and state the cut-off date.
Do not turn the page into "report and win a reward/catch the mole", and do not name or hint that a supplier rigged bids on the public page; unproven allegations carry reputational/legal risk. The page should let procurement/tendering/legal/audit/HR judge "what signals to watch, how to investigate, how to dispose, how to prevent", while protecting the investigation and suppliers' lawful rights.
Go-live acceptance checklist
Ten checks: types/red flags; data/analysis; investigation procedure; evidence preservation; response/confidentiality; disposition/recovery; remediation/review; governance/whistleblowing; training/audit; public boundary. Each needs evidence and a review date. The pass standard is not "there is a hotline", but that procurement/tendering/legal/audit/HR can judge lead strength, investigation steps, disposition basis and remediation closure, without treating red flags as conclusions.
Before go-live, run a tabletop exercise on a real (redacted) project: red-flag detection → registration/triage → case opening → evidence preservation → interview/response → legal assessment → disposition → remediation → review, simulating "false positive", "employee involved" and "supplier threatens litigation", to see whether the page and process work.
| Check | Pass standard | Evidence | If failed |
|---|---|---|---|
| Types/red flags | Types, grading, verification, false positives | List | Add red flags |
| Data/analysis | Master/metadata/pricing/history/clustering | Report | Add data |
| Investigation | Intake/triage/opening/authority/timeline | Policy | Add procedure |
| Evidence/confidentiality | Preservation/list/access/need-to-know | Record | Add preservation |
| Response | Supplier/employee response, appeal | Notes | Add response |
| Disposition/recovery | Rejection/contract/debarment/recovery/referral | Decision | Add disposition |
| Remediation/review | Control deficiency/owner/validation | Plan | Add remediation |
| Governance/whistleblowing | Segregation/rotation/declaration/channel/protection | Policy | Add governance |
| Training/audit | Annual training/monitoring/audit | Record | Add training |
| Public boundary | No naming/evidence/results | Page/permissions | Take down |
The acceptance list is editorial; the company's policy, applicable law and legal judgment control.
Who should read it, who should not, and what decisions does it support?
For procurement, tendering, legal, internal audit, finance, quality and website teams at equipment, electronics, automotive-parts, medical-device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby; also for companies handling "hotline only, unclear red flags, no data, no investigation procedure, no closed-loop disposition, public naming". Not for teams without procurement fraud/bid-rigging management, or that want one page to replace legal/audit/discipline advice.
Read it if: building a fraud/bid-rigging page; only "clean procurement"; red flags not graded; no data; no investigation procedure; disposition not closed; public naming. Not suitable if: treating "red flag" as "conclusion"; "investigation" as "conviction"; "whistleblowing" as "revenge"; "page" as "legal opinion/penalty decision". Supports: types/red flags, data/analysis, investigation/evidence, disposition/remediation, governance/whistleblowing and public-boundary self-checks.
FAQ
What is the difference between the fraud page, the debarment/sanctions page and the related-party page?
The fraud page covers "identifying red flags, investigating, disposing and remediating"; the debarment/sanctions page covers "screening lists before/during cooperation"; the related-party page covers "disclosure, pricing and approval of related suppliers". They complement each other: debarment is entry screening, related-party is conflict disclosure, and the fraud page is behaviour analysis and investigation/disposition; none can replace another.
What counts as bid-rigging red flags?
For tendered projects, focus on Implementing Regulations Articles 39–41: bidders agreeing prices/winner/withdrawal, same-group coordination; bid documents prepared by the same entity/person, same person handling bids, same project members, unusually identical documents or regular price differences, mixed documents, deposit from the same account; tenderee leaking the base/evaluators or hinting price changes. Commercial RFQs may use the same signals for internal control, but legality is for legal judgment; a red flag is not a conclusion.
How should data be checked (same IP/author/deposit account)?
Build supplier master (name/credit code/address/phone/email/account/shareholders/beneficiaries), bid metadata (author/created/modified/IP/MAC/device), pricing, bid history, orders/invoices/payment and employee links; run duplicate/similarity, address/phone/email/account clustering, price patterns, win concentration, splitting thresholds and account-change analysis. Preserve original files and logs, control access and keep trails; statistical correlation is not evidence by itself.
How should a suspected fraud be investigated and evidence preserved?
Register source/time/project/supplier/person → triage red-flag strength/value/risk → case opening/authority (legal/internal audit/discipline/HR) → confidentiality → preserve originals/emails/logs/metadata → interviews/supplier response → legal assessment → conclusion/archive. Avoid tipping off, evidence loss, false accusations and defamation; tendered projects follow bid-rejection/review rules, commercial contracts follow terms/law. Procedure is subject to company policy and law.
Should bidding/payment/contracts be stopped during an investigation?
Decide by risk/rules/contract, not automatically: tendered projects may pause/reject/review per rules; contracts may pause payment/terminate/claim per terms; assess supply continuity, employee/customer impact, evidence risk and legal advice. Disposition needs basis, approval, proportionality and records, and the supplier needs a response/appeal channel.
How should suppliers and internal personnel be dealt with?
Suppliers: bid rejection/re-tendering/deposit/contract termination/claims/debarment/restricted cooperation/remediation acceptance/referral; internal personnel: discipline/role/legal action; loss recovery; criminal referral where suspected. Disposition should follow "facts—rules—proportionality—approval—records" and avoid selective enforcement; Article 53 provides invalid award, fines and disqualification, while company-side action follows applicable rules/contracts/legal advice.
Should the website publish fraud/investigation information?
Usually not specific suppliers/projects/people, investigation details, evidence, penalties, contracts/prices, system screenshots or undisclosed allegations; it can publish fraud types, red flags, investigation principles, disposition framework, whistleblowing channels and protection policy, and update date. The goal is to let customers/suppliers understand the integrity and investigation mechanism, not to expose or prejudge guilt.
One-sentence takeaway
The procurement fraud and bid-rigging detection page on a Changzhou manufacturer's website is not about "catching the mole"; it is about turning fraud types/red-flag grading, data/analysis, investigation/evidence/response, disposition/recovery/remediation, governance/whistleblowing/prevention and public boundaries into a checkable list, so procurement/tendering/legal/audit/HR can judge lead strength, investigation steps, disposition basis and remediation closure without treating red flags as conclusions.
Research method and limitations
This article is a summary of public rules and page method, not legal/audit/discipline advice. It uses no unpublished company suppliers/projects/people, investigation details, evidence, penalties, contracts/prices, system screenshots or undisclosed allegations; the tables and acceptance items are editorial and not legal/audit/discipline conclusions. The Tendering and Bidding Law, its Implementing Regulations and MOF Internal Control Application Guideline No. 7 (Procurement) are public sources; the company's policy, applicable project, contracts and legal judgment control. This article does not decide whether any specific supplier/conduct constitutes collusion or fraud, and does not promise "zero fraud"; companies should handle each case based on project, evidence and law.
Sources and basis
Current to 2026-11-10; the official pages below control.
- Tendering and Bidding Law of the PRC: Hangzhou Xihu District Government. Article 32: prohibits bidder collusion, collusion with the tenderee and bribery; Article 53: invalid award, fines and disqualification; used for tendered-project red lines.
- Implementing Regulations of the Tendering and Bidding Law (State Council Order No. 613): The State Council of China. Articles 39–41: collusion situations and deemed situations (same preparer, same bid handler, same project member, unusually identical documents/price patterns, mixed documents, deposit from the same account); used for the red-flag list.
- MOF Internal Control Application Guideline No. 7 — Procurement (Cai Kuai [2010] No. 11): Linyi Finance Bureau. Segregation of duties, authorisation/approval, supplier selection, acceptance, payment and records; used for governance/prevention.