Sales Invoicing is where ERP discipline either begins or breaks.
Create and Send a One-Off Sales Invoice looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: Customer receives a legally compliant invoice within seconds of posting; AR balance increases correctly; revenue is recognized on the invoice date.
The control flow a finance team actually needs.
Step 1
Invoice Number Be -Generated Sequential...
Step 2
Tax Auto-Calculate Per Line Item'S Tax...
Step 3
PDF Include Company Logo, Remittance...
Step 4
Posting Create A Balanced GL Journal Entry
Step 5
Duplicate Invoice Number Be Rejected...
The ERP surface involved.
Module
Sales Invoicing
Actors
AR Clerk, Customer, Email/Portal System
Tier
Tier 1
Finance area
Accounts Receivable & Order-to-Cash
Region lens
US and UK finance teams
Publication date
March 15, 2026
Invoice number must be system-generated sequential with no gaps; tax must auto-calculate per line item's tax code and jurisdiction; PDF must include company logo, remittance instructions, and payment link; posting must create a balanced GL journal entry (DR Accounts Receivable, CR Revenue, CR Tax Payable); duplicate invoice number must be rejected with 409; delivery status (sent/bounced/opened) must be tracked; non-functional: invoice creation to delivery < 3 seconds.
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | Invoice number must be system-generated sequential with no gaps | Given a posted customer master and at least one line item with a tax code |
| Control 2 | tax must auto-calculate per line item's tax code and jurisdiction | when AR clerk drafts and posts a sales invoice |
| Control 3 | PDF must include company logo, remittance instructions, and payment link | then system assigns a unique sequential invoice_number, computes per-line tax, creates GL entry DR accounts_receivable CR revenue CR tax_payable, sets status=SENT, and invoice appears on AR aging |
| Control 4 | posting must create a balanced GL journal entry (DR Accounts Receivable, CR Revenue, CR Tax Payable | negative) when clerk posts a second invoice with the same external_id then 409 DUPLICATE_INVOICE_NUMBER is returned. |
| Control 5 | duplicate invoice number must be rejected with 409 | Customer receives a legally compliant invoice within seconds of posting; AR balance increases correctly; revenue is recognized on the invoice date. |
| Control 6 | delivery status (sent/bounced/opened) must be tracked | Customer receives a legally compliant invoice within seconds of posting; AR balance increases correctly; revenue is recognized on the invoice date. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | AR clerk drafts a sales invoice selecting the customer, line items, quantities, unit prices, tax codes, and due date; the system assigns a sequential invoice number and computes totals including tax; clerk reviews and posts the invoice, which debits Accounts Receivable and credits Revenue; the system emails a PDF to the customer's billing contact and marks the invoice as Sent; the invoice appears on the AR aging report immediately. |
| Control rules | Invoice number must be system-generated sequential with no gaps; tax must auto-calculate per line item's tax code and jurisdiction; PDF must include company logo, remittance instructions, and payment link; posting must create a balanced GL journal entry (DR Accounts Receivable, CR Revenue, CR Tax Payable); duplicate invoice number must be rejected with 409; delivery status (sent/bounced/opened) must be tracked; non-functional: invoice creation to delivery < 3 seconds. |
| Acceptance proof | Given a posted customer master and at least one line item with a tax code; when AR clerk drafts and posts a sales invoice; then system assigns a unique sequential invoice_number, computes per-line tax, creates GL entry DR accounts_receivable CR revenue CR tax_payable, sets status=SENT, and invoice appears on AR aging; (negative) when clerk posts a second invoice with the same external_id then 409 DUPLICATE_INVOICE_NUMBER is returned. |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`sales_invoice` { id: invoice_*, external_id: string, customer_id: cust_*, invoice_number: string(sequential), invoice_date: date, due_date: date, amount_minor: int64, currency_code: char(3), tax_amount_minor: int64, status: enum, delivery_status: enum }; `invoice_line` { invoice_id: invoice_*, product_code: string, qty: decimal, unit_price_minor: int64, tax_code: string, tax_amount_minor: int64 }; many invoice_lines per sales_invoice; (reference, product may differ).API and events
`POST /v1/invoices` { customer_id, invoice_date, due_date, lines[{product_code, qty, unit_price_minor, currency_code, tax_code}], external_id } -> 201 { id, invoice_number, amount_minor, currency_code, tax_amount_minor, status }; `GET /v1/invoices/{id}`; `POST /v1/invoices/{id}/send`; emits `ar.invoice.posted` and `ar.invoice.sent`; idempotent via `external_id`.State transitions
`DRAFT -> POSTED -> SENT`; terminal `VOID`; guard: VOID blocked if any payment or credit memo is applied; POSTED requires balanced GL entry; SENT requires delivery attempt recorded.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.