Skip to main content

Merchant of Record: a continuity plan for ISVs

Marina Campos
Marina CamposNovember 19, 202620 min. read
Merchant of Record: a continuity plan for ISVs

If the merchant of record, the party that takes on the role of registered seller and can run charging and documentation under the contract and applicable law, leaves the operation, ISVs (Independent Software Vendors, software companies that sell to other companies) have to inventory subscriptions, validate seller, buyer and tax coverage, define billing per cycle and reconcile renewal, payments and tax documents.

Decision frame / Key facts:

  1. Acceptance of the selling entity does not prove coverage for every buyer.
  2. Contract and responsibilities must be agreed before any real charge at the destination.
  3. A payment in transit or an uncertain termination keeps the new schedule blocked.
  4. The bank payout must be reconciled with transactions, adjustments and holdbacks.

The merchant of record role does not remove every obligation from the software company. The guide to the model and how to choose it explains the structure; here the focus is keeping contracts and renewals under control.

Set up access and assign the decision

Before changing billing, bring finance, product, the people responsible for the subscription system, support, legal and tax together. The group has to read the current contract, reach reports and integrations, identify who owns the decision and agree on who can authorize the cut. No universal deadline fits every portfolio.

A batch with no owner does not move.

ISV finance checks settlements, refunds and payouts, including the balances that remain pending after the contract ends and require follow-up until they reach the bank. Product verifies access to the software. The billing team compares the schedules, while support receives customer messages and legal and tax examine the responsibilities by contract and jurisdiction. One person coordinates the exceptions and records the decisions, including when the answer is still pending. The record must identify the batch, the reference date, the systems involved, who can stop the operation and where the confirmations needed for that decision are kept. If access to the reports ends with the contract, the team can lose the evidence needed to examine a later reversal. Preparation therefore includes access to the data after termination and a channel to track adjustments that have not yet reached the bank. The sequence separates the decisions taken before the cut from the actual execution.

  1. Inventory subscriptions, products and payment evidence.
  2. Validate the seller's establishment, the buyer's location and the tax coverage, without treating one confirmation as proof of the others.
  3. Review documents by jurisdiction and negotiate the contract, the responsibilities and the exit.
  4. Design the cut and the treatment of delinquency by subscription group, with owners defined for exceptions.
  5. Test and execute the authorized cut, with reconciliation and an interruption plan.
  6. Check the payouts, correct divergences and follow later events.

Step 1: inventory the portfolio before changing billing

A useful list links each customer to the contract, the paid period and the next renewal. The inventory includes active, trialing, canceled, suspended, past-due subscriptions and those with a renewal pending. An import without those states can create a charge where access should be closed or suspend access that is still contracted.

Do not confuse registration with payment.

For each ISV subscription, gather identifier, product, plan, price, currency, cycle, status, paid period and contract, plus the date of the next renewal and the person responsible for the check. A canceled subscription may keep access until the end of the paid period, under the applicable terms; a past-due one requires a decision on charging and access. Cross the list with invoices, tax documents where applicable, settled payments, credits, reversals and disputes. Keep the buyer's country and the tax identification when it is needed for the document analysis. Define a reference date for the export and log later changes, because the portfolio keeps moving during preparation. Compare totals and identifiers with the source reports, investigate missing records and preserve evidence of the check. Organize the groups by renewal, currency, country and payment method. Name one owner per group and record the impediment of every subscription that cannot move forward.

Separate subscription data from payment credentials

A subscription identifier is not the card number. A token is a substitute credential used in a payment flow; its transfer depends on the technical and contractual conditions and on the authorizations that apply. Do not assume portability. When it is not confirmed, the plan must provide for the secure request of a new payment method.

Do not copy sensitive card data into spreadsheets, messages or unauthorized environments. Restrict access to the exports, check who may receive them and define retention and disposal with the people responsible for data protection. Before the cut, compare the export with the source again to capture payments, cancellations and other changes that happened since the first copy.

