Reverse-Charge VAT and Cross-Border Services: How ERP Should Handle Both

Two mechanisms that get confused

Talk to an export software vendor about cross-border services and you will hear reverse charge used as a synonym for anything involving a foreign counterparty and VAT. That is not what it means, and the confusion matters because the two mechanisms point in opposite directions. One governs how a Chinese supplier treats a service it sells abroad. The other governs how a buyer treats a service it purchases from abroad. In the first the supplier's tax position changes; in the second the buyer becomes the taxpayer.

For a Chinese company selling design, software, consulting or logistics services to an overseas customer, the relevant question is whether that service qualifies for zero-rating or exemption under China's cross-border taxable activity rules — and under what conditions, since qualification is typically conditional on contract terms, delivery location and documentary evidence. For a Chinese group with an overseas subsidiary buying services from a third country, or for that subsidiary buying from the Chinese parent, the relevant question is whether the local reverse-charge mechanism applies, making the local entity account for VAT on a supply it did not make. Different rules, different data, different risk.

The China side: zero-rated or exempt

China's cross-border service regime distinguishes zero-rating from exemption, and the distinction is not cosmetic. Zero-rating keeps the service within the VAT system at a zero rate, which generally preserves the supplier's ability to credit input VAT. Exemption takes the supply out of the tax net, which typically means related input VAT cannot be credited and must be absorbed as cost. For a service business with significant input VAT — software development with large cloud and labour costs, for instance — the difference between the two treatments is a real amount of money, not a filing formality.

Eligibility is conditional. The rules look at the nature of the service, where it is consumed, the contractual arrangement and the evidence that the service was in fact provided to an overseas party. Services consumed within China generally do not qualify simply because the invoice is addressed abroad. This is the trap in practice: a Chinese supplier invoices a Hong Kong or Singapore affiliate, treats the revenue as zero-rated, but the service was delivered to and consumed by the group's mainland operations. The paperwork says export; the substance says domestic.

Any statement about eligibility for a specific service should be confirmed with a tax adviser, because the categories are detailed and the conditions are documentary. What the ERP must do is narrower and clearer: capture the facts on which the determination rests, so that a treatment is defensible rather than assumed.

• The customer's identity and location, with evidence of the counterparty rather than only a billing address.
• The contract terms describing what is delivered, where, and to whom — the substance, not the invoice text.
• The basis on which the treatment was chosen (zero-rated or exempt), recorded per contract rather than per customer.
• The documentary pack supporting that basis, linked to the transaction and retained.
• Any change in circumstances — new delivery location, new consumption point — that could invalidate the original treatment.

The other side: reverse charge abroad

Reverse charge, in the sense used in the EU and UK and in a growing number of other jurisdictions, is a mechanism for business-to-business services where the supplier is outside the customer's country. The supplier does not charge local VAT; the customer accounts for it itself, usually reporting it as output VAT and simultaneously claiming it as input VAT where it has full recovery rights. The net cash effect is often nil, which is precisely why it is ignored — and why it becomes a compliance failure rather than a cash cost.

The traps are administrative. The reverse-charged amount must appear on the local VAT return even when fully recoverable. It must be captured in the local accounting records with the correct treatment codes so the return can be produced. And the supplier's invoice must be identifiable as a cross-border service, because an invoice that looks like a domestic supply will be treated as one. A Chinese group's German subsidiary buying IT support from the Chinese parent, or from a Vietnamese development centre, meets this mechanism constantly, and the failure mode is not a large tax bill — it is an accumulating reporting gap discovered at the next local audit.

This is why the group-level design question matters. If each entity runs its own system with its own tax logic, reverse-charge treatment must be implemented locally, repeatedly, with local knowledge. If the group runs a shared platform with a configurable tax engine, the treatment can be modelled once per jurisdiction and applied consistently. The latter is the more common reason groups standardise — not cost, but the impossibility of auditing five different implementations of the same rule.

When services are bundled with goods

