Appearance
Event Type To Billing
This guide explains how to test an event flow from setup through event creation, resources, observations, documents, inspection, charges, billing, and accounting review.
Use this flow for service visits, field work, inspections, maintenance events, billable activities, deliveries, training activities, or any operational activity that needs supporting evidence.
Workspace Reference
| Workspace | How Users Reach It | What Users Usually Do There |
|---|---|---|
| Event Types | Events -> Setup -> Event Types | Configure event category, billable behavior, required evidence, resources, and accounting handoff. |
| Document Transaction Types | Events -> Setup -> Document Transaction Types | Configure structured documents used by events. |
| Events | Events -> Operations -> Events | Create events, add participants, resources, items, charges, observations, documents, inspections, and workflow actions. |
| Document Transactions | Events -> Operations -> Document Transactions | Review documents linked to events. |
| Inspections | Inspections -> Operations -> Inspection Records | Record evidence and outcomes where the event needs QC or compliance checks. |
| Billing | Billing -> Operations -> Invoices | Bill approved event charges where needed. |
| Accounting And Reporting | Accounting and Reporting workspaces | Review event charge posting, reports, and operational history. |
Scenario
An organization performs a billable field service visit for a customer.
The team must:
- configure the event type
- create the event
- attach the customer, location, resource, and observations
- add charges
- attach or create supporting documents
- record inspection evidence if required
- approve or complete the event
- send approved charges to billing
- review invoice, payment, and accounting outcomes
End-To-End Flow
| Step | Workspace | Business Meaning |
|---|---|---|
| 1 | Event Type Setup | Allowed event behavior is defined. |
| 2 | Event Creation | Activity header is captured. |
| 3 | Participants And Resources | People, customer, location, and capacity are connected. |
| 4 | Observations And Items | Measurements, notes, and operational lines are recorded. |
| 5 | Documents | Structured evidence is linked. |
| 6 | Inspections | QC or compliance results are captured where required. |
| 7 | Charges | Billable lines are reviewed and approved. |
| 8 | Billing | Invoice is created or reviewed from approved charges. |
| 9 | Accounting And Reports | Finance impact and operational reports are checked. |
Key Steps And Fields
1. Configure Event Type
Open Events -> Setup -> Event Types.
Important setup fields:
| Field | Meaning |
|---|---|
| Event Type Name | User-facing activity type. |
| Category Or Domain | Groups event behavior and reporting. |
| Billable Flag | Determines whether charges can be captured and billed. |
| Product Or Pricing Reference | Optional link to the commercial item or pricing behavior. |
| Charge Posting Rule | Accounting rule for direct event-charge posting where billable events use it. |
| Resource Requirements | Indicates whether the event expects resource or capacity booking. |
| Evidence Requirements | Indicates whether documents, observations, or inspections are expected. |
2. Create Event
Open Events -> Operations -> Events.
Important event fields:
| Field | Meaning |
|---|---|
| Event Type | Determines visible tabs, required data, and lifecycle behavior. |
| Event Date And Time | When the activity happens. |
| Party Or Customer | Person or organization involved. |
| Location | Where the activity occurs. |
| Business Unit | Team or branch responsible. |
| Status | Draft, submitted, approved, completed, cancelled, billed, or related lifecycle state. |
| Notes | Activity context, exception, or instruction. |
3. Add Supporting Evidence
Use the event detail tabs to add:
- items or operational lines
- charges
- observations
- resources
- documents
- inspections
- workflow notes
Each tab should support the event purpose. Do not put structured quantities, charges, or inspection outcomes only in notes if the event type expects structured evidence.
4. Review Charges And Billing
For billable events, review charge quantity, unit price, discount, tax, approval, waiver, and submission status.
Approved charges can move into Billing. Billing remains the receivable workspace; Events records the activity and charge basis.
5. Review Accounting And Reports
Check invoice balance, payment allocation, charge posting, event status, and operational reports. Event completion and billing completion are related but not identical.
Pass Criteria For The Test Flow
The flow is complete when:
- event type controls required event behavior
- event captures party, date, location, status, and responsible unit
- supporting tabs show the right evidence
- inspection result is linked where required
- charges are approved before billing
- billing invoice traces back to the event or charge
- accounting and reports reflect approved financial activity
Common Problems
| Problem | What To Check |
|---|---|
| Event type missing | Event type setup, active status, permissions, and service context. |
| Charge cannot be billed | Billable flag, pricing, approval status, charge posting rule, and billing setup. |
| Resource conflict exists | Resource status, booking window, capacity slot, and existing bookings. |
| Inspection is not linked | Inspected record type, event reference, and inspection template. |
| Invoice does not match event | Charge approval, billing handoff, invoice lines, and reference fields. |