Step 2: validate three axes of the merchant of record proposal

Accepting a buyer in a given country does not prove that the selling entity will be accepted, nor that every tax obligation of the sale is covered. The team has to test those questions separately, in writing, for each relevant type of operation. A missing answer remains an open item.

These are three distinct decisions.

The ISV has to check the entity that will contract and sell, the buyer's location and the tax coverage. Ask the provider for confirmation of the establishment, the product and the conditions for the account. For the buyer, location, product and payment method must fall within the coverage offered for the transaction. Tax coverage requires a matrix of obligations, documents and owners by operation and jurisdiction, so that tax and the local adviser can examine what remains with each party. Keep the version of the conditions and the date of the confirmation. Ask which exclusions exist, when coverage can change and how the company will be notified. If the provider answers only with a list of buyer countries, record the other axes as unconfirmed. The obligations matrix separates the questions without turning a commercial answer into a tax conclusion.

Verification axisQuestion that needs an answerEvidence to requestRisk if missingOwner of the check
Seller establishmentAre the contracting entity and its place of establishment accepted for this product and flow?Confirmation for the entity, with conditions and dateContract or receipt not viableLegal and finance
Buyer locationAre the sale and the payment method accepted at the buyer's location?Coverage by location, product and method, including exclusionsCustomer with no purchase or renewal pathSales and billing
Tax coverageWho performs each obligation, and in which operations and jurisdictions?Matrix by country, sale type, document and responsible partyObligation or document with no defined ownerTax and local adviser
inline-01.png

The European Commission describes the One Stop Shop as a set of optional schemes for declaring and paying value added tax on covered operations.[1] That information does not confirm the eligibility of a specific company. The choice of scheme, the operation and the responsible party require their own analysis.

Step 3: review documents and negotiate the contract before the cut

Legal and tax have to examine the nature of the supply, the parties, the documentation and the issuer of each flow before a real charge at the destination. In parallel, the company negotiates the contract and confirms the acceptance of the entity and the exit conditions. Pending answers block execution.

The contract comes before the payment.

In Brazil, hand the ISV's adviser the contract, the service description, the buyer's data, the documents issued and the payment record. Ask that person to confirm the classification, the documents required and who must issue them for that operation, including the service invoice (nota fiscal de serviços) when applicable. The team of a Mexican entity must request a separate local analysis, with its own contracts, service classification and countries served. Do not transfer the Brazilian conclusion to Mexico. For European operations, the OSS registration page distinguishes conditions related to the establishment and to the scheme chosen.[3] That page does not confirm the coverage of a specific company. The country compliance guide helps prepare the questions, without replacing the local analysis. Record the answers by operation and keep unapproved those that still depend on review.

Turn the proposal into verifiable responsibilities

The proposal must state who charges, who issues each document, who answers for refunds and disputes and who keeps the records. Confirm in writing the accepted entity, the coverage of each transaction, the conditions for change, the costs and the payout currencies. The simulated test also requires internal authorization, even without moving money.

Read the exit clause before the entry. The contract must clarify which data can be exported, in what format, with which authorizations, for how long it will remain accessible and whether there will be assistance after termination. Examine access to the reports of balances, reserves, disputes and later reversals. The transfer of tokens and the continuity of consents require specific technical and legal confirmation. Compare merchant of record and operating your own entity to identify capabilities the company will have to keep in house. Without an agreed destination contract and authorization for the batch, do not move to real charging.

Step 4: design the transition by subscription group

The transition has to preserve the period already paid and state who will make the next charge. For each subscription, record the source and destination identifiers, the last confirmed charge, the end of the paid period, the next renewal, the amount, the currency, the payment method status and the owner of the check for each data point. Consents and contractual changes require their own verification.

A pending payment stops the cut.

