# China Fapiao Data Field Template for ERP Projects

> Source: https://netray.co/tools/china-fapiao-data-field-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A data field specification you can hand to your ERP team: the customer, seller, invoice and line fields needed to issue a Chinese fapiao.

## Category

regional

## Erp

Kingdee, Yonyou, SAP, Oracle

## Region

China

## Audience

- ERP consultant
- Finance controller
- Tax manager
- ERP developer

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Seller legal name

**Key:** seller

**Type:** text

**Default:** Suzhou Example Precision Co., Ltd.

#### Seller tax ID (USCC)

**Key:** seller_id

**Type:** text

**Default:** 91320500XXXXXXXXXX

#### Buyer legal name

**Key:** buyer

**Type:** text

**Default:** Shanghai Sample Machinery Co., Ltd.

#### Buyer tax ID (USCC)

**Key:** buyer_id

**Type:** text

**Default:** 91310000XXXXXXXXXX

#### Invoice type

**Key:** invoice_type

**Type:** select

**Options:**

- VAT special invoice
- VAT ordinary invoice
- Digital special invoice
- Digital ordinary invoice

**Default:** Digital special invoice

#### VAT rate

**Key:** tax_rate

**Type:** select

**Options:**

- 13%
- 9%
- 6%
- 3%
- 0%

**Default:** 13%

#### ERP system

**Key:** erp

**Type:** text

**Default:** Kingdee Cloud Galaxy

#### Project owner

**Key:** owner

**Type:** text

**Default:** Finance systems lead

#### Date

**Key:** date

**Type:** date

**Default:** 2026-10-20

#### Local rules to confirm

**Key:** notes

**Type:** textarea

**Default:** Confirm current invoice types, limits and reduced rates with the local tax bureau and the invoicing platform vendor before go-live.

**Blocks:**

#### Fapiao Data Field Specification

**Body:** Seller: {{seller}} ({{seller_id}})
ERP system: {{erp}}
Project owner: {{owner}}
Date: {{date}}
Primary invoice type: {{invoice_type}}
Default VAT rate: {{tax_rate}}

#### Customer master data (buyer)

**Body:** Example buyer: {{buyer}} ({{buyer_id}}). Each field below must exist in the customer master or be captured at order entry. Names must match registration records exactly, because mismatches cause invoice rejection or buyer deduction problems.

**Table:**

**Columns:**

- Field
- Rule or note
- Required

**Rows:**

**0:** Buyer legal name

**1:** As registered, full name, no abbreviations

**2:** Yes

**0:** Buyer tax ID

**1:** Unified Social Credit Code, 18 characters

**2:** Yes for special invoices

**0:** Buyer address and phone

**1:** Required on VAT special invoices

**2:** Special invoices

**0:** Buyer bank and account

**1:** Required on VAT special invoices

**2:** Special invoices

**0:** Invoice email or mobile

**1:** For delivery of digital invoices

**2:** Recommended

**0:** Invoice type preference

**1:** Special, ordinary or digital

**2:** Yes

#### Seller and header fields

**Table:**

**Columns:**

- Field
- Rule or note
- Required

**Rows:**

**0:** Seller name and tax ID

**1:** From the legal entity master

**2:** Yes

**0:** Seller address, phone, bank, account

**1:** Printed on special invoices

**2:** Special invoices

**0:** Invoice date

**1:** Date of issue, normally within the tax period of the sale

**2:** Yes

**0:** Invoice number and code

**1:** Assigned by the invoicing platform, store back in ERP

**2:** Yes

**0:** Issuer, reviewer, payee

**1:** Names of staff roles where the format shows them

**2:** As format

**0:** Remarks

**1:** Contract or order reference, per customer request

**2:** Optional

**0:** Red-letter (credit) reference

**1:** Original invoice number for reversals

**2:** Credit notes

#### Line item fields

**Table:**

**Columns:**

- Field
- Rule or note
- Required

**Rows:**

**0:** Goods or service name

**1:** Must be consistent with the tax classification code

**2:** Yes

**0:** Tax classification code

