Solar EPC Bill Analysis Checklist

A solar EPC bill analysis checklist is a pre-survey filter that tells the consultant what the bill really supports. It catches wrong tariffs, demand charges, PF issues, document gaps and client objections before the proposal becomes a promise. It also helps owners see that the EPC is reading their business, not just selling panels.

The best checklist is short enough to use in the first call and detailed enough to prevent embarrassing assumptions later.

Which documents should be collected first?

Ask for the full electricity bill PDF, not only a payment receipt. The full bill usually carries consumer number, billing category, sanctioned load, contract demand, meter readings, demand rows, PF rows, taxes, arrears and adjustment notes.

Collect these items before the survey:

• recent full bill PDFs across a full operating year, where available
• consumer number and connection name
• tariff category and voltage level
• sanctioned load or contract demand record
• meter type and net metering status, if any
• last payment receipt, if arrears are visible
• basic shift schedule and weekly holiday pattern
• any previous solar proposal or approval file

If the client cannot find bills, ask accounts, the consultant who files power expenses or the DISCOM portal user. The article on DISCOM portal bill download problems is useful when teams depend on screenshots and missing PDFs.

Which bill fields should be verified before sizing?

Start with the fields that change the economics. Monthly units matter, but they are not enough. Demand, tariff category, ToD, PF and adjustments can change the answer.

Check:

• billed units, kWh or kVAh
• maximum demand and contract demand
• demand charge and fixed charge rows
• PF incentive, PF penalty or kVAh billing indicators
• ToD or ToU energy rows
• fuel surcharge or adjustment rows
• electricity duty and other government charges
• meter status, multiplying factor and reading basis

This is where solar sizing from electricity bills becomes practical. Sizing is not a panel count exercise. It is a bill-backed argument about usable generation.

If the bill has a strange adjustment, do not bury it inside the savings rate. Flag it. The client will notice when the same row remains after solar.

What tariff and meter questions should be asked?

Tariff category decides how the bill behaves. A commercial shop, HT factory, school, hospital and cold storage may all talk about “solar saving”, but their bills can treat demand, timing and adjustments differently.

Ask these questions:

• Is the category current, or is it an old category after business use changed?
• Is the meter LT, HT, three phase or CT operated?
• Is net metering, net billing or gross metering applicable in that area?
• Is the connection name same as the proposed applicant?
• Are there arrears, deposits or disputes that may delay processing?
• Has the load been enhanced recently?

The bill audit guide helps separate billing hygiene from energy use. A solar consultant does not need to become a tariff lawyer, but should know when the bill is not clean enough for a firm proposal.

How should load and roof questions be linked?

A roof survey without load questions gives only half the picture. A factory with a large roof and low daytime load may need a different commercial explanation from a plant that runs steady day shifts.

Before visiting, ask:

• Which shifts operate in normal months?
• Which days are weekly holidays?
• Which large loads run during sunlight hours?
• Are there future expansion plans?
• Does the roof have fragile sheets, skylights, asbestos, tanks or chimneys?
• Is there safe access for cleaning and maintenance?

Roof and bill must speak to each other. A shaded roof may reduce useful generation. A night-heavy process may reduce self-consumption. A weak document set may delay net meter approval.

Tips from the field

• Rename every collected bill PDF by month and consumer number so proposal assumptions can be traced later.
• Ask for the bill page that shows demand and PF rows, not only the page with the total payable amount.
• Put tariff category and sanctioned load in the first proposal draft, because clients often correct wrong records when they see them.
• Record whether savings are calculated from energy rows only or from a blended bill amount.
• Ask the client who controls the DISCOM login, because portal access delays can slow net metering paperwork.
• Keep roof objections separate from bill objections so the next meeting has a clear agenda.

How do findings become a stronger proposal?

The checklist should end in a one-page summary. Keep it simple:

For leads with weak data, say so. A line like “capacity and payback are indicative until full bills and DISCOM documents are verified” is not weakness. It is professional.

Bill analysis also helps answer objections. If the owner asks why your size differs from another EPC, you can point to load timing, demand rows, export risk and approval assumptions instead of arguing from panel count.

The result is a proposal that earns trust before the first panel is discussed. That is a better sales tool than a glossy saving number that collapses under the first serious question.

What should be checked again before final submission?

Before sending the commercial proposal, repeat the checklist once with the latest bill. Many projects move slowly, and a new bill may reveal a changed demand row, fresh arrears, a tariff correction or a production shift that the first discussion missed.

This final pass is also useful for internal handover. The sales person, designer and documentation team should not work from different stories. If the sales note says day shift operation but the design file assumes weekend export, the error will show up later in generation and billing conversations.

Keep a small handover note:

• final bill month used for proposal
• consumer name and number verified
• pending documents from client
• roof risks still open
• approval assumptions still open
• calculation rows used for savings

This note helps when the client calls after signing and asks why a document is needed. The answer should come from the same checklist, not from memory.