Interconnection Application Rejection Reasons in the USA

A utility email saying your solar interconnection application cannot proceed may describe six different problems. Interconnection application rejection reasons in the USA extend beyond electrical design. One missing authorization can make the file incomplete. A failed technical screen can move a valid project into another review track.

Direct answer. US solar interconnection applications get returned for six main issue types. These include incomplete forms, customer mismatches, unsupported equipment, inconsistent design data, failed screens, and unresolved studies. Read the governing tariff, identify the actual status, preserve every response right, and reconcile project records before resubmitting.

This guide covers distribution-connected solar and storage applications. It does not create one national procedure because utilities and state commissions use different rules. Every deadline, screen, fee, and response option must be checked against the current project documents.

Was the interconnection application actually rejected?

Often, no. Teams use rejected for any utility response that stops automatic progress. The governing procedure may call the same event incomplete, invalid, failed initial review, subject to supplemental review, moved to study, or deemed withdrawn.

That language matters because each status preserves different options. An incompleteness notice usually asks for missing information. A technical screen result may offer a meeting, supplemental review, design modification, or study. A withdrawal notice may end the current request under the applicable procedure.

The official FERC Small Generator Interconnection Procedures separate these states. The posted procedure requires a written list when a request is incomplete. It also routes projects that do not pass fast-track review toward other process options.

FERC’s procedure is not the retail rule for every distribution project. State commissions and utilities adopt their own processes. Use it to understand the categories, then open the tariff that governs the actual request.

The solar interconnection application guide explains the full submission path. This article begins when the utility returns a notice or produces an unfavorable review result.

What are the main interconnection application rejection reasons in the USA?

Start with the notice language, not the project team’s interpretation. Record the exact status, cited section, response date, required payment, available meeting, and consequence of no response. Then assign an owner.

Notice language	Actual status	First owner	Evidence to open	Likely response paths
Incomplete application	Completeness review did not close	Application coordinator	Current form, checklist, portal record	Supply listed items or request allowed relief
Invalid request	Required information failed validation	Coordinator and customer owner	Tariff validation section, account record	Correct data, authorization, or site information
Failed initial screen	Valid request did not clear fast track	Interconnection engineer	Screen result, data, SLD, equipment record	Results meeting, supplemental review, modification, or study
Supplemental review required	Initial result needs deeper screening	Project manager	Fee notice, screen analysis, tariff options	Pay, proceed, meet, modify, or withdraw
Detailed study required	Project needs system analysis	Developer and engineer	Study scope, deposit, assumptions	Enter study, revise project, or withdraw
Upgrades required	Interconnection depends on facilities or network work	Commercial lead and engineer	Study report, cost estimate, agreement	Accept, dispute, redesign, relocate, or withdraw
Deemed withdrawn	A procedural deadline or condition ended the request	Project manager and counsel	Notice, tariff deadline, correspondence	Dispute if available or submit a new request
Permit not approved	Separate AHJ process remains open	Permit coordinator	AHJ comments and plan set	Correct permit package without mislabeling utility status

This matrix is not a substitute for the tariff. It prevents the first operational error: sending an engineering comment to customer support or a customer-record problem to the electrical designer.

Capture the original notice as a controlled record. Do not rewrite its wording in a task ticket. The distinction between removed from queue and detailed study required can determine the next commercial decision.

Why do completeness deficiencies stop applications?

Completeness review asks whether the utility received the information required to evaluate the request. It does not decide whether the grid can accommodate the project. Missing forms, signatures, drawings, fees, or attachments can stop the application before technical review begins.

The New York State Department of Public Service publishes Standardized Interconnection Requirements effective February 9, 2026. Its process requires a detailed explanation when an application is incomplete. The utility must also identify the additional information needed within that procedure.

New York’s Appendix F illustrates how broad completeness can be. The package can include:

A completed application form.
Customer authorization when an agent acts for the customer.
Property-owner consent where the procedure requires it.
Account and meter numbers for existing service.
A site plan for a new service request.
Project technology, configuration, and AC size.
Product data and equipment compliance records.
A single-line or three-line diagram with required electrical information.

Those are New York requirements, not a national checklist. Another utility may name different documents or collect them through portal fields. The operating lesson still transfers: validate the package against the current utility checklist, not a prior project folder.

Common completeness defects include blank required fields, an unsigned authorization, a missing fee, and an outdated form revision. Files can also be present but unusable. A cropped certificate, locked PDF, or drawing without a readable point of common coupling may not satisfy review.

