Who Signs a Solar Interconnection Application

Most of what goes wrong on a residential PV solar interconnection filing is not technical. It is a question of identity: which human being, or which legal entity, is entitled to sign.

The answer is not the installing contractor, and it is not always the person who signed the sales agreement.

Two tracks, two different counterparties

A residential PV solar project runs two approval tracks in parallel, and each one contracts with a different party.

The permitting side is intuitive: a licensed contractor pulls a permit under its own licence and carries the code responsibility. The utility side runs on a separate approval track with its own reviewer and its own clock. That relationship is set out in who is the contractor of record on a solar project.

The interconnection side surprises people. The utility is not regulating construction. It is agreeing to allow a generating facility to operate in parallel with its distribution system at a specific service address, and it makes that agreement with the customer who holds the account at that address. The contractor is a service provider to that customer, not a party to the arrangement.

What an authorisation letter actually does

In practice the contractor prepares the application, submits it, answers the utility's questions and chases it to permission to operate. It does all of that as the customer's authorised agent.

That authority has to come from somewhere, and it comes from a signed authorisation by the account holder. Many utilities publish their own form and will not accept a generic one drafted by the contractor. Where a utility runs an interconnection portal that allows a contractor to be registered as an agent against an account, the authorisation is usually still what establishes the permission.

Three properties of an authorisation worth understanding:

• It is scoped. It normally authorises action on the interconnection matter for a specific address. It is not a general power of attorney and it does not authorise the agent to change the account, the rate schedule or anything else.
• It does not transfer the obligation. The account holder remains the party to the interconnection agreement. An agent files, corresponds and submits. It does not assume the customer's obligations under the agreement.
• It can go stale. Where a project runs long, or where a home changes hands mid-project, an authorisation signed by a person who is no longer the account holder authorises nothing.

The last point is the one that catches people, and it connects directly to the ownership cases below.

The identity mismatches that stall filings

Every one of these is common, none is exotic, and all of them surface as a rejection or a hold with very little explanation attached.

One spouse signs, the other holds the account

The sales agreement is signed by whoever was home. The utility account is in one name. If those differ, the filing does not reconcile.

This is the highest-frequency case by a wide margin, and it is the cheapest to prevent: read the name on the current utility bill rather than assuming it matches the person in front of you. Note that "both are on the deed" does not settle it. The utility cares about its account, not about title, and the account is normally in one name.

The property is held in a trust

Living trusts are common enough in residential property that this is not an edge case. Where the title is held by a trust, the signature has to come from a trustee, signing in that capacity rather than personally.

Utilities differ in what they ask for. Some accept a trustee signature that identifies the trust; some request a certification of trust or an excerpt evidencing the trustee's authority. What none of them accept indefinitely is an individual signing personally for a property their trust owns, because that produces a three-way mismatch between the signer, the account name and the title.

The property is owned by an LLC

Investment properties, family holding companies and short-term rental entities all produce this. The signature has to come from a person with authority to bind the entity, in that capacity: a manager, a managing member, or an officer, depending on how the entity is structured.

The related trap is that the utility account may be in an individual's name even where the LLC owns the property, or the reverse. Both the signer and the account have to reconcile with each other, and both have to be defensible against the title.

The home was recently purchased

A property that changed hands in the last few months frequently still shows the seller as the customer of record, because account transfer is a task people complete late or not at all.

An application signed by the buyer against an account in the seller's name will not reconcile. The fix is not difficult, the account is transferred and the filing proceeds, but it is a fix that has to be initiated by the homeowner with the utility and it takes as long as it takes. The general principle is worth holding on to: transitions of ownership are where utility records and property records drift apart, and the drift is never visible from the project side.

A tenant is the account holder

A tenant can perfectly well be the utility's customer of record and still have no authority to authorise a permanent generating facility on somebody else's roof.

Expect the utility to require the owner's involvement. Expect the tenancy agreement not to answer the questions that then arise, about who owns the equipment at the end of the term and who is responsible for removal. This is a case to resolve at qualification, not at filing, because the answer is sometimes that the project cannot proceed in its current form.

The account name is a legacy or a variant

A surprisingly large number of applications are held up because the account is in the name of a deceased parent, a maiden name, an abbreviated form, or a spelling the utility recorded years ago and nobody has looked at since.

None of these are the homeowner's fault and all of them are the homeowner's to fix, which is worth saying out loud to them early and neutrally rather than as an accusation at week six.

Where to catch this: the survey, not the filing

Every failure above is detectable from one artefact: the current utility bill for the service address.

It carries the account holder's name as the utility has it, the service address as the utility has it, and the account number. Checking it against the sales agreement and against who is actually signing takes about two minutes and eliminates most of this category.

The reason it does not happen is that the site survey is understood as a physical exercise. Somebody goes to the roof, measures, photographs the service panel, checks the shading. Nobody thinks of the utility bill as survey data, so it is collected later, by a different person, for a different reason.

Moving it earlier has a second benefit. An identity problem found at qualification is a conversation. The same problem found after the design is complete and the permit is filed is a stalled project with committed costs, and the party absorbing those costs is usually whoever is carrying the working capital rather than whoever missed the check. The general shape of that is set out in who pays for what on a solar project.

Why this failure is invisible until it is expensive

Interconnection and permitting run in parallel, not in sequence. That is normally an advantage, because two clocks run at once instead of one after the other.

It has one specific cost. A permitting track can proceed perfectly, with an approved plan set and an issued permit, while the interconnection filing has never validly opened because the wrong party signed. Nothing on the permitting side reports that. The project looks healthy on every dashboard that watches permits.

The discovery point is usually installation scheduling or close-out, which is the worst possible moment: the design is paid for, the permit fee is spent, the materials may be ordered, and the correction now requires the homeowner to do something with their utility that takes weeks. That is the same late-discovery penalty described in why solar projects stall after the sale, applied to a document rather than to a design constraint.

Who owns this on your projects

Three questions, and they are answerable:

• Who verifies the customer of record before filing, and against what evidence? "The homeowner told us" is not evidence. A current bill is.
• Who obtains the authorisation, on which utility's form, and where is it stored? Utilities differ, and an authorisation on the wrong form is not an authorisation.
• Who handles a mismatch when one is found? This involves a conversation with a homeowner about their trust, their divorce, their late parent's account, or their landlord. It needs someone who will actually make the call.

A sales organisation that does not do fulfilment never touches any of this and still absorbs all of its schedule consequences. That makes it a fair and specific question to ask a fulfilment partner, and it sits alongside the licensing and insurance checks in the installer vetting scorecard.

How Seamless Home handles it

Seamless Home is a licensed contractor. Interconnection filing runs as inside operations, which means the customer-of-record check happens before submission rather than being discovered by a utility rejection, and the authorisation is obtained on the form the relevant utility actually accepts. Installing partners are engaged as our subcontractors, and the filing does not depend on the party whose scope begins at installation day.

Utility requirements for authorisation, evidence of authority and entity-held property differ per service territory. Coverage is confirmed per service area rather than promised as blanket availability.

Talk to us if your interconnection rejections cluster around names and accounts rather than around engineering.

The bottom line

The jurisdiction cares who is licensed. The utility cares who is on the account. A residential PV solar project has to satisfy both, and the two parties are related only by coincidence.

An interconnection application signed by the wrong person is not a technical defect and does not look like one. It looks like a project that is going fine, right up until it is not.