7. Order Invoiced
Step 7 is the final step in the Order-to-Cash process. The Finance system generates the invoice, which completes the entire order lifecycle. This step triggers accounts receivable processes and customer billing. The Log Event for this step is the only one in the Finance Domain.

Animated walkthrough: in BPM Log Search, open Show Details on the Order Invoiced event of order ORD-10005 (Tailspin Toys), then the Context Values tab with the step's business data. The walkthrough shows ORD-10005; the examples below use order 1.
Understanding Step 7
WMS (Logistics)"] --> This["fa:fa-file-invoice-dollar Step 7: Order Invoiced
ERP-Finance (Finance)"] This -->|"Log Event
O2C.Order.Invoice/1.0"| LogAPI["fa:fa-cloud-arrow-down Log API"] This --> Done["fa:fa-flag-checkered Order closed"] style Prev fill:#2678BD style This fill:#E47528 style LogAPI fill:#3F827B style Done fill:#93d16d
Step 7 (orange) receives the delivery proof (blue), logs to the Log API (teal), and closes the order (green).
Message Details
- Message Type:
O2C.Order.Invoice/1.0(Message Types) - Domain: Finance (Domains)
- System: ERP-Finance (Systems)
- Service: INT1337-INV-Order-Invoiced (Services)
- Direction: Send (outgoing from Finance)
- Format: JSON
- Log Status: Always
0(Success); an order that reaches Step 7 is complete, so the demo never marks this step with-1337 - Timing: In the generated data, 30-300 seconds after Step 6
Log Events in This Step
Step 7 logs two Log Events with the same Body. Only the business event appears in the BPM.
| SequenceNo (sent) | Service | Direction | EndPointName | Message Type | LogText | In BPM |
|---|---|---|---|---|---|---|
| 13 | INT1337-RCV-Invoice-Incoming | Receive | ERP-Finance-Invoice-Receive | O2C.Forwarding/1.0 |
Invoice Request Received | ❌ No |
| 14 | INT1337-INV-Order-Invoiced | Send | ERP-Finance-Invoice-Send | O2C.Order.Invoice/1.0 |
Order Invoiced | ✅ Yes |
The demo sends SequenceNo 1 to 14 per order. Nodinite keeps that value as the event's ServiceInstanceSequenceNo and gives the event its own SequenceNo, a running number in the Log Database.
Business Data (Happy Path)
The data of the order from Step 1, here order 1. Other orders carry their own customer, product, quantity, and total, the same in every step (see Generate O2C Demo Data):
- Order ID:
ORD-10001(same as source order) - Customer ID:
CUST-001 - Product SKU:
SKU-DEMO-001 - Quantity:
1 - Order Total:
USD 99.95
Sample JSON Message
This is the raw message payload that the Log Event carries base64-encoded in its Body field.
{
"invoiceId": "INV-2025-10001",
"orderId": "ORD-10001",
"customerId": "CUST-001",
"customerName": "Contoso Corporation",
"customerEmail": "orders@Contoso.example.com",
"invoiceDate": "2025-10-21T09:15:00Z",
"dueDate": "2025-11-20",
"paymentTerms": "NET30",
"invoiceStatus": "ISSUED",
"invoiceItems": [
{
"lineNumber": 1,
"description": "Demo Widget",
"sku": "SKU-DEMO-001",
"quantity": 1,
"unitPrice": 99.95,
"lineTotal": 99.95,
"taxCode": "STANDARD",
"taxRate": 0.0,
"taxAmount": 0.0
}
],
"subtotal": 99.95,
"taxTotal": 0.0,
"shippingCharge": 0.0,
"invoiceTotal": 99.95,
"currency": "USD",
"paymentMethod": "INVOICE",
"purchaseOrder": "PO-2025-10001",
"trackingNumber": "TRK-20251016-10001",
"gl_account": "4100-Sales-Revenue",
"revenue_recognition_date": "2025-10-20"
}
Nodinite Log Event (JSON formatted)
This step creates a Log Event that the demo sends to the Nodinite Log API. See Log Event Reference for the O2C Log Event structure, and JSON formatted Log Event for every field.
Context Properties (Business Data)
The Context Options carry the business data and the Repository Binding:
{
"FileName": "ORD-10001-order-invoiced.json",
"OrderNumber": "ORD-10001",
"CustomerId": "CUST-001",
"CustomerName": "Contoso Corporation",
"OrderAmount": "99.95",
"ExtendedProperties/1.0#RepositoryBinding": "..."
}
The invoice id, invoice and due dates, and purchase order stay in the message body, not in the Context.
View the Message in Nodinite
With the demo Stylesheet installed, users read this JSON message as an invoice. In the BPM Viewer, or a Log View, open Action on the Order Invoiced event and choose View message formatted as 'O2C - View Order Invoice'.

The message rendered by the Liquid Stylesheet: bill-to, dates and terms, the invoice lines with tax, and the totals.
Key Points for Step 7
- Finance Domain Entry: First and only involvement of a Finance domain system (ERP-Finance)
- Revenue Recognition: Includes the GL account and revenue recognition date for accounting compliance
- Complete Order Closure: This final step closes the Order-to-Cash cycle
- Cross-Domain Closure: The Finance domain (Index 3, Step 6) receives delivery proof from Logistics to start billing
- Payment Terms: DueDate and PaymentTerms set accounts receivable expectations
- Complete BPM Journey: The BPM now shows all 4 domains and 7 steps with connectors
- Correlation Completed: The same Correlation ID completes the full traceability chain
Order-to-Cash Journey Summary
| Step | Domain | System | Message Type | SequenceNo sent (Receive, Send) |
|---|---|---|---|---|
| 1 | Sales | Portal | O2C.Order.Received/1.0 | 1, 2 |
| 2 | Planning | ERP | O2C.Order.Entry/1.0 | 3, 4 |
| 3 | Sales | Portal | O2C.Order.Confirmation/1.0 | 5, 6 |
| 4 | Planning | ERP | O2C.Order.Scheduled/1.0 | 7, 8 |
| 5 | Logistics | WMS | O2C.Order.Ready/1.0 | 9, 10 |
| 6 | Logistics | WMS | O2C.Order.Delivered/1.0 | 11, 12 |
| 7 | Finance | ERP-Finance | O2C.Order.Invoice/1.0 | 13, 14 |
Total Journey Time: In the generated data, each step starts 30-300 seconds after the previous one, so a complete order spans about 4-36 minutes (about 20 minutes on average). The business dates inside the messages (order on 2025-10-14, invoice on 2025-10-21) are fixed sample values.
Next Steps
- Order Invoiced Stylesheet — Render this message as an invoice
- Generate O2C Demo Data — Create the demo Log Events for all 7 steps
- Order-to-Cash Process Demo — Back to the complete process
Related Topics
- 6. Order Delivered — Previous step
- Log Event Reference — The O2C Log Event structure
- BPM