NF-e at the auto shop: what SEFAZ requires from your system

The essentials

The shop deals with two fiscal documents: NF-e (or NFC-e) for the part and NFS-e for labor. Different authorities: state and municipality.
The NF-e is born as an XML authorized by SEFAZ. The DANFE is just the printout that travels with the merchandise.
Without a digital certificate (A1 on file or A3 on a card/token), nothing gets signed.
The fields that most often reject a shop's nota are CFOP, NCM and taxation — CST under the normal regime, CSOSN under Simples Nacional.
Promec still doesn't issue NF-e. Said plainly, below.

Anyone running a shop in Brazil lives with something that barely exists in any other country: the same job, a clutch swap, splits into two fiscal documents issued to two different authorities. The part is merchandise and answers to the state. Labor is a service and answers to the municipality. That's not an accounting detail: it's what decides how your quote needs to be structured internally.

This piece covers the state-level part, the NF-e. The other two pieces of the series cover NFC-e, for counter sales, and NFS-e, for labor.

What Promec does today in Brazil. The system runs the whole shop — AI quotes, scheduling, the mechanic's app, inventory, the customer portal and accounting — and it invoices with your own series, taxes and currency. What it doesn't do yet is issue NF-e, NFC-e or NFS-e directly against SEFAZ or the municipality: that integration is in development and we don't have a date for it. Meanwhile, fiscal issuing stays with your current issuer. We prefer to say this before you sign up, not after. Where direct integration already exists is on the coverage page.

What NF-e is, in practical terms

The Nota Fiscal Eletrônica, model 55, is an XML file your system builds, signs with the company's digital certificate, and sends to your state's SEFAZ. SEFAZ validates it and returns an authorization protocol. Only from that protocol on does the document exist. Before that there's no nota — there's a draft.

What travels with the merchandise is the DANFE — Documento Auxiliar da NF-e —, a sheet with the main data and the access key in barcode form. It's useful for the driver and the customer, but it's not the fiscal document. If an audit ever asks for the nota, what they want is the authorized XML.

The access key, decoded

44 digits, and each block means something: the state code, the year and month of issue, the issuer's CNPJ, the model, the series, the nota number, the issuance method, a random numeric code and the check digit. That's why the key is unique across the whole country, and why the customer can check the nota on the portal with just that key.

Digital certificate: without it, nothing gets signed

Signing the XML requires an ICP-Brasil digital certificate belonging to the company. There are two formats, and the choice has practical consequences:

A1: a file, installable on a server or in a cloud service, shorter validity. It's what lets you issue without anyone having to plug anything in anywhere — and the only viable format if you want to issue from more than one location or in an automated way.
A3: a physical card or token, longer validity. Cheaper to renew, but ties issuing to the machine where the token is plugged in. At a shop with a front desk and a back office, that tends to turn into a line.

The certificate expires. It's the most common, most banal cause of "the system stopped issuing": nobody renewed it. It's worth putting the expiration date in the same place you track the rest of the operation.

The fields that reject a shop's nota

SEFAZ rejection almost never comes from something exotic. At a shop, it comes from four places:

Field	What it is	Where the shop gets it wrong
CFOP	Código Fiscal de Operações e Prestações: states what the transaction is and where it's going.	Using the same CFOP for an in-state sale and an out-of-state one, or for a sale and a warranty part shipment.
NCM	Merchandise classification, eight digits.	Registering a part without an NCM, or reusing a generic NCM across the whole inventory "so issuing doesn't stop."
CST / CSOSN	Tax situation. CST under the normal regime; CSOSN under Simples Nacional.	Switching regimes and not reviewing the records: notas keep going out with the old regime's taxation.
ICMS-ST	Tax substitution: the tax was already collected earlier in the chain.	Auto parts are one of the sectors most affected. Treating an ST part like a regular one distorts the price and the nota.

None of these fields is a decision you make at the moment of issuing: they're attributes of the part's record and the customer's record. That's why the quality of your inventory decides the quality of your notas. An inventory where the same brake pad is written three different ways, with three different NCM codes, will generate inconsistent notas no matter which issuer you use.

After issuing: cancel, correct, void

Three different situations that tend to get confused:

