E-invoice Submissions
Customer invoices submitted as e-invoices because their profile submits automatically: sent, retrying with back-off, out of attempts, or not valid -- with the reason. Retry sends one again now.
Where to find it
- Module: Accounting
- Group: Close & Compliance
- Section: Finance Automation
- Screen: E-invoice Submissions
Address in the console: /accounting/einvoice-submissions
Read-only list · 10 columns · 2 actions
This list is read-only: its records are written by the work that produces them. A correction, where one is possible at all, is made where the record was created.
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| Invoice | Code | invoice_no |
| Customer | Text | customer_name |
| Profile | Text | profile_name |
| Format | Status | format |
| Document | Code | document_no |
| Attempts | Number | attempts |
| Of | Number | max_attempts |
| Next attempt | Date and time | next_attempt_at |
| Last error | Text | last_error |
| Status | Status | status |
What you can do here
Send what is due primary
Asks for confirmation: Send the e-invoices queued or due a retry now?
Retry primary
Asks for confirmation: Try this e-invoice again now?
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.