What an RVSF Actually Has to Keep on File: A Record-Keeping Guide for Vehicle Scrapping Operators

The car that sat in the corner for five months

Every yard that starts taking end-of-life vehicles eventually collects one of these. A car arrives on a flatbed. The person dropping it off is not the registered owner. There is a photocopy of an RC, a mobile number, and an assurance that the rest of the paperwork will come tomorrow. The car gets parked at the back. Five months later it is still there, still registered to somebody, still that person's liability on a government database, and now it is also occupying yard space nobody is paying you for.

That is the whole difference between scrap metal and a scrapped vehicle. A heap of shredded steel has a weight and a grade. A car has an identity, an owner, possibly a lender with a charge on it, an insurer, a tax history, and a registration that stays alive until somebody actively ends it. A Registered Vehicle Scrapping Facility, or RVSF, is in the business of ending that identity in a way that can be proven to a third party years later.

A note on scope before we go further. This is an operational guide about what to record and how to keep it retrievable. It is not legal advice. The exact conditions, formats, retention periods and incentives that apply to you come from your own authorisation, the central rules that created the RVSF category in 2021, the state transport department, and pollution control board conditions. Those change. Read them, and take professional advice on the ones that carry real consequences.

Four record chains, one job file

It helps to stop thinking about "documents" and start thinking about four parallel chains that all have to point at the same vehicle:

• Identity: what physical object came through the gate.
• Authority: who was entitled to hand it over, and on what basis.
• Extinction: proof that the vehicle's registration has been ended and the certificate issued.
• Output: what that vehicle became, by weight and stream, and where each stream went.

If any one of those chains is broken, the file is worthless in an audit even if the other three are immaculate. The single most useful structural decision an RVSF makes is to give every incoming vehicle one job number on day one and hang everything off it. Ticket, photos, RC scan, cancellation acknowledgement, dismantling record, output weights, hazardous stream handovers. One identifier, one folder.

Chain 1: identity at intake

The registration number is the weakest identifier you have. Plates come off, get swapped, get repainted. The chassis or VIN stamping and the engine number are what actually tie a heap of metal to a record.

At intake, capture at minimum:

• Chassis or VIN, photographed at the stamping, not just typed in
• Engine number
• Registration mark, with a photograph of the plate as received
• Make, model, variant, fuel type, year
• Odometer reading if the cluster is readable
• Condition on arrival: accident damage, missing assemblies, whether it arrived driven or towed
• Gross weight on the weighbridge with the ticket number
• Wide photos of all four sides plus interior

Photos matter more than most operators expect. Months later, a dispute about whether a vehicle arrived with its engine, catalytic converter or battery still fitted is unwinnable without dated images. Capture them at the scale, at the moment of weighing, attached to the ticket. Not later, from a phone gallery, sorted by memory.

Chain 2: authority to scrap

This is where yards get hurt. The question is not "did somebody bring the car" but "was that person entitled to end this vehicle's life".

Typical situations, each with its own paper trail:

Two items catch people out repeatedly. The first is hypothecation. If a loan charge is still recorded against the vehicle, the lender has an interest in it, and scrapping it without addressing that charge is somebody else's problem becoming yours. Record the hypothecation status and the no-objection evidence explicitly as a field, not as a vague "documents attached".

The second is outstanding dues: pending tax, challans or enforcement holds attached to the vehicle record. Whether these block the process and who clears them varies, but the yard should know the position before the vehicle is cut, because after it is cut you have no leverage and no vehicle.

Chain 3: the certificate of deposit and deregistration

The mechanism that makes the Indian scheme work is the certificate of deposit. When an owner deposits an end-of-life vehicle at an RVSF, the facility issues a certificate against that specific vehicle. That certificate is what the owner or a subsequent holder presents to claim the benefits linked to scrapping, which typically include concessions on motor vehicle tax and registration fees for a new vehicle, along with whatever discounts manufacturers choose to offer.

Two operational points matter more than the policy detail:

• The certificate is vehicle-specific and serialised. It is not a generic receipt. It is evidence tied to one chassis number and one deposit event, and your records must be able to reproduce that link on demand.
• It can change hands. Because the benefit can be used by someone other than the original depositor, you may be asked later to confirm who held the certificate and when. Record issue date, the party it was issued to, and any transfer you are notified of.

The precise quantum of each incentive is notified separately and differs by state and by vehicle category. Do not quote figures to customers from memory or from a two-year-old circular. Point them at the current notification.

Alongside the certificate sits the deregistration evidence. The vehicle's registration is cancelled on the national vehicle database, and the acknowledgement of that cancellation is arguably the single most important document in the file. It is the proof that the object you destroyed is no longer a live registered vehicle anywhere. File it against the same job number, and treat a job with no cancellation acknowledgement as an open item on a weekly exception report, not as done.

Chain 4: from one vehicle to many materials

The moment the vehicle is depolluted and dismantled, it stops being one record and becomes several. Fluids, battery, tyres, airbag units and refrigerant gas come out first and go to authorised handlers under their own rules. Ferrous, non-ferrous, plastics, glass and rubber enter inventory as ordinary material. Reusable assemblies, where permitted and where you have chosen to sell them, need their own traceability back to the donor vehicle.

The number an auditor will eventually ask for is the reconciliation. Suppose a yard takes in a small hatchback weighing 950 kg at the gate. An illustrative output record might look like this:

Those figures are illustrative, not a benchmark. The point is the shape of the record, not the numbers. Input weight, output weights by stream, destination for each regulated stream, and an unaccounted line that you can explain. A file where 950 kg goes in and 690 kg of steel comes out with nothing else recorded invites exactly the questions you do not want.

Build the habit of reviewing the unaccounted percentage across vehicles rather than per vehicle. One outlier is noise. A drift across a month usually means either the weighbridge or the dismantling recording has a systematic problem.

Retention and retrieval

The obligation people plan for is retention. The obligation that actually bites is retrieval. An inspector or an insurer does not ask for your 2025 records. They ask for one chassis number from fourteen months ago, and they ask on a Tuesday afternoon.

Test yourself on that. Pick a vehicle scrapped last year at random and try to produce, in under ten minutes: the gate photographs, the RC and authorisation set, the certificate of deposit, the deregistration acknowledgement, the dismantling and output record, and the handover documents for the battery and tyres. If it takes an afternoon and two phone calls, the record-keeping is not compliant in any meaningful sense. It is just stored.

Where a system earns its keep

Most of this is achievable on paper by a disciplined team. What software changes is the failure mode. In Scraplytics, the intake weighbridge ticket carries photo capture, so the arrival images are bound to the weight event rather than to somebody's phone. Documents attach to the job, so the RC, the authorisation and the cancellation acknowledgement live in one retrievable place. Dismantled output flows into inventory by category and grade with weighted-average costing, so the vehicle-to-material reconciliation is a report rather than a reconstruction. Onward sales carry GST invoicing with e-way bill and e-invoice IRN, and dispatch with proof of delivery covers the handover leg. Multi-location keeps a collection centre and a scrapping facility on separate books without separate systems.

None of that makes an operator compliant. Compliance is a set of decisions about what you refuse to accept at the gate. What a system does is remove the excuse that the evidence was too hard to keep.

The short version

Give every vehicle a job number on arrival. Photograph the chassis stamping, not just the plate. Treat hypothecation and dues as fields, not as attachments. Never let a certificate of deposit exist without a matching deregistration acknowledgement in the same file. Record output by stream and reconcile it against intake weight. Then test retrieval on a random old vehicle once a quarter.

Do those six things consistently and the inspection is boring, which is exactly what you want an inspection to be.