Fiscal documents
Documents > Fiscal documents (/fiscal-documents) gathers the "Notes received against the workspace's companies" — the NF-e (product) and NFS-e (service) invoices your suppliers issued against your registered CNPJs. They come in automatically through the integrations or by hand, and from here you reconcile them and turn them into bills.
These are the notes YOU receive, not the ones you issue. Smart Finance never emits or cancels a fiscal document — it stores, reads and reconciles what arrives. Cancelling or reissuing always belongs to whoever issued the note.
Where each note comes from
| Origin | How it enters | How it appears |
|---|---|---|
| nfe.io | automatic capture of received NFS-e service notes | Service notes, ready in the list |
| XML import | you send the files under "Import XML" | a single XML or a ZIP with the whole month |
| SEFAZ | lookup by access key | the note pulled from SEFAZ by its key |
A ZIP with the whole month works. Under "Import XML" you can drop a package with many XMLs at once — anything that already exists is skipped, and only what is new comes in.
Finding a note
The search box accepts "Search by key, number or issuer". The tabs split by type — All, Service and Product — and the filters narrow what matters:
| Filter | What it shows |
|---|---|
| No linked company | notes whose recipient CNPJ matched no company |
| With generated bill | notes that already became a payable |
| Without generated bill | notes not yet turned into a bill |
| Creation date | when the note entered the workspace |
Each note shows its status — Authorized, Cancelled or Undefined — and, when only the note's summary is known, the Summary marker.
A summary is a note without the detail. SEFAZ hands the recipient only the NF-e header until you acknowledge it — no items, no duplicates. A Summary note shows up in the list but has no items to check nor installments to turn into bills.
The linked company
A note is tied to a workspace company by the recipient's CNPJ. When no registered CNPJ matches, it stays No linked company — expected, not an error: the note may have been issued against a CNPJ you have not registered yet, or against a CPF.
On the note screen, when there is no link, a button re-links it — handy after you register the missing company.
Reading the note
Opening a note shows:
- Provider and Customer — legal name, CNPJ and address on each side.
- Amounts and taxes — service value, tax base, ISS and the withheld taxes (IRRF, PIS, COFINS, CSLL, INSS), with the net amount.
- Service (NFS-e) or Items (NF-e) — the description and fiscal codes, or the product list.
- Duplicates and Payables — the note's installments and the bills already generated from it.
Turning it into a payable
From the note's duplicates you generate the payables — one per installment. Notes with no duplicate use the due date you supply at generation time. What has been generated appears under the note's Payables tab, and the With generated bill filter separates in the list what has already been converted from what is still pending.
Downloading the files
| Action | What it does |
|---|---|
| Copy XML | copies the note's XML to the clipboard |
| Download XML | downloads the note's stored XML |
| Download all | builds a ZIP with the XMLs of every note in the current filter |
Not every note keeps a stored XML. A Summary note may have no XML — in that case "Download XML" is unavailable and the label reads "No stored XML".
Through the API
Fiscal documents are also exposed, read-only, on the v1 API under the finance.fiscal_documents scope:
- List fiscal documents — a paginated page, with filters by company, kind, status, source, key, number and date.
- Get a fiscal document by id — the individual note.
The xml_download_url the API returns points at the attachments resource, so fetching the XML bytes also requires the finance.attachments scope.
Related
- Payment receipts — the proof of a payment that leaves
- Attachments — where the notes' files are kept
- Payables — what a note turns into
- Integrations — the NFS-e capture through nfe.io