Do not answer an incompleteness notice with a general explanation. Build a response table with every utility item, the corrected document, the exact file name, and the submitting owner. Confirm portal receipt after upload.

How do customer, account, and site-control issues cause returns?

Interconnection applications bind a technical project to a customer, account, meter, site, and authorized representative. If those records disagree, the utility may be unable to validate the request even when the design is complete.

Typical conflicts include:

Applicant name differs from the customer of record.
The agent authorization names another contractor or legal entity.
The account number belongs to another meter or premises.
The meter number changed after service work.
The project address and point of interconnection describe different locations.
Property-owner consent is missing for a leased site.
A business name changed without supporting account documentation.
A new-service request lacks enough location information.

PG&E’s current Electric Rule 21 shows why these identifiers matter. Its pre-application provisions allow combinations of location, meter, account, mapping, and utility-equipment data to identify the proposed point. Its customer-information process also addresses third-party authorization.

Do not ask the designer to guess the correct legal name from a utility bill screenshot. Assign customer and account verification to the person who can access the current account record. Record the verified value once, then use it across the portal, authorization, agreement, and closeout documents.

Site control can also be a formal procedural requirement. The FERC SGIP includes site-control documentation within its request framework. The applicable state or utility rule decides what evidence your project needs.

Why do equipment and drawing mismatches fail validation?

The utility reviews one interconnected system, but project teams often submit several versions of it. The portal may name one inverter. The single-line diagram may show another. The certificate may cover a related model with different firmware or functions.

Start with these cross-file fields:

Project field	Records that must agree
Inverter identity	Portal, SLD, schedule, datasheet, certificate
AC rating	Application, diagram, study input, export control record
Point of interconnection	Site plan, SLD, account, meter, utility map
Service characteristics	Application, field survey, diagram, utility record
Export mode	Application, controls narrative, certificate, settings
Storage operating mode	Application, diagram, controls, tariff selection
Protection settings	SLD or 3LD, relay file, utility requirements
Existing equipment	Field survey, photos, site plan, diagram

The 2026 New York SIR requires equipment records and a diagram that identifies major components. Its Appendix F also asks for proposed settings and detailed transformer information where applicable. That example shows why a clean-looking SLD can remain technically incomplete.

For an Arizona Public Service project, use the APS record reconciliation check across the portal, drawings, equipment evidence, inspection record, meter work, and Permission to Operate.

Use exact model identifiers. A marketing family name does not prove the submitted unit has the required certification or function. For smart-inverter projects, retain the certificate pages that cover the model, firmware, rating, and requested mode.

Our UL 1741 SB inverter verification guide explains that equipment evidence layer. The IEEE 1547-2018 interconnection guide explains why certification, adoption, selected categories, and project settings remain separate decisions.

Equipment changes after submission need controlled review. Do not update only the permit plan set. Reconcile the utility application, SLD, certificate, equipment schedule, calculations, and customer-facing change record.

What does a failed technical screen mean?

A failed screen means the proposed interconnection did not satisfy one or more fast-track tests under the governing procedure. It does not automatically mean the project is impossible. It often means the utility needs supplemental review, a study, an agreed modification, or system upgrades.

PG&E’s Rule 21 states this distinction directly in its fast-track overview. Failure to pass fast-track evaluation means further review or study is required. It does not mean the generating facility cannot interconnect.

The actual screens vary. They can examine:

Network or feeder configuration.
Certified equipment status.
Transformer or conductor loading.
Phase balance.
Short-circuit contribution and interrupting capability.
Line and grounding compatibility.
Export behavior.
Aggregate generation compared with grid conditions.
Voltage, power quality, safety, and reliability.

Do not diagnose a failed screen from its letter alone. Request or open the supporting data and analysis available under the procedure. Identify the precise screen, tested value, utility input, project input, and limiting condition.

The current New York SIR illustrates a structured response. When a project does not pass preliminary screens, the procedure provides several choices. They can include a results meeting, supplemental screening, a full CESIR, or withdrawal. New York-specific response windows apply only within that procedure.

Build a screen-result worksheet:

Copy the screen name and result from the notice.
Record the utility data used in the test.
Record the project data used in the test.
Compare those inputs with the submitted application and SLD.
Identify any factual error before proposing a redesign.
List the response paths allowed by the tariff.
Model the cost and schedule effect of each path.
Obtain the required commercial approval before responding.

