Community solar subscription
How do we subscribe a customer to a community solar project with the allocation recorded and the credits applied on the bill under the program's rules?
Treat the subscription as a verified allocation with a bill credit behind it. Callvu identifies the customer and prefills the account (the premise, the rate, the usage history that sets the allowed subscription size, any existing subscription), takes the subscription from the customer or the subscriber organization's feed (the project, the share in kilowatts or a percentage, the start date, the subscriber organization's disclosures and the contract), checks the program's rules (the size cap against usage, the project's available capacity, the low-income carve-out where applicable, the one-subscription rule, the geographic eligibility), chases the signed disclosure and the consent to share billing data with the subscriber organization, routes a cap or eligibility exception to the program desk in the Decision Desk, writes the allocation to CIS and the billing system with the credit rate and the start cycle, and reconciles each month's generation allocation so the credit on the bill matches the project's output.
In scopeComplex: multi-party handoffsCallvu moves: prefill, chase and verify, write back
Last updated November 7, 2026.
The problem today
The subscriber organization sold the customer a share bigger than their usage allowed, the credits rolled over unused, and the utility's billing team fielded the complaint.
Community solar brings a third party into the bill: the subscriber organization sells the share, the project generates, the utility allocates the generation and credits the bill. The subscription arrives as a spreadsheet from the organization; the allocation is keyed; the credit rate depends on the customer's class and the program's vintage; the customer sees a credit that does not match what they were promised, or none, and both the organization and the utility blame the other.
The state's community solar program rules set the eligibility, the subscription size limits against the customer's usage, the project caps and the low-income carve-outs, the consumer protection disclosures the organization must provide, the consent to share billing data, the credit rate and its application, the allocation reporting between the organization and the utility, and the transfer and cancellation rules. The subscription is a rule check and a billing write; the monthly allocation is a reconciliation.
A subscription checked against the rules at enrollment is a credit the customer can trust.
How it runs
From the requestto the system of record.
A customer subscribes through the subscriber organization, the utility's portal or a call, or the organization submits a subscription feed. Callvu opens the subscription on the account.
- Customer
- Confirms the subscription, signs the disclosure and the data consent on a secure screen.
- Subscriber organization
- Submits the subscription and the monthly allocation through its feed and receives the acceptance or the rejection.
- Program desk
- Decides cap and eligibility exceptions in the Decision Desk.
- Callvu
- Prefills, checks the rules, chases the signatures, routes, writes and reconciles.
Prefill and take the subscription
The account, the premise, the rate class, the twelve-month usage (which sets the allowed subscription size under the program's rule), the geographic eligibility and any existing subscription are prefilled; the subscription captures the project, the share, the start date, the organization's identity and the contract reference.
Check the rules, chase and verify the consents
The program's rules run: the share against the usage-based cap, the project's available capacity and its subscriber mix requirements (the low-income carve-out, the small subscriber share), one subscription per account, the project in the customer's service territory or zone; the customer's signed disclosure (the program's required consumer disclosure with the credit rate, the fees, the term and the cancellation terms) and the consent to share billing data with the organization are chased and captured on a secure screen.
Decide and write back
A subscription that passes is accepted by rule; a share above the cap, a project at capacity, an eligibility question or a customer with a conflicting subscription goes to the program desk in the Decision Desk with the checks and only the allowed outcomes (accept, accept a reduced share, waitlist, or reject with the reason to the organization and the customer); the allocation with the credit rate and the start cycle is written to CIS and the billing system and the organization receives the acceptance.
Reconcile monthly
Each month the project's metered generation and the organization's allocation file are received, checked (the allocations total the generation, each subscriber's share matches the enrollment), the credits are computed at the program's rate and applied on each subscriber's bill, discrepancies are returned to the organization with the specifics, and a cancellation or a transfer is processed under the program's notice rules.
Where it ends: The subscription was checked against the program's rules at enrollment, the customer signed the disclosure and the consent, CIS and the billing system hold the allocation, and each month's credits match the project's output. The Decision Trace shows the rule checks and any decision; the Audit Trace shows the signatures, the write and each month's reconciliation.
Runtime enforcement
What is enforcedwhile the work runs.
The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.
The handoff
Between the front doorand the back office.
The front door
The subscriber organization's feed, the utility's portal or a call; the customer signs on a secure screen.
The back office
The program desk decides only exceptions; billing posts reconciled credits.
The Decision Desk
- A share above the cap, a project at capacity, an eligibility question or a conflicting subscription goes to the program desk in the Decision Desk with the checks and only accept, accept reduced, waitlist, or reject with the reason.
Proof
In scope.Proof at scale, not one process at a time.
The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.
More than 1,000 processes are live across Callvu customers.
Across Callvu customers
PSEG Long Island runs start, stop and move service on Callvu, live in 4 weeks.
Across Callvu customers
Questions
What buyers ask next,answered plainly.
How big a share can a customer subscribe to?
Up to the program's limit relative to their historical usage, checked against the twelve-month usage at enrollment, with the project's capacity and subscriber mix also applied.
What does the customer sign?
The program's required consumer disclosure (the credit rate, the fees, the term, the cancellation terms) and the consent to share billing data with the subscriber organization.
How are the credits checked?
Each month the organization's allocation file is reconciled to the project's metered generation and each subscriber's enrollment before the credits post on the bill.
Related processes
Bring this process, or the one that costs you most.
We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.