On 13 November 2026, registration opens for consent managers under India's data protection rules. Six months later, on 13 May 2027, the rest of the DPDP Act switches on, and the Data Protection Board can start taking complaints and imposing penalties.
Most Indian SMEs treat DPDP as a website job. Update the privacy policy, add a cookie banner, move on.
That misses the biggest store of personal data in a mid-sized company: the ERP. In SAP Business One, personal data is spread across more screens than most finance heads would guess, and much of it belongs to people you think of as "business" contacts.
This post shows where that data sits, what the law expects, and five practical steps to get SAP Business One ready before the deadline. We've written it as an SAP Business One agency that configures these systems for Indian manufacturers, traders and service firms, so it stays close to the screens your team uses every day.
Key takeaways
- Full DPDP compliance is due on 13 May 2027. Penalties go up to ₹250 crore for weak security safeguards.
- Your ERP is in scope. Proprietorship customers, contact persons, employees and webshop buyers are all individuals.
- SAP Business One already has data protection tools: personal data management, an access log for sensitive data, data ownership and change logs. Many companies have never switched them on.
- Every breach must be reported to the Board, with a detailed report within 72 hours. There is no minimum size.
- An MSME should plan for roughly 12 to 14 weeks of work. Starting in November leaves room to do it calmly.
What does the DPDP Act actually ask of an Indian SME?
The Act covers every organisation that processes digital personal data of individuals in India. There is no turnover threshold for the core duties, so a 25-person trading firm in Kolkata has the same basic obligations as a listed company.
These are the dates and limits that matter for your ERP:
| Obligation |
Date or limit |
| Consent manager registration opens |
13 November 2026 |
| Full compliance; Board can take complaints and fine |
13 May 2027 |
| Tell the Board and each affected person about a breach |
Without delay |
| Detailed breach report to the Board |
Within 72 hours |
| Keep personal data and processing logs |
At least 1 year from processing |
| Resolve a grievance |
Within 90 days |
| Maximum penalty, missing security safeguards |
₹250 crore |
| Maximum penalty, missed breach notice |
₹200 crore |
The ₹250 crore figure gets the headlines. It's a ceiling, though, not a fine per record, and the Board weighs how serious the breach was and how quickly you acted.
What catches small firms out is something more ordinary.
Picture this: a sales executive leaving your company exports the full customer list from SAP Business One into Excel and mails it to his personal Gmail. Under DPDP that is a personal data breach. You now have to tell the Board and every person in that file. And if your ERP has no access log, you can't even say who pulled the list or when.
There is also no minimum size. Unlike Europe's GDPR, India's rules don't let you skip reporting because a breach looks small. Every one counts.
Where does personal data sit inside SAP Business One?
Ask an Indian finance team this and the usual answer is "nowhere, we only deal with companies." Look a little closer.
1Proprietorship customers and vendors. A large share of Indian B2B trade runs through sole proprietors. Their PAN is the owner's own PAN, and the trade name, mobile and address all point to one person. That business partner record is personal data.
2Contact persons. Every business partner has them: names, mobile and WhatsApp numbers, email addresses, sometimes birthdays.
3Employees and sales employees. Bank details, PAN, home addresses and anything your team keeps in the employee master.
4Webshop and D2C buyers. Customers synced from Shopify or WooCommerce bring delivery addresses and phone numbers used for COD confirmation calls.
5Activities, service calls and opportunities. Free-text notes like "spoke to Mr Sharma, call after his daughter's wedding" are personal data too.
6Attachments. Scanned KYC documents, cancelled cheques and visiting cards stored against the business partner.
7User-defined fields. Fields a consultant added years ago, often holding a date of birth or an ID number nobody remembers asking for.
8Dispatch details. Driver names and mobile numbers keyed in for transport and e-way bills.
None of this is wrong to hold. GST and income tax rules expect you to keep transaction records for years, and DPDP doesn't override that. What DPDP asks is that you know where the data is, limit who can see it, record who looked at it, protect it properly, and erase what you no longer need.
How do you lock down personal data in SAP Business One? Five steps
The good news: SAP Business One has shipped data protection tools since version 9.3, when they were added for Europe's GDPR. Most Indian installations have them sitting unused.
Step 1: Switch on personal data protection management
In Company Details, enable Personal Data Protection Management. That opens the Data Protection Tools under Administration, where you mark which fields count as personal or sensitive. Include the user-defined fields. This is where an old "DOB" field on the business partner master finally gets caught.
Step 2: Turn on the access log for sensitive data
SAP Business One can record every time someone opens sensitive personal data. That log is your answer to "who pulled the customer list?" DPDP also asks you to keep processing logs for at least a year, so check that your backups and hosting keep them that long.
Step 3: Tighten authorisations and data ownership
New users in SAP Business One start with no rights, which is a good default that often gets undone on go-live day with a quick "full authorisation". Review it. Data ownership lets you limit records by owner, so your Pune branch team sees Pune customers and not the whole country. Export rights to Excel deserve a hard look of their own.
Step 4: Clean up and set a retention schedule
Use the personal data management wizard to find records that belong to individuals. Then decide, category by category, how long each type of data stays. Invoices and ledgers stay as long as tax law needs them. A marketing contact who hasn't bought in years probably doesn't need to stay at all.
Step 5: Rehearse the bad day
Write down who notices a breach, who decides it is one, and who files the first notice with the Board. Then run it as a drill. Do the same for a customer who asks to see or correct their data, since grievances must be closed within 90 days.
What SAP Business One won't do for you
The ERP can protect and log the data inside it. It can't write your privacy notice, collect consent on your website, or sign data processing agreements with your transporter, payroll vendor or CA firm. That part is legal and process work. The best setup pairs your SAP Business One agency with your legal adviser, each doing their half.
Hosting matters too. If SAP Business One still runs on a server in the office storeroom, encryption, patching and backups are your job. Ingold Solutions runs SAP Business One cloud hosting on Microsoft Azure and is ISO 27001 certified, which covers much of the "reasonable security safeguards" groundwork.
How long does all this take? One Indian compliance firm puts a full DPDP programme for an MSME at 12 to 14 weeks, and notes that companies usually underestimate the cost by 30 to 40 percent. The SAP Business One part is only one piece of that, which is exactly why it's worth starting now.
Get a free DPDP check of your SAP Business One system
You don't need to start with a big compliance project. Start with a short look at what's already in your ERP.
Book a free SAP Business One health check with Ingold Solutions. As your SAP Business One agency, we'll check which data protection settings are switched on, list the fields and attachments that hold personal data, and give you a short, prioritised fix list. No obligation, and it takes about an hour of your team's time.