How to invoice recurring SaaS subscriptions in Brazil

A software company in São Paulo can close a month with 1,200 active subscriptions and discover that a search for “SaaS invoice” points to the wrong document. Domestic software as a service is generally documented through a municipal service invoice, not the national goods flow. This guide shows how a Brazilian ISV invoices its own recurring subscriptions without turning market practice into a national obligation.

What is needed to invoice recurring subscriptions?

Four pieces must exist before the first batch: a digital certificate, registration in the competent municipality’s tax system, classification under the list attached to Complementary Law 116/2003, and a reliable base of active subscriptions. Without them, invoicing becomes a backlog. For domestic SaaS services, the typical document is the municipal NFS-e.

ISVs (Independent Software Vendors, software companies that sell their product to other businesses) issue their own outgoing invoice to the Brazilian customer. NF-e model 55, with a national access key and DANFE, describes the goods flow or operations that state law places in that document. Treating every SaaS subscription as a national NF-e mixes different jurisdictions.

The NFS-e records a service listed in the annex to Complementary Law 116/2003. The tax attached to that list is ISS, administered by the municipality. The commercial name “electronic invoice” does not select the document. The nature of the operation and the municipality’s system do.

Step 1: Identify the competent tax document

The first step is not generating XML. It is identifying the document required by the municipality where the establishment is located, or by the customer’s municipality when local law assigns competence there. In most Brazilian municipalities, domestic SaaS is issued through NFS-e. Confirm the official issuer for that city before automating a batch.

Complementary Law 116/2003, article 1, caput and paragraph 2 applies ISS to services in its annex and, subject to the list’s exceptions, separates them from ICMS even when the service involves goods. In ADI 5659, the STF consolidated software’s classification as a service subject to ISS. That supports municipal competence. It does not create one national authorization flow, access key, and DANFE for every recurring subscription.

When the operation is genuinely a sale of goods, the state NF-e applies. When it is SaaS service supplied to a customer in Brazil, the default path is the municipal document. Do not make a DANFE an automatic consequence of a recurring subscription.

Step 2: Classify the operation as a service

The tax classification comes from the list attached to Complementary Law 116/2003. Item 1.05 covers licensing or assignment of the right to use computer programs. Continued access to hosted software is read, for ISS purposes, as a service rather than movement of goods subject to ICMS. That reading determines the document.

The operational consequence is direct: the domestic SaaS invoice highlights ISS, not ICMS on goods. A customer receiving a goods document loses the service classification reserved by item 1.05. A wrong classification moves the tax and the compliance work with it.

Item 1.07 of the same list covers technical support in information technology. If the contract combines a license, support, and customization, the ISV classifies each line according to the service actually supplied, not according to the commercial plan name. The product label does not choose the tax. Article 1, paragraph 4, of Complementary Law 116/2003 makes that principle explicit.

Step 3: Set the cadence by the taxable event and municipal law

Invoice cadence follows the ISS taxable event, the contract, and municipal legislation. There is no national rule requiring an invoice at renewal, on the first business day, or one document for each subscription every month. The billing cycle is evidence of the service period. It is not the rule itself.

Complementary Law 116/2003, articles 1, 3, 4, 5, 6, and 7 defines the taxable event, location, taxpayer, and tax base, while leaving due dates, periodicity, and the number of documents to municipal regulation and to the slice of service the contract actually separates. One municipality may require monthly competence. Another may accept a different period. Read the local regulation.

Companies that charge by usage close measurement and issue the document for the period supported by local law and the contract. Delaying issuance after the taxable event creates municipal exposure. Inventing a national “day 10” does the same because the complementary law does not establish one universal deadline.

Step 4: Show ISS according to the municipality

ISS applies in the competent municipality, with a rate between the 2% floor and 5% ceiling established by Complementary Law 116/2003, articles 8 and 8-A. The concrete rate is the local law’s rate for the relevant list item. Confirm that law before saving a percentage in the issuer.

The NFS-e service code normally follows the attached list, commonly item 1.05 for a right to use software. Withholding by the customer exists only when article 3 of Complementary Law 116/2003 and the customer municipality’s law require withholding at source. Do not treat withholding as automatic.

