City of Tallahassee has lost their minds with billing periods lately. I've got five clients who received bills covering 39-42 days in December and January. One poor restaurant got a 41-day bill for $3,847 when their normal monthly bill runs $2,200-2,400. The city claims it's due to holiday scheduling and staff shortages, but this is ridiculous. Anyone else dealing with Tallahassee's billing chaos?
Tallahassee going crazy with 41-day billing periods
Brenda, we're seeing similar issues with other Florida munis. JEA has been better lately but smaller cities seem to be struggling with staffing. The key is making sure they're not double-charging for overlapping days and that demand charges reflect only the actual billing period. A 41-day period in winter should show lower demand than typical summer months unless there's heating load. Check the daily peaks to see if they're legitimate.
Rob's right about the demand charges. Here in Miami, FPL occasionally has extended periods but they're pretty good about accurate demand billing. Municipal utilities often have less sophisticated billing systems that struggle with irregular periods. Brenda, have you contacted the city manager's office? Sometimes political pressure works better than technical arguments with munis.
Manny, that's a good suggestion. The restaurant client is particularly frustrated because the 41-day bill covers Christmas and New Year's when they were closed several days. Their usage should have been lower, not 75% higher. I'm seeing demand charges of 127 kW when their normal peak is around 85-90 kW. Something is definitely wrong with either the meter or the billing calculation.
Brenda, that demand spike during a holiday closure period is a huge red flag. Either there was a meter malfunction or they're applying demand from a different period. Demand the interval data immediately - Tallahassee should have 15-minute readings that show exactly when that 127 kW peak occurred. If it happened while the restaurant was closed, you've got them dead to rights on a billing error.
This sounds like the same problem we had with Georgia Power a few years back during their AMI deployment. Meters were recording peaks that never actually occurred due to communication errors. The utility was applying phantom demand charges for months before they figured out the system glitch. Robert's advice about interval data is spot-on - that's the only way to prove what really happened.
Update: Got the interval data and you guys were absolutely right. The 127 kW "peak" occurred at 3:47 AM on December 27th when the restaurant was definitely closed and locked up. No way they had that kind of load - probably a meter communication error or data corruption. Tallahassee is now investigating all December and January bills for similar anomalies.
Brenda, excellent work on catching that phantom demand! Oklahoma munis have had similar issues with AMI rollouts. The scary part is how many customers probably just paid the inflated bills without questioning them. You might have uncovered a city-wide billing problem that affects hundreds of accounts.
Susan, you're absolutely right. Tallahassee admitted they found similar phantom peaks on over 200 commercial accounts in December and January. They're issuing credits automatically and implementing new validation protocols for demand readings. The restaurant is getting a $1,247 credit, plus they're waiving late fees that accumulated due to the inflated bills.
This is why we do what we do! Great detective work Brenda. Municipal utilities sometimes get sloppy because they think nobody is watching. Your persistence probably saved hundreds of businesses from phantom demand charges. Hope Tallahassee learned their lesson about proper quality control on billing data.
Following this thread from Kansas - we've seen similar AMI issues with Evergy and other utilities. Brenda's case is a perfect example of why interval data requests are so critical. Most customers would never think to question a 3:47 AM demand peak, but that timing made it obviously bogus. Filing this thread under my "phantom demand" reference folder.
Harold, definitely worth filing for reference. The other thing I learned is that Tallahassee's AMI system was defaulting to the previous month's peak demand when it couldn't get a valid reading. So accounts with historically high demand were getting stuck with phantom peaks every time there was a communication glitch. Absolutely crazy that nobody caught this for months.
Brenda, that default-to-previous-peak logic is a nightmare scenario for billing accuracy. It explains why the restaurant got hit with 127 kW when their normal peak is 85-90 kW. The system probably defaulted to their summer air conditioning peak from months earlier. This case should be required reading for anyone auditing municipal utility bills. Excellent work exposing this systematic error.
Final thought: This Tallahassee case highlights why irregular billing periods are so dangerous for customers. Extended periods give more opportunities for phantom readings and billing errors to compound. Municipal utilities need much better oversight of their AMI systems and billing validation procedures. Great teamwork everyone on helping Brenda solve this puzzle.