Access key in the Id attribute
- Input
- Id="NFe35261011222333000181550010000001231123456783"
- Expected output
- 35261011222333000181550010000001231123456783
The key is the 44 characters after the word NFe; the last one is the check digit.
read nfe xml file
Open the invoice .xml file in the viewer and the NF-e tab shows the access key, issuer, recipient, items with taxes, totals and the authorization protocol, all read inside your browser.
The key is the 44 characters after the word NFe; the last one is the check digit.
The decimal point is the file's own; the NF-e tab shows the same value in reais.
Each det is one item, numbered by nItem.
Value 2 is homologation: a test invoice with no fiscal value.
It matches the header vProd, so the NF-e tab shows the check as passing.
That is the sample vNF, by the total composition rule.
Drop the file on the upload area or pick it with the button. The tool detects the encoding (UTF-8, UTF-16 or the one declared in the header, such as ISO-8859-1), shows the formatted text and builds the tree. You can also paste the content. Any text editor or browser can open XML, but only here do you get formatting, a tree, search and NF-e reading in one place with nothing to install.
No. The DANFE is a printed sheet generated from the XML to travel with the goods. The same data, plus some that do not fit on paper, is in the file, and the viewer lays it out as issuer, items, totals and payment.
No. The XML is read and parsed in the browser itself, with no upload and no external lookup. That matters because an invoice carries tax IDs, addresses and business amounts.
The readable view covers NF-e and NFC-e. For CT-e and MDF-e the viewer names the type and you browse with the tree, the search and XPath, which work on any XML.