Skip to main content

China recurring billing: how to reconcile with NFS-e

Marina Campos
Marina CamposNovember 17, 202615 min. read
China recurring billing: how to reconcile with NFS-e

To reconcile China recurring billing, the international software vendor closes the month with three numbers per contract: what was billed, what was received and what was invoiced. All three are compared in the accrual period of the service, meaning the period the service belongs to, not the date the money arrived.

Decision framework

  • Reconciliation separates the markets and closes by accrual period and by currency.
  • Billed, received and invoiced close as three numbers, not two.
  • NFS-e, the Brazilian electronic service invoice, covers the Brazilian share of revenue; revenue from China needs a trail of its own.
  • Cancelling the subscription, revoking the debit authorization and issuing a refund are distinct events, with effects to be verified.

The ISV (Independent Software Vendor, a company that sells its product to other companies) that sells subscriptions in both markets has one revenue figure and two evidence sets. For revenue that comes from China, the invoiced amount does not come from the same set of records that closes billed and received. The Brazilian contract produces a document per accrual period. The Chinese contract produces authorization, attempt, settlement and payout. Adding the two without separating the evidence is the mistake the close inherits the following month.

What are the prerequisites for China recurring billing?

Before the first charge, the vendor defines which contract each receivable comes from, in which currency it was billed and which document the Brazilian market requires. That map separates revenue that already has a document from revenue whose document depends on the tax classification. Without it, the close adds up amounts that cannot be compared.

Sales identifies who contracts in each market, and finance confirms which entity receives the settlement. The tax owner points out which of them issues the Brazilian document. In the Chinese market, the question is different: which records the payment arrangement returns to the vendor, and how often they arrive. The brand shown at checkout answers neither question, because on its own it does not identify the party that contracts, receives or issues.

Coverage of the Chinese market, accepted currencies and the authorization provided for go into the same check before contracting. For data held by another participant in the arrangement, the vendor agrees on a request channel and names who answers for it. The Brazilian market and the Chinese market demand different evidence, and the same record request serves neither, because one answers with a fiscal document and the other answers with arrangement settlement. None of this gets resolved later.

The Chinese regulatory check is preliminary and requires counsel with local competence.

The sequence of work is this:

  1. Map the contract, the market and the currency of each receivable.
  2. Record the authorization tied to the customer and the subscription.
  3. Track the outcome of each renewal.
  4. Handle failure and unknown outcomes without duplicating the charge.
  5. Coordinate cancellation, revocation and refund.
  6. Reconcile billed, received and invoiced, market by market.

Step 1: how do you record the debit authorization?

The authorization fixes the first of the three numbers: what may be billed, from whom and for which period. The vendor records the identifier the integration returns, the contract and the current state. Without that record, the month's billed amount has no proven origin.

The record holds, at a minimum, the authorization identifier, the customer, the subscription, the contracted period, the date, the channel where consent was given and the state. Availability of each field depends on the integration contracted, and it is confirmed with the payment provider before the control becomes routine at close.

The decisive question is operational: if the customer revokes, how will the vendor know? Revocation is its own event, and the effect on the subscription depends on the contract. Revocation does not cancel everything. On receiving it, the operator records the new state, stops the debit that has no valid authorization and routes the commercial decision to the owner. Each authorization belongs to the accrual period of the charge, not to the month the money arrived, and the accrual period is what the close uses to compare the line, not the payout date.

Step 2: how do you track each renewal?

Every renewal needs its own record, tied to the subscription and to the billing attempt. The vendor separates the schedule from the informed outcome and keeps the case open while no outcome is known. The subscription state describes the contract, not the payment.

An active subscription describes the commercial state. An attempt records the outcome of one specific charge. Settlement and payout require their own evidence, and that separation is what allows the vendor to say how much of the month's billed amount actually arrived.

Attempt stateWhat the record allows you to stateOperator's next action
ScheduledRenewal expected, no outcomeCheck authorization and period
PendingProcessing or confirmation not concludedTrack through the channel agreed with the payment provider
ConfirmedPayment provider reported a positive outcomeTie the transaction to settlement and payout
Declined or failedPayment provider reported a negative outcomeCheck the reason and the recovery policy
No known outcomeNo reliable responseCheck the state before creating another charge

The table organizes the reading. It does not replace the record.

For each renewal, the history keeps the attempt identifier, the expected date, the outcome date, the amount and the currency billed, the reason when a decline is reported and the channel through which the team obtained the response. A line without the amount, the currency and the outcome date does not support the Step 5 reconciliation, nor the sample the close examines.

The names in the table are working categories, not payment provider codes. The team confronts each category with the records received and points out who investigates the divergence.

inline-01.png

Step 3: what do you do when a renewal fails?

