Energy
EPC milestone invoices, transformers and turbines booked years ahead, and a draw for the lender and the independent engineer every month. Kos checks every payment against the contract that governs it.
Kos reads all 812 pages of Ridge Electric’s pay app #14, ties out the distribution and generator lines, and flags switchgear billed ahead of the work, Hollis Supply’s missing lien waiver and retainage held at 2.5% where the contract keeps 5%. It recommends $754,300 of the $1,374,750 requested, drafted in NetSuite for your approval.
Procure-to-pay: Calder Power emails a milestone invoice to the AP inbox. Kos enters it as a bill in your ERP, matches it to PO-4512 and the signed factory test report, codes it, flags $4,860 of freight that isn’t on the PO, and saves the bill at $486,000, pending your approval.
Maya invites Kos to a video call and walks it through a bill on screen share, Kos asks who to tell when a bill doesn’t match the PO, then replays the workflow on a new bill in the ERP sandbox while she watches: it finds the prepayment already went out, tells the requester on Teams, and leaves the bill pending your approval.
The Problem
Three problems energy finance teams describe, and who feels each one most.
A deposit paid in 2026 meets a partial delivery in 2028, a price adjustment, and an invoice that matches neither the PO nor the receipt.
Felt most by procurement
The EPC contractor bills milestones ahead of the work, and equipment gets claimed before it ships.
Felt most by the CFO
The draw is due, the lender’s engineer is waiting and COD won’t move, so you sign off on milestone invoices you couldn’t check.
Felt most by project accounting
It’s the most critical part of the construction project. Like if people don’t get paid, there’s no project.
I just press send and I’m like, hopefully they don’t find that one.
Nobody in their right mind has the time to review it. So they’re getting scammed and things are getting missed.
It’s too hard to throw bodies at. And you have the attrition and people moving into different roles. And something’s almost getting dropped.
The Solution
The answer to each problem above: every equipment invoice matched, every milestone checked against the work, and every draw tied out before you press send.
The match holds on real life. Kos ties every deposit, progress payment and equipment invoice to the supply agreement, PO and delivery, so you know what’s paid and what’s owed on every order.
Learn more: Procure-to-payNobody bills ahead of the work. Kos checks every EPC milestone invoice against the contract, milestone schedule, change orders and retainage. At a hyperscale data center developer, review went from 7–10 days to the same day.
Learn more: Billing reviewNo more pressing send and hoping. Show Kos how your draw package comes together once on a screenshare, and it runs it that way every month.
How It Works
Nothing new for your team or your OEMs. The invoice goes to Kos the way it goes to a colleague, and comes back checked the same day.
Email Kos the OEM’s milestone invoice like you would a colleague, or ask it in Slack, Teams, iMessage or on a call.
The supply agreement, the PO and its milestones, the factory test report, and every deposit and payment already made.
A price adjustment over the cap, retention not held, or a missing storage certificate comes back with the page and clause behind it.
A line-by-line review in your Excel format, the questions to the OEM, and the bill drafted in your ERP for your approval.
Long-Lead Equipment
Transformers, turbines, inverters and breakers are ordered a year or more ahead and billed in milestones. Kos matches each milestone invoice to the supply agreement and the payments already made, checks the backup for anything billed before delivery, and holds what the contract caps.
What It Catches
Each flag comes back with the clause behind it, before the draw goes out. What you recover is your call.
A transformer milestone billed before its factory test, or a deposit invoiced twice.
Milestones
Price adjustments past the supply agreement’s cap, or over the PO’s remaining balance.
Supply agreement
Bills coded to the developer instead of the project LLC that owns the PO.
Entity
Inverters and modules billed before they’re received on site.
Receipt
Equipment billed before delivery with no storage or insurance certificate.
Stored materials
Percent complete billed past what the independent engineer’s report shows in place.
IE report
In Your ERP
Kos works inside your ERP with its own login, like a new hire, whether that’s NetSuite or another system. Nothing to install, and nothing posts until your team approves it.
Solvane emails INV-5531 for seven inverter skids to the AP inbox, where Kos has its own address. Or forward it to Kos as you would to a colleague.
Kos opens PO-6144 and its receipts in your ERP. Shipment 2 bills seven skids, and five have arrived on site.
Cinder Basin Solar, cost code 48-1400, GL 1710. Two skids aren’t on site yet, so Kos flags $620,000 and recommends $1,550,000.
The bill waits as pending approval with the flag noted. Nothing posts until someone on your team approves it.
Not New Software
Kos has its own email address and accounts, like anyone you hire. Forward it an EPC pay app, ask it about an equipment delivery in Slack, text it about the draw or bring it into a call. Nothing to install.
Invite Kos to a Zoom, Google Meet or Teams call and share your screen. Show it how you check an OEM milestone invoice once, and it checks the next one the same way.
Instead Of
What energy developers reach for today, next to a colleague who reads every page.
| Compared on | Accountants | Owner’s engineer | Deposit trackers | Frontier LLMs | Kos |
|---|---|---|---|---|---|
| Time per invoice | Days of accountant time | Days, billed by the hour | As fast as someone types | Hours of prompting and checking | Same day |
| What gets read | A sample of the backup | The site, not every invoice | What someone typed in | The pages you upload | Every page, against the contract |
| Where the work lands | Spreadsheets and email | A monthly PDF report | One more spreadsheet | A chat reply | Your Excel, inbox and ERP, once you approve |
| How you work with it | Hire, train, retain, per project | Engage, wait, pay by the hour | Update, reconcile, repeat | Build, prompt, check every draw | Email, Slack, a call |
| What it takes to start | Months of hiring | A statement of work | A template to maintain | A custom build on the models | Forward one milestone invoice |
Outcome
Kos reads every milestone invoice, equipment invoice and draw, and your team approves what goes out.
Every milestone invoice is checked against the EPC schedule and the work in place, every equipment invoice against the PO and delivery, and retainage stays at what the contract says.
Each invoice comes back reviewed the day it lands, so the draw ties out before the lender’s engineer asks. The EPC and your OEMs get paid on time, which protects your place in a years-long equipment queue.
Kos works in your email, Slack and calls like anyone on your team. Ask it at 11pm how much you’ve paid against the transformer order, and it answers with the page behind the number.
You Stay in Control
Who It’s For
For the developers and owners who pay for their own generation and storage, and the finance teams inside them.
Every project is its own LLC, with its own EPC, equipment orders and lender. Kos checks each EPC milestone invoice against the contract before the draw.
For the CFO and project accounting
Turbines and transformers are booked years ahead, often to power data centers. Kos tracks every deposit and milestone against the supply agreement.
For procurement
A fleet of projects is a fleet of entities. Kos codes interconnection, O&M and utility invoices to the project LLC that owns them.
For finance across projects
Kos reads every page, not a sample, and shows the page and contract clause behind every flag. On a hyperscale data center developer’s pay apps, it caught every human finding, plus 46% more.
Nothing posts until someone on your team approves it. When Kos is unsure about a line, it asks instead of guessing.
There’s nothing to implement. Kos gets a login like a new hire, and your team emails it the invoices.
Yes. It reads whichever contract governs the payment, from the EPC contract to each supply agreement, and fills out your draw workbook in your columns.
Yes. Kos reads the OEM’s invoice and the EPC’s pay app against the same schedule of values, and flags any line billed on both.
Kos works inside your systems under its own identity, with only the access you grant, and every action is logged.
No. They keep sending milestone invoices to the same inbox.
A project accountant takes months to find and covers a few projects. Kos covers every project from the day it starts, to the same standard.
Why Now
Up from 53 GW built in 2025, itself the most since 2002. Every gigawatt is an EPC contract, a stack of supply agreements and a draw your team has to check.
86 GW
of new US power plants planned for 2026
Up from $124B in 2019, with $1.4T planned through 2030. You compete with them for transformers, turbines and crews, and every slot you reserve becomes a deposit to track.
1.9×
utility capital spending, 2026 against 2019
Every price move reaches your desk as an escalation on a milestone invoice, and someone has to check it against the cap in the supply agreement.
+30%
turbine prices, August 2026 against 2019
Up from 36 months in 2015. All that time, study deposits, upgrade invoices and equipment payments go out, and each one has to tie to its agreement.
61 months
from grid request to power, median project built in 2025
No new software to learn. Email Kos the work and watch it run.
