By vimtara_admin on 8/31/2026
Table of Contents
ToggleDPT 3 compliance is often treated as a yearly filing exercise.
That is the wrong starting point.
The real DPT 3 challenge begins with the financial transactions recorded during the year. A company may receive money through director loans, promoter funding, business advances, bank borrowings, convertible notes or other arrangements. Some of these transactions may fall outside the definition of deposits. Some may not.
The company still needs to identify, review and report the relevant transactions correctly.
This is why Statutory Compliance Software is becoming important for modern finance and compliance teams. Instead of relying on spreadsheets and last minute reviews, companies can use a structured compliance workflow to identify transactions, organize documents, assign responsibility and prepare clean information for professional review.
For companies preparing DPT 3 filing, the objective should not be simply to meet the June 30 deadline.
The objective should be to know exactly what is being reported, why it is being reported and what evidence supports it.
Form DPT 3 is an annual MCA filing under the Companies (Acceptance of Deposits) Rules, 2014.
The filing is used for deposits and for reporting particulars of transactions that are not considered deposits under the relevant provisions. The MCA’s DPT 3 instruction kit states that a company other than a government company is required to file the return with the Registrar on or before June 30 every year, using information as of March 31.
This distinction is important.
A company should not look through its accounts only for transactions labelled as “deposits.”
It should review the wider population of receipts that could have DPT 3 relevance.
That includes areas such as:
The exact treatment depends on the facts and the conditions prescribed under the applicable rules.
That is why DPT 3 compliance is fundamentally a classification and documentation exercise.

The DPT 3 form is only one part of the process.
The information required to complete it often sits in different places.
A loan may be recorded in the accounting system.
The loan agreement may be stored in a folder.
A director declaration may be in an email.
A promoter funding document may be with the legal team.
An advance may be recorded in a customer ledger.
The CA may receive a spreadsheet containing some of this information.
This creates a fragmented process.
| Common problem | Business impact |
|---|---|
| Financial data is spread across systems | Relevant transactions can be missed |
| Documents are stored separately | Evidence takes longer to locate |
| Compliance is managed in spreadsheets | Status may become outdated |
| Responsibility is unclear | Issues remain unresolved |
| Review begins close to June 30 | Less time to correct errors |
| CA receives incomplete data | More manual follow ups |
| No clear audit trail | Difficult to reconstruct decisions |
This is where Statutory Compliance Software changes the operating model.
Instead of managing DPT 3 through a collection of files and reminders, the company can create one structured workflow.
The software becomes the control layer.
The accounting data provides the source information.
The compliance workflow identifies what needs attention.
The CA or CS provides professional judgement.
The final filing is then prepared from a cleaner and more traceable information set.
A financial ledger tells you what happened.
It does not always tell you how a transaction should be treated under the Companies (Acceptance of Deposits) Rules.
Consider a company that receives ₹40 lakh from a director.
The accounting system may simply show:
Unsecured loan from director
That is not enough to complete the compliance analysis.
The company also needs to consider whether the relevant conditions for the applicable exclusion have been satisfied and whether the required declaration and disclosures are available.
The same issue can arise with a customer advance.
The ledger may show:
Advance from customer
But the compliance team still needs to consider why the advance was received and whether the applicable conditions for exclusion are satisfied.
This is the central challenge:
Accounting classification and statutory classification are related, but they are not always the same thing.
A good Statutory Compliance Software workflow should therefore help the team identify potential transactions and organize the evidence needed for review.
It should not simply automate a label.
Director loans are a common area of confusion.
Certain amounts received from directors can fall outside the definition of deposits when the prescribed conditions are met. The rules include conditions relating to the source of funds and require relevant documentation and disclosure.
This means director loans compliance needs more than a lender name.
Finance teams should ask:
This is a practical area where Statutory Compliance Software can improve control.
The system can help surface relevant transactions.
The compliance team can collect the supporting documents.
The CA or CS can review the statutory treatment.
The company can then maintain the final decision and evidence as part of its compliance record.
That is a much stronger process than keeping the information in separate spreadsheets and email threads.
Business advances are also covered by specific provisions under the deposit rules.
Certain advances received in connection with goods or services may fall under exclusions when the conditions prescribed by the rules are satisfied.
The same principle applies to certain property related advances and other specified transactions.
The important point is simple:
Calling a receipt an “advance” does not automatically make it an excluded transaction.
The facts and the statutory conditions matter.
That is why finance teams should review:
A DPT 3 compliance process that begins with transaction review gives the CA a much cleaner starting point.
A Statutory Compliance Software platform can also make unresolved items visible instead of allowing them to disappear inside a spreadsheet.
Growing companies often use different forms of funding.
Promoter loans may be used to support working capital.
Startups may also issue qualifying convertible notes during fundraising.
The deposit rules contain specific exclusions for certain promoter loans and qualifying convertible note transactions, subject to the conditions set out in the rules.
The practical lesson is important:
The transaction type alone does not determine the compliance treatment.
The conditions must be checked.
This is where a connected compliance workflow can provide value.
| Transaction | What the finance team should review |
|---|---|
| Director loan | Lender, declaration, source of funds and applicable conditions |
| Promoter loan | Purpose, lender, financing conditions and supporting records |
| Business advance | Nature of supply, terms, adjustment and applicable conditions |
| Convertible note | Instrument terms, company eligibility and applicable conditions |
| Bank borrowing | Lender, facility documents and statutory classification |
| Deposit | Amount, terms, source, reporting and supporting records |
A Statutory Compliance Software platform does not remove the need for professional interpretation.
It makes sure the transaction is visible, the documents are available and the review has an owner.
Spreadsheets are useful for analysis.
They are less effective as the central control system for a growing compliance operation.
The issue is not that Excel cannot hold DPT 3 data.
It can.
The issue is everything around the spreadsheet.
Who updated it?
When was it updated?
Which version is correct?
Where is the supporting document?
Who owns the unresolved transaction?
Did the CA review the latest version?
Was the classification changed after review?
A spreadsheet can answer some of these questions.
A compliance platform can answer them systematically.
Vimtara describes this difference as moving from static trackers to live compliance visibility. Its platform provides deadlines, owners, status, document trails and escalation paths in one system.

