Automatically create an invoice for an eligible booking
Generate a CRM invoice after a qualifying paid-service booking by an authenticated client contact.
What this feature does
Generate a CRM invoice after a qualifying paid-service booking by an authenticated client contact. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
Automatic invoice logic applies only when the module invoice option is enabled.
The booking must be external, created by a logged-in contact, linked to a paid service and have no existing invoice.
The configured tax mode is applied and the new invoice identifier is stored on the appointment.
Step-by-step workflow
- Enable and configure appointment invoicing.
- Set a positive price on the active service.
- Sign in as an authorised customer contact.
- Book the eligible service.
- Open the appointment and verify its linked invoice.
Important fields and decisions
What happens after completion
After this workflow completes, Britixo keeps the appointment and its supported relationships connected. Reopen the appointment and verify the saved status, date, timezone, customer or lead, service, provider, attendees, reminder state, calendar or meeting reference, invoice reference and history that apply to this feature. External email, SMS, Google, Microsoft or payment outcomes must be checked separately from the Britixo database save.
- Open the saved appointment and confirm the final status and source.
- Check the participant, provider, timing and timezone from the full detail page.
- Review the relevant table filter, calendar, history, report or linked invoice instead of relying only on a success message.
Controls, checks and common mistakes
- Guest booking alone does not meet the authenticated-contact condition.
- A free service should not generate a paid invoice.
- Verify tax and invoice status before customer communication.
- Use the least destructive correction and retain the appointment history when the booking existed operationally.
- Never bypass a permission, availability, approval, client-access or verification control by changing an unrelated route or setting.
