- To prove List-II, trace the cells from maker to site with documents, not claims.
- Collect the cell invoice, cell test certificate and the module BOM declaration.
- Cross-check the cell maker on the live ALMM List-II and save a dated record.
- Map each module serial / RFID to its cell batch, then keep site delivery proof.
- Exact required documents are still being clarified mid-2026 — verify the latest order.
Proving how to prove ALMM List-II cell compliance is a paperwork job, not a guess. You do not just say the cells are Indian — you show it. The trick is a clean chain of custody: a set of documents that follows the cells from the cell maker, into the module, onto the truck, and onto your roof. Get that file right and a review takes minutes, not weeks.
What does proving ALMM List-II cell compliance mean?
Proving ALMM List-II cell compliance means showing that the cells inside your modules came from an MNRE-approved Indian cell maker. List-II is the MNRE list of approved cell makers. It is a separate layer from List-I, which approves the finished module model. You must prove both, not one.
The hard part is that the cell is hidden inside a sealed module. You cannot open a panel to check. So you rely on documents from the people who can see inside the supply chain — the cell maker and the module maker — plus your own checks. That bundle of documents is the chain of custody.
Why a self-declaration is not enough
A one-line letter saying "our cells are Indian" will not survive a real audit. Reviewers want to trace the cells. They want an invoice with a named cell maker, a test certificate, and a way to tie that maker to the exact modules on your site. Each link must connect to the next.
The List-II cell mandate effective date sits around 1 June 2026, but it faced deferment requests and court proceedings. Do not treat the date as settled — confirm whether it was deferred in the latest MNRE order, status as of 20 Jun 2026. Our List-II mandate guide tracks the timing.
What is the chain of custody from cell to site?
The chain of custody is the path the cells travel, with a document at each handover. It runs in four hops: cell maker → module maker → EPC → site. Each hop adds one or two documents. When every hop is covered, a reviewer can walk the whole path without a gap.
The four hops, in plain terms
First, the cell maker sells cells to the module maker and issues an invoice plus a test certificate. Second, the module maker builds the cells into modules and issues a bill-of-materials (BOM) declaration that names the cell maker and model. Third, the EPC buys those modules and cross-checks the cell maker on the live List-II. Fourth, the modules reach the site, and you keep delivery proof for the exact serials.
One missing hop breaks the whole chain
A chain is only as strong as its weakest link. If the module maker will not name the cell maker, you cannot cross-check List-II. If you cannot map serials, you cannot prove the panels on this roof are the ones you checked. Plan to close every hop before you order, not after.
Which documents prove List-II compliance?
Seven documents carry the List-II chain of custody, and each one proves a different fact. The table below lists each document, who issues it, and exactly what it proves. Treat this as your collection checklist for every project.
Exact requirements vary by scheme and tender — verify against the latest ALMM List-II order and any SECI tender RfS. Source: MNRE ALMM order (point-in-time).
Ask for these in writing before you pay
The best time to demand these documents is in the purchase order, not after delivery. Write the full list into your PO terms and make payment depend on a complete document pack. A module maker who balks at naming the cell maker is a warning sign — note it and ask why.
How do you build the proof, step by step?
You build List-II proof in six steps, each adding one part of the chain. Follow them in order and your project file fills itself as the order moves. Here is the flow from the cell invoice to the finished project file.
Get the cell invoice and test certificate
Ask the module maker for the cell purchase invoice and test certificate from the cell maker. These name the Indian cell maker and show the cells were tested.
Collect the module BOM declaration
The module maker issues a bill-of-materials declaration. It states which cell maker and cell model sit inside each module batch you bought.
Cross-check the cell maker against ALMM List-II
Open the live ALMM List-II on the MNRE portal. Confirm the named cell maker was enlisted on the supply date. Save a dated screenshot.
Map module serials to cell batches
Use the maker serial or RFID mapping sheet. Link each module serial number to the cell batch it contains, so every panel is traceable.
Capture site delivery proof
Record the dispatch list, e-way bill and goods-received note. These show the exact serials you cross-checked actually arrived at this project site.
Assemble the project compliance file
Put every document in one file per project. A reviewer should follow the cells from maker to site without asking you a single question.
Notice that the first two steps depend on the supplier, the middle two on your own checks, and the last two on logistics. If you wait until install to start, the early documents are hard to chase. Start the file at the purchase order. Our BOM compliance guide shows how to bake these terms into procurement.
How do you cross-check the cell maker on List-II?
You cross-check by opening the live ALMM List-II on the MNRE portal and matching the cell maker named in the BOM declaration against the enlisted makers. The match must be exact and it must hold for the date of supply, not just today.
Check the maker, the model and the date
Enlistment can change. A cell maker can be added, suspended or removed, and capacity caps apply. So you check three things: the maker name is on the list, the cell model matches, and the maker was enlisted when your cells were made or shipped. Save a dated screenshot or PDF of the list as your record.
Treat names and capacities as point-in-time
Do not copy a list of "approved cell makers" from anywhere and trust it. The live MNRE list is the only source that counts, and it is point-in-time — verify on the MNRE portal each time. Our List-II manufacturers guide explains how to read the live list and its capacity columns.
List-II is not the same as DCR. A module can sit on List-I and use List-II cells yet still not carry a DCR certificate. Where a scheme needs domestic content — such as the PM Surya Ghar residential subsidy — you also need a DCR certificate from the NISE portal. See our DCR certificate check and the PM Surya Ghar hub for that path.
How do module serials and RFID prove the cells reached your site?
Module serials and RFID tags prove the cells reached your site by tying each physical panel back to a cell batch. Every module carries a unique serial and an RFID or QR tag. The maker mapping sheet links that serial to the cell maker and batch inside.
The serial is the spine of the chain
Without serial mapping, your documents float free of the actual panels. With it, a reviewer can pick any module on the roof, read its serial, and trace it to a List-II cell maker. Record the serial range you received and check it against the dispatch list, so no stray panels slip in.
Match RFID to ALMM where the portal supports it
ALMM ties modules to RFID and serial data, and tests such as IEC 61215 and IS 14286 back the module specification. Where the portal lets you scan or look up a serial, do it and save the result. This second source confirms the maker mapping sheet rather than relying on it alone.
How do you build a project compliance file?
You build a project compliance file by putting every chain-of-custody document for one project in one place, in order, with the serial mapping on top. The goal is simple: a reviewer should follow the cells from maker to site without asking you a single question.
One file per project, in cell-to-site order
Order the file the way the cells travelled: cell invoice and test certificate first, then the BOM declaration, then your dated List-II cross-check, then the module invoice and datasheet, then the serial mapping, then site delivery proof. A clear cover sheet listing the modules and the cell maker speeds every review.
Keep it ready before the inspector asks
The file matters most at net-metering approval, subsidy claim, or an audit. By then it is too late to chase a cell maker. Build the file as the project runs and store it where the whole team can reach it. Then any request — from a DISCOM, SECI or an auditor — is a quick send, not a scramble.
Where does the chain of custody usually break?
The chain usually breaks at the handover points, where one party assumes another holds the proof. Most gaps are predictable. Knowing them lets you close each one before it costs you an approval.
- Module maker will not name the cell maker — then you cannot cross-check List-II at all. Make naming a PO condition.
- No serial mapping sheet — without it, you cannot link the panels on site to a cell batch.
- Undated List-II screenshot — a record with no date cannot prove enlistment held on the supply date.
- Wrong or partial delivery list — if the received serials do not match what you checked, the chain has a hole.
- Documents scattered across emails — a file you cannot assemble fast is a file you effectively do not have.
Many of these are the same errors that get whole submissions rejected. Our compliance mistakes guide lists the rejection patterns and the fixes, so you can pressure-test your file before you submit.
How does SuryaHub help you prove List-II compliance?
SuryaHub keeps the whole chain of custody in one place, tied to the right purchase order and project. The procurement and inventory module stores the cell invoice, test certificate, BOM declaration and your List-II cross-check against each order, links module serials to cell batches, and flags a missing List-II proof before dispatch — so the project file is built as you buy, not patched together at audit time. SuryaHub is pre-revenue; real pilots are Suryantra Energy and RGESPL, and every rule here must still be verified on the MNRE portal, not taken as a guarantee.
Enforce List-II proof on every BOM
See how SuryaHub ties cell-to-site documents to each purchase order and project.
Related guides
Frequently asked questions
How do I prove ALMM List-II cell compliance?+
To prove ALMM List-II cell compliance, build a chain-of-custody file: the cell invoice and test certificate, the module BOM declaration naming the cell maker, a dated cross-check of that maker on the live List-II, serial and RFID mapping, and site delivery proof for the exact modules installed.
What is ALMM List-II?+
ALMM List-II is the MNRE approved list of solar cell makers. List-II asks that the cells inside an enlisted module come from an enlisted Indian cell maker. The List-II cell mandate effective date is litigated — confirm whether it was deferred in the latest MNRE order, status as of 20 Jun 2026.
What documents prove the chain of custody for List-II cells?+
The List-II chain-of-custody documents are the cell purchase invoice, the cell test certificate, the module BOM declaration, your dated ALMM List-II cross-check, the module invoice and datasheet, the serial or RFID mapping sheet, and the site delivery proof. Together they trace the cells from maker to site.
Does ALMM List-I cover the cells inside a module?+
No. ALMM List-I approves the finished module model, not the cells inside it. List-II covers the cell makers. A module can sit on List-I while its cells still need to come from a List-II maker, so EPCs must prove both layers separately, not assume List-I settles List-II.
How does the module serial number help prove List-II compliance?+
Each module carries a serial number and RFID or QR tag. The maker mapping sheet links that serial to the cell batch and cell maker inside. This lets you tie the exact panels delivered to a List-II cell maker, so the chain of custody stays unbroken from cell to site.
Which List-II documents do MNRE, SECI or DISCOMs require?+
The exact List-II proof documents that MNRE, SECI and DISCOMs require are still being clarified in mid-2026. Collect the full chain-of-custody set, then verify against the latest ALMM List-II order and any SECI tender RfS, because requirements differ by scheme and tender and keep changing.
How does SuryaHub help prove List-II compliance?+
SuryaHub stores every chain-of-custody document against the right purchase order and project, links module serials to cell batches, and flags a missing List-II proof before dispatch. SuryaHub is pre-revenue; real pilots are Suryantra Energy and RGESPL, and rules must still be verified on the MNRE portal.
Sources & references
List-II rules, the approved cell-maker list, and the document requirements come from primary government sources and shift often. Always confirm the current process against the latest MNRE order, the live ALMM list, and any SECI tender RfS before you submit.
- Ministry of New & Renewable Energy (MNRE) ↗
ALMM List-II order and the live approved cell-maker list (point-in-time — verify).
- NISE DCR portal ↗
Where domestic-content certificates are issued and verified (verify the live URL).
- Bureau of Indian Standards (BIS) ↗
IS 14286 / Compulsory Registration Scheme for solar modules (verify scope).
Written by the SuryaHub team · reviewed against MNRE, NISE & BIS sources · updated 20 June 2026.
Method: The document flow and cross-check steps are drawn from the government sources above and re-checked every 30 days. Dates, names and capacities are point-in-time — verify on the MNRE portal and any SECI tender RfS. SuryaHub is pre-revenue; only Suryantra Energy and RGESPL are real pilots.
Change log: 20 Jun 2026 — first published.