Five to Seven Days of Manual Matching in a Thirty-Day Window
ERCOT's monthly settlement cycle produces invoice line items that must be reconciled against internal position records before disputes can be identified. For settlements analysts working in Excel against Openlink Endur records, that reconciliation is a manual, time-intensive process — and in a market where invoice complexity reflects nodal pricing, load zone settlement points, and ancillary service charges, the number of line items that require review can be substantial. Five to seven days of matching work at the start of each cycle doesn't leave much runway for building protest packages for the disputes you find, particularly when ERCOT's 30-day window under the Nodal Protocol doesn't move.
Automated Matching and Pre-Populated Protest Packages
An AI Labor Company agent mines historical ERCOT settlements reconciliation patterns and dispute outcomes from your Openlink Endur records, then deploys a Gemini agent that runs the invoice-to-position match automatically at month close. The agent compares ERCOT invoice line items against internal records, identifies discrepancies above your materiality threshold, and pre-populates ERCOT protest filing packages for each dispute flagged. The Director of Settlements receives a structured dispute queue rather than raw data to mine. The 30-day protest window starts with identified disputes and draft filings, not with a blank spreadsheet.
Revenue Recovery Within the Protest Window
Every legitimate dispute that expires unfiled inside ERCOT's 30-day window is revenue left on the table — permanently. The business case is partly efficiency (a 65–85% reduction in reconciliation labor) and partly revenue protection: ensuring that material invoice discrepancies are identified, documented, and filed before the window closes, every month, regardless of team bandwidth or competing priorities. The agent tracks protest window status per dispute so nothing ages out unnoticed. Teams in this position are typically live and running reconciliation on a production cycle in about 5 weeks.
How does the agent determine the materiality threshold for flagging disputes?
The materiality threshold is configured based on your current practice — whatever dollar or percentage threshold your settlements team applies when triaging disputes. This can be adjusted over time as your team's capacity and the market environment change.
Does the agent work with ERCOT's specific nodal settlement data format, or does it require reformatting first?
The agent is built to work with ERCOT's invoice data structure directly, alongside your Openlink Endur position records. No manual reformatting step is required in the reconciliation workflow.
Can this workflow extend to PJM Manual 28 reconciliation if we operate in both ISOs?
Yes. PJM's settlement data structure and protest procedures differ from ERCOT's, but the same agent framework can be configured to run parallel reconciliation across both markets with their respective filing window tracking.