Energy AI agent · FERC forms and EQR
FERC Forms and EQR Filing AI Agent
Reconcile each reported figure back to the ledger account it was drawn from, run the six due dates and the taxonomy version in parallel, and hold the form for the officer who certifies.
- Typical delivery
- 4–6 weeks
- Deployment
- Your stack
- Named officer
- Date-bound
- After launch
- Agent Care
What this agent does
Builds the form, not the certification
In
- 01
A calendar year closes, and Forms 1, 2 and 6 fall due 18 April under 18 CFR 141.1, 260.1 and 357.2.
- 02
A service company year closes, and 18 CFR 366.23 sets 1 May for Form 60 or the narrative.
Reason
- 03
A planning year closes, and 18 CFR 141.51(b) reads on or before each June 1 — not 15 June.
- 04
A quarter closes, and 18 CFR 141.400 allows 60 days for a Major filer, 70 for a Nonmajor.
- 05
An EQR quarter closes, and 18 CFR 35.10b still sets 30 April, 31 July, 31 October and 31 January.
Decide
- 06
A due date lands on a weekend, and the 5:00 p.m. Eastern cut-off rolls to the next business day.
- 07
A taxonomy version lands, and the notice of 19 December 2025 made 2026-04-01 operative 26 March.
Out
- 08
A CFR table is scraped, and each EQR period sits against the following quarter's due date.
- 09
Execute write actions only inside the approval boundaries agreed during implementation.
Product statement
The agent assembles and reconciles; a named officer examines the report, certifies it and files it, and the respondent answers.
Example workflow
One form, ledger to filing
- 1Ledger and schedule data receivedTrial balances, subsidiary ledgers, transaction extracts or prior filings
- 2Filing context assembledThe respondent, the form it owes, the period, the due date and the taxonomy version in force
- 3Form draft assembledThe schedules, the accounts behind them, the gaps and completeness
- 4Controls appliedAccount-mapping checks, cross-schedule ties, date checks and completeness confidence
No human action required
Stages 1 to 4 run unaided, and no certification is made at any of them — the agent builds the form, and the compliance lane opens at the completeness gate.
Goes to the certifying officer to sign.
Adds a regulatory counsel read first.
Compliance review
The draft is held with its accounts, its gaps and the schedules they sit in.
Certify and file · Append evidence · Send to counsel
Filed — by a named officer
- 6Ledger and filing records updatedOnly where write access and records policy allow it
- 7Outcome evaluatedAccount provenance, schedule ties, counsel corrections and what review found
Corrections
Each counsel correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required
8 items
- Examining the report and stating personal knowledge.
- Applying the officer certification to any form.
- Stating that a figure conforms to the Uniform System.
- Deciding which entity is in scope for which form.
Automation boundary
Agent acts unaided
- ✓Bind each reported figure to the ledger account that carries it.
- ✓Read every due date from the rule text, not a summary.
- ✓Check the draft against the taxonomy version operative that day.
- ✓Reconcile each quarterly report against the annual one.
Nothing is certified or filed except by a named officer, inside the agreed boundaries.
- Judging whether a filing was in fact timely.
- Telling FERC that a respondent is in compliance.
- Setting the account a figure is booked to.
- Changes to the ledger or the filed schedules.
Example output
One schedule line, annotated
Our compliance reporting assistant builds packages from a register, naming no regime; this record is one form, one period, one account.
Filing draft · single form
Illustrative example- Form
- Form 3-Q electric, Major filer
- Drafted as
- Operating revenue, Account 447
- Period
- Quarter ended 30 June 2026
- Evidence of record
- General ledger extract, 6 August 2026
- Confidence
- Held uncertified
- Held for
- The certifying officer, by name
As received
Drawn from the general ledger and your account mapping — it reaches no further than they do.
What the record holds
- Ledger account and figure
- Taxonomy version
- Prior-year annual line
Why no conformity call here
The certification is an officer act, with 18 U.S.C. 1001 on its face.
What the score decides
Under the configured threshold a counsel read comes first, and only then the officer.
Action
Certify and fileAppend evidenceSend to counselValue
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value lands
Value 01 – 04
Every figure
From the account that carries it
Where the filing is used
Our trading and bidding agent holds each order for an authorised trader to release; a missed EQR is how that market-based rate authority gets suspended.
Six dates, one set of books
Forms 1, 1-F, 2, 2-A and 6 fall on 18 April; Form 60 on 1 May; Form 714 on 1 June; and the EQR four times a year — off one ledger.
What was screened, and not found
FERC screens filings each quarter and answers with deficiency letters and audits; no standalone late-filing penalty order was found for 2024 to 2026.
Build an evidence trail
The figure, the account it was drawn from and the officer who certified stay on the filing.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Ledger and financial systems
- General ledger
- trial balance
- Uniform System account mapping
Market and settlement data
- ISO settlements
- contracts
- EQR transaction records
Filing and docket
- eFiling
- eForms
- XBRL
- Taxonomy versions and validation
Agent
FERC forms and EQR filing
- Reads the due dates
- Assembles the form
- Holds for the officer
Corporate and entity records
- Holding company structure
- Service company agreements
Observability & evaluation
- OpenTelemetry
- Langfuse
- Supported monitoring/evaluation sources
Integration availability depends on the client's existing systems and API access.
Agent controls
Six rings between the model and the officer
Six rings, the innermost the tightest. What gets through all of them is drawn in the map below.
L6 · Outermost — last line of defence
Inward → L1 · closest to the model
- L1 – L2
- Test whether a draft may stand
- L3
- Puts the certification in a person's hands
- L4 – L5
- Keep the figure and the account behind it
- L6
- Holds the form undrafted when signals degrade
How Nestack evaluates it
Evaluate the whole assembly — not only the form that comes out.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the form an officer certifies
- E1Final-output evaluationDid the draft record the account behind each figure?
- E2Step-level evaluationDid the agent read the right form, the right due date and the operative taxonomy?
- E3Tool evaluationDid it read and write the correct ledger account and the correct period?
- E4Confidence calibrationDo low-confidence drafts actually attract more counsel corrections?
- E5Slice evaluationHow does performance change across specific forms?
- E6Business outcomeHow many drafts needed a correction before the officer certified?
Floor — the outcome the respondent answers for
Failure modes
Where each failure originates in the agent
Seven failure modes, each pinned to the stage of the agent it starts in.
Agent lifecycle
Direction of processing →
01 · Retrieval
1 mode
- IY-03
Stale ledger read
The balance read is not the one now closed.
Stage gathers
The ledgers, the accounts, the periods and the dates
02 · Reasoning
2 modes
- IY-04
Figure asserted, not sourced
A figure is drafted with no account behind it.
- IY-06
Scraped calendar read as rule
A due date is taken from a scraped CFR table.
Stage proposes
The schedules, their accounts and completeness
03 · Tool / write
2 modes
- IY-02
Thin draft passed forward
A draft goes forward without the counsel read.
- IY-05
Figure bound to wrong account
A figure is booked against the wrong account.
Stage writes
Only where write access and approval policy allow it
04 · Output
1 mode
- IY-01
Filed, provenance unrecorded
The filing stands with no account trail behind it.
Stage returns
The form an officer certifies and FERC reads
05 · Change / Version
1 mode
- IY-07
Silent taxonomy regression
A version change moves validation, not the draft.
Stage tracks
Model, prompt, form rules and taxonomy version
- Sev-1 · a form filed without an officer
- Sev-2 · a wrong figure reaches the filing
- Sev-3 · source degrades, draft holds unfiled
Affected slices
The quarterly report carries the corrections
A form-level account-provenance figure can read clean while the Electric Quarterly Report carries most of the corrections. Nestack reports the correction rate by form, not only in total.
Slice performance — reported separately, not only in aggregate
Illustrative example| Slice | Failure rate | Lift | Lift vs. threshold | Status |
|---|---|---|---|---|
| Electric Quarterly Reports | 9.4% | 3.6× | Review | |
| Form 3-Q quarterly reports | 6.8% | 2.6× | Review | |
| Form 60 service company | 4.2% | 1.6× | Watch | |
| Form 1 annual report | 2.5% | 1.0× | Normal |
Bar: correction-rate lift vs. Form 1 annual-report baseline · scale 0–4.0× · tick marks the 2.0× review threshold
2 of 4 slices over threshold
Evidence-linked improvement
What a stale taxonomy costs
The loop shuts when the stale taxonomy version is a regression case. That suite is what the next form built is measured against.
Improvement cycle · five stages
Switchback — the path turns at Improve and returns at Learn
- 01
Detect
Correction rate rises on the quarterly reports.
- 02
Diagnose
The schedule that validated last April and would not validate this one is traced back until one cause is left standing.
- 03
Improve
Any change goes out numbered, with the schedules that caused it attached.
- 04
Verify
One schedule case still failing is enough to hold the release back.
- 05
Learn
One case joins the suite, one line joins the filing record.
Learn → Detect
The return edge. The next form is measured against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, form assembly, evaluation, integration, then production validation and handover.
Workstream
Week 1Week 2Week 3Week 4Week 5Week 6
- 01Filing-calendar and automation-boundary discovery.Week 1
- 02Ledger, settlement and docket sources.Week 1, Week 2
- 03Account-provenance and schedule-coverage mapping.Week 1, Week 2
- 04Schedule and account ingestion.Week 2
- 05Form, period and account binding.Week 2, Week 3
- 06Completeness scoring and counsel routing.Week 3
- 07Officer certification workflow.Week 3, Week 4
- 08Ledger and docket-system integration.Week 5
- 09Account-mapping and schedule cases.Week 4, Week 5
- 10Guardrails and officer-signing controls.Week 4
- 11Filing-trail instrumentation.Week 5, Week 6
- 12Deployment, documentation and Agent Care handover.Week 6
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel
Final scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
| Capability✓ in scope · — not at this tier | PilotOne form, one year | ProductionProduction filing workflow | AdvancedMultiple forms / respondents |
|---|---|---|---|
| Introduced at Pilot | |||
| Form assembly to your accounts | ✓ | ✓ | ✓ |
| Named-officer release | ✓ | ✓ | ✓ |
| Account-mapping baseline | ✓ | ✓ | ✓ |
| Introduced at Production | |||
| Reporting by form | — | ✓ | ✓ |
| Certification workflow in your systems | — | ✓ | ✓ |
| Approved write-back | — | ✓ | ✓ |
| General-ledger integration | — | ✓ | ✓ |
| Introduced at Advanced | |||
| Multi-respondent filing duties | — | — | ✓ |
| Cross-form reconciliation packs | — | — | ✓ |
| High schedule volume | — | — | ✓ |
| Multi-form deadline controls | — | — | ✓ |
| Build price | From $5,000 | From $8,000 | Custom quote |
- Final build price
- Confirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
- Separate from build
- Build pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bring
We build with it
01Your general ledger and its account mapping
→Account-provenance mapping and schedule capture
Week 102Representative prior filings and transaction extracts
→Schedule binding, form logic and the provenance baseline
Week 203Your entity list and the forms each one owes
→Form mapping, account binding and the automation boundary
Week 104Access to relevant APIs, feeds or exports
→Ledger, settlement and docket-source assessment, then integration setup
Week 205Filings you would not want certified
→Schedule cases and the evaluation run
Week 406What no financial report may state
→Completeness scoring, counsel routing, guardrails and release controls
Week 307A named officer to certify and file
→Officer certification workflow, then pilot and production validation
Weeks 5–6
Nothing else is required
Deployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Width here is worked time rather than layout space, and so two of the bands share the fifth week.
Phase
W1
W2
W3
W4
W5
W6
- DiscoveryW1
- BuildW2 – W3
- EvaluateW4 – W5
- Pilot & LaunchW5 – W6
Week focus
W1Filing workflow discovery, form mapping and the automation boundary
W2Source integration and the account-provenance baseline
W3Form assembly, schedule logic and release controls
W4Evaluation suite, schedule cases and failure-mode testing
W5Ledger integration, pilot filings and targeted corrections
W6One filing year run under the certifying officer, then Agent Care handover
- Reading the band
- Each bar runs over the weeks its own work is named for. Two of them share week five because the work does.
- At the end of W6
- Once the filing record validates, Agent Care assumes the agent.
- Duration
- Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Energy AI agent
Build a FERC filing agent around the six dates your books already owe.
Show us one form and the account behind one figure. A named officer certifies the Financial Reports, and no EQR certification text was found in primary rule. A Form 556 self-certification has been protestable since 31 December 2020.
- Typical delivery
- 4–6 weeks
- Deployment
- Your general ledger
- Named officer
- Date-bound
- After launch
- Agent Care available
Nestack Agents · FERC forms and EQR
AGT-EN-11 · Agent Care available after launch