The ISV billing team has to agree on one date per group and reduce competing changes where possible. First, check attempts started, automatic retries, pending charges and payments in transit at the source. Resolve the uncertain states. Confirm that future charges are switched off in the old schedule. Until there is evidence of those controls, keep the new schedule inactive and the subscription in exception. The next charge must be scheduled for the end of the period already paid, without charging that period again. The import date does not replace the access end date. Closing or recreating a contract depends on the applicable terms and authorizations; copying a record does not prove the customer's agreement. Preserve the identifiers and the event history to investigate payments that arrive after the cut. Record who follows each exception and keep support informed about the communication with the customer.

Define communication and the charging of past-due accounts

The billing team has to decide, per group, who will charge outstanding amounts and how to suspend or coordinate the old retries. Before any attempt at the destination, check the history, the relevant authorization and the decision on the regularization period. A debt should not be recreated just because the subscription was imported.

Tell the customer what changes in the charging name, in the documentation and in any secure update of the payment method, under the contract. State the support channel, who follows the answer and how access or suspension will be handled under the applicable terms. Do not ask for sensitive data by message. When the customer needs to update the payment, record the request and avoid activating a new attempt while an earlier charge is still unresolved.

inline-02.png

Step 5: test, execute and reconcile each renewal

Start with a test identified as simulated or real, limited to an authorized group of plans, countries and payment methods. Record who approved the batch, the operation limit and who can stop it. Only then compare the results with the source and decide whether another group can move forward.

A test is not financial acceptance.

In the execution of the ISV subscription transition, take a secure export and keep a recovery copy with restricted access. Check by identifier the period already paid, the next date, the amount and the payment state in both schedules. Confirm that no payment in transit remains without a decision and that the old schedule was disabled before activating the next charge at the destination. If any of those checks fails, keep the subscription blocked. A record created at the destination does not prove payment, document issuance or adequate access. The batch owner has to compare real events and investigate divergences in price, currency, date or customer before expanding the operation. Keep the evidence of the simulation or real charge, the open exceptions and the decision to continue or stop. Those controls reduce risk, but they do not guarantee a migration without errors.

Prepare the rollback without reactivating two schedules

The rollback plan must name who decides, which records have to be preserved and how to prevent both schedules from charging at the same time. Before reactivating any charge, check the old and the new schedules and the events that actually happened, including late attempts. Reverting a configuration does not erase a charge that was made.

The European Commission guidance on OSS records identifies information such as the type and date of the operation, the place of consumption and the data used to determine the customer's location in covered operations.[2] Preserve retrievable evidence and confirm the retention period applicable to each case with the competent owners.

Step 6: reconcile payouts and follow adjustments

A recorded charge is not the same as money received in the bank. Finance has to link transactions and adjustments to the payout report, check the currency and verify the bank credit. Differences stay open until there is a documented explanation and a person responsible for the correction.

Do not accept the total alone.

In the ISV payout reconciliation, compare by period and identifier the transactions with refunds, disputes, fees and reserves or holdbacks provided for in the contract. Where there is conversion, record the currencies and the amounts shown in the corresponding reports. Then compare the resulting balance with the payout report and the credit on the bank statement. A difference may be tied to events from different periods, to a holdback agreed in the contract or to an adjustment not yet processed; each hypothesis needs evidence, not an entry to close the spreadsheet. For each divergence, record amount, currency, period, owner and investigation deadline. Keep access to the reports after termination and follow balances, reserve releases, disputes and reversals that occur after the last payout. Tell support when the correction requires contact with the customer or a review of access.

Check the result before accepting the transition

Operational acceptance requires that the team can explain, for each subscription in the group, which period was paid, which schedule is active, where to find the payment and who handles a divergence. Compare identifiers, not only totals. A completed import is not the same as a reconciled renewal.

Appearances do not close the books.

