1001Ferramentas
📄Utilities

NFe XML Viewer

Reads and displays the main fields of a Brazilian NF-e/NFC-e XML: issuer, recipient, items, totals, ICMS.

What is it for?

An NF-e is really just an XML file following the standard SEFAZ defines. This page reads the key fields and lays them out visually so you can review them quickly, no dedicated NFe reader required.

It handles both the NF-e (model 55) and the NFC-e (65). You get the issuer and recipient, the line items, the totals and the access key.

All of the parsing happens right here through DOMParser. Your file never gets uploaded anywhere.

View an NF-e XML

All the information of a Brazilian electronic invoice lives in the XML, but in raw form that's nearly impossible for a human to read. This tool reads the NF-e and NFC-e XML and shows the main fields in an organised layout, almost like the invoice itself in front of you.

It brings up the issuer and recipient data, the access key, the list of items with quantity and value, and the invoice total, all split into clear sections. Tax fields (ICMS, IPI, PIS, COFINS) and fiscal codes (CFOP, NCM, CST) are not extracted. You can check an invoice that arrived, validate data before an entry, or simply make sense of an XML file without opening the fiscal system.

Since the XML carries fiscal and commercial data, the reading happens entirely in the browser and nothing leaves your device. It's a support tool for accountants and anyone handling invoices every day.

Frequently asked questions

Does it show ICMS and the other taxes on the invoice?
It doesn't. The screen brings five things: the access key, the issuer (name and CNPJ), the recipient (name and CNPJ or CPF), the item list with number, description, quantity and value, and the invoice total, read from the vNF field. No tax appears on its own — there is no ICMS, IPI, PIS or COFINS per item, and no CFOP, NCM or CST in the table. For fiscal work the XML still has to go into a full reader or into the accounting system.
Can I tell whether the invoice is valid and authorised?
You can't. The page reads what the file says and puts it on screen, checking nothing: the check digit of the 44-character key never gets recalculated, the digital signature never gets verified and the SEFAZ authorisation protocol never gets queried. A hand-edited XML looks exactly like a legitimate one. To confirm an invoice's real standing, the route is still a key lookup on the SEFAZ portal.
I parsed the file and everything came out as a dash with R$ 0.00.
That points to an XML that isn't a real NF-e or NFC-e, or to a file that arrived broken. The page never validates the structure: when the expected fields turn up missing, the panel opens anyway, with a dash in every slot and a zeroed total, and with no error message at all. The usual suspects are an event XML (cancellation, correction letter), a voiding request, a renamed DANFE PDF or just a fragment pasted in. Uploading drops the raw content into the text box, where the actual input can be inspected.

Related Tools