Billing & permitting automation for energy
Turn energy paperwork
into execution.
We didn't start with AI. We started with the problem—utility formats that change without warning, edge cases that break spreadsheets, midnight reconciliations when something doesn't match.
Gridline handles the whole cycle so you don't have to.
from utility statement to subscriber invoice. automatically.
Measured outcomes
Real numbers from production
Published metrics from the billing workflow running in production
Cycle time
10–30 min
Close a billing cycle in 10–30 minutes per project vs 1–3 days manual. From bill PDFs to delivered statements with full audit trail.
Straight-through rate
96.4%
Only low-confidence parses and rule violations route to review — 50–80% fewer manual touches. Exceptions are actually exceptions, not the norm.
Artifacts per run
7-12 outputs
Generate 7–12 auditable artifacts per run: bill.pdf, extraction.json, ledger, statement.pdf, invoice, email event, audit log. Every step traced.
See Gridline Platform in action
Community solar billing was our first workflow. Real screens, no mockups.
Track record
Built on real operational knowledge
Not just document AI. Domain expertise built into every extraction.
Positioning
Why not just use a general document tool?
You could run utility bills through any document AI. It'll extract text. Maybe even some numbers.
What it won't do:
- Know that a "community solar credit" isn't the same as a "payment received"
- Understand how allocations work across subscriber classes
- Recognize when a format change is routine vs. when something's actually wrong
- Handle the edge cases that aren't in any training set
We built Gridline on years of community solar billing—not just documents, but the operational knowledge of what matters and what breaks.
That's why most bills process automatically. And why exceptions are actually exceptions, not the norm.
| General Document AI | Gridline | |
|---|---|---|
| Training approach | General-purpose + prompting | Domain-specific training |
| Energy terminology | Learned from prompts | Native understanding |
| Edge case handling | Requires custom rules | Built into model |
| Utility format coverage | Build per customer | 30+ pre-built |
| Human review needed | Frequent | Exception-based only |
| New format adaptation | Days to weeks | Hours |
Before / with
The difference
What changes when manual processes become automated workflows
Before Gridline
With Gridline
- 2-5 days every month on billing
- Copy-paste from PDFs into spreadsheets
- Manual invoice creation, one by one
- Mistakes caught after invoices sent
- No vacation during billing week
- Billing runs complete in minutes
- Credits extracted automatically from PDFs
- Statements and invoices generated together
- Review flagged items before anything sends
- Full audit trail if anything looks wrong
The product
The universal workflow for energy projects
A six-step pipeline for any energy operations process — from document ingestion to delivery
Ingest
PDFs, forms, emails — any document type
bill.pdf Extract
Fields + tables pulled automatically
parsed_data.json Allocate
Apply rules, splits, rate schedules
allocations.json Generate
Statements, filings, packets
statement.pdf Sync
Create transactions in ERP/CRM/payments
invoice_id Deliver + track
Portal, email, full audit trail
delivered Production workflows
Running real billing on two continents
Each workflow is a config plus a few step functions on one universal pipeline — not a new app. Humans approve before anything with money attached moves.
| Workflow | Region | Systems it drives | Status |
|---|---|---|---|
| Community Solar Billing | United States | Utility bills · Google · PayPal · Resend | Production |
| Solar Project Billing (SolarAbo) | Switzerland | SolarManager · Bexio · Google · Resend | Production |
| vZEV Invoicing | Switzerland | Zevvy (browser automation) · Bexio | Production |
| Interconnection & Permitting | United States | Utility portals · Forms · RFI tracking | Coming Q3 |
| Project Finance | United States | Data rooms · Compliance reports | Coming Q3 |
Product surfaces
One platform, four role-aware experiences
Behind all four: an automation worker executing steps, pausing for approvals, retrying safely, storing evidence.
Operations workspace
Admins & operators
Configure workflows, run and review billing, manage members and invoices, inspect audit history.
Partner console
Implementation partners
Run demos, track pipeline, manage action items, submit workflow requests, access sales assets.
Member portal
Energy members
Self-service bills, usage, savings, invoices, and change requests — cuts operator support load.
Secure statement portal
Invoice recipients
A signed, run-scoped link to one statement and invoice. No account, no access to anything else.
Safety is built into the flow
Paused by default
Every new deployment starts paused. Nothing runs live until you activate it.
Zero-write test runs
Reads are real, writes are previews. Pilot a workflow without risking anything.
Approval gates
Humans approve before anything with money attached moves. Approvals record a hash of the exact data reviewed.
Immutable evidence
Every run pins its exact version. Failed attempts, retries, and reruns are preserved — never overwritten.
What you get
Built for operations teams who need workflows, not features
Documents processed automatically
Upload PDFs, forms, emails. Gridline extracts data, applies rules, and generates outputs — no copy-paste, no manual data entry.
Human-in-the-loop when needed
Low-confidence extractions get flagged for review. You validate before anything gets delivered.
Full audit trail + reruns
Every workflow run is traceable. See exactly what happened at each step. Re-run any process without starting from scratch.
See it run.
Run a complete billing workflow with sample data. No signup. No sales pitch. Just the product.