If you’re managing a Power Purchase Agreement (PPA), you already know how manual, error-prone, and unclear the allocation of Guarantees of Origin (GOs) can be. You’ve got contractual obligations to meet, volumes across multiple years and devices, and ongoing generation, but you’re likely still working with significant manual input requirements. Most systems leave you stuck in spreadsheets, organizing data by hand to make sense of things. Soldera doesn't.
We designed the PPA allocation process to eliminate that complexity for you. And if you’ve got devices in more than one country, we’ve also integrated with the complex map of registries in Europe. That means one account, fewer delays, smoother allocations, and a consistent overview of your PPA and GO position across jurisdictions. You don’t have to be the expert on any poorly designed registry interface, because our platform acts as an intuitive registry of registries by default.
Upload the Contract, Let the Platform Handle the Rest
When onboarding a PPA, whether physical or virtual (vPPA), upcoming or ongoing, you don’t need to worry about mapping every clause or term. Just upload the signed contract, and our platform pulls out the relevant data with guaranteed accuracy in device identifiers, volumes, timelines, and counterparties. Then it builds a portfolio configuration automatically. Using our highly refined AI tooling, your PPA logic gets implemented fast, cutting out all the manual data entry in your current workflow.
The GO Allocation Funnel: Everything Taken Care Of
Here’s how it works. First, our system checks for any PPA contracts linked to your devices. Each PPA portfolio is configured with expected volumes per year and per device. As new GOs are issued, they are matched and reserved for these PPAs until the contractual obligation is fulfilled.
The entire process runs automatically every night. If your assets have generated new GOs, our system detects them and routes them through a logical, priority-based funnel to meet your needs one by one: starting with PPAs (pre-arranged personal cancellations) and cascading through forward sales reservations, holds, and spot sales.
Each step in the allocation tree reduces the volume available to the next. The logic is clean, transparent, and built around what your portfolio needs. By the end, every GO with a purpose has been allocated properly, and you’re left with what you can send to spot. Have a play with our calculator by plugging in your own numbers to get a feel for things.
Allocation Calculator: GOs & PPAs
→
1,000 MWh/year
PPA Volumes
500 MWh
ON
Forward Sales
0 MWh
OFF
Hold
0 MWh
OFF
/MWh
Spot Sales
500 MWh
50.0%
Revenue
€0
- PPA Volumes: Your PPA volumes are completely ringfenced, reserved for their intended use.
- Forward Sales (if enabled): We then check for forward sales obligations. This will be the percentage you have previously configured in the Soldera platform based on your personal risk tolerance. If you have existing forward sales agreements, we can reserve allocation for those as well. This facilitates forward hedging.
- Hold: If there is still GO volume left over, we apply your portfolio’s hold settings, allowing you to retain a configured amount for later use.
- Spot: Whatever is left finally goes to spot aggregation and is sold automatically via Soldera’s frequent tenders to our network of highly active, competitive bidders.
The Business Case Beyond Time-Saving
If you’ve got PPAs, the reality is you’re already running an energy operation that demands your time elsewhere. On top of this split focus, if you're still dealing with system constraints, you can't make informed decisions about your EACs. You need a system that takes care of GO allocation in a way that reflects contractual reality, handles overlapping commercial strategies, and doesn’t force you into hours of spreadsheeting. You also need that system to play nicely with the rest of your certificate portfolio.
Soldera does all of that, and for free. We simply take a success fee on sales (where we usually fetch over-market prices). You upload a contract, the engine reads it, the nightly allocation loop kicks in, and you get real-time clarity.
