Invoices
| Field | Value |
|---|---|
| Audience | public |
| Page type | reference |
| Area | sg-dashboard |
| Updated | 2026-05-14 |
How invoices work in SGEN — historical record, download, email delivery, reconciliation.
Invoices in SGEN are the historical record of every billing event against the account. Each invoice carries date, line items, total, payment method used, and payment state. This page is the Reference definition of the Invoices sub-page — what an invoice contains, how the history is structured, and how invoices are delivered.
What is this for?
Read this page when you want the structural definition of invoice handling — what each invoice carries, how the history is browsed, and how delivery works.
Good use cases
- You need to download a past invoice for accounting reconciliation.
- You are explaining to a stakeholder how SGEN handles invoice records.
- You hit a "where is the invoice for last month?" question and want the model laid out.
- You are designing internal SOPs around accounting handoff.
What NOT to use this for
- Step-by-step download procedures — open the relevant Guide.
- Per-customer pricing — customer agreement.
- Per-release shipped change — open What's New or Changelog.
- Issuing manual invoices for store transactions — out of scope.
How this connects to other features
- Billing Overview — parent Reference area.
- Subscriptions — what produces the recurring invoices.
- Payment Methods — what charged against each invoice.
- SG-Dashboard Overview — parent surface.
Definition
An invoice in SGEN is the historical record of one billing event against the account. The record carries identifying metadata (number, date), line items (what the invoice covers), the total amount, the payment method used, and the payment state.
The defining property is historical. Once issued, an invoice does not change. The record persists in the invoice history for compliance, reconciliation, and review.
Purpose
The purpose of this page is to define invoice handling as a Reference layer rather than as a configuration walkthrough. It explains invoice structure, history browsing, and delivery model.
Scope
This page covers Invoices at the Reference level.
The page covers:
- The structural shape of an invoice.
- The invoice history surface.
- Download and email delivery.
- The boundary against store-side transactions.
- Per-step download procedures — Guides.
- Per-customer pricing — customer agreement.
- Store-side customer transactions — out of scope.
Invoice structure
Each invoice carries the same structural elements.
Identifying metadata
Invoice number, issue date, billing period, account identity.
Line items
What the invoice covers — subscription charges, capacity adjustments, prorated changes from upgrades/downgrades, applied credits, taxes.
Total
The total amount due, broken into subtotal + tax (where applicable) + total.
Payment method used
Identification of the renewal-target instrument that charged against the invoice (or "manual" for invoice-based accounts).
Payment state
Paid, pending, failed. The state reflects the outcome of the charge attempt.
Account · Billing · Invoices
History
| Number | Date | Period | Total | Method | Status | |
|---|---|---|---|---|---|---|
| INV-1247 | 2026-05-01 | May 2026 | USD 149.00 | Visa ···· 4242 | Paid | Download |
| INV-1180 | 2026-04-01 | April 2026 | USD 149.00 | Visa ···· 4242 | Paid | Download |
| INV-1112 | 2026-03-01 | March 2026 | USD 149.00 | Visa ···· 4242 | Paid | Download |
| INV-1045 | 2026-02-01 | February 2026 | USD 99.00 | Visa ···· 4242 | Paid | Download |
Invoice history surface
The Invoices sub-page surfaces the historical ledger.
Browse by date
The default view is reverse-chronological. Operators see the most recent invoice first; older invoices descend from there.
Filter and search
Filters by status (paid / pending / failed) and by date range support targeted retrieval.
Per-invoice detail
Clicking into an invoice opens the per-invoice view with full structural detail (line items, total breakdown, payment method, payment state).
Delivery
Invoices are delivered through two channels.
Download from history
Each invoice is downloadable from the history surface as a PDF for accounting use.
Email delivery
The platform emails each invoice to the account's billing-contact email address at issue time. Email delivery uses the account-level email transport.
Constraints and boundaries
Invoices is a Reference area for the historical billing record. It is not a substitute for the customer agreement or for store-side transaction records.
Use this Reference for:
- Browsing the invoice history.
- Downloading past invoices for reconciliation.
- Reasoning about invoice delivery.
- Per-customer pricing — customer agreement.
- Store-side customer transactions — out of scope.
- Per-step procedures — Guides.
Public boundary
This page is intentionally public-safe. It does not expose internal billing engine internals or protected operational identifiers.
Examples
Example 1 — Accountant downloads last quarter's invoices
The accountant opens SG-Dashboard → Billing → Invoices, filters to the last three months, downloads each invoice for the quarterly reconciliation. The history surface supports the workflow without leaving SGEN.
Example 2 — Failed renewal produces a failed-state invoice
A failed renewal produces an invoice in failed-state. The operator sees the failed invoice in the history surface, opens the per-invoice detail to confirm the line items, and proceeds to the recovery flow.
Example 3 — Stakeholder asks "are all invoices accounted for?"
The platform lead opens the invoice history, filters to last quarter, confirms every invoice is in paid-state, and provides a clean record for the stakeholder.
Documentation guidance
Use this page as the structural definition for invoice handling. Procedural detail belongs in Guides; per-release behavior change belongs in What's New or Changelog.
Reading order
Open this page when scoping invoice retrieval or reconciliation. Pair with Subscriptions for the recurring-invoice context and Payment Methods for the charge instrument detail.
Related reading
- Billing Overview — parent Reference area.
- Subscriptions — what produces recurring invoices.
- Payment Methods — what charged against each invoice.
- SG-Dashboard Overview — parent surface.
Vocabulary cross-reference
- Invoice is the historical record of one billing event.
- Invoice number is the per-invoice identifier.
- Line item is one charge or credit on an invoice.
- Payment state is the outcome of the charge attempt (paid / pending / failed).
- Renewal-target is the payment method that charged against the invoice (per Payment Methods Reference).
Maintenance discipline
When invoice handling changes across releases (new line-item type, new download format, new email delivery option), update this Reference and log the change in Changelog. The structural shape stays valuable because the per-invoice anatomy stays small.
Related reading
| Topic |
|---|
| Billing Overview |
| Subscriptions |
| Payment Methods |
| SG-Dashboard |