Cancellation: only within the legal deadline and provided the merchandise hasn't circulated. Outside that, the correct path is a return or adjustment nota.
Carta de Correção Eletrônica: corrects data that doesn't change amounts, tax rates, issue date or the parties involved. It's for a mistyped address, not for fixing a price.
Inutilização (voiding): for when a series number was used up and never became a nota. Numbering has to be sequential with no gaps, and voiding is how you justify the gap.

Contingency: when SEFAZ or your internet goes down

It happens, and not rarely. The law provides for contingency modes — which ones are available varies by state and by the type of outage — that let the merchandise go out with a provisional document while authorization comes later. From the point of view of someone choosing software, what matters is a simple question: when SEFAZ is down, does the system let me keep handing back cars, or do I stop?

The tax reform on the horizon

Constitutional Amendment 132/2023 replaces current taxes with CBS and IBS, with a transition period of several years. The timeline and layouts have been published in stages, and the NF-e's technical documentation has already been receiving new fields through technical notes. It's not worth making permanent decisions today based on what the final model will look like — it is worth choosing tools that keep up with the technical notes instead of freezing the layout. Always confirm the current timeline with your accountant.

What this requires from the shop's software

Issuing the nota is the last step, and the most visible one. The real work happens before: a quote that separates the labor line from the parts line, an inventory with NCM and taxation by reference, a customer record with complete tax details, and a work order from which the document comes out without retyping anything.

A shop that builds the quote on paper and then types it all again into the issuer doesn't have a nota fiscal problem: it has a rework problem, and the nota is just where the error shows up.

Sources

National NF-e Portal (nfe.fazenda.gov.br), Manual de Orientação do Contribuinte, Ajuste SINIEF 07/05 and technical notes published by ENCAT, state SEFAZ portals and municipal ISS legislation. This text is informational and doesn't replace your accountant's guidance: the rules vary by state and municipality and change often.

Try Promec with your own shop's data

AI quotes, scheduling, mechanic app, inventory and customer portal. 3 months for €1, no lock-in.

Start for €1

FAQ

Does the shop need to issue NF-e, or is NFS-e enough?

It depends on what you're charging for. Labor is a service and goes on an NFS-e, under municipal jurisdiction. The part applied or sold is merchandise and goes on an NF-e (model 55) or, for an over-the-counter sale to an end consumer, an NFC-e (model 65). Most shops issue both types of document and, in practice, need the same quote to know how to split those two lines.

What's the access key, and why does it matter?

It's the 44-digit number that uniquely identifies the nota across the whole country. It encodes the state, the year and month of issue, the issuer's CNPJ, the model, the series, the number, the issuance method, a numeric code and a check digit. It's the key the customer uses to look up the nota on the portal, and it's what links the nota to the authorized XML.

Is keeping the DANFE as a PDF enough?

No. The fiscal document is the XML authorized by SEFAZ; the DANFE is only the printed representation that travels with the merchandise. If your system only gives you the PDF and doesn't store or let you download the XML files, you have an archiving problem that will show up the day of an audit. The retention period is set by tax law, counted in years, not months.

Can I cancel an NF-e after it's issued?

Only within the legally set deadline and provided the merchandise hasn't circulated yet. Past that deadline, the correct path isn't cancellation, but issuing a return or adjustment nota. To correct data that doesn't change amounts, tax rates or the parties involved, there's the Carta de Correção Eletrônica (Electronic Correction Letter). And if a series number was burned without becoming a nota, the procedure is numbering inutilização (voiding).

Is there shop software 'approved by SEFAZ'?

Not for that category. SEFAZ validates the document, it doesn't certify shop management programs. When a vendor advertises their software as 'approved,' they're describing a seal that doesn't exist. The useful question is different: does the system issue the XML in the current layout, does it handle the technical updates when the layout changes, and does it store the authorized XML files so you can download them?

What if the internet goes down mid-shift?

There's contingency. The available modes depend on the state and the type of outage — EPEC, FS-DA and others — and they all share the same idea: the merchandise can go out with a provisional document, and authorization is regularized afterward. What matters when choosing a system is a simple question: when SEFAZ is down, does the system let me keep handing back cars, or do I stop?