ISS belongs to the service regime. On the municipal invoice, it appears in the field reserved by that city’s layout. The highlighted amount must match the rate currently in force there because the reconciliation is local. Copying a rate from another municipality creates a difference payable with interest.

Step 5: Handle IBS and CBS in 2026 without assuming automatic highlighting

Complementary Law 214/2025 creates the dual VAT. In 2026, article 343 sets IBS at 0.1% and article 346 sets CBS at 0.9%. These are legal parameters for the test year. They are not an automatic instruction to highlight new lines.

Article 348, paragraph 1, dispenses with IBS and CBS payment in 2026 for taxable persons that comply with the accessory obligations established in the legislation. Item III, point “c”, of that article excludes operations by Simples Nacional taxpayers from applying those rates. Whether the NFS-e or NF-e layout changes depends on the regulated accessory obligation, not on a universal command to add lines to every invoice.

The long ISS transition through 2033 is in Constitutional Amendment 132/2023, ADCT articles 128 and 129, not only in the body of Complementary Law 214/2025. PIS and COFINS remain in force until CBS takes over under the consolidated rules. A combined 28% burden is a planning assumption. Do not use it as a 2026 issuance instruction.

Step 6: Separate what the invoice shows from what the regime collects

The invoice calculation should not place every tax in one undifferentiated total. ISS is the municipal tax on the service. PIS and COFINS depend on the company’s regime. IBS and CBS in 2026 follow articles 343, 346, and 348 of Complementary Law 214/2025, including the payment dispensation and Simples exclusion. Keep the lines separate.

A numerical example is safe only with complete assumptions. Without the municipality, regime, document, and 2026 treatment stated, a total becomes invented tax burden. That is why this guide does not publish one universal tax range for a R$1,000 subscription. Each line has its own legal basis. Add only what the facts support.

The useful reconciliation is different: total billed against total documented in the municipal system; ISS highlighted against ISS paid in that municipality; IBS and CBS accessory obligations against what the 2026 regulation requires. This comparison catches a wrong rate or wrong document before it becomes a tax assessment.

Step 7: Issue, validate, and archive in the competent system

Final issuance goes through the authorization system required by the document. For NFS-e, the ISV generates the municipality’s file standard, signs it with an A1 or A3 certificate, and retains the XML for the period required by applicable law. Confirm federal and municipal rules before setting an archive policy. Do not claim one universal five-year retention period.

A municipal invoice exists only after authorization by that system. Do not describe a national access key and DANFE as universal stages for SaaS subscriptions. Those belong to the goods NF-e flow when the operation is actually a goods operation. Copying the NF-e route into NFS-e produces the wrong file in the wrong place.

At scale, the issuer reads the billing base and generates a batch in the correct document. Cadence becomes a continuous process. A wrong batch, with a national document replacing a municipal one, scales the error at the same speed.

How can you verify that a SaaS invoice is correct?

Before the municipal due date, the ISV checks the document type, the Complementary Law 116/2003 list item, the local ISS rate, and, in 2026, whether any IBS and CBS accessory obligation applies to that regime. A sheet reconciling billed and documented amounts remains the simplest control.

The second signal is the competent municipality. If the invoice separates provider and customer in different cities, the ISV reads article 3 of Complementary Law 116/2003 and local law before assuming withholding. The third is payment: ISS paid for the period should match the amount highlighted on invoices for that municipality. That is where a copied rate appears.

Do not use a generic CFOP table as proof of correctness. The reviewed legal corpus does not contain an official table authorizing one CFOP for domestic SaaS. Without an official source specific to the document actually used, this guide does not prescribe a code.

What common errors appear in SaaS invoicing?

The first error is treating domestic SaaS as goods and shifting tax to ICMS, replacing the municipal service document with a state circulation flow and erasing item 1.05. The second is copying the NF-e workflow. The third is highlighting ISS below the local rate. All three scale quickly.

Another error is recording IBS and CBS in 2026 as automatic lines on every invoice, ignoring article 348 of Complementary Law 214/2025 and the Simples Nacional exclusion reserved by item III, point “c”. These are shortcuts, not creative interpretations. One monthly control hour can prevent months of corrections.

Where do CIDE and importation fit in this invoice?

