Skip to main content

Invoice detail

Clicking a row of the E-Invoicing list opens a modal with seven tabs along the top: Summary, Parties, Lines, VAT, Notes, History, PDF. The modal title shows the invoice's DOC / DCT / KCO triplet. At the right of the tabs, the Reviewed chip sets or clears the review mark of an invoice in error. A fullscreen toggle in the header switches between a windowed and a full-screen view.

Previous / next arrows (and the ← → keys) in the header move through the invoices of the list without closing the window — the same order and filters as the table on screen — with a position indicator (e.g. 3 / 50). Past the last invoice, navigation loops back to the first.

12345 / RI / 00070
⛶ ✕
Summary
Parties
Lines (8)
VAT
Notes 3
History (5)
PDF
Tab content — depends on the active tab

Summary tab (default)​

The Summary tab shows a coloured status badge at the top — with, under it, the status details and the Rule set the invoice was produced under (see Rule sets) — followed by action buttons (Edit UBL, Copy, Delete) on the right. Delete removes the invoice and every related record — log row (source XML, PA transaction reference, source file name), lifecycle, lines, VAT and validation — so a later run of the same document starts fresh and the watched folders can pick its source file up again. Deletion follows the same protection as Fix buyer: the button is hidden once the PA has processed the invoice, except for a 213 rejection with an addressing reason. Right under the badge, when the platform returned them, the current rejection reason, expected action and status note are shown inline, and the full status message sits in a collapsed group — expand it for the platform's long error text. The same values feed the custom actions as {message}, {reasonLabel}, {actionLabel} and {actionNote} placeholders (see Actions), with no list-view column needed.

Fix buyer​

The most frequent PA rejections are about the buyer's identifiers — SIREN (BT-47), SIRET (BT-46), intra-community VAT (BT-48) and electronic address (BT-49). A Fix buyer button opens a compact form pre-filled from the stored UBL, with the INSEE company search and the PPF electronic-address picker, to correct just those fields without re-editing the whole invoice. Only the changed identifiers are replaced inside the stored UBL — the rest of the document stays untouched — then the invoice is revalidated on the spot, an audit event records the old and new values in the history, and an option resends to the PA when validation passes. The button appears only while the invoice is still correctable — before the PA has taken it over, or when it was Rejected (213) for an addressing reason: ADR_ERR, REJ_ADR (the platform's addressing control) or DEST_INC (recipient unknown in the directory). In those three cases the invoice never reached the customer, which makes the resend safe; every other PA-processed status stays locked. A repair whose validation raises no error also marks the invoice Reviewed in the list. The buyer electronic address (BT-49) keeps the scheme already on the document — 0225 when there is none. The correction is logged as a plain history entry (Identifiants acheteur corrigés), without triggering the notification rule of the current status again, and the outcome of the new validation (9901 / 9902) is added to the history whenever it differs from the latest event. The keys stored on the row when the document was first processed (alpha key, customer number, business unit, routing code) are kept; the same applies to a save from the edit window. Format safeguards (SIREN/SIRET length and coherence, VAT shape) and the PA-protection rule apply — the same checks as the POST /api/invoices/{doc}/{dct}/{kco}/fix-buyer endpoint in the API reference.

Below the status, when the invoice is in a status that requires a follow-up action by the seller (e.g. 205, 206, 207, 208, 210, 213, 9904, 9907), a blue Seller actions banner appears with the recommended actions:

Seller actions
Mark payment receivedIssue credit noteCancel accountingIssue corrected invoice

Status-by-status mapping:

StatusSuggested actions
205 PaidMark payment received
206 Partially approved / 207 DisputedIssue credit note, Issue corrected invoice
208 SuspendedSend completed
210 RefusedCancel accounting
213 RejectedCancel accounting, Issue new invoice
9904 Send error / 9907 PA rejectedResend to PA

Each action is bound to an API connector endpoint configured in Configuration → API Connectors — clicking the button executes the connector with the invoice's data. Greyed-out actions (faded) indicate the connector is not configured for this deployment.

A second group sits below the regulatory one — Custom actions. Always-visible buttons configured on the Actions page; each fires its own chain of connector calls and is independent of the invoice's current status. The result banner is anchored to the group whose button fired — a custom-action failure does not stomp on a regulatory-action banner shown at the same time, and stale banners are cleared automatically when the modal closes or switches invoice.

The rest of the Summary tab presents collapsible groups:

  • Document — DOC / DCT / KCO, UBL number, invoice type, profile ID, contract / buyer / order / project references, accounting cost.
  • Dates & Currency — issue date, due date, currency, period start / end.
  • Amounts — total HT, total TTC, amount due.
  • Payment — payment means code, IBAN, account name, BIC, payment ID, payment terms.
  • Document allowances / charges — document-level discounts or charges with type, reason, amount, tax category.

Parties tab​

Three collapsible groups, populated from the UBL document:

  • Supplier — name, SIREN, SIRET, VAT identifier, electronic endpoint, postal address, contact (name, phone, e-mail).
  • Customer — name, company ID, electronic endpoint, VAT, address, contact.
  • Agent Party (optional) — for the French extension — name, address, country.
  • Delivery (optional) — date, party name, location ID, address.

A group with no data on the invoice is not displayed.

Supplier (BG-4)
Nomana-IT SAS
SIREN 123 456 789
SIRET 123 456 789 00012
VAT FR12123456789
📧 Endpoint 0009:12345678900012
10 rue de Paris
75001 Paris · FR
👤 Contact — accounting@nomana-it.fr
Customer (BG-7)
Acme Industries SA
SIREN 987 654 321
VAT FR98987654321
📧 Endpoint 0009:98765432100015
50 avenue des Champs
69002 Lyon · FR
👤 J. Dupont — j.dupont@acme.fr · +33 4 72 00 00 00
Delivery (optional · BG-13)
Acme — Lyon Warehouse
Delivery date 2026-04-26
Location ID 0088:3012345600003
Zone industrielle Sud
69800 Saint-Priest · FR