A failed renewal calls for diagnosis before a new attempt. The vendor checks the reported outcome, verifies whether the authorization is still valid and confirms the recovery policy with the payment provider. The number of attempts and the interval between them are not defined in the available evidence.

A reported decline differs from a response that never arrived. The reason is never invented from the subscription state. If the outcome is unknown, the team queries the attempt before creating another charge, and the case stays open with a named owner.

That care reduces the risk of duplication. Repeating the same request with the same identifier only prevents a duplicate charge if the integration contracted offers idempotency for the identifier used, under the applicable conditions, and that condition is confirmed with the provider. At close, a duplicate charge appears as a billed amount larger than the invoiced one, and the two lines stop closing.

The contract defines who informs the buyer, when to request a new authorization and who decides on access. Deadlines and the number of attempts depend on the contract, the provider and the applicable law; local counsel verifies the mandatory limits before that policy.

The guide on Pix Automático and SaaS recurrence in Brazil covers another market. Its rules do not define the Chinese integration.

Step 4: how do you coordinate cancellation and revocation?

Commercial cancellation ends or changes the subscription; revocation removes the debit authorization; a refund addresses a transaction already charged. Each event moves one of the month's three numbers and needs a record with date, owner and evidence.

The decisions are not interchangeable. On receiving a cancellation request, the owner confirms the subscription, the date, the rule for ending access and whether there is an authorization to revoke. The same person checks how to inform the payment provider and how to record the revocation in the commercial system.

A cancellation recorded in the commercial system and not propagated to the billing flow leaves the next renewal without a contractual basis. That gap is what the review shows, and it reappears the following month as a charge with no contract behind it.

To request a refund, the operator locates the original transaction, checks its outcome and reviews the contractual conditions with local counsel. The request does not erase the original attempt or the subscription state for the period. If a renewal is in progress, the team preserves the state and checks the outcome before suspending the charge.

Step 5: how do you reconcile billed, received and invoiced?

Reconciliation compares three numbers per contract: what the subscription generated, what was settled and paid out, and what received a fiscal document. In the Brazilian market, the comparison follows the accrual period of the service. In the Chinese market, the invoiced amount does not come from the same set of records, and the close has to state that in writing.

Revenue is not a single line. A contract with a Brazilian customer and another with a Chinese customer, in the same month, do not close on the same table: in the first, the three numbers are compared in the same accrual period and the difference between them is explained by a fee, a conversion or the outcome of each attempt; in the second, billed and received are compared through the arrangement records, when those records arrive, and the invoiced amount depends on a question NFS-e does not answer on its own.

Finance ties, when available, the subscription and transaction identifiers to the contracted period, to the settlement and to the payout. If the charge and the payout appear in different currencies, the operator asks for the calculation memo and the contractual conditions for conversion and fees. Without that data, the difference stays under investigation.

Number for the monthWhat it answersEvidence that closes the line
BilledHow much the subscription generated in the periodAuthorization and outcome of each attempt
ReceivedHow much was settled and paid outSettlement, fee and payout from the arrangement
InvoicedHow much of the revenue has a document, and under which classificationNFS-e for the accrual period and the basis for the market's classification

The team requests the attempt and cancellation records from the participant responsible and checks whether the report contains the necessary occurrences. Exceptions get an owner and pending evidence.

Step 6: how do you review NFS-e and the contractual arrangement?

The tax review starts with identifying provider, buyer and commercial relationship in each market. The vendor compares the direct contract with an intermediated arrangement and takes the applicable rule, the relevant event and the deadlines to counsel. The name of the model does not replace reading the contract.

NFS-e is a Brazilian fiscal document: it follows the service provided and the accrual period of the service, not the month the money arrived. It does not carry, on the same line, revenue settled in the Chinese arrangement, because each document describes one provider, one buyer and one accrual period. Whether revenue from that market requires a Brazilian document, and on what basis, is a question for the tax owner.

CheckpointDirect contractArrangement with an intermediary participant
Relationship with the buyerIdentify the parties and the sale contractIdentify who sells to the buyer and the contracts between the parties
Billing and recordsCheck who receives and which evidence the vendor can accessCheck who receives, who holds each record and how to obtain it
Fiscal documentationAsk counsel for the analysis of the operation's obligationsAsk counsel for the analysis of the roles and of the obligations

The NFS-e National Portal published guidance on the document schedule for IBS and CBS, with a distinction by classification.

ISS requires a review of its own. LC 116/2003, art. 2, item I and sole paragraph addresses non-incidence on service exports, with an exception for a service developed in Brazil whose result is verified here.

The ADCT, arts. 128 and 129 and LC 214/2025, arts. 342, II, and 508 support the transition: ISS reduction between 2029 and 2032, extinction from 2033. The NFS-e document schedule differs, and Ato Conjunto RFB/CGIBS No. 7/2026, art. 1 does not eliminate other obligations.

How do you check whether reconciliation is complete?

