EP-MEL-13 — Reporting (Operational, Financial, Regulatory)
Companion: Backlog README ·
EPICS.md· canonical:07-epics-and-user-stories.md§15
Summary
| Wave | R1 (+ jurisdiction add-ons in R3) |
| Priority | P0 |
| Primary owner | reporting-service |
| Participating services | analytics-service, reservation-service, billing-service, payment-gateway-service, file-storage-service, notification-service |
| Journeys realised | J-12 (Daily / monthly reporting cycle) |
| Workflows | WF-12 |
| Frontend surfaces | Electron Desktop · Control Plane |
| Story count | 6 |
Outcome
Operational, financial, and regulatory reports run on a schedule or on-demand, render to PDF/CSV/Excel, can be emailed to recipients, are cached for offline access on the desktop, and (where mandated) export the daily guest registration in the local-government-required format.
Cross-cutting AC for this epic
- Every report carries a
report_idfor re-runnability and audit; inputs frozen at run time. - PII fields masked unless explicit role grant; export-to-third-party emits an audit event.
- Templates support en/ps/dr/ar/fa/tg/fr; numerals follow user preference.
- Recent reports cached in encrypted local store for offline desktop access (last 30 days).
Stories
| ID | Title |
|---|---|
| US-MEL-0105 | Operational report templates (occupancy, ADR, RevPAR) |
| US-MEL-0106 | Financial reports (folio, revenue, payment mix, taxes) |
| US-MEL-0107 | Daily guest registration export (regulatory, where mandated) |
| US-MEL-0108 | Scheduled runs and email delivery |
| US-MEL-0109 | Multi-format export (PDF/CSV/Excel) |
| US-MEL-0110 | Offline-cached recent reports |
Full AC in
../07-epics-and-user-stories.md§15.
Cross-references
- Compliance epic (jurisdiction rules):
EP-MEL-19.md - Definition of Done:
../standards/DEFINITION_OF_DONE.md