Lines tab​

A table of the invoice line items, one main row per line plus sub-rows that surface the additional information carried by the UBL.

Description
Quantity
Unit
Unit price
Line amount
Tax cat.
Rate
Consulting service — financial reporting
5.00
DAY
800.00
4,000.00
S
20%
↳ Period: 2026-04-01 → 2026-04-30 · Buyer ref: PO-2026-042
Office supplies — paper A4 80g/m²
20.00
EA
25.00
500.00
S
20%
↳ Item code: SKU-A4-80 · Allowance: −2.5% volume rebate
Software licence — annual subscription
1.00
EA
1,200.00
1,200.00
AE
0%
↳ Note: Reverse charge — VAT due by the customer (EU intra-community)
ColumnDescription
DescriptionFree-text description of the line item.
ItemItem identifier (article code, SKU).
QuantityQuantity invoiced.
UnitUnit-of-measure code (e.g. EA piece, H87 unit, DAY day, KGM kilogram).
Unit priceUnit price excluding VAT. Shown to its full precision — up to 6 decimals (BT-146), matching the source. EN 16931 allows finer precision on the price than on the monetary totals, which stay at 2 decimals.
Line amountQuantity × unit price (excluding VAT).
Tax categoryUBL VAT category code (S standard, AE reverse charge, E exempt, Z zero rate, O out of scope, K intra-EU, G export, L Canary Islands, M Ceuta/Melilla).
Tax rateApplicable VAT rate as a percentage.

Sub-rows appear under each main row for:

  • Item description
  • Period (start → end)
  • Buyer / standard / classification item identifiers
  • Line note (BT-127)
  • Price-level allowance / charge (BT-147)
  • Line-level allowances / charges (BG-27 / BG-28)
  • Additional item properties (BG-32)

When several lines share the same delivery group, document references (BT-128) or customer order number (EXT-FR-FE-135), a delivery header, a document-reference header or a Customer Order Reference header appears once at the top of that group rather than repeating on every line.

VAT tab​

A table of the VAT subtotals carried by the UBL: category code, rate, taxable base, VAT amount, currency, exemption code + label (when applicable).

Category
Rate
Taxable base
VAT amount
Cur.
Exemption
S Standard
20%
4,500.00
900.00
EUR
—
AE Reverse
0%
1,200.00
0.00
EUR
VATEX-EU-AE · Reverse charge
E Exempt
0%
800.00
0.00
EUR
VATEX-FR-261 · Article 261 CGI
Total
6,500.00
900.00
EUR

Notes tab​

Document-level notes (BT-22). Each note appears as a card with a prefix badge (e.g. PMD, PMT, REG) and the free-text body. The prefix label is resolved from the note-types reference list; hovering on the badge shows the label.

PMD
Payment terms — 30 days net, end of month. Late-payment penalty 3 × ECB rate; recovery indemnity €40.
REG
Member of an approved trade association — payment by cheque accepted.
AAI
Order PO-2026-042 confirmed by the buyer on 2026-04-15.

History tab​

Three sections in this tab:

Action bar at the top​

ButtonBehaviour
Validate UBLRe-runs XSD + Schematron validation on the UBL stored in the database. The result is shown inline (valid / warning / error) with details when applicable.
Set statusOpens the Set Status modal — see below.
ResendSubmits the UBL to the Plateforme Agréée again. Confirms before running.
Download UBLSaves the archived UBL of the invoice.
Download CIIShown when the document has a post-transform: the archived UBL converted on demand, named after the post-transform (Download converted file when it has no name).

Lifecycle group​

The lifecycle is the audit trail of every status the invoice has been in. Each event shows:

  • The status badge (code + colour-coded family).
  • The status label and the message returned by the platform.
  • Optional details for refusals: rejection reason code + label, expected action code + label, additional status note.

The lifecycle is append-only — events are added by the Sync → Retrieve Statuses sweep and never modified. Each event does carry a delete button (with confirmation): removing an event realigns the invoice status on the last remaining one — the clean manual fix when the platform delivered a stray status (a Refusée it later superseded, say). It is gated by a dedicated Delete lifecycle event action in the roles.

The three refusal fields — rejection reason, expected action and status note — also live in the column catalog, so they can be pinned as list columns and filtered from the List Views editor when a team needs to scan or sort by refusal reason without opening each invoice.

9900 UBL generated2026-04-24 09:14:02
UBL document built from source XML and persisted in NomaUBL.
9906 Pending PA import2026-04-24 09:14:18
Submitted to the Plateforme Agréée — awaiting acknowledgement.
200 Submitted2026-04-24 09:15:47
Accepted by the addressing platform · technical ack returned.
202 Received by recipient2026-04-24 11:32:09
Acme Industries SA confirmed receipt on its Plateforme Agréée.
207 Disputed2026-04-25 14:08:51current
Customer raised a dispute — line 2 quantity does not match delivery slip.
Reason RR-016 — Quantity mismatch with delivery
Expected action AC-04 — Issue corrected invoice
Note — « Bordereau de livraison BL-2026-018 ne mentionne que 18 unités sur la ligne 2. »

Validation errors group​

Lists the validation errors (XSD / Schematron) that were recorded for this invoice. Each row carries the severity, the rule identifier and the human-readable message. Empty when the invoice validates cleanly.

PDF tab​

The PDF tab renders a generated PDF of the invoice inline (an <iframe> view). The bottom of the tab carries:

ButtonBehaviour
E-mailOpens the E-mail modal with the displayed PDF pre-attached.
DownloadSaves the PDF to the local computer.