In the verification of the ISV subscription transition, an aggregate count can match even when one customer is duplicated and another is missing. So compare source and destination record by record, including price, currency, date, access, payment and applicable document. Keep the test result and separate the accepted cases from the exceptions that still await information from the customer or the provider. Review the alerts after the first cycle and keep support ready to receive complaints. The decision to expand the batch belongs to the person designated in the preparation, with evidence that the identified problems were handled. Commercial acceptance, tax coverage, consent, portability and charging are different confirmations. If any confirmation is pending for a given operation, record the limitation and do not mark the operation as approved just because the other confirmations passed. Keep one owner for the investigation of each divergence.

Common failures and how to correct them

A divergence needs an owner and a next step, not a completion mark. The failures below involve schedules, credentials, collection recovery and payouts. In each case, the team has to preserve the events, stop new attempts when necessary and record the correction before releasing the subscription.

Do not restart charging blindly.

In the subscription transition of an ISV, the investigation starts by comparing the real events with the source and destination schedules. A duplicate charge requires suspending new attempts and analyzing the payments and the eventual refund under the applicable terms. A missing renewal requires checking the schedule, the payment method and the declines. If the token is unavailable, the customer receives a secure request to update the payment method through the approved flow, and the team records the request. For delinquency, identify who charges, reconcile the attempts and confirm the authorization. A divergent payout requires comparing transactions, reversals, disputes, fees and holdbacks with the report and the bank statement. In each case, the record shows the owner, the affected period, the decision on access and the communication to the customer. Before reverting the configuration, check the schedules and any late events again.

Duplicate charge: suspend new attempts, compare the two schedules and the effective payments and route the refund analysis under the applicable terms.

Missing renewal: check the schedule status, the payment method and any declines; request a secure update when needed, keep support informed and record who will follow the customer's answer.

Token unavailable: do not copy card data outside an authorized environment; obtain a payment method from the customer through the approved flow.

Open delinquency: identify who charges, reconcile the attempt history and confirm the authorization before creating any new attempt.

Divergent payout: link transactions, reversals, disputes, fees and holdbacks to the report and the bank statement; assign an owner and a deadline to the difference.

In every case, record the affected period, the decision on access and the communication made to the customer. A late event requires a new check of the schedules before any rollback.

Assess the local contracting alternative

In direct international contracting, the team has to coordinate contract, currency, documents and responsibilities for the operation. The Nexforce Marketplace is presented by Nexforce as a channel to contract and manage international software, with local payment in reais for the buyer. The team must confirm the conditions applicable to the operation.

That does not prove the reverse flow.

The public offer describes the acquisition of international software; it does not confirm that a Brazilian ISV can sell to buyers abroad through the same flow. The interested company must request written commercial and contractual confirmation on the selling entity, buyer countries, payer, payee, currency, issuer of each document and payout schedule. Coverage of buyers abroad, subscription migration and the replacement of the international flow described in this guide are not demonstrated by the pages consulted. There is also no confirmation that a Mexican entity can use the channel for the operation described. Before adopting the alternative, the ISV must ask its own adviser what the tax treatment of the buyer is in the concrete jurisdiction and transaction. Nexforce is not presented as a merchant of record or as a tax adviser for that operation. A commercial answer does not replace the adviser's analysis.

Frequently asked questions

The answers below guide the check of contracts, payments and documents in a change of the party responsible for charging. They do not replace confirmation with the participants or the local legal and tax assessment. Each answer addresses a different decision; none of them proves, on its own, the full acceptance of the operation or the adequacy of the conditions offered by the provider for that portfolio.

When a merchant of record leaves, the continuity of the ISV subscriptions requires checking the contracts and the applicable conditions, without assuming cancellation or automatic transfer. Acceptance of the selling entity, the buyer's location and the tax coverage are distinct checks, which need written confirmation. The transfer of tokens depends on the technical and contractual conditions and on the authorizations that apply. When there is no confirmed transfer, the ISV must plan the secure update of the payment method by the customer. To reduce the risk of a duplicate charge, the billing team has to resolve payments in transit and confirm the shutdown of the previous schedule before activating the next charge at the destination. The check must consider the paid period, the events by subscription and the exceptions. Those controls reduce the risk, but they do not guarantee the absence of duplication; the legal and tax assessment remains specific to each operation and jurisdiction.