Some failures can reflect a correct grid constraint. Others can reflect stale or inconsistent project inputs. The worksheet keeps the team from redesigning a system before it verifies the tested case.

Is supplemental review or detailed study a rejection?

No. Supplemental review and detailed study are process tracks. They ask whether more analysis, mitigation, facilities, or upgrades can support interconnection. They can still produce a commercially unacceptable outcome, but the procedural state is different from an invalid request.

Supplemental review usually applies another defined set of technical tests. A detailed study can examine protection, fault current, thermal loading, voltage, power quality, equipment stress, and required facilities. The exact study name and scope vary.

The New York SIR calls its full distribution study a Coordinated Electric System Interconnection Review, or CESIR. PG&E Rule 21 offers detailed-study tracks within its own framework. FERC SGIP also separates fast track, supplemental review, and study processes.

When a project enters study, open five records before approving payment:

The study scope and assumptions.
The fee or deposit notice.
The applicant response deadline.
The tariff rules for changes and withdrawal.
The commercial threshold for acceptable upgrade exposure.

A study result may identify interconnection facilities or distribution upgrades. That result is not merely a drawing correction. It can change capital cost, energization sequence, equipment scope, site design, and contract risk.

Do not promise the customer that an export limit or smaller inverter will clear review. The utility must evaluate the revised operating case under the applicable procedure. Treat design alternatives as proposals until accepted.

Why does the governing interconnection rule matter?

The governing rule decides what the notice means and what happens next. A process label from one utility may not exist in another territory. Even similar labels can carry different requirements.

Start by identifying the project’s legal and program path. Ask these questions:

Which utility serves the point of interconnection?
Is the request retail, wholesale, or under another program?
Which commission, tariff, manual, and technical document apply?
Which version was effective when the application was filed?
Did a transition provision preserve an older process?
Which utility notice or agreement controls the current step?

California shows this boundary clearly. The California Public Utilities Commission Rule 21 page describes Rule 21 for covered investor-owned utility interconnections. It also states that FERC-jurisdictional requests use the applicable wholesale distribution access tariff instead.

PG&E administers its own Rule 21 tariff within that framework. The current document includes validation, deficiency, fast-track, supplemental-review, and detailed-study sections. The PG&E Rule 21 project guide separates those review tracks and the records that must remain aligned. The SDG&E application and deficiency workflow uses that utility’s current tariff and portal records. Another California utility maintains its own approved tariff version.

Florida also uses utility-specific records within state rules. The FPL interconnection requirements guide maps account identity, tier evidence, drawings, inspection, metering, and Permission to Operate for FPL projects.

The Duke Energy interconnection guide separates Duke Energy Carolinas, Duke Energy Progress, and Duke Energy Florida. A notice from one operating company should not be answered with another company’s portal or tariff instructions.

Xcel Energy also uses state-specific authority. The Colorado and Minnesota Xcel guide separates those operating companies, technical manuals, review records, and closeout steps. Check the state lane before responding to a returned application.

New York uses its statewide SIR for covered distributed generation and energy storage projects. The 2026 version names preliminary screening, supplemental screening, and CESIR steps. The Con Edison and National Grid New York guide shows how the common rule meets distinct utility portals and records. Those labels should not be pasted into a project governed by another state.

FERC’s SGIP offers another process structure within its stated scope. It should not be cited as direct authority for every retail distribution application. Confirm state and utility implementation before using its terms.

Create a one-page rule register for each project. Include the source title, revision, effective date, direct URL, applicable program, and reviewer. Attach it to the application record.

This small record prevents a common internal error. Teams often answer a current utility notice using a checklist saved from another territory. The form may look similar while the response choices differ.

What happens when the project changes after submission?

A submitted project is a defined technical case. Changing equipment, capacity, controls, operating mode, or connection location can change that case. The utility procedure decides whether the change is acceptable, material, or a new request.

Changes that deserve immediate review include:

A different inverter model, firmware, or AC rating.
A revised point of interconnection.
Added or removed battery capacity.
A change from export to limited-export operation.
A revised power-control method or settings range.
A service, transformer, panel, or protection change.
A different project size or phase configuration.
A customer, ownership, or site-control change.

The FERC SGIP states that unagreed machine, equipment, or site modifications may be treated as withdrawal. It also provides a notice and cure concept within that procedure. The project tariff may use another standard.