The hardest cross-border cases are not pure services. They are transactions where goods and services move together under one commercial arrangement — equipment sold with installation, a machine supplied with a three-year maintenance agreement, software delivered on a device with an ongoing subscription. Each component can carry a different tax treatment, and the treatments interact with customs valuation as well as VAT. Split the arrangement wrongly and you create exposure on both sides at once.

The valuation link is the part exporters miss. A contract quoted as a single price covering goods and post-import services generally cannot have the service element deducted from customs value, because nothing separately identifies it. The same contract, structured with the goods and services as distinct line items from the outset, can often be treated differently — and the difference is a genuine duty saving rather than a technicality. The data requirement is upstream of the ERP, in how the quotation is built, but the ERP must preserve the separation through the order, the invoice and the declaration rather than collapsing it into one amount. That is the same discipline discussed in customs valuation for import and export.

Intragroup management fees

A Chinese group with overseas entities almost always has service flows between them: management fees, shared service charges, technical support, seconded staff, group IT. These are the transactions most likely to be treated casually and most likely to attract attention, because they sit at the intersection of VAT treatment, transfer pricing and local deductibility. A management fee charged from the Chinese parent to a European subsidiary may be a service export on one side and a reverse-charged purchase on the other, and both sides need to record it consistently.

Consistency is the practical requirement. If the parent books revenue with an export-of-services treatment while the subsidiary books a cost with no reverse-charge line, the group has two irreconcilable positions on one transaction, and the mismatch will surface in whichever jurisdiction reviews first. A shared platform with a configurable tax engine lets both entities record the same transaction under the same identifier with the correct local treatment on each side — which is also what a transfer pricing file needs in order to describe the flow coherently. Group structures are covered in multi-entity consolidation for Chinese groups going overseas.

What the ERP needs to model

The requirement splits into two configurations that must not share a single flag. Sellers need an export-of-services treatment on the sales side. Buyers need a self-assessed tax line on the purchase side.

On the sales side, the system should treat the service export treatment as a per-line or per-contract attribute with a recorded basis and supporting evidence, not a global setting. It should be able to produce the documentary pack that supports the treatment, and it should flag transactions where the customer's location and the place of consumption diverge — the single most common source of an incorrect zero-rating claim.

On the purchase side, the system needs to recognise a cross-border service purchase, apply reverse charge automatically based on the supplier's country and the entity's jurisdiction, generate both the output and input tax lines at the correct rate, and post them so the VAT return can be assembled without manual adjustment. Critically, the two lines must be visible separately even though they net to zero, because a return that shows nothing looks like an omission rather than a compliant nil effect.

Why this is worth attention now

Cross-border services are where a manufacturing-oriented ERP most often has no model at all. Export modules are built around goods: customs declarations, bills of lading, rebates. Services have none of those artefacts, so they fall through the design, and the tax treatment defaults to whatever the invoice template does. As Chinese groups expand abroad and intragroup service flows grow — management fees, shared services, technical support, software licensing — that gap moves from an edge case to a material share of intercompany transactions.

The consequence is not only tax. Transfer pricing documentation depends on the same data: what service, delivered where, to whom, priced how, evidenced by what. A system that can describe a cross-border service transaction coherently serves both the VAT question and the pricing question, which is the practical argument for modelling services as first-class transactions rather than as miscellaneous revenue. Group structures and consolidation mechanics are covered in multi-entity consolidation for Chinese groups going overseas, and the local invoicing context in fully digitalized e-fapiao and ERP readiness.

A short checklist before you sign

Ask the vendor to demonstrate, not describe: can the system record a service export treatment per contract with its supporting evidence; can it flag divergence between customer location and place of consumption; can it apply reverse charge automatically for a purchase from a supplier in another jurisdiction and produce both tax lines; and can it do all of that for a group entity other than the Chinese parent. A system that answers yes has been built for cross-border groups. A system that answers yes to the first two and no to the last two has been built for a domestic Chinese business that happens to export goods.