Does the provider's exit automatically cancel the subscriptions?

It is not possible to conclude that without examining the contracts and the applicable conditions. Some subscriptions may need closing, recreation or action by the customer. The plan must record who authorizes the change, how the customer will be notified and what access will look like during the period already paid.

Does one accepted buyer mean the seller is eligible?

No. The selling entity, the buyer's location and the tax coverage are distinct checks. The team must ask for written confirmation for each axis and record the exclusions by product and transaction. A positive answer about the buyer does not confirm the acceptance of the entity or the obligations covered.

Do tokens and consents move automatically to the new flow?

The transfer should not be assumed. Check the technical and contractual conditions, the applicable authorizations and the availability of the payment method at the destination. If there is no confirmed path, plan the secure update by the customer, define who will follow the answer and keep the subscription in exception until the check.

How to reduce the risk of a duplicate charge?

Confirm the shutdown of the previous schedule, resolve payments and attempts in transit and only then activate the next charge at the destination. Preserve the paid period and reconcile the events by subscription. Keep alerts and an investigation routine: those measures reduce the risk, but they do not guarantee that a duplication is impossible.

References and further reading

  1. The One Stop Shop. European Commission. https://vat-one-stop-shop.ec.europa.eu/one-stop-shop_en. Accessed on: Nov. 19, 2026.
  2. Record Keeping and Audits in OSS. European Commission. https://vat-one-stop-shop.ec.europa.eu/one-stop-shop/record-keeping-and-audits-oss_en. Accessed on: Nov. 19, 2026.
  3. Register to OSS. European Commission. https://vat-one-stop-shop.ec.europa.eu/one-stop-shop/register-oss_en. Accessed on: Nov. 19, 2026.
  4. Merchant of record: what it is, when the software company needs one, and how to choose. Nexforce. https://nexforce.ai/en/blog/merchant-of-record-software-latam-how-to-choose. Accessed on: Nov. 19, 2026.
  5. SaaS compliance in Latin America: country guide. Nexforce. https://nexforce.ai/en/blog/saas-compliance-latin-america-country-guide. Accessed on: Nov. 19, 2026.
  6. Merchant of Record vs your own entity: how to sell in LatAm. Nexforce. https://nexforce.ai/en/blog/merchant-of-record-vs-own-entity-latam-saas. Accessed on: Nov. 19, 2026.
  7. Nexforce Marketplace. Nexforce. https://nexforce.ai/marketplace. Accessed on: Nov. 19, 2026.

Confirm the next step

Before deciding, confirm the eligibility and the tax treatment of each operation with the provider and with your own legal and tax adviser. Record the answers in writing and keep operations without confirmation pending, before authorizing any real charge at the destination.

To decide continuity after the exit of a merchant of record, the ISV has to rank the subscriptions by recurring revenue and by proximity of the renewal. A lower-value subscription that expires first may require attention before a larger contract with more preparation time. In each group, record the renewal date, the open item that blocks the decision and the person responsible for resolving it. Do not release open items. If there is enough evidence and authorization for the cut, choose a date for the batch and confirm who will follow the first cycle. If a confirmation is missing or a payment is in transit, keep the subscription out of the batch and set a review date with the owner. Priority organizes the work, but it does not replace approval. As for the Nexforce Marketplace, the ISV must confirm the intended operation in writing: the public offer consulted does not demonstrate subscription migration or coverage of buyers abroad for the flow described. The tax analysis belongs to the adviser.

This content is informative and does not replace legal, accounting or tax guidance from qualified professionals for your operation and jurisdiction.

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