CIDE does not appear on the domestic invoice for recurring subscriptions. It is import context: “CIDE at 10% applies to SaaS and technical services. The exemption in paragraph 1-A of article 2 of Law 10.168/2000 applies exclusively to pure software licenses without technology transfer.”

SC Cosit No. 191/2017 treats remote SaaS as a technical service for IRRF and CIDE in the facts it describes. It has administrative scope within the Brazilian Federal Revenue for those classifications, not the force of a statute or a judicial precedent for every contract. The object must still be read.

The outgoing invoice to the final customer in Brazil contains ISS and taxes under the company’s regime. CBS and IBS enter only if the 2026 accessory obligation reaches that taxpayer. The calculation of tax on imported software, including CIDE on a remittance, is covered in the imported software tax calculation guide.

How does Nexforce Marketplace relate to this issuance?

Nexforce Marketplace does not issue the subscription invoice instead of the ISV. The duty to document domestic service to a Brazilian customer remains with the provider in the competent municipal system. ISS remains in place while applicable. IBS and CBS depend on law, not on a private replacement.

Marketplace enters when the operation crosses a border and an ISV needs implementation structure, FX, and a BRL invoice for a foreign supplier that cannot solve those needs through the municipal issuer used for domestic subscriptions. For cost, consult the total cost guide for foreign SaaS. The broader regime appears in the Latin America SaaS compliance guide and the Brazil SaaS tax compliance guide.

The rule remains simple: the invoice for domestic recurring subscriptions belongs to the ISV. Service classification, the municipal document, and ISS highlighting are its responsibility. Where the operation crosses a border, Nexforce Marketplace can support fiscal structure and FX. It does not replace the duty to issue the Brazilian outgoing invoice.

FAQ

Does an ISV need one invoice for every subscription each month?

No. Complementary Law 116/2003 defines the ISS taxable event, not a universal cadence of one document per subscription. Periodicity comes from the contract, the service period, and the competent municipality’s law. Many issuers follow the billing cycle. That is practice, not a national rule.

Which CFOP should be used for SaaS sold to a Brazilian customer?

This guide does not prescribe a CFOP. Domestic SaaS is generally documented through municipal NFS-e, and the reviewed corpus has no official table authorizing one code for this operation. If an NF-e is used for an operation that genuinely supports CFOP, the code must come from that document’s official table.

Is SaaS a service or goods on the invoice?

It is a service when the object is licensing or continued access covered by the Complementary Law 116/2003 list, generally item 1.05. STF ADI 5659 supports ISS on software. A goods NF-e applies only when the operation is genuinely movement of goods. The commercial plan name does not decide classification.

How does Complementary Law 214/2025 change the invoice in 2026?

The law sets IBS at 0.1% and CBS at 0.9% for 2026 events. Article 348 dispenses payment when accessory obligations are met and excludes Simples Nacional from those rates. New lines depend on the accessory regulation and regime. Do not make highlighting automatic on every NFS-e or NF-e.

Does CIDE appear on the domestic subscription invoice?

No. CIDE is remittance context. CIDE at 10% applies to SaaS and technical services. The paragraph 1-A exemption in article 2 of Law 10.168/2000 applies exclusively to pure software licenses without technology transfer. SC Cosit 191/2017 binds the Administration within the facts it classifies.

References

• Complementary Law 116/2003, including articles 1, 3 to 8-A, and item 1.05.
• STF ADI 5659, software subject to ISS.
• Complementary Law 214/2025, articles 343, 346, and 348.
• Constitutional Amendment 132/2023, ADCT articles 128 and 129.
• SC Cosit No. 191/2017, administrative treatment of SaaS as a technical service in the consulted facts.
• Law 10.168/2000, article 2, paragraph 1-A, pure license exemption without technology transfer.

The next operational step for your issuance cycle

The guide ends where the process begins: classify the product under the Complementary Law 116/2003 list and open the competent municipality’s issuer before the first batch. Define the document, generally NFS-e, item 1.05, and the local ISS rate. Validate one short cycle. Automate afterward.

Nexforce Marketplace can support cross-border operations with fiscal structure, FX, and BRL invoicing. For imported software tax calculations and the cost of foreign suppliers, the Nexforce guides remain available. The domestic recurring-subscription invoice remains the ISV’s responsibility.