A modern Statutory Compliance Software workflow should not begin with the final MCA form.
It should begin with the underlying compliance data.
Find the transactions that may need DPT 3 review.
This creates a complete review population before the filing is prepared.
Group the transactions by type.
Examples include director loans, promoter loans, advances, borrowings, convertible instruments and deposits.
Review the conditions that apply to each category.
This is where the finance team and professional advisors can determine whether the relevant exclusion or reporting treatment applies.
Connect the relevant agreements, declarations, approvals and other documents to the transaction or compliance item.
Every unresolved item should have a responsible person and a clear deadline.
Transactions that require legal, tax or accounting judgement should be routed to the appropriate expert.
Record the review, decision, supporting evidence and final status.
This is the difference between simply tracking DPT 3 and actually controlling the DPT 3 process.
| Area | Traditional approach | Modern approach with Statutory Compliance Software |
|---|---|---|
| DPT 3 deadline | Calendar reminder | Tracked compliance obligation |
| Transaction review | Manual spreadsheet | Structured review workflow |
| Documents | Separate folders | Connected document trail |
| Ownership | Email follow ups | Assigned owner |
| Exceptions | Buried in comments | Visible risk or task |
| CA coordination | Multiple files | Shared compliance workspace |
| Status | Updated periodically | Live compliance status |
| History | Difficult to reconstruct | Audit trail with timestamps |
The value is not automation for its own sake.
The value is control.
Vimtara’s Statutory Compliance Software is built around a live compliance model rather than a static checklist.
The platform brings GST, TDS, ROC, MCA, PF, ESI and Professional Tax obligations into one dashboard. It tracks deadlines, filings, documents, ownership and risks.
For DPT 3 workflows, the same operating model can help finance and compliance teams organize the work required before filing.
Instead of checking several trackers, teams can see what is due, what is delayed and what needs action from one place.
Each compliance item can have a responsible owner, deadline and escalation path.
Supporting documents can remain part of the compliance record instead of being separated across email and local folders.
Issues can be surfaced before they become deadline problems.
Vimtara combines software visibility with human experts for compliance items that need review or judgement.
Vimtara positions its platform around ownership, timestamps and a built in audit trail, making it easier to understand what was done and when.
This is important for DPT 3 because a good filing process should not end with submission.
The company should be able to explain the path from transaction to classification to evidence to final filing.
Traditional Statutory Compliance Software focuses on tracking.
AI can add another layer.
Vimtara’s AI compliance platform is designed to continuously monitor obligations, identify risks, track documents and surface compliance issues before they become penalties or audit problems.
For a DPT 3 workflow, the principle is valuable.
A smarter compliance system can help teams:
The goal is not to replace the CA.
The goal is to give the CA better information.
That distinction matters.
AI should accelerate compliance operations while professional judgement remains where statutory interpretation is required.
There is another reason DPT 3 deserves more attention.
It is connected to corporate financial transparency.
A well controlled company should be able to answer basic questions about significant financial receipts:
Who provided the money?
Why was it received?
How was it classified?
What rule or condition supports that treatment?
Where is the evidence?
Who reviewed it?
These questions matter beyond DPT 3.
They can also matter during:
That makes DPT 3 compliance part of a broader governance process.
A strong Statutory Compliance Software system can support that process by keeping compliance information organized and accessible throughout the year.
Section 73 of the Companies Act, 2013 deals with acceptance of deposits from the public, subject to the Act and applicable provisions.
The penalty framework for certain contraventions involving Section 73 or Section 76 and the relevant rules is set out in Section 76A.
Under Section 76A, a company can face a fine of at least ₹1 crore or twice the amount of the deposit accepted, whichever is lower, and up to ₹10 crore, in the circumstances covered by that provision. The law also provides consequences relating to repayment and interest, along with penalties applicable to officers in default.
This is why the commonly used phrase “MCA Section 73 penalties” should be used carefully.
The ₹10 crore ceiling is associated with Section 76A, not Section 73 itself.
For finance leaders, the practical message is more important than the terminology:
Deposit related compliance failures can create material financial and governance risk.
A proactive compliance process is therefore more valuable than a last minute filing reminder.
Before the company prepares its DPT 3 return of deposits, the finance and compliance teams should review the following.
A Statutory Compliance Software workflow can turn these steps into assigned, trackable compliance tasks.
The traditional question is:
“Who will prepare DPT 3?”
The better question is:
“Who owns the DPT 3 data, classification, evidence and review process?”
That change matters.
DPT 3 is not only a compliance team’s responsibility.
It can involve:
When each stakeholder works from a different file, the process becomes slower.
When they work from one controlled workflow, the process becomes easier to manage.
This is one of the strongest use cases for Statutory Compliance Software.
A reactive process starts when the deadline is close.
A proactive process starts with the transaction.
That means the company does not wait until June to ask:
“Do we have all the information?”
Instead, it builds the record during the year.
The benefits are straightforward:
| Proactive approach | Business benefit |
|---|---|
| Early transaction identification | Fewer surprises |
| Continuous document collection | Less last minute searching |
| Clear ownership | Faster issue resolution |
| Early exception review | More time for professional judgement |
| Connected audit trail | Better audit readiness |
| Live deadline visibility | Lower risk of missed actions |
This is the broader value of Statutory Compliance Software.
It moves compliance from a deadline driven activity to an operating process.
Vimtara’s approach is based on replacing fragmented compliance operations with a live, connected workflow.
Its Statutory Compliance Software brings multiple statutory obligations into one platform and provides visibility into deadlines, filings, documents, ownership and risks.
Its AI compliance layer adds continuous monitoring and early risk detection, while Vimtara also provides human support when an issue requires professional judgement.
For a business preparing for DPT 3, this creates a stronger operating model:
Financial data → Transaction review → Classification → Documentation → Expert review → Filing → Audit trail
That is the process companies should aim for.
Not simply:
Spreadsheet → Email → Filing.
DPT 3 compliance is not a form filling exercise.
It is a financial data and governance exercise.
The filing depends on what the company received, how those transactions should be treated under the applicable rules, what evidence exists and whether the final information has been properly reviewed.
That is why Statutory Compliance Software can make a meaningful difference.
Instead of managing DPT 3 through disconnected spreadsheets, email chains and deadline reminders, companies can create a structured workflow for:
Identify. Classify. Document. Review. File.
For finance teams, this means better visibility.
For Chartered Accountants, it means cleaner information.
For management, it means stronger corporate financial transparency.
For the business, it means a more controlled approach to statutory risk.
Vimtara brings statutory compliance obligations, deadlines, ownership, documents and risk into one live platform, with AI based monitoring and human support for issues that need expert attention.
The goal is not to wait for June 30 and hope everything is ready.
The goal is to make sure the company is ready long before June 30.
Bring statutory obligations, compliance workflows, documents, ownership and risk visibility into one platform.
DPT 3 is an annual MCA filing under the Companies (Acceptance of Deposits) Rules, 2014. It covers deposits and particulars of certain transactions that are not considered deposits under the applicable rules.
The annual DPT 3 due date is June 30. The filing contains information as of March 31, and the MCA instruction kit states that the information is to be duly audited by the company’s auditor.
No. DPT 3 also covers particulars of certain transactions that are not considered deposits. This is why finance teams need to review relevant receipts and not only transactions labelled as deposits.
Yes. Certain amounts received from directors can fall outside the definition of deposits when the applicable conditions are satisfied. The company should review the transaction, supporting declaration and other relevant requirements.
Certain advances can fall within exclusions from the definition of deposits when the prescribed conditions are satisfied. The company should therefore review the purpose and terms of the advance instead of relying only on its accounting label.