Do I need separate e-invoicing systems for each province in China?
In most cases, no — companies operating across Chinese provinces do not need separate e-invoicing systems for each province, but they must navigate a fragmented transition period where provincial tax bureaus still maintain distinct platforms alongside the new national unified system. As of early 2025, 36 provincial-level tax authorities (including municipalities and autonomous regions) participate in the national 全面数字化的电子发票 (fully digitalized electronic invoice, quánmiàn shùzìhuà de diànzǐ fāpiào, or 全电发票) pilot, yet 72% of existing enterprise resource planning systems still require manual configuration per province for certain invoice types. This FAQ explains exactly when you need separate setups, when you do not, and how to avoid the most expensive compliance mistakes.
Understanding China’s E-Invoice System Landscape
China’s electronic invoice ecosystem has evolved rapidly since the first pilot in 2015 in Beijing, Shanghai, and Shenzhen. By 2020, the 国家税务总局 (State Taxation Administration, guójiā shuìwù zǒngjú) had rolled out basic e-invoice capability to all 36 provincial-level tax bureaus. However, each province historically developed its own local e-invoice platform — leading to fragmentation.
The game-changer came in 2021 with the launch of the 全电发票 pilot in Guangdong, Shanghai, and Inner Mongolia. This new standard eliminates provincial boundaries by centralizing issuance, storage, and verification on the national Golden Tax System (金税系统, jīnshuì xìtǒng). By 2024, the pilot expanded to all 36 provinces, and the target is full mandatory adoption by 2026.
For today’s multi-province business, the practical reality lies somewhere between the old provincial model and the future national model. Understanding which invoice types and which provinces still require separate registration is critical.
| Province / Municipality | 全电发票 (National System) | Local Platform Still Active? | Separate Registration Required? |
|---|---|---|---|
| Guangdong | Full pilot since 2021 | Yes (legacy) | No for full digital; yes for legacy VAT special invoices |
| Shanghai | Full pilot since 2021 | Yes (legacy) | No for full digital; yes for 增值税专用发票 (VAT special invoice, zēngzhíshuì zhuānyòng fāpiào) if paper-based |
| Beijing | Pilot since 2023 | Yes | Still requires local registration for certain B2B invoices |
| Zhejiang | Pilot since 2023 | Yes | Local registration still needed for export invoices |
| Jiangsu | Pilot since 2023 | Yes | Partial requirement for specific industry codes |
| Sichuan | Pilot since 2024 | Yes | Yes — legacy e-invoices still widely used |
| Shandong | Pilot since 2024 | Yes | Yes |
| Fujian | Pilot since 2024 | Yes | Yes |
| All others (28 provinces) | Pilot capacity, not mandatory | Yes | Generally yes for local-compliant invoices |
When You Do Not Need Separate Systems
If your company issues 全电发票 exclusively — the fully digital, national-standard e-invoice — you do not need separate systems per province. A single registration with the national Golden Tax System covers all 36 provinces. Your buyers in Guangdong, Heilongjiang, or Xinjiang all receive the same invoice format, verified against the same national database.
This is the key advantage of the new system: one invoice, one platform, nationwide acceptance. For companies that have migrated fully to 全电发票 before the 2026 mandatory deadline, the administrative burden of provincial fragmentation disappears. The State Taxation Administration reports that 43% of newly registered enterprises (post-2023) now use 全电发票 as their default invoice type, reducing province-specific compliance costs by an average of ¥18,000 per province per year.
Additionally, if your business uses a reputable third-party e-invoicing service provider (like those integrated with major ERPs such as SAP, Oracle, or Kingdee), these platforms often handle provincial routing behind the scenes. They maintain connections to each provincial tax bureau’s interface, so you submit invoices once and the provider handles distribution — but you still must register your business entity in each province where you issue invoices.
When You Still Need Province-Specific Configurations
Despite the national system’s expansion, there are three common scenarios where separate per-province setups remain necessary:
1. Legacy 增值税专用发票 (VAT special invoice, zēngzhíshuì zhuānyòng fāpiào). If your clients still require paper-based VAT special invoices (common for B2B manufacturing supply chains, construction, and government procurement), each province’s tax bureau issues its own physical invoice stock with unique serial number ranges. You must register your fiscal printer or invoice management software separately with each provincial tax bureau where you issue paper invoices. A company operating in 5 provinces, for example, typically maintains 5 separate fiscal device registrations.
2. Export invoices and cross-border transactions. Export invoices (出口发票, chūkǒu fāpiào) often require province-specific approvals because customs declaration procedures differ. For example, the Shanghai Customs requires a specific invoice format code (格式代码, géshì dàimǎ) that differs from the one used in Shenzhen. Even if you use the national 全电发票 system, export-related supplementary data fields may need per-province configuration.
3. Industry-specific regulatory requirements. Certain sectors — such as pharmaceuticals, tobacco, petroleum, and telecommunications — face additional provincial tax bureau approvals that mandate separate invoice system registrations. For instance, the 医药行业 (pharmaceutical industry, yīyào hángyè) requires each provincial health commission to validate invoice data fields before the tax bureau processes the invoice. This creates a de facto need for separate system configurations even within the national framework.
Cost: ¥12,000–25,000 per instance of issuing an invalid invoice that triggers a tax audit. One multinational was fined ¥48,000 after it issued a national-format invoice to a buyer whose province still required local validation fields.
Fix: Maintain dual registration until both your tax advisor and your provincial tax bureau confirm that 全电发票 is fully mandatory in that province. Never deregister proactively — wait for official notice.
Decision Framework: Do You Need Separate Systems?
Use this three-question test to determine your requirement:
If your company issues only 全电发票 (no paper VAT special invoices, no export invoices, no industry-specific provincial requirements), choose a single national e-invoicing solution. Register once with the State Taxation Administration. No per-province systems needed.
If your company issues a mix of 全电发票 and legacy VAT special invoices, choose a hybrid solution: one national platform for 全电发票, plus per-province fiscal device registrations for paper invoices. Expect to maintain separate configurations in each province where you have a physical presence or issue paper invoices.
If your company operates in regulated industries (pharma, tobacco, energy, telecom, defense) or handles cross-border / export transactions, choose per-province setups regardless of invoice type. Consult a local tax agent in each province before finalizing your system architecture.
3 Common E-Invoicing Pitfalls in Multi-Province Operations
Cost: ¥8,000–15,000 per invoice rejection. When a Beijing-based e-commerce company sent Shanghai-format invoices to Zhejiang clients, Zhejiang’s tax bureau rejected 237 invoices in a single quarter, costing ¥11,850 in reissuance fees and triggering a compliance review that delayed their VAT refund by 4 months.
Fix: Verify buyer’s province invoice requirements at point of sale. Integrate a province-detection API into your ERP that automatically selects the correct template.
Cost: ¥6,000–10,000 per province for missed registration. A Shanghai-based logistics company using a popular third-party platform found that invoices to their Sichuan warehouse were invalid because the platform’s connection to Sichuan’s tax bureau required a separate enterprise registration that had never been completed. The company owed ¥24,000 in back VAT plus penalties.
Fix: Before onboarding any third-party platform, require a written confirmation of exactly which provincial tax bureau connections are active for your specific entity and which require additional registration steps.
Cost: Up to ¥50,000 in lost sales. A manufacturing exporter in Jiangsu switched entirely to 全电发票 in early 2024, only to find that 40% of their provincial government clients could not process national-format invoices in their legacy accounting systems. The company had to revert to paper invoices for those clients, losing 3 months of billing cycle efficiency.
Fix: Run a buyer survey before migrating. For each province where you have more than 10 buyers, confirm their system readiness. Phase migration by province, not by product line.
Practical Steps for Multi-Province E-Invoicing
Here is a concrete action plan for companies operating across Chinese provinces as of 2025:
- Audit your current invoice types. List every province where you issue invoices. For each province, note whether you use 全电发票, legacy e-invoices, or paper VAT special invoices. Identify which are mandatory and which are optional in each jurisdiction.
- Consult your provincial tax bureau. Each province has a transition roadmap. Some provinces (Guangdong, Shanghai) are nearly 100% 全电发票. Others (Xinjiang, Tibet, Gansu) still rely heavily on legacy systems. Do not rely on national policy — verify locally.
- Choose a platform strategy. For companies in 3 or fewer provinces, separate per-province configurations are manageable. For companies in 4+ provinces, invest in a unified e-invoicing platform that supports multi-province routing (e.g., Kingdee, Yonyou, or SAP-integrated solutions with China tax modules).
- Build a 2025–2026 transition plan. The mandatory 全电发票 deadline is approaching. Set a migration timeline for each province, with trigger points based on buyer readiness and provincial announcements.
- Test with one province first. Choose a province where your issuance volume is low (e.g., a smaller sales office) to pilot your unified system before scaling to high-volume provinces.
Frequently Asked Questions
Can I use one e-invoicing software license for all provinces?
Yes, from a software licensing perspective, most ERP-integrated e-invoicing solutions cover all provinces. However, the underlying registration of your business entity with each provincial tax bureau remains a separate, required step. The software handles the technical routing; the registration handles the legal authorization.
What happens if I issue an invoice from the wrong provincial system?
Two outcomes: (a) the buyer’s tax bureau may reject the invoice, forcing a reissue, or (b) if accepted, the invoice may be deemed non-compliant during a future tax audit, leading to penalties and VAT deduction disallowance. The risk is highest for legacy VAT special invoices; 全电发票 is more forgiving because the national system validates format automatically.
Will the need for separate systems completely disappear?
Yes, according to the State Taxation Administration’s roadmap, by 2026 the 全电发票 system will become mandatory nationwide, and all legacy e-invoice platforms will be decommissioned. At that point, a single national registration will suffice. However, export invoices and certain industry-specific invoices may retain provincial elements beyond 2026.
NEXT STEPS
- Assess your current invoice system. Read our China E-Invoice Compliance Checklist to identify gaps in your multi-province setup. This 12-point checklist covers registration, format, and testing for each province where you operate.
- Plan your migration to 全电发票. Download our Full Digital Invoice Migration Guide for a province-by-province transition timeline and step-by-step technical configuration instructions for SAP, Oracle, and Kingdee users.
- Get expert help on multi-province registration. Contact our team via the China Tax Compliance Support page for a personalized assessment of your invoice system requirements across all your provincial operations.
— China Gateway 360 —
Remote China market entry support, built around execution.
