Describe your process for validating data accuracy when building a dashboard for executive stakeholders.
Use the provided source and dashboard tables to demonstrate the validation process for monthly completed-transaction metrics. Return every month represented by either table and classify whether the dashboard values match the source calculations.
metric_month, source revenue and count, dashboard revenue and count, revenue variance, and validation_status.MATCH, MISMATCH, MISSING_DASHBOARD_MONTH, or UNEXPECTED_DASHBOARD_MONTH.metric_month ascending.metric_month, source_revenue, dashboard_revenue, revenue_variance, source_transaction_count, dashboard_transaction_count, validation_status.status equals completed, summing amount and counting every transaction.metric_month values exactly.revenue_variance as dashboard revenue minus source revenue, returning NULL whenever either revenue value is NULL.MATCH only when both revenues and both counts are equal, including zero values.NULL values rather than converting them to zero.| Column | Type | Description |
|---|---|---|
| transaction_idPK | INT | Unique source transaction identifier |
| transaction_date | DATE | Date of the transaction |
| amount | NUMERIC(12,2) | Transaction amount |
| status | VARCHAR(20) | Transaction processing status |
| Column | Type | Description |
|---|---|---|
| metric_monthPK | DATE | Month represented by the dashboard metric |
| reported_revenue | NUMERIC(12,2) | Revenue displayed in the dashboard |
| reported_transaction_count | INT | Transaction count displayed in the dashboard |
| refreshed_at | TIMESTAMP | Timestamp of the dashboard metric refresh |