Invoicing

Invoices are first-class documents in /invoices/ with line items carrying individual tax_rate and tax_amount fields; the Invoice rolls these up into subtotal, tax_total and total. Two automatic generators run on business events: /invoices/auto-generate/license-renewal accepts a list of fee_components (name, amount, recipient type), pulls the default InvoiceTemplate, applies its tax_rate and payment terms and assigns a sequenced number per season, while /invoices/auto-generate/affiliation issues a single-line invoice for club affiliation. Branding lives in the tenant-scoped InvoiceTemplate collection — logo, primary and secondary colour, header and footer text in i18n, issuer identity (name, address, organisation number, VAT number) and payment instructions; exactly one default template per tenant is enforced.

Multi-issuer invoicing distinguishes platform-issued, tenant-issued and OrgNode-issued invoices via Invoice.issuer_type plus issuer_tenant_id and issuer_org_node_id, enabling cross-tenant invoices such as FIPJP billing a national federation; validators enforce consistency and a backfill script tagged historical invoices as platform-issued. Multi-language PDFs render from templates/invoice/{template_name}/{lang}.html with English fallback and a structlog warning when a translation is missing; platform invoices are locked to English. The ECB reference rate captured at issue time travels with the Invoice for cross-currency audit.

PDF delivery runs through GET /invoices/{id}/pdf for download and POST /invoices/{id}/deliver for emailed delivery, which marks the Invoice delivered and emits INVOICE_DELIVERED notifications. Credit notes are modelled as their own CreditNote documents with line references back to the original Invoice, sequenced as CN-YYYY-NNNNNN per tenant, and progress through draft -> issued -> applied -> voided; the credit amount cannot exceed the remaining invoice balance. Status changes append to status_history with from_status, to_status, changed_by and reason; POST /invoices/mark-overdue is a cron-friendly batch that flips due-date-passed invoices to overdue.

Reminder cadence is configured per tenant via ReminderConfig (max_reminders 1-10, grace_period_days 0-90, schedule of days_after_due offsets, escalate_to_collection_after); /invoices/send-due-reminders runs the entire cycle and /invoices/reminder-queue previews the next batch. Outstanding sent / overdue / partially_paid invoices block club transfer (PL-301) and licence renewal through /debts/check/{debtor_id}.