Pro Services Billing

A ProServiceEngagement is the consulting contract scoped to one tenant: it pins the hourly rate at 150 EUR per hour, captures the estimated hour count and the billing contact. Time is recorded as TimeEntry rows with quarter-hour precision (multiples of 0.25); each entry moves through DRAFT (consultant's working state, never visible to the customer) -> SUBMITTED (locked for review, customer can see) -> INVOICED (rolled onto a ProServiceInvoice) or VOIDED. A safety guard caps any consultant at 24 hours per day across all engagements to catch data-entry errors.

Monthly invoicing runs as an idempotent job on the first of each month: it scans every tenant for SUBMITTED TimeEntries from the previous month, aggregates them per engagement, generates a ProServiceInvoice per tenant and flips the underlying TimeEntries to INVOICED. Idempotency means the job can be safely re-run without producing duplicate invoices. Financial separation is strict: every ProServiceEngagement, TimeEntry and ProServiceInvoice carries revenue_category = pro_services_consulting and is excluded from subscription ARR calculations — the platform's recurring-revenue metrics are not contaminated by one-off consulting income.

The customer-facing report exposes the customer's own SUBMITTED and INVOICED entries; consultant_user_id is hidden so the customer sees what they were billed for but not which individual consultant did the work, and DRAFT is never exposed. Admins get an Invoice preview before the monthly job runs so they can spot anomalies, and a separate Pro Services revenue report aggregates monthly and yearly totals separately from subscription revenue.