A successful login to CPCB's Common EPR Portal is the start of a migration review, not proof that every registration, certificate and return has transferred correctly. A business should compare its old records with the new account, stream by stream, and resolve material differences before relying on the displayed position for a filing or credit transaction.
As reviewed on 18 October 2026, the legacy plastic EPR portal states that operational use ended on 28 June 2026 and registered-unit data moved to the Common EPR Portal. The old system is retained for comparison of data available up to that cut-off. Battery and e-waste portals also direct users to the common single sign-on route. These developments do not combine the underlying waste rules into one registration or one annual obligation.
Distinguish the account from the statutory registration
The common account provides an access layer. The business may still have separate roles, approvals, equipment or packaging categories, certificates, targets and returns under the different waste streams. An electronics importer could need plastic, e-waste and battery reviews for different aspects of the same goods.
Keep three identifiers separate: the new Common EPR account identifier, each legacy portal account reference and each statutory registration number. Do not replace an EPR registration number on a supplier record merely because a new common login has been created. First check what the field requests and what the authority has actually issued.
Migration also does not cure a suspended registration, an unanswered clarification or an unfulfilled target. A historic compliance problem can remain after its records move to another interface. Conversely, a missing screen entry should be investigated rather than immediately treated as proof that an approved registration has been cancelled.
Build the pre-linking inventory
Create one inventory for each legal entity. Include its exact legal name, company PAN, GST registrations, applicable incorporation or business identifiers, registered address, authorised-person details and all existing EPR numbers. Attach the underlying certificates and approved amendments rather than copying only a consultant's spreadsheet.
The plastic migration notice specifically requires the company PAN and authorised-person PAN to match the existing account exactly when linking. These are two different identifiers. A company PAN matching correctly does not resolve a mismatch in the authorised person's PAN.
List existing email addresses and mobile numbers, their current custodian and whether the company can receive messages and verification codes through them. Do not circulate full PANs, passwords or OTPs in a general project tracker. Store sensitive identity evidence securely with access limited to those who need it.
For a corporate group, identify each legal entity separately even if the same employee manages all accounts. A parent, subsidiary and sister company do not become one regulated person because they use a common brand or finance team. A merger or business transfer also needs the appropriate statutory and profile changes; account linking is not a substitute.
Use a controlled linking process
Start from the official Common EPR Portal and current manuals. Confirm that the link reached is the intended CPCB service, especially when following an old bookmark. Keep a dated copy of the applicable migration instructions and identify the waste stream to which each instruction applies.
For an existing plastic account, use the exact matching company and authorised-person PAN details required by the notice. If they do not match, investigate the legacy record and authorised-person history before creating further accounts. Repeated registrations using slightly different names can make the record harder to resolve.
Record the common account identifier, linking acknowledgement and the legacy registration connected. Then open the relevant stream and check the registration itself. Do not mark every stream “migrated” merely because its icon appears on the landing page.
Where the employee who originally managed the account has left, follow the authorised update or recovery route. Never use an outgoing person's identity as if that person still authorises the filing. Retaining the historic identifier for matching and appointing the current authorised person are related but distinct steps that should be handled through the prescribed process.
Reconcile the legal and profile records first
Compare these items against the approved source documents:
| Record area | What to compare |
|---|---|
| Legal identity | Name, company PAN, legal constitution and correct entity |
| Authorised person | Name, PAN where required, designation, authority and contact details |
| Registrations | Stream, role, registration number, status, approved scope and amendments |
| Locations | Registered address, facilities and other approved operational locations |
| Applications | Submitted, pending, clarified, approved, rejected or withdrawn status |
Preserve differences exactly. “Address wrong” is less useful than recording that the migrated profile shows a previous registered office while the approved amendment shows the new address. Attach both records with dates and the amendment reference.
Do not edit a legal fact simply to make two screens agree. If the legacy record is itself wrong, explain that history and request the correct official change. A migration discrepancy and a substantive amendment may require different handling.
Compare obligations and historical returns
For each financial year and stream, list the quantity data used, target assessed, adjustments, fulfilment position and return acknowledgement. Reconcile the new display with the actual submitted return, approved corrections and source records.
A draft saved in the old portal is different from a submitted return. An uploaded attachment is different from an accepted or acknowledged filing. Preserve the distinction so that an incomplete historical task is not mistakenly treated as finished after migration.
Use consistent units and category codes. Packaging weight in kilograms should not be compared directly with a display in tonnes. Equipment counts, battery weights and plastic packaging quantities should remain in their proper streams and classifications. A migration review should not net unrelated quantities against each other merely because one company generated them.
Prepare a year-by-year exception list rather than relying only on the total visible on the dashboard. A matching total can conceal allocation to the wrong year or material category. If the source records show a correction that the new system does not, record the correction acknowledgement and the remaining difference.
Reconcile certificates as individual records
Keep a certificate register showing the stream, unique certificate reference, issuing entity, relevant category, quantity, date, validity where applicable, transfer and utilisation status, and transaction evidence. Compare available, transferred, accepted and used positions separately where the system distinguishes them.
Avoid treating a payment to a recycler as proof that an EPR certificate is available for use. A commercial invoice and a portal certificate serve different functions. Likewise, a certificate visible in history may already have been used or otherwise be unavailable for a new obligation.
For example, the old return file identifies a certificate against one year's target, while the new account displays the same reference in an available balance. Preserve the evidence and raise the discrepancy before using the apparent balance again. Do not assume that migration creates an additional credit.
A missing certificate should be traced through the legacy acknowledgement, counterparty records and new system status. Ask the counterparty to confirm its transaction reference where appropriate, but keep the authority's resolution and the final account correction as the decisive record. Reissuing or repurchasing credit without investigation can create duplicate records or unnecessary expense.
Open a useful discrepancy ticket
Use the current helpdesk or ticketing route for the relevant stream or common portal. The plastic migration notice asks users to report mismatches through the Common EPR Portal. Battery users are directed to the battery ticketing module for their stream issues. Do not assume that a support address for one waste stream handles every issue identically.
A useful ticket contains the legal entity, common account identifier, affected stream, registration number, financial year, exact field or transaction affected, expected position, displayed position and supporting evidence. State the requested correction clearly. Avoid sending passwords, OTPs or unnecessary identity documents through ordinary email.
Save the ticket number, submission date, attachments, responses and follow-up dates. If a deadline is near, explain its significance in the ticket and escalate through the published official channel. A ticket does not itself suspend an obligation, establish a filing extension or substitute for a submitted return.
After CPCB resolves the matter, recheck the account and reconcile the corrected value. “Ticket closed” and “record corrected” are not necessarily the same outcome. Preserve the resolution and a dated post-correction extract.
Distinguish password reset, authorised-person change and lost credentials
These situations need different action. A user who controls the registered contact details but forgot the password can use the ordinary reset route. A company with accessible credentials that wants to replace its authorised person should use the appropriate authorised-person update process.
The battery portal's August 2026 lost-credential manual provides a separate route when registered email or mobile access is unavailable. It requires identity and authority evidence, verification and CPCB review; it is not an instant unrestricted account transfer. Its supporting pack includes company registration and identity documents, a company declaration and a notarised affidavit in the prescribed format.
The battery manual also warns against using lost-credential recovery when the ordinary authorised-person update is the correct route, and against multiple concurrent requests. Treat this as a battery-specific procedure. Check the current common portal and other streams' own recovery instructions rather than copying the battery form into every case.
Keep ownership of access within the business
The battery portal directs users to dedicated contact details of the authorised person and says consultant or agent contact details should not be supplied in their place. The business should therefore control its account communication and authorisation arrangements while allowing advisers to assist within permitted access rules.
Create a handover record when an employee or consultant changes. It should identify registrations, open tasks, pending applications, tickets, outstanding notices, saved returns and where evidence is held. Remove obsolete access through the proper process and ensure the new authorised person has the required corporate authority.
Do not write passwords into the handover spreadsheet. Use an appropriate secure credential-management arrangement, maintain a responsible company custodian and test recovery access before the outgoing person leaves. Shared knowledge of a password is not evidence that the present filer is duly authorised.
Keep deadlines separate from migration problems
Account migration does not automatically extend a return date or postpone a target. Check the applicable stream, financial year, entity role and the actual extension order. An extension for battery producers does not necessarily apply to plastic processors, e-waste producers or an unrelated waste generator.
Similarly, restoration of a filing module and extension of a deadline are different developments. Keep the notice and effective dates with the filing calendar. Do not rely on an old banner saying the module is unavailable if the current portal has reopened it.
An assureOffice adviser can use the reconciliation as an internal client-record review alongside other practice work. The useful product is a verified inventory and a list of differences requiring official action; no integration with CPCB or automated migration should be assumed.
A practice using assureoffice.in can also include access ownership and document handover in its client onboarding checklist. The actual linking, changes and regulatory decisions remain within the official system and the business's authorised process.
Frequently asked questions
1. Does one common login replace separate waste-stream registrations?
No. The account provides shared access. The underlying plastic, battery, e-waste or other applicable registrations, roles, conditions, targets and filings remain separate and should each be verified against their own records.
2. What changed for the legacy plastic portal on 28 June 2026?
Its notice states that operational use was discontinued and registered-unit data moved to the Common EPR Portal. The old system is retained for comparison of data available up to the cut-off, rather than as the current filing destination.
3. Which PAN details must match for linking an existing plastic account?
The company PAN and authorised-person PAN must match the existing account exactly. Check both against the saved approved profile. Do not assume that a matching company PAN alone resolves every linking problem.
4. What if the authorised person's PAN differs between accounts?
Identify why the difference exists and use the appropriate official correction or authorised-person process. Do not invent an identity or create duplicate accounts to bypass matching. Retain the appointment and earlier account history as supporting evidence.
5. Does a new Common EPR ID mean our registration number changed?
Not necessarily. Account identifiers and statutory registration numbers serve different purposes. Retain both and use the identifier requested by the particular transaction or form, supported by the authority's actual records.
6. Can we assume all historical certificates migrated correctly?
No. Compare unique references, categories, quantities and transaction or utilisation status. Matching the overall balance is insufficient if a certificate is missing, duplicated or allocated to the wrong year or obligation.
7. Should we compare draft returns with submitted returns?
Keep them separate. A saved draft does not prove filing. Use submitted copies, acknowledgements and approved correction records to establish the historical position, while listing unfinished drafts as open tasks requiring action.
8. Does migration change an already applicable return deadline?
Not automatically. Only the applicable rule or official extension does that. Check the waste stream, year and entity role covered by the notice, and preserve the actual order with the compliance calendar.
9. Can a helpdesk ticket substitute for filing a return?
No. It records a reported problem and the request for assistance. Continue available compliance steps, preserve evidence and seek official resolution or instructions where necessary; do not treat ticket submission as a statutory filing.
10. Who should control the registered email address?
The business should maintain reliable authorised-person access and corporate custody. The battery portal specifically advises dedicated authorised-person contacts rather than consultant or agent details. Arrange continuity before personnel or adviser changes.
11. Is password reset the same as changing the authorised person?
No. Password reset restores access through existing contacts. Replacing the person authorised to act requires the relevant update process and corporate authority. A new password does not itself appoint a new signatory.
12. When should the battery lost-credential module be used?
Its manual reserves it for situations where registered contact access is no longer available. If existing credentials remain accessible, use the authorised-person update route where that is the actual need. Recovery is subject to verification and review.
13. Is credential recovery instantly approved?
No. The battery procedure involves supporting documents and CPCB review, which can lead to approval or rejection. Keep the application reference and the decision; do not promise an automatic account transfer based only on form submission.
14. Can one company create repeated recovery requests?
The battery manual allows only one pending lost-credential application for an entity at a time and warns about misuse. Track the existing request, respond accurately and follow the prescribed correction process rather than submitting duplicates.
15. Should a group of companies use one legal-entity record?
No. Separate companies need identity and registration records appropriate to each regulated entity. A common finance team or brand does not merge PANs, registrations, obligations or statutory responsibility.
16. Does linking cure a suspended registration?
No. Resolve the underlying suspension or other regulatory issue through the proper process. Migration can change how the record is accessed without changing its legal status, conditions or outstanding compliance requirements.
17. What should a discrepancy ticket say?
Identify the entity, account, stream, registration, affected year or transaction, exact mismatch and requested correction. Attach relevant source records and dated evidence. A precise ticket is more useful than a general statement that the portal is wrong.
18. What if the ticket is closed but the figures remain wrong?
Recheck the resolution, retain evidence of the remaining difference and follow up through the appropriate official channel. Do not mark reconciliation complete solely because the helpdesk status changed; verify the actual regulatory record.
19. Can we net a surplus in one waste stream against another?
Do not assume so. Each stream has its own rules and certificate framework. A shared interface does not make unrelated credits interchangeable or allow packaging, equipment and battery quantities to be combined indiscriminately.
20. When is migration review complete?
When identity and access are controlled, every relevant registration is linked and checked, historical returns and certificates reconcile, open differences are resolved or accurately tracked, and the current filing calendar is confirmed. Record who reviewed the result and the date.