Last verified with: 10.8.6.0
Event subscriptions allow LogiSense Billing to react when specific business events occur. Administrators can use these events to trigger downstream actions such as webhooks, email notifications, or report generation when activity in the system reaches an important point in a workflow.
The events listed below use the same names that are shown in the user interface when configuring an event subscription.
| Event | What It Means |
|---|---|
| Account Service State Transition | Raised when an account service moves into a new effective state based on its configured dates and lifecycle timing. This is useful when other systems or teams need to react when a service becomes active, changes state, or reaches a scheduled transition point. |
| Account Status Change | Raised when an account changes status. This can be used to monitor lifecycle changes such as activation, suspension, or cancellation-related status movement. |
| Bill Run Started | Raised when a bill run begins processing. This is useful when operations teams or downstream systems need to know that a scheduled billing cycle has started. |
| Bill Run Completion | Raised when a bill run finishes. This can be used to trigger post-billing actions such as notifications, reconciliations, exports, or reporting workflows. |
| Invoice Posted | Raised when an invoice is created and posted by the billing process. This event is commonly used when other systems need to be notified that a billable document is now available. |
| Invoice Delivery | Raised when invoice delivery processing occurs. This is useful when you want to react to invoice distribution activity, such as confirming delivery-related processing or triggering follow-up communication. |
| Account Package Status Change | Raised when an account package changes status. This helps track package-level lifecycle activity independently from the overall account. |
| Credit Note Rendered | Raised when a credit note document has been rendered. This is useful when external processes need to react once the credit note output has been generated and is ready for delivery or follow-up processing. |
| Bucket Threshold Percentage Exceeded | Raised when a configured usage bucket threshold has been exceeded. This event is typically used for threshold monitoring, alerts, or customer communication when consumption reaches a defined percentage of a bucket. |
| Scheduled Report Generated | Raised when a scheduled report has been generated. This event can be used to trigger notification or delivery processes once the report output is ready. |
| Payment Processed Successfully | Raised when payment processing completes successfully. This is useful when integrated systems or customer communication workflows need confirmation of a successful payment event. |
| Payment Processed with Errors | Raised when payment processing completes with an error condition. This can be used to trigger troubleshooting, exception handling, or failed-payment communication workflows. |
| Usage File Processed | Raised when a usage file has completed processing. This is useful when teams want visibility into ingestion progress or need to trigger downstream processes after usage data has been loaded. |
| Payment Status Updated | Raised when a payment record changes status. This can be useful when downstream processes need to respond to payment lifecycle changes after the initial processing event. |