NF-e issuer with a tax engine and the reform already built in
Issue the product invoice in the same system as your CT-e and MDF-e. Own quota, a tax engine that resolves CFOP, ICMS and PIS/COFINS, per-state contingency and the IBS/CBS rules of Brazil’s tax reform.
The NF-e (model 55) is Brazil’s electronic invoice for the movement of goods — unlike the CT-e, which documents the freight service itself. In BrainCargo, the NF-e is issued in the same system that already issues your CT-e, MDF-e and CIOT, with an independent quota: product invoices do not consume the transport-document limit. The module carries a tax engine that resolves CFOP (fiscal operation code), ICMS (state VAT), PIS and COFINS (federal contributions) from rules versioned by regulation, already includes the IBS and CBS rates of the tax reform, and covers export operations, per-state contingency (when Sefaz, the state tax authority, is down) and automatic reconciliation of issued invoices.
BrainCargo’s NF-e issuer (the electronic goods invoice, model 55) was built for carriers that already issue transport documents (CT-e, the electronic freight bill of lading, and MDF-e, the electronic manifest) and also need to invoice goods — without running two systems and two master-data bases.
The tax engine works with a versioned regulatory dictionary: rules have effective dates, so an invoice issued today uses today’s rule and the history stays auditable when the legislation changes.
What you can achieve
0
quota conflicts with the CT-e
The NF-e has its own independent quota: issuing product invoices never consumes the transport-document limit.
1
master data for invoice and transport
Customers, products and certificate shared across NF-e, CT-e and MDF-e — no exporting spreadsheets between systems.
IBS/CBS
rules already in the calculation
The tax-reform rates arrive as a regulation with effective dates, cut by state and municipality — and the history stays auditable.
0
issuing blocked when Sefaz drops
Per-state contingency keeps invoicing running when the authorizing environment goes down.
Why this module
One system, two worlds
Product invoice and transport document on the same customer, product and certificate master data — no exporting spreadsheets between systems.
The reform is already inside
IBS and CBS rules arrive as a regulation with effective dates, not a patch: the tax assessment accepts the state and municipality breakdown the transition requires.
A quota that doesn’t fight
The NF-e has its own limit. Heavy CT-e issuers don’t lose room to invoice goods, and each product line can be sold separately.
Keeps issuing when Sefaz drops
Per-state contingency, so the operation doesn’t stop when the authorizing environment goes down.
How to issue an NF-e in BrainCargo, in 4 steps
The product invoice comes out of the same master data as the CT-e, with its own quota.
-
Register the product with its NCM and the operation
Products, customers and the certificate are shared with the CT-e and MDF-e. The nature of the operation (return, transfer, fixed-asset sale, shipment) defines the CFOP.
-
Let the tax engine calculate
CFOP, ICMS, PIS and COFINS from rules versioned by regulation, with the reform’s IBS and CBS already available and cut by state and municipality.
-
Validate and authorize
Validation before sending; if the state’s Sefaz drops, per-state contingency keeps invoicing running.
-
Print the DANFE and reconcile
DANFE (the printed invoice companion document) in PDF, XML archived and automatic reconciliation against Sefaz, with an issuing-metrics dashboard.
What's included
Brazil's freight tax documents and receipts, integrated
- NF-e model 55 with its own quota (does not consume the CT-e and MDF-e quota)
- Tax engine: CFOP, ICMS, PIS and COFINS from rules versioned by regulation
- IBS and CBS tax-reform rules already available
- Export operations, with fiscal-benefit codes
- Per-state contingency when Sefaz is unavailable
- Automatic reconciliation and an issuing-metrics dashboard
NF-e in the same system as the CT-e, or somewhere else: what changes
| Criterion | BrainCargo | Separate ERP or NF-e issuer | Accountant |
|---|---|---|---|
| Customer and product master data | Shared with the CT-e and MDF-e | Duplicated, exported via spreadsheet | By e-mail |
| Document quota | NF-e has its own; does not consume CT-e/MDF-e | Depends on the plan | — |
| Tax reform (IBS/CBS) | Rules with effective dates, by state and municipality | Depends on the vendor | Depends on the accountant |
| Sefaz outage | Per-state contingency | Varies | Waits |
| Reconciliation | Automatic | Manual | Manual |
Criteria observed across BrainCargo client operations.
Frequently asked questions
What is the difference between NF-e and CT-e?
The NF-e (model 55) documents the movement of goods — whoever sells a product issues an NF-e. The CT-e documents the freight service — whoever hauls the load issues a CT-e. Operations that do both need both documents, and BrainCargo issues them in the same system.
Does NF-e issuing consume my CT-e quota?
No. The NF-e has its own independent quota. Carriers already on a CT-e and MDF-e plan keep that limit intact when they start issuing product invoices.
Is the system ready for the tax reform?
Yes. IBS and CBS rules are implemented as regulations with effective dates, including the rate reduction and calculation cut by state and municipality. Because the dictionary is versioned, older invoices remain auditable under the rule in force at the time.
What if my state’s Sefaz goes down?
The module has per-state contingency: issuing continues in the mode provided by legislation and invoices are regularized when the environment comes back.
Do I need a digital certificate?
Yes, as with any tax issuing — the A1 certificate is registered once and covers NF-e, CT-e, MDF-e and the operation’s other documents.
Issue NF-e in the same system as your CT-e
Talk to us on WhatsApp and see it working.
Modular pricing, sized to your operation: you only pay for the modules you use, and the plan scales with your volume. Ask for a quote on WhatsApp.