Raw user request follow-up from #111:
Connect sponsor bookings to invoicing and payment tracking so operators can see commercial follow-through without mixing finance controls into the CRM MVP. Define invoice-request/invoice artifact links, amount/currency/tax metadata, issued/due/paid/overdue states, payment reconciliation with bookkeeping #107, and alerts for missing or overdue invoices/payments. Determine the system of record and permissions before implementation; do not duplicate bookkeeping transactions or store bank data in sponsor records. Any real invoice creation, payment confirmation, or production finance write requires explicit human-controlled verification.
This issue needs PM grooming for the data boundary, API/UI flow, accounting integration, privacy/retention, idempotency, alerts, and test strategy. Depends on #107 and #111.
Raw user request follow-up from #111:
Connect sponsor bookings to invoicing and payment tracking so operators can see commercial follow-through without mixing finance controls into the CRM MVP. Define invoice-request/invoice artifact links, amount/currency/tax metadata, issued/due/paid/overdue states, payment reconciliation with bookkeeping #107, and alerts for missing or overdue invoices/payments. Determine the system of record and permissions before implementation; do not duplicate bookkeeping transactions or store bank data in sponsor records. Any real invoice creation, payment confirmation, or production finance write requires explicit human-controlled verification.
This issue needs PM grooming for the data boundary, API/UI flow, accounting integration, privacy/retention, idempotency, alerts, and test strategy. Depends on #107 and #111.