The check starts from a sample of subscriptions and follows each one through to the evidence of authorization, outcome, settlement and document treatment. The sample includes failures, cancellations and cases with no known outcome. The expected result is a close with three numbers per market and an open difference per named owner.

The sample must contain at least one subscription of each recorded outcome: a confirmed renewal, a reported decline, an attempt with no known outcome and a cancelled subscription. When it gathers only successful renewals, the test does not exercise the exception the close has to explain, and the close starts checking only what already worked.

For each subscription, the team checks the contracted period, the authorization, the outcome of the attempt and the evidence of settlement or of the exception. It also checks the date and the state of the revocation or the refund record, when there is one.

If the identifier linking charge and payout is missing, finance obtains the data or documents the pending item. The account closes per currency, and each market closes its own. The identifier is requested in writing.

Finance and tax identify the origin of the records and who answers for the open differences.

Which errors require correction before the close?

Errors include confusing authorization with receipt, creating a charge without querying the previous attempt and treating commercial cancellation as revocation. Repeating the same request with the same identifier only prevents duplication if the integration offers idempotency, under the applicable conditions. Before repeating, the team confirms the condition with the payment provider.

Failures also count. Finance checks whether the available records cover failed attempts and cancelled transactions and seeks further evidence when needed. For the tax analysis, it delivers the contract and the trail of the operation, not just the receipt.

Five checks close the list. An authorization recorded with no transaction in the period points to a charge that did not happen. If the transaction appears confirmed and the settlement does not arrive, one participant's record stayed incomplete. When a payout has no reconciliation, the amount sits outside the trail. A cancellation without revocation keeps the next renewal exposed. A refund without the original transaction blocks the check of the reversal. Each item gets an owner and an internal deadline set by the company itself, because the arrangement's deadlines depend on the contract and on the payment provider. No item resolves with the receipt alone, because the receipt does not describe the attempt that generated it nor the subscription state in the period when the charge was authorized, and that comparison is what the close has to show.

Frequently asked questions

In the debit flow it has chosen, the vendor checks with the payment provider how to obtain the authorization and track each attempt. Recovery, cancellation and documentation depend on the contract and on the applicable rules. Local counsel verifies the legal limits before the team executes any billing policy.

Does revenue from China go into the same close?

It goes into the same revenue account, not into the same evidence trail. The close shows billed and received for the Chinese market with the arrangement records, and treats the Brazilian document as a separate question, answered by the tax owner. A single total hides that difference.

What do you do if a renewal gets no response?

The team keeps the occurrence open. Before creating another charge, it asks the payment provider about the outcome of the attempt and checks the controls against duplication. Repeating the same request with the same identifier depends on the integration rules, and the access decision considers the contract and the applicable law.

Does revoking the authorization cancel the subscription?

Not necessarily. Revoking the authorization and commercial cancellation are distinct events; their effects depend on the contract, on the integration and on the applicable rules. The vendor must verify how it receives the information, what the subscription state is and when access ends, with support from local counsel.

Does a cancellation require an automatic refund?

Cancellation does not by itself demonstrate that a transaction will be refunded. The team locates the original charge, checks its outcome and reviews the contractual conditions with local counsel. If a request exists, the refund record stays tied to the transaction, without replacing the subscription history.

Does every confirmed charge require an immediate NFS-e?

The tax owner identifies the applicable rule, the relevant event and the deadlines for issuance or adjustment for the operation, considering the commercial relationship and the parties. The IBS and CBS guidance published by the NFS-e National Portal does not, on its own, classify a sale to a buyer in China.

References and further reading

The guide on Pix installments at SaaS checkout examines installment payment and cash flow in Brazil. It is another market. The reading helps separate commercial conditions from the financial records needed to check transactions, but it does not establish the rules of the integration contracted for a renewal in China.

Next step

The decision to buy moves from an impression about the interface to the document when the vendor can name, for each receivable, who authorizes, what was billed, what was received and which document covers that line of the month.

Two answers end the evaluation. The first is whether the payment provider delivers, in writing, the set of records and the query channel for each state. The second is whether the contract defines who answers for a renewal failure, for a revocation and for a refund before the charge happens.

For revenue in Latin America there is a named solution: selling with Nexforce Marketplace running the billing. The vendor reaches the buyer on local infrastructure, receives in local currency in Latin America and, in Brazil, bills in reais with a fiscal document for the buyer under the contracted model, without opening an entity in the country. In the practice of the close, the distance between billed and received shortens, because the buyer pays in installments with the Marketplace and the vendor receives upfront. That does not reach revenue from China: for that market, the integration and the records stay with a payment provider evaluated separately, with no assumption of Marketplace coverage.

Nexforce

Sell software in Latin Americawith no setup and saving 50%

Distribute your SaaS through the Nexforce platform scaling sales channels in a simple way

Run Simulation

Related articles