Use cases
Three billing workflows
in production on two continents.
Each one is a config plus a few step functions on the same universal pipeline - not a new app. Read how the pipeline works →
Use case 01
Community Solar Billing
Production United StatesUtility bill PDFs arrive in thirty-plus formats that change without warning. Gridline extracts credits and usage with confidence scores, applies subscriber allocation rules for MA SMART and MN Community Solar Garden program structures, generates branded statements, creates PayPal invoices with payment links, and delivers by email and portal - every step leaving audit evidence.
Use case 02
Solar Project Billing (SolarAbo)
Production SwitzerlandChallenge
Monthly SolarAbo billing across a portfolio: consumption data locked in SolarManager, invoices built by hand in Bexio, statements assembled manually.
Solution
Ingest from SolarManager, allocate per member, log to Sheets, create and send Bexio invoices, email statements - approval-gated before anything sends.
"We used to spend 3 days every month on billing. Now it runs in under an hour with full audit trails."
Use case 03
vZEV Invoicing
Production SwitzerlandChallenge
Consumption data only reachable through the Zevvy web interface - no export API for the billing flow. Every cycle meant manual portal navigation.
Solution
A hardened browser automation logs in, selects property and period, and downloads consumption; validation gates the data; Bexio invoices are created automatically.
Evidence built in
Every browser action captures a screenshot into the run details, so operators can replay exactly what the automation did, click by click. It is also the easiest thing to show in a live demo.
Operational depth
The edge cases are the product
Seven years of community solar billing means the hard parts are already handled:
Roadmap
On the roadmap
Planned workflows are never presented as available. These two are coming in Q3:
See a real run, end to end.
Run a complete billing workflow with sample data. No signup. No sales pitch.