Issued Invoices
Access prerequisites
- Permission (module):
viewInvoices - License/Feature:
FIAT_PAYMENTS - Menu container: GENERAL → Accounting group
What it is / when to use
Lists all invoices requested/issued to users based on operations performed on the platform. Unlike Manage Invoices (which configures the template per operation type), here you find the concrete records: for each operation that triggered an invoice request, you can see the user, the date, the amount, the operation type, the invoice identifier, and whether it has already been generated by the provider. This is the consultation and accounting/tax reconciliation screen for invoices — used during closings, audits, and tax inspections.
Prerequisites
- Permission:
viewInvoicesregistered for the operator's role (double permission — CPM enum on the backend + dynamic module in the DB). - License/Feature:
FIAT_PAYMENTSenabled in the tenant's license (Vault). If disabled, the item does not appear in the menu at all. - Dependencies on other screens: invoices only exist if there is an invoice configuration for the operation type (Manage Invoices) and if the integration with the invoice provider is active.
Step by step
- Go to the Accounting → Issued Invoices menu.
- Browse the table; each row is an invoice request generated by a user operation.
- In the Generated column, check whether the invoice has already been effectively issued by the provider.
- Click the receipt icon to open the invoice PDF/file (when already generated) in a new tab.
- Click the view icon (eye) to navigate to the details of the user who originated the invoice.
- Use Export to download the current list as a
.csvfile (separator;, with BOM, file nameinvoices_<date>.csv).
Filters and columns
| Filter/Column | What it shows | Data source |
|---|---|---|
| User / Name | E-mail of the user who originated the invoice | user.email (UserNFE record) |
| Date | Date of the operation that generated the invoice | when |
| Amount | Amount of the base operation for the invoice | amount (monetary value — BigNumber, see caveats) |
| Operation | Type of operation that originated the invoice | operation_type |
| ID | Invoice identifier | nfe_id |
| Generated | Whether the invoice has already been effectively issued by the provider (yes/no) | processed (boolean) |
| Actions | View user details / open the invoice file | — |
TIP
This screen has no search filters — it is a paginated listing with export. For date/user-based slices, use Export and process the CSV, or cross-reference with the IN 1888 Report.
Actions and modals
- Receipt (receipt icon): opens the invoice by building the URL
NFEBasePathUrl + nfe_idin a new tab. Only works when there is annfe_id(invoice already generated). The base URL is fetched from the backend (getNFEBasePathUrl). - View (eye icon): navigates to User Details (
/users/informations/details) pre-filled with the client's e-mail, to investigate the origin of the invoice. - Export: generates a
.csvof the current page with the columns: user, date, amount, operation, ID, and "generated".
Business rules / caveats
Attention
- The Generated = no column indicates that the request exists but the invoice has not yet been issued by the provider (processing or failure). Invoices with
processed = falsehave no file to open. - The invoice ID (
nfe_id) is the link between the internal record and the tax document at the provider — use it for tracking during audits.
- Financial values: the displayed value comes from the base operation and must be treated as BigNumber — no manual rounding; check the decimal places according to the currency/token of the operation.
- Idempotency: issuance follows the BillingService (bls-lib) idempotent financial standard. Reprocessing an already completed issuance is safe; an
E00021"already processed" response means the invoice has already been processed — treat it as success, not as an error.