Sponsorship & Grants
En resumen
Sponsorship and Grants captures every external revenue stream that does not come from members — sponsor records at Platinum, Gold, Silver and Bronze tiers, contract management with periods and amounts, exposure logging to evidence delivery, grant applications progressing through draft, submitted, approved and reporting, and OrgNode-level revenue allocation that splits sponsor income across federation, district and club according to negotiated percentages summing to 100.
Cómo funciona
Sponsors are managed through /sponsors/ as records carrying contact information, sponsorship tier (Platinum, Gold, Silver, Bronze) and the entities they sponsor. Each sponsor's contractual commitments live in /sponsors/{id}/contracts with amount, period and terms; renewal and termination are tracked on the contract document. Exposure obligations — logo placements, mentions, tournament naming — are logged via /sponsors/{id}/exposure so the federation can prove delivery against contract.
Grant applications follow a four-state lifecycle on /grants/: draft (freely editable), submitted (awaiting decision), approved (amount fixed, reporting deadline set) or rejected. Once approved, the federation files accountability reports via /grants/{id}/reports describing how the funds were spent — required by most public sports councils. Sponsorship revenue allocation runs through /sponsor-allocations/: an allocation is created with percentage shares per recipient OrgNode (federation, district, club) totalling 100 percent and amounts totalling the sponsor payment.
The allocation moves pending -> allocated -> reconciled, with each transition writing AccountingEntry rows on the corresponding OrgNode books. The reporting layer aggregates SponsorRevenueAllocation entries with status disbursed and GrantApplication entries with status approved or reporting into /financial-reporting/revenue-summary so non-member income shows up in the consolidated revenue picture alongside licence and competition fees. Reconciled allocations also feed the bookkeeping subsystem, writing AccountingEntry rows on the recipient OrgNode books with the correct revenue account and project code so the auditor can trace any sponsor euro from the original contract through to the bank deposit.
Capacidades clave
- Sponsor registry with Platinum, Gold, Silver and Bronze tiers driving exposure entitlements
- Sponsorship contract management with amount, period and renewal tracking
- Exposure logging at /sponsors/{id}/exposure to evidence delivery against contracted visibility
- Grant application lifecycle draft -> submitted -> approved -> reporting with mandatory accountability reports
- Per-OrgNode sponsor revenue allocation with percentage and amount validation summing to 100 percent
- Allocation lifecycle pending -> allocated -> reconciled writing AccountingEntry rows
- Aggregated revenue reporting that consolidates sponsor and grant income with member fees
En la práctica
A district secures a 30 000 EUR Gold sponsor for the year. She registers the sponsor at Gold tier, creates the contract with annual amount and exposure obligations (logo on bibs, mention at six tournaments) and books the first 15 000 EUR payment. She then opens /sponsor-allocations/, splits the income 60 percent to the district and 40 percent to two affiliated clubs running the supported tournaments.
After the first tournament she logs the exposure delivery — logo placement photographed, announcer script timestamped — so when the sponsor requests proof at year end, the exposure ledger is ready. In parallel she submits a 12 000 EUR youth-development grant; on approval she sets the reporting deadline and files the use-of-funds report through /grants/{id}/reports.
Funcionalidades de este subsistema
9| ID | Status | Funcionalidades |
|---|---|---|
| F08.05.01 | Entregado | Sponsor registry (company, contact, contract period, amount) ✅ PL-F0805 |
| F08.05.02 | Entregado | Sponsorship contract management ✅ PL-F0805 |
| F08.05.03 | Entregado | Sponsor exposure tracking (logo placement, mentions) ✅ PL-F0805 |
| F08.05.04 | Entregado | Grant application tracking (government, sports council) ✅ PL-F0805 |
| F08.05.05 | Entregado | Grant reporting and accountability ✅ PL-F0805 |
| F08.05.06 | Entregado | Sponsorship revenue allocation (competition, federation, club) ✅ PL-F0805 |
| F08.05.07 | Entregado | Grant application workflow — MinistryGrantApplication med 8-state-machine (draft → submitted → under_review → awarded → in_progress → reporting_due → closed; rejected som terminal-gren) ✅ PL-T223 |
| F08.05.08 | Entregado | Multi-stage status — capability-gated transitions via submit/record_decision/mark_in_progress/close med immutabel audit-trail ✅ PL-T223 |
| F08.05.09 | Entregado | Reporting-due reminder — daglig cron-trigg 30/14/7 dagar före closes_at, deduplicerad per bucket, status promoveras till reporting_due vid minsta bucket ✅ PL-T223 |
Subsistemas relacionados
Partes interesadas que necesitan este subsistema
Aparece en 3 análisis de partes interesadas