PG&E Rule 21 likewise restricts certain changes during fast-track review unless the tariff or distribution provider permits them. Its current initial-review section directs some size or connection changes toward a new request.

Do not hide a substitution inside the permit revision. Create a change-impact record before procurement releases the alternate item.

Changed input	Interconnection records to reopen	Other records to reconcile
Inverter model	Application, SLD, certificate, settings	Permit equipment schedule and purchasing record
Project AC rating	Application, screen case, study input	Proposal, energy model, SLD
Export mode	Controls narrative, certificate, application	Customer agreement and commissioning plan
Point of interconnection	Site data, SLD, utility mapping	Permit plan and field scope
Battery operation	Application, SLD, controls, tariff path	Fire and electrical permit package
Customer entity	Account, authorization, agreement	Contract and permit applicant record

Ask the utility for written direction when the procedure requires consent. Retain the request, supporting documents, response, and accepted drawing revision. Verbal guidance is weak change control.

How does a kickback move through a real project team?

Consider an illustrative commercial rooftop application. The utility marks the request incomplete because the inverter certificate does not match the submitted model. It also notes that the customer authorization names an earlier project entity.

The first issue belongs to the design and equipment records. The second belongs to the customer and account records. Combining both into one redraw request would leave the authorization unresolved.

The project manager creates two response items:

The electrical owner verifies the exact inverter, rating, firmware, and certificate scope.
The account owner obtains a corrected authorization from the customer of record.

The drawing review then discovers a third conflict. The SLD uses the correct inverter family but shows an older AC rating. The team revises the SLD and checks the portal field, schedule, and permit set.

The response package names every corrected file. It includes a short index tying each utility item to its evidence. A second reviewer confirms that the submission still describes one system.

Assume the utility then validates the application but reports a failed technical screen. That new result is not another completeness defect. The interconnection engineer opens the screen data and compares its inputs with the accepted application.

If the data are correct, the commercial owner evaluates the allowed next paths. Those paths may include supplemental review, study, an agreed modification, or withdrawal. The tariff and notice define the available choices.

This example shows why rejected is a weak tracker status. The same project moved through incompleteness, validation, and technical review. Each state required another owner, evidence set, and decision.

How do missed responses turn problems into withdrawals?

A correctable issue can become a withdrawn request when the applicant misses a response, fee, meeting election, document, or study commitment. The governing procedure defines the consequence.

Under the FERC SGIP text, an applicant receiving an incompleteness notice has a stated period to provide listed information or request an extension. Failure to act can cause the request to be deemed withdrawn. That example does not set every utility deadline.

PG&E Rule 21 contains its own deficiency sequence and withdrawal provisions. Its sheets effective August 29, 2025 describe first and second notices, an extension option, and withdrawal when deficiencies remain unresolved. New York’s 2026 SIR also describes queue removal when specified responses or payments do not arrive.

Create a notice register on the day any utility message arrives. Include:

Utility and governing tariff.
Project and application identifier.
Exact notice type.
Date received.
Response deadline and time zone.
Extension right and request method.
Required fee or deposit.
Decision owner.
Technical owner.
Customer action.
Proof of submission.

Do not rely on an email flag as deadline control. Portal messages, invoices, and utility letters may start different clocks. A human interconnection reviewer should confirm the operative date.

If a request has already been deemed withdrawn, do not resubmit blindly. Check whether dispute relief, reinstatement, or a new application is available. Confirm how a new filing affects application position, study data, fees, and commercial commitments.

What is the difference between permit rejection and interconnection rejection?

A permit decision and an interconnection decision come from different authorities. The authority having jurisdiction reviews building, electrical, structural, and fire requirements. The utility reviews connection to its electric system under its tariff and interconnection process.

The same drawing can appear in both packages, but the decisions remain separate. An approved permit does not prove the utility will approve interconnection. A valid interconnection request does not authorize construction that still needs a permit.

Question	Permit review	Interconnection review
Primary authority	Building or electrical AHJ	Utility under applicable tariff or procedure
Core decision	May the proposed work be built under adopted requirements?	May the generating facility connect under system requirements?
Common documents	Plans, calculations, product sheets, forms	Application, SLD, customer records, equipment evidence, studies
Typical returned item	Code or document correction	Deficiency, screen result, study requirement, agreement issue
Final milestone	Permit or inspection approval	Interconnection agreement and applicable operating authorization

Our AHJ solar plan-set rejection guide covers permit-side causes. Keep separate trackers for permit comments and utility notices, then reconcile every shared field.

