Revised Schedule M Compliance: Batch Records, Deviations and Change Control in ERPNext
Schedule M compliance stopped being a future problem for Indian pharma MSMEs on 31 December 2025. That was the end of the extension window for units with turnover under Rs 250 crore that had formally applied for more time; larger manufacturers had to comply by June 2024. CDSCO has said publicly that no further extensions will be granted, and state drug controllers now send it monthly compliance reports. For many plants, the gap inspectors find is not in the cleanroom. It is in the records.
What revised Schedule M changes
Revised Schedule M brings Indian good manufacturing practice in line with WHO-GMP and PIC/S thinking. In practice that means a documented pharmaceutical quality system, quality risk management, product quality reviews, change control, deviation and CAPA handling, supplier qualification and validated computerised systems. Every one of these depends on records that are complete, attributable and hard to alter after the fact.
Where paper and spreadsheets fail Schedule M compliance
Most MSME plants we visit still run batch records on paper and stock in a mix of Tally and Excel. That setup breaks down in three places during an inspection:
- Traceability. Tracing one API lot to every finished batch and customer takes days of manual searching.
- Data integrity. Spreadsheets can be edited without a trail, which undermines the credibility of every figure in them.
- Linkage. Deviations, quality results and stock movements live in separate places, so no one can show the full story of a batch.
6 ERP controls that support Schedule M compliance
1. Batch-wise stock with expiry control
ERPNext tracks every material by batch, with manufacturing and expiry dates, and can block expired or unreleased stock from being issued or dispatched.
2. Batch genealogy and traceability
Work orders consume specific input batches and produce specific output batches. The serial and batch traceability report in ERPNext v16 traces materials backward and forward, so a recall question is answered in minutes.
3. Quality inspection at every stage
Incoming, in-process and outgoing inspections can be made mandatory before stock moves, with results stored against the batch.
4. Quarantine and release
Separate quarantine, approved and rejected warehouses, with release controlled by quality staff, mirror the physical status of material.
5. Deviations, CAPA and change control
Non-conformance and corrective action records, together with approval workflows for changes to masters and processes, give inspectors a clear, dated history.
6. Audit trail and access control
Role-based permissions and document version history show who created or changed a record and when, which is the heart of data integrity.
What ERPNext does not do on its own
An ERP is a tool, not a compliance certificate. Any computerised system used for GMP records must be validated for its intended use, which means documented requirements, testing and controlled change. Some plants also need a dedicated electronic batch record or LIMS alongside the ERP. Our approach is to configure ERPNext for the controls above, support the validation documentation, and integrate specialist systems where they genuinely add value.
A practical path to Schedule M compliance
- Map your current batch, quality and stock records against the revised Schedule M requirements.
- Fix traceability first: batch-wise stock, work orders and genealogy.
- Add quality inspection, quarantine and release.
- Layer deviations, CAPA and change control workflows.
- Validate, train and run a mock inspection before the real one.
Facing an inspection soon? Talk to KlyONIX Tech about a Schedule M ERP gap review for your plant, or see how we run ERPNext for pharma formulations.
Frequently asked questions
Is the Schedule M deadline for MSMEs over?
Yes. The extension for units that applied ended on 31 December 2025, and units that never applied were already expected to comply. Inspections are under way.
Does revised Schedule M require an ERP?
No specific software is mandated. But the record-keeping, traceability and data integrity it expects are very hard to prove on paper and spreadsheets.
Can ERPNext be validated for GMP use?
Yes, with a documented computerised system validation for its intended use. Validation covers your configuration and processes, not just the software.
Schedule M compliance: key takeaways
Schedule M compliance is now enforced, and records are where most MSME plants are weakest. Check official notices on the CDSCO website. Our ERPNext for pharmaceutical solution and compliance and governance service help you close the gaps with a system inspectors can trust.