Currently, reporting around event registrations reflects the latest state of a registrant’s record (e.g., updated totals after cancellations or refunds), but does not provide a historical audit trail of changes made over time. This creates a gap for teams that need visibility into: what specific tickets or add-ons were cancelled how a registration changed over time and how refunds map to those changes While the Payments/Transactions report helps track the financial side (original payments and refunds), it does not provide a clear breakdown of what exactly was modified within the registration. Suggested enhancement: Introduce an audit log or change history at the registration level that captures: -> additions/removals of tickets or add-ons. -> changes made to a registration after initial submission. -> refund actions mapped to specific items. -> timestamps and (optionally) user/admin actions. Expected Outcome: -> Easier reconciliation for finance and audit workflows. -> Reduced need for manual cross-referencing between reports.