The point of interconnection deserves special attention. The utility application, SLD, permit plan, and NEC 705 interconnection analysis should describe the same project. For C&I systems, use the three-phase commercial interconnection checklist to reconcile service, protection, metering, controls, and study records. Each review still applies its own requirements.

How should you respond without creating a second kickback?

Use a controlled response package. A quick portal upload without cross-file review can close one deficiency while creating another.

1. Preserve the notice

Save the original email, letter, portal message, attachments, and timestamp. Record the governing tariff section and application identifier.

2. Classify the status

Choose completeness, validation, technical screen, study, upgrade, agreement, closeout, or withdrawal. Do not use rejected as the status field.

3. Assign the correct owner

Customer-record issues go to the account owner. Drawing conflicts go to the designer. Screen and study decisions go to the interconnection engineer and commercial owner.

4. Build an itemized response table

Quote each utility item. Name the correction, source file, sheet or field, owner, reviewer, and proof of submission. Keep unanswered items visible.

5. Reconcile shared data

Compare the application, SLD, equipment schedule, certificate, site plan, customer authorization, permit set, and study input. Search for old equipment identifiers before release.

6. Review material changes

A changed inverter, export setting, project size, or point of interconnection may need utility consent. It can also require a revised request under the applicable procedure.

7. Obtain human approval

An interconnection specialist should confirm the response path, technical explanation, deadline, and commercial effect. Legal or regulatory review may be appropriate for a dispute.

8. Submit and retain proof

Capture the portal confirmation, transmitted files, recipient, date, and application status. Do not overwrite the prior package.

What should a pre-submission interconnection audit check?

The most useful audit follows the utility’s current application checklist. A generic national checklist should only organize the review.

Before filing, confirm:

The tariff, procedure, form revision, and program are current.
The customer, applicant, agent, account, meter, and site records agree.
The point of interconnection matches every drawing and portal field.
AC size, export mode, and storage mode are consistent.
Exact equipment models match schedules, data sheets, and certificates.
The single-line diagram includes the utility’s required information.
Required settings, transformer data, and protection records are present.
Fees, signatures, authorizations, and consent documents are complete.
Permit and interconnection packages share the same design revision.
The team has assigned owners for notices, fees, meetings, and studies.

Use a frozen application export when the portal allows it. Reviewers need to compare what was submitted, not what the live project database shows after another revision.

How can Heaven Designs support the application package?

Heaven Designs can prepare coordinated drawings and supporting design records within an agreed scope. That work can include site plans, single-line diagrams, equipment schedules, and revisions responding to documented utility comments.

Our US solar permit design service can align shared drawing data across permit and interconnection packages. You can also review sample design deliverables before defining the required output.

The utility, customer, applicant, and qualified interconnection professionals retain their own responsibilities. Heaven Designs does not guarantee approval, control a utility queue, or replace tariff and regulatory review.

If you need drawing support for a returned application, send the notice and current package. Include the utility, tariff or program, application identifier, submitted SLD, equipment records, portal export, and response date.

Frequently asked questions

Does a failed fast-track screen mean the project cannot interconnect?

Not necessarily. It usually means the project needs another response path under the governing procedure. Options may include a results meeting, supplemental review, agreed modification, detailed study, or withdrawal. Confirm the exact choices in the utility notice and tariff.

Can an equipment change invalidate an interconnection application?

It can require review, consent, or a new request, depending on the change and procedure. Reconcile the application, diagram, certificate, rating, settings, and permit package before asking the utility to accept a substitution.

Is an incomplete application the same as a denied project?

No. Incomplete generally means required information is missing or invalid. A timely, complete response may cure the issue. The notice and governing procedure define the response right and consequence of no action.

Can a building permit fix a utility interconnection problem?

No. Permit approval and utility interconnection are separate decisions. Correct shared drawing data in both packages, but answer each authority through its own process.

Should every returned application receive an engineering response?

No. Some returns concern customer authorization, account data, signatures, fees, or portal fields. Classify the notice first, then assign engineering only when the issue is technical.

Which deadline applies to a utility notice?

The deadline in the current governing procedure and project notice controls. Do not reuse a deadline from another state, utility, program, or article. Confirm the start date, extension method, and consequence with a human reviewer.

Final review note

This article is an operational triage guide, not a tariff interpretation or project decision. A qualified interconnection professional must verify every project-specific deadline, procedure, technical response, fee, and application consequence.