Direct answer: A procurement abnormal-invoice and input-VAT risk page is not "check whether the invoice is genuine". The page should state: which invoices are listed as abnormal vouchers (lost/stolen tax-control devices, non-normal taxpayers, audit mismatches/missing/void invoices, suspected false invoicing, absconded businesses); the tax treatment (undeducted input VAT temporarily not allowed; already deducted input VAT transferred out; export refund suspended/recovered; A-grade taxpayers may request verification within 10 working days; objections may be verified); business evidence (contract/order/goods receipt/acceptance/logistics/payment/invoice "three-stream consistency"); supplier recovery/contract terms (quality/compliance/indemnity/payment hold/termination); prevention (supplier onboarding, invoice verification, payment controls, training, metrics); public boundary. On the rules: the State Taxation Administration Announcement No. 38 of 2019 lists abnormal vouchers and treatment; the Invoice Management Measures (2023 revision) state that non-compliant invoices cannot be used for reimbursement and may be refused, and prohibit false invoicing, lending/transferring invoices, and using other documents in place of invoices; MOF Internal Control Application Guideline No. 7 (Procurement) requires supplier selection, contracts, acceptance, payment and records. This article is current to 2026-11-10 and is a summary of public rules and page method, not tax/legal/audit advice; the tax authority's determination, the company's tax treatment and contracts control.
This article is for procurement, finance/tax, legal, internal audit, 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 abnormal-invoice and input-VAT risk page. The usual gap is "genuineness only, no business reality, reacting only when the abnormal notice arrives, no budget for transfer-out, supplier does not indemnify, no contract clause, three streams inconsistent", ending with a page that only says "invoice compliance, tax risk controlled", while back-taxes/late fees/supplier recovery still disagree.
An abnormal voucher is not a synonym for a fake invoice: it is a tax-risk signal, and treatment depends on the determination and verification. Business reality rests on the contract/order/receipt/logistics/payment/invoice evidence chain, not the invoice face. Contract terms should require supplier indemnity and cooperation; on an alert, hold payment first, then verify, then recover.
How does this page relate to three-way match, payment/settlement, supplier screening, contract claims, archive and tax pages?
The abnormal-invoice/input-VAT page answers "which invoices are risky, how to handle, recover and prevent"; the three-way match/reconciliation page answers "how order/receipt/invoice/red-letter are matched"; the payment/settlement page answers "terms/documents/payment"; the supplier screening page answers "lists/credit/sanctions"; the contract/claim page answers "breach/indemnity/termination"; the archive page answers "retention/access"; the tax page answers "filing/tax burden". The abnormal-invoice page is the main page for "invoice risk and input-VAT treatment" and cannot be replaced by a three-way match page.
Common breaks: genuineness only; no business reality; looking for the contract only after an alert; no budget for transfer-out; supplier does not cooperate/indemnify; no contract clause; three streams inconsistent; missing archive. The page separates "types—evidence—handling—recovery—prevention—boundary" so procurement/finance-tax/legal/audit/quality share one vocabulary.
| Page | Question it answers | Key content | Cannot replace |
|---|---|---|---|
| Abnormal invoice/input VAT | Risk/handling/recovery/prevention | Types, evidence, transfer-out, verification | Three-way match |
| Three-way match | How order/receipt/invoice match | Quantity, price, red-letter, variance | Tax treatment |
| Payment/settlement | Terms/documents/payment | Terms, approval, reconciliation | Invoice risk |
| Supplier screening | Lists/credit/sanctions | Lists, hits, review | Invoice verification |
| Contract/claims | Breach/indemnity/termination | Terms, claims, disputes | Tax determination |
| Archive | Retention/access | Retention, archive, borrow | Risk handling |
| Tax filing | Filing/tax burden | Returns, deduction, burden | Business evidence |
Page relationships are editorial; the tax authority's determination, the company's tax treatment and contracts control.
Which invoices are listed as abnormal vouchers, and what are the business red flags?
Under Announcement No. 38, special VAT invoices listed as abnormal include at least: lost/stolen tax-control devices with uninvoiced or uploaded-not-issued invoices; non-normal taxpayers failing to declare/pay; audit comparison "mismatch/missing/void"; big-data analysis indicating suspected false invoicing/unpaid consumption tax; invoices from absconded (lost-contact) businesses meeting Article 2(1) of Announcement No. 76 of 2016. There is also a derivative situation where abnormal input VAT is ≥70% of all special-invoice input VAT in the same period and exceeds RMB 50,000. Business red flags: newly established/odd-address supplier, account inconsistent with contract, price far from market, invoice without logistics/receipt, fund round-tripping, invoice items inconsistent with contract, frequent void/red-letter, supplier lost contact, multiple entities under the same controller. A red flag is not a conclusion and must be verified.
Acceptance checks: abnormal types; derivative situation; business red flags; verification; false positives; records. Common gaps: lost-contact only; no ratio/value; red flag as conclusion; no verification; no records.
| Type | What to write | Evidence | Common gap |
|---|---|---|---|
| Tax-control device | Lost/stolen, uninvoiced/not uploaded | Tax notice | Not monitored |
| Non-normal taxpayer | No filing/payment | System | Licence only |
| Audit comparison | Mismatch/missing/void | Invoice system | Not checked |
| Suspected false invoicing | Big data/unpaid consumption tax | Tax notice | Treated as conclusion |
| Absconded business | Announcement No. 76 situation | Notice/system | Not tracked |
| Derivative situation | Abnormal input ≥70% and >RMB 50k | Calculation | No ratio |
| Business red flags | Address/account/price/logistics/round-trip | Due diligence | Invoice only |
| Verification/false positive | Method, records, conclusion | Record | No verification |
Abnormal types follow Announcement No. 38 and the tax authority's determination; business red flags are editorial and not a false-invoicing conclusion.
How should business reality and "three-stream consistency" evidence be accepted?
Evidence at minimum: contract/order (parties, items, quantity, price, delivery), goods receipt/acceptance (receiver, date, quantity, inspection), logistics/transport (waybill, plate, signature), payment (account consistent with contract/invoice, bank receipt), invoice (title/tax ID/items/amount/tax rate), communication (RFQ/change/reconciliation). It must answer "who bought, what, where the goods went, who received, who was paid, who invoiced". Three-stream consistency is not mechanically "the same three names"; it is real business, consistent parties, matching amounts and reasonable explanations for differences; entrusted payment/collection needs authorisation/agreement. Guideline No. 7 requires contracts, acceptance, payment and records to be consistent.
Acceptance checks: contract/order; receipt/acceptance; logistics; payment; invoice; communication; variance explanation; entrusted-payment authorisation; archive. Common gaps: invoice only; no receipt; no logistics; payment to a third party without authorisation; invoice/goods mismatch; unexplained variance.
| Evidence | What to write | Evidence | Common gap |
|---|---|---|---|
| Contract/order | Parties/items/quantity/price/delivery | Contract/PO | No contract |
| Receipt/acceptance | Receiver/date/quantity/inspection | Receipt | No receipt |
| Logistics | Waybill/plate/signature | Waybill | No logistics |
| Payment | Matching account/receipt | Bank receipt | Third-party payment |
| Invoice | Title/tax ID/items/amount/tax rate | Invoice | Invoice/goods mismatch |
| Communication | RFQ/change/reconciliation | Email/minutes | No record |
| Variance explanation | Quantity/price/discount/freight | Note | No explanation |
| Entrusted payment | Authorisation/agreement/relationship | Authorisation | No authorisation |
The evidence chain is editorial; business facts, contracts, tax requirements and the authority's determination control.
How should an abnormal voucher be handled and accepted?
Handling at minimum: receive the tax notice/system alert → register (invoice number/supplier/amount/tax/period) → hold payment/suspend deduction → business verification (contract/receipt/logistics/payment/supplier contact) → tax treatment (undeducted temporarily not allowed; already deducted transferred out unless otherwise provided; export refund suspended/recovered per rules) → A-grade taxpayers may request verification within 10 working days of the notice → objection verification with the competent tax authority → assess back-tax/late fees/penalties → supplier recovery → archive. Keep notices/calculations/filings/communications/verification results; do not "split/replace invoices or abscond" to circumvent. Specific treatment is subject to the tax authority's determination and tax adviser's advice.
Acceptance checks: registration; payment/deduction hold; business verification; tax treatment; A-grade 10 days; objection; back-tax/late fees; recovery; archive. Common gaps: no registration; continue paying; transfer-out without budget; miss the 10 days; no verification; no recovery; no archive.
| Step | What to write | Evidence | Common gap |
|---|---|---|---|
| Receive/register | Invoice/supplier/amount/tax/period | Register | No registration |
| Payment/deduction hold | Freeze, approval, notice | System | Keep paying |
| Business verification | Contract/receipt/logistics/payment/contact | Evidence | Ask supplier only |
| Tax treatment | Undeducted/transfer-out/refund suspension | Filing | Wrong treatment |
| A-grade 10 days | Verification request/timeline | Request | Missed |
| Objection verification | Request/materials/result | Record | No request |
| Back-tax/late fees | Calculation/budget/responsibility | Finance | No budget |
| Recovery/archive | Claim/chargeback/archive | Contract/archive | No recovery |
Handling steps are editorial; Announcement No. 38, the tax authority's determination and the company's tax treatment control, and this is not tax advice.
How should supplier recovery and contract clauses be accepted?
The contract should at least state: the supplier guarantees invoices are genuine/lawful/consistent with the actual business; cooperate with tax verification/provide documents; indemnify back-tax, late fees, penalties and losses caused by the supplier's invoice/tax issues; payment hold/chargeback/set-off; termination; replacement/reissue; dispute resolution. Recovery at minimum: loss calculation (back-tax + late fees + penalties + adviser fees + funding cost), evidence, letters, reconciliation, chargeback/litigation; if the supplier is lost, assess debarment/referral. Guideline No. 7 requires contract/payment/records control; the Invoice Management Measures prohibit false invoicing/lending/using other documents. Recovery should "protect the business first, the tax position second, then recover losses"; charging back the payable without solving the invoice is not enough.
Acceptance checks: invoice warranty; cooperation; indemnity scope; hold/chargeback/set-off; termination; reissue/replacement; loss calculation; letters; litigation; debarment. Common gaps: no clause; only "provide compliant invoices"; narrow indemnity; no chargeback; no recovery; no action if lost.
| Clause/action | What to write | Evidence | Common gap |
|---|---|---|---|
| Invoice warranty | Genuine/lawful/consistent | Contract | No clause |
| Cooperation | Documents/explanation/deadline | Contract | No cooperation |
| Indemnity scope | Back-tax/late fees/penalties/adviser fees | Contract | Narrow scope |
| Hold/chargeback | Payment hold/chargeback/set-off | Contract | Chargeback only |
| Termination/replacement | Termination/reissue/alternate supplier | Contract | No alternative |
| Loss calculation | Amount/evidence/funding cost | Finance | Guesswork |
| Letters/litigation | Demand/claim/arbitration | Letter | No recovery |
| Debarment/referral | Restriction/referral | Record | No action |
Recovery/clauses are editorial; contracts, applicable law and tax treatment control, and this is not legal advice.
How should prevention, governance and metrics be accepted?
Prevention at minimum: supplier onboarding (business licence/general-taxpayer status/credit/address/account/tax risk), invoice verification (face/genuineness/status), three-stream consistency, payment controls (account matches contract/change verification), contract clauses, training, abnormal-voucher register, supplier rating. Governance at minimum: segregation of procurement/finance/tax/legal, authorisation, review, exception escalation, metrics (abnormal invoices/count/value, input-VAT transfer-out, recovery rate, supplier cooperation rate, three-stream mismatch rate), review. Guideline No. 7 requires segregation of incompatible duties/authorisation/records; the Invoice Management Measures require invoices to be obtained/used per rules. Metrics should drive action, not "number of invoices".
Acceptance checks: onboarding; verification; three streams; payment; clauses; training; register; duties; metrics; review. Common gaps: no credit check; no status check; payment ignores account; no training; no register; metrics count only.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| Supplier onboarding | Licence/general taxpayer/credit/address/account | Due diligence | Licence only |
| Invoice verification | Face/genuineness/status | System | No status check |
| Three streams | Contract/goods/payment/invoice | Evidence | Invoice only |
| Payment control | Account match/change verification | System | Change freely |
| Contract clauses | Warranty/cooperation/indemnity | Contract | No clause |
| Training/register | Training/abnormal register | Record | No register |
| Duties/authority | Procurement/finance/tax/legal separation | Policy | One person |
| Metrics/review | Abnormal/transfer-out/recovery/cooperation | Report | Count only |
Prevention/governance are editorial; the company's internal control, tax policy and system capability control.
How should the website page be written, and what must not be published?
Suggested sections: (1) abnormal types/business red flags; (2) business reality/three-stream evidence; (3) handling process (hold/transfer-out/verification/objection); (4) supplier recovery/contract clauses; (5) prevention/governance/metrics; (6) contact window/update date. The public page explains "types, evidence, process, recovery, prevention, boundary" and does not publish specific suppliers/invoice numbers/amounts/tax, tax notices/determinations, back-tax/penalties, contracts/prices or system screenshots. The English page should use consistent terms (abnormal VAT credit voucher, input VAT, deduction, transfer-out, tax authority verification, three-stream consistency, supplier indemnity) and state the cut-off date.
Do not turn the page into "tax planning/how to pay less tax", and do not claim "zero risk/100% deductible" if it cannot be proven. The page should let procurement/finance-tax/legal/audit judge "which invoices are risky, whether the evidence is sufficient, how to handle and recover", without exposing supplier and tax information.
Go-live acceptance checklist
Ten checks: abnormal types/red flags; three-stream evidence; handling process; A-grade/objection verification; back-tax/budget; supplier recovery; contract clauses; prevention/onboarding; governance/metrics; public boundary. Each needs evidence and a review date. The pass standard is not "there is invoice verification", but that procurement/finance-tax/legal/audit can judge risk, evidence, handling path, recovery and prevention, without treating abnormal vouchers as a false-invoicing conclusion.
Before go-live, run a tabletop exercise on a real (redacted) invoice: receive → verify → three-stream check → abnormal alert → payment hold → business verification → tax treatment → supplier recovery → archive, simulating "A-grade 10 days", "supplier lost contact" and "entrusted payment", to see whether the page and process work.
| Check | Pass standard | Evidence | If failed |
|---|---|---|---|
| Types/red flags | Announcement No. 38 types, derivative, business flags, verification | List | Add types |
| Three-stream evidence | Contract/receipt/logistics/payment/invoice | Evidence chain | Add evidence |
| Handling process | Register/hold/transfer-out/verification/archive | Policy | Add process |
| A-grade/objection | 10 days/materials/result | Request | Add deadline |
| Back-tax/budget | Calculation/budget/responsibility | Finance | Add budget |
| Recovery/clauses | Warranty/cooperation/indemnity/chargeback | Contract | Add clauses |
| Prevention/onboarding | Due diligence/verification/payment control | Record | Add prevention |
| Governance/metrics | Separation/authority/metrics/review | Report | Add governance |
| Archive | Notice/evidence/filing/recovery | Archive | Add archive |
| Public boundary | No suppliers/invoices/tax amounts | Page/permissions | Take down |
The acceptance list is editorial; the tax authority's determination, the company's tax treatment and contracts control.
Who should read it, who should not, and what decisions does it support?
For procurement, finance/tax, legal, internal audit, 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 "genuineness only, no business reality, reacting only on notice, no budget for transfer-out, supplier does not indemnify, no contract clause". Not for teams without invoice/input-VAT management, or that want one page to replace tax/legal/audit advice.
Read it if: building an abnormal-invoice/input-VAT page; only "invoice compliance"; genuineness only; no three-stream evidence; no handling process; no recovery; no contract clause. Not suitable if: treating "abnormal voucher" as "false invoicing"; "verification" as "business reality"; "transfer-out" as "the end of loss"; "page" as "tax opinion/penalty decision". Supports: types/red flags, three-stream evidence, handling, recovery/clauses, prevention/governance and public-boundary self-checks.
FAQ
What is the difference between the abnormal-invoice page, the three-way match page and the payment page?
The three-way match page answers "how order/receipt/invoice are matched and variances handled"; the payment page answers "terms/documents/payment"; the abnormal-invoice page answers "which invoices are listed as abnormal, how input VAT is treated, how to verify, recover from the supplier and prevent". Three-way matching is business reconciliation, the abnormal-invoice page is tax-risk handling; they cannot replace each other.
Which invoices are listed as abnormal vouchers?
Under Announcement No. 38, at least: lost/stolen tax-control devices with uninvoiced or not-uploaded invoices; non-normal taxpayers failing to declare/pay; audit comparison "mismatch/missing/void"; big-data analysis indicating suspected false invoicing/unpaid consumption tax; absconded businesses meeting Article 2(1) of Announcement No. 76 of 2016; plus the derivative situation where abnormal input VAT is ≥70% of all special-invoice input VAT and exceeds RMB 50,000. The tax authority's determination controls.
Can abnormal vouchers never be deducted?
Under Announcement No. 38: undeducted input VAT is temporarily not allowed; already deducted input VAT is transferred out unless otherwise provided; export refunds are suspended/recovered per rules; A-grade taxpayers may request verification within 10 working days of the notice and, if compliant, avoid transfer-out/recovery; objections may be verified. Specific treatment is subject to the tax authority and the company's facts; consult a tax adviser.
What evidence is needed for business reality?
At least contract/order, goods receipt/acceptance, logistics/transport, payment receipt, invoice and communication records; it must answer "who bought, what, where the goods went, who received, who was paid, who invoiced". Three-stream consistency is not mechanically three identical names; it is real business, consistent parties, matching amounts and reasonable explanations; entrusted payment/collection needs authorisation/agreement.
What should be done first when an abnormal voucher arrives?
Register (invoice/supplier/amount/tax/period), hold payment/suspend deduction, verify the business (contract/receipt/logistics/payment/supplier contact), apply the tax treatment (undeducted/transfer-out/refund), assess A-grade 10-day verification/objection, calculate back-tax/late fees/penalties, recover from the supplier, archive. Do not split/replace invoices or abscond to circumvent.
How should the supplier be asked to indemnify?
The contract should state invoice genuineness/lawfulness/consistency, cooperation with verification, indemnity for back-tax/late fees/penalties/losses caused by the supplier, payment hold/chargeback/set-off, termination/replacement; on an alert, hold payment, send letters, reconcile, calculate losses, chargeback/litigate; if the supplier is lost, assess debarment/referral. Recovery should protect the business first, the tax position second, then recover losses; charging back the payable without solving the invoice is not enough.
Should the website publish abnormal invoices/tax amounts?
Usually not specific suppliers/invoice numbers/amounts/tax, tax notices/determinations, back-tax/penalties, contracts/prices or system screenshots; it can publish abnormal types, business-evidence requirements, handling process, recovery/contract clauses, prevention/governance and update date. The goal is to let customers/suppliers understand invoice-compliance methods, not to disclose supplier and tax information.
One-sentence takeaway
The procurement abnormal-invoice and input-VAT risk page on a Changzhou manufacturer's website is not "invoice verification"; it is about turning abnormal types/business red flags, three-stream evidence, handling (hold/transfer-out/verification/objection), back-tax budget, supplier recovery/contract clauses, prevention/onboarding, governance/metrics and public boundaries into a checkable list, so procurement/finance-tax/legal/audit can judge risk, evidence, handling path, recovery and prevention without treating abnormal vouchers as a false-invoicing conclusion.
Research method and limitations
This article is a summary of public rules and page method, not tax/legal/audit advice. It uses no unpublished company suppliers/invoice numbers/amounts/tax, tax notices/determinations, back-tax/penalties, contracts/prices or system screenshots; the tables and acceptance items are editorial and not tax/legal/audit conclusions. State Taxation Administration Announcement No. 38 of 2019, the Invoice Management Measures (2023 revision) and MOF Internal Control Application Guideline No. 7 (Procurement) are public sources; the tax authority's determination, the company's tax treatment and contracts control. This article does not decide whether any specific invoice is falsely issued/deductible, and does not promise "zero risk/100% deductible"; companies should handle each case based on business, evidence and tax advice.
Sources and basis
Current to 2026-11-10; the official pages below control.
- State Taxation Administration, Announcement No. 38 of 2019 on Abnormal VAT Credit Voucher Management: The State Council of China. Abnormal voucher scope, derivative situation, deduction/transfer-out/refund treatment, A-grade 10-working-day verification, objection verification; used for types and handling.
- Invoice Management Measures of the PRC (2023 revision, State Council Order No. 764): Guangdong Tax Service, STA. Non-compliant invoices cannot be used for reimbursement and may be refused; false invoicing, lending/transferring invoices and using other documents are prohibited; used for invoice legality and refusal basis.
- MOF Internal Control Application Guideline No. 7 — Procurement (Cai Kuai [2010] No. 11): Linyi Finance Bureau. Supplier selection, contracts, acceptance, payment and records; used for three-stream evidence, payment control and segregation of duties.