Comment 9 for bug 1818917

Steven,

We tested this patch today! We found that it didn't work consistently. After puzzling it out a bit, we found that the issue most likely* has to do with the date in which the fine generator ran compared to the date in which the fine actually applies. Sometimes those two timestamps can be off by anywhere from a few hours to a few days! (because the fine generator cron job can be delayed for one reason or another). And if we're using billing_ts as the date in which the file applies, we'd be wrong. billing_ts is not* the timestamp for the fine, instead billing_ts is the time when the fine_generator got around to applying the fine.

We suggest that the SQL code compare the timestamp to money.billing.period_end. Regardless of when the billing period starts, the ending timestamp will give us an easy timestamp comparison which should* be a timestamp for the day/hour/minute that the fine applied.

-Jane's Monday wrangling test team-