William KimFinance × Engineering
Quick view

Financial systems

Fast Close Report Fix

A SQL-based close report that produced wrong data for months, traced to its defect and followed until it ran clean.

The Fast Close report is SQL-based, and it had produced wrong data for months. Wrong numbers in a close report are worse than none, because people act on them.

I wrote the SQL myself to isolate the defect, then gave the BI team the exact fix to apply.

Then I followed through for four months, close by close, until the August close ran clean.

Fast Close Report Fix: how the defect was closedThe SQL-based Fast Close report had produced wrong data for months. Diagnostic SQL isolated the defect. The exact fix was handed to BI to apply. Four months of follow-through, close by close, confirmed it, and the August close ran clean.SourceFast Close report, SQL-based, wrongdata for monthsProcessingDiagnostic SQL isolates the defectGuardrailThe exact fix, applied by BIHuman reviewFour months of follow-through, closeby closeOutputThe August close ran clean
Of follow-through, close by close
4 months
August close
Clean

Turn the diagnostic SQL into a standing check that runs before each close, so a regression shows up in hours instead of months.

  • T-SQL
  • Diagnostic queries
  • BI partnership