Information date: 24 September 2026 — This composite case follows the typical sequence after a foreign manufacturer incorporates in China: tax registration, which is largely merged into the business licence and multi-certificate integration process; a bank account; a tripartite agreement allowing the bank to withhold tax; and registration for value-added tax and the invoice system before any customer can be billed. Each step unlocks the next. Knowing that statement is not enough for an operating, research or compliance decision. The team must first establish who and what it applies to, how the effect reaches the real process, and which evidence would justify action.
Verified facts and scope
This composite case follows the typical sequence after a foreign manufacturer incorporates in China: tax registration, which is largely merged into the business licence and multi-certificate integration process; a bank account; a tripartite agreement allowing the bank to withhold tax; and registration for value-added tax and the invoice system before any customer can be billed. Each step unlocks the next.
Applies to any newly established foreign-invested enterprise that will issue value-added tax invoices. Before starting, confirm the registered business scope and whether its wording maps to the tax bureau's item codes, whether you will be a general or small-scale value-added tax taxpayer, which bank account type the tripartite agreement accepts, and which software or device will issue electronic invoices.
How the effect reaches operations
Registration is a chain of dependencies rather than a single event. The business licence creates the unified social credit code, the bank account enables the tripartite withholding agreement, and that agreement unlocks invoice issuance. Because each step feeds the next, a delay in document legalisation, bank customer due diligence or item-code matching pushes back the first invoice by weeks.
Typical problems include business scope wording that does not map to a tax item code, forcing an amendment; a bank account that is not accepted for the tripartite agreement; assuming small-scale taxpayer treatment when customers require a special value-added tax invoice; and issuing invoices before registration is complete, which can be treated as unauthorised and denied to the customer as input credit.
For “Case: Tax Registration and Fapiao Setup for a New Foreign-Invested Manufacturer”, official rules or published findings, direct evidence from the relevant product or process, and assumptions that remain untested should be recorded separately. A broad source defines the external boundary; it does not replace batch records, protocols, contracts, labels or direct observations.
Decision
If your customers require special value-added tax invoices, register as a general taxpayer from the outset and align scope wording with tax item codes. If you bill only overseas customers initially, you can sequence registration after the bank account to avoid idle compliance work. Either way, appoint one internal owner for the entire chain rather than splitting it across finance, legal and the bank.
Implementation checklist
- Match business scope wording to tax item codes before submitting the filing.
- Complete the bank account and tripartite agreement before printing any invoice.
- Assign custody of the invoice device, official seal and passwords to one named owner.
- Assign one decision owner, one implementation owner and a dated review point for “Case: Tax Registration and Fapiao Setup for a New Foreign-Invested Manufacturer”.
- For “Case: Tax Registration and Fapiao Setup for a New Foreign-Invested Manufacturer”, archive the source page, access date, applicable population or entity, and internal evidence both supporting and opposing the current decision.
- When a rule, formulation, supplier, protocol or observed result changes, reopen only the affected question in “Case: Tax Registration and Fapiao Setup for a New Foreign-Invested Manufacturer”.
Evidence and review
For “Case: Tax Registration and Fapiao Setup for a New Foreign-Invested Manufacturer”, start with one real case rather than an abstract checklist. Record the input version, responsible owner, start time, observed result and stop condition. If the team cannot complete “Match business scope wording to tax item codes before submitting the filing.” with current evidence, it should not expand the process to more products, patients, suppliers or markets. The first review should focus only on facts capable of changing the decision.
The second control follows “Complete the bank account and tripartite agreement before printing any invoice.”. Keep the source date, applicable population or entity, deadline, cost effect and owner in the same evidence file. A wording preference does not justify a new version. A repeated discrepancy, an unsupported health claim or a regulatory mismatch does: correct that point and hold release until the evidence is available.
After “Assign custody of the invoice device, official seal and passwords to one named owner.”, compare the intended outcome with what actually happened. Apply the same success criteria to each later expansion. If only one number, date or responsibility changes, update that field and the affected conclusion instead of recreating evidence that remains valid. This keeps the decision traceable without turning review into an open-ended rewrite cycle.
Limits of the conclusion
This is an illustrative composite case for planning purposes, not tax, legal or accounting advice, and it does not describe any specific company. Registration sequences, item-code lists and invoice rules vary by city and change over time, so confirm the current requirements with the competent tax authority and a licensed adviser.