**1:** Assigned per material or service from the national code list

**2:** Yes

**0:** Specification and unit

**1:** Model and unit of measure shown on invoice

**2:** As needed

**0:** Quantity and unit price

**1:** Pre-tax or tax-inclusive, set one convention

**2:** Yes

**0:** Amount excluding tax

**1:** Rounded per line, watch rounding differences

**2:** Yes

**0:** Tax rate and tax amount

**1:** Per line, must reconcile to header totals

**2:** Yes

**0:** Preferential policy flag

**1:** Where a reduced or exempt treatment applies

**2:** If used

#### Open points and approvals

**Body:** {{notes}}

**Signatures:**

- Finance systems lead
- Tax manager
- ERP integration lead

**Notes:** This is a data planning aid, not tax advice. Invoice formats, limits and rules change, including the rollout of fully digitalized invoices, so confirm current requirements with your tax advisor, the local tax bureau and your invoicing platform vendor.

## Content

**Intro:** A fapiao is the official tax invoice in China, and an ERP that cannot capture the right fields cannot issue one. This template lists the buyer, seller, header and line fields your project team needs, so you can agree them with finance and tax before configuration starts.

**Sections:**

#### How to use this template

**Body:** Fill in the entity, ERP name and primary invoice type, then export the document to PDF or Word and use it as the field specification in your design workshop. Each table is a checklist: for every row, decide where the field lives in the ERP (customer master, material master, sales order, billing document) and who maintains it. Add rows for your own needs, such as customer-specific remarks.

#### Why the fields matter

**Body:** China's tax system is built around the fapiao. Invoices are issued through the tax authority's invoicing platform or an approved connected system, and buyers rely on them for input VAT credit and expense deduction. Errors in the buyer name, the tax ID or the tax classification code can force a credit note, which in China is handled as a red-letter invoice, and that creates rework and delays in collection.

**Bullets:**

- Buyer name and Unified Social Credit Code must match records
- Special invoices need address, phone and bank details
- Each line needs a tax classification code
- Header totals must reconcile to line totals

#### Digital invoices and ERP integration

**Body:** China has been moving to fully digitalized invoices that are delivered electronically and do not depend on paper or special devices. In an ERP project this means integrating through an approved platform or API so that the invoice number and status come back into the billing document automatically. Decide early who triggers issuance, how rejections are handled and how credit notes link to the original invoice.

#### Common mistakes

**Body:** Frequent problems include abbreviated customer names, missing tax classification codes on new materials, mixing tax-inclusive and tax-exclusive prices, rounding differences that break header-to-line reconciliation, and no process for red-letter reversals. Test with real customers and edge cases such as discounts, free goods, advance payments and exports before go-live.

**Cta:** If you want help mapping these fields into your ERP billing process or building the integration to your invoicing platform, Netray and its partners can scope it with you.

**Faq:**

#### What is the difference between a special and an ordinary VAT invoice?

**Answer:** A VAT special invoice lets the buyer claim input VAT credit and therefore needs full buyer details such as address, phone and bank account. An ordinary invoice does not support input credit in the same way. Check current rules with your tax advisor.

#### What is a tax classification code?

**Answer:** It is a code from the national classification list that describes the goods or service on each invoice line. The ERP needs a code per material or service so the invoice line can be issued correctly. Your tax team normally owns the mapping.

#### How are fapiao corrected after issue?

**Answer:** Errors are normally corrected by issuing a red-letter invoice that reverses the original, followed by a new correct invoice, subject to the rules in force. Your ERP should link the reversal to the original invoice number and keep an audit trail.

#### Does this template work for any ERP?

**Answer:** Yes, it is system neutral. The fields are what the invoice requires, whether you run Kingdee, Yonyou, SAP, Oracle or another ERP. The technical integration with the invoicing platform differs by product and by the platform vendor you choose.

## Search terms

china fapiao template, fapiao data fields, china e-fapiao erp, fapiao requirements erp, china vat invoice fields, unified social credit code invoice, digital fapiao integration, golden tax erp integration

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json