Configuration steps
Create API credentials
Generate scoped tokens for billing integration.
Map invoice events
Define how paid, failed, and refunded events update bookings.
Test notifications
Send test webhooks and confirm delivery status.
Documentation
Connect billing with Plexidy.
Sync invoice status, trigger notifications, and keep finance teams informed.
Checklist
Item
Status
Token created
Scoped to billing
Webhook endpoint
Receives invoice events
Notification routing
Customers + finance copied
Rollback plan
Documented for billing changes
Simple test plan before go-live
Test
Expected result
Create invoice
Webhook received; booking tagged as invoiced.
Mark paid
Status updates in Plexidy and customer notified.
Mark refunded
Booking flagged and finance alerted.
Operational depth
Align billing integration procedures with finance operations timing
Billing integration documentation should show data handoff checkpoints, reconciliation cadence, and fallback actions for broken sync states.
Primary audience
Finance systems owners, integration engineers, and support specialists
Decision focus
Validate whether billing events are flowing and reconciling as expected across connected systems
Operational risk
Undetected sync delays create invoice disputes and downstream reporting errors
Field scenario
A billing event appears in one system but not another and a deadline requires same-day resolution.
Execution walkthrough
1. Frame the objective
Billing integration documentation should show data handoff checkpoints, reconciliation cadence, and fallback actions for broken sync states.
2. Align participants
Finance systems owners, integration engineers, and support specialists
3. Validate the decision
Validate whether billing events are flowing and reconciling as expected across connected systems
4. Mitigate known risk
Undetected sync delays create invoice disputes and downstream reporting errors
Interpretation matrix
Signal
Interpretation
Operational scenario
A billing event appears in one system but not another and a deadline requires same-day resolution.
Successful outcome
Successful use of this page leaves teams with clear direction on Validate whether billing events are flowing and reconciling as expected across connected systems.
If skipped
Skipping this step often introduces Undetected sync delays create invoice disputes and downstream reporting errors.
Recommended next step
Use integration detail and support contact paths when reconciliation fails after documented checks.