Bank officials who register mortgages related to bank loans or other security interests on the CERSAI portal often come across two submission options—Submit With Deduplication and Submit Without Deduplication. Many users are unsure about the meaning of these options and which one should be selected while filing a CERSAI registration.
Choosing the correct option is important because it can help prevent duplicate records and improve the accuracy of the information stored in the CERSAI database. In this article, we explain the meaning of both options in simple English along with their differences, benefits, examples and frequently asked questions.
What is CERSAI?
The Central Registry of Securitisation Asset Reconstruction and Security Interest of India (CERSAI) is an online registry established by the Government of India. Banks, financial institutions and housing finance companies register the security interests created on loans through the CERSAI portal.
Whenever a borrower creates a mortgage, hypothecation or any other security in favour of a bank, the lender registers that security with CERSAI. This creates a central record that can be searched by other lenders and helps prevent fraud involving the same property or asset.
The objective of CERSAI is to improve transparency in lending and reduce the chances of multiple loans being obtained against the same property without disclosure.
What is Deduplication in CERSAI?
Deduplication means checking whether a similar record already exists in the CERSAI database before creating a new registration.
The CERSAI system compares the information entered by the bank with existing records. If a similar record is found, the system alerts the user. This helps banks avoid creating duplicate registrations for the same borrower or the same secured asset.
Deduplication improves data quality and keeps the CERSAI database accurate.
What is “Submit With Deduplication” in CERSAI?
The Submit With Deduplication option instructs the CERSAI system to perform a duplicate check before accepting the registration.
Before the registration is completed, the system searches for similar entries based on the details entered by the bank. If a possible duplicate is identified, the user receives an alert and can verify whether a new registration is actually required.
This feature reduces the possibility of duplicate records and makes the registration process more reliable.
For most CERSAI mortgage registrations and security interest registrations, this is the preferred option.
Benefits of Submit With Deduplication
Using Submit With Deduplication offers several advantages:
- Prevents duplicate CERSAI registrations.
- Improves the accuracy of the central database.
- Reduces operational mistakes.
- Saves time required for future corrections.
- Helps maintain proper loan records.
- Supports better compliance with banking procedures.
What is “Submit Without Deduplication” in CERSAI?
The Submit Without Deduplication option submits the registration directly without checking whether a similar record already exists.
The system accepts the filing immediately and does not perform any duplicate verification before submission.
If another registration already exists for the same security interest, a duplicate record may be created.
This option is generally used only in specific situations where the bank is certain that the registration is unique or when internal procedures require direct submission.
Risks of Submit Without Deduplication
Banks should use this option carefully because it may lead to:
- Duplicate registrations.
- Incorrect records in the CERSAI database.
- Additional work for correction.
- Confusion during future property searches.
- Operational issues during loan processing.
Difference Between Submit With Deduplication and Submit Without Deduplication
| Submit With Deduplication | Submit Without Deduplication |
|---|---|
| Checks for duplicate records before submission. | Does not check for duplicate records. |
| Helps prevent duplicate registrations. | Duplicate registrations may occur. |
| Improves data accuracy. | Higher chance of errors. |
| Recommended for most loan registrations. | Used only in special situations. |
| Safer option. | Requires extra caution. |
Example of Deduplication in CERSAI
Suppose a bank has already registered the mortgage of a customer’s property in CERSAI.
Later, another employee accidentally attempts to register the same mortgage again.
If Submit With Deduplication is selected, the system may detect the existing record and alert the user before the registration is completed.
If Submit Without Deduplication is selected, the registration may be submitted without any duplicate verification, resulting in multiple records for the same security.
Which Option Should Banks Choose?
For most bank loan registrations, Submit With Deduplication is the recommended option because it helps identify possible duplicate entries before submission.
Banks should use Submit Without Deduplication only when they are confident that no duplicate record exists or when their internal policy specifically requires direct submission.
Choosing the correct option improves the quality of CERSAI records and reduces future operational issues.
Why is Deduplication Important for Banks?
Every day, banks across India register thousands of mortgages and security interests in CERSAI. If duplicate records are created, they can cause confusion during property verification, loan processing and legal proceedings.
Deduplication helps maintain a clean database and ensures that lenders can rely on the information available in CERSAI while sanctioning loans.
Frequently Asked Questions (FAQs)
Submit With Deduplication is an option in the CERSAI portal that checks whether a similar security interest or mortgage record already exists before submitting a new registration. It helps banks avoid duplicate entries and improves the accuracy of CERSAI records.
Submit Without Deduplication submits the registration directly without checking for duplicate records in the CERSAI database. This option should be used only when the bank is certain that no duplicate registration exists.
Submit With Deduplication checks for duplicate records before registration, while Submit Without Deduplication submits the record immediately without any duplicate verification. The first option helps prevent duplicate registrations, whereas the second may create duplicate entries if the same security interest has already been registered.
For most mortgage and security interest registrations, banks should use Submit With Deduplication because it helps identify duplicate records and ensures accurate registration. Submit Without Deduplication should only be used when the bank is confident that no duplicate record exists or as per internal guidelines.
Deduplication helps maintain an accurate CERSAI database by preventing duplicate registrations of the same security interest. It improves transparency, reduces operational errors and makes property verification easier for banks and financial institutions.
Yes. Duplicate CERSAI registrations can create confusion during property searches, loan processing and verification. They may also require additional correction by the bank, increasing operational work.
