Generate RPT documents under Section 188 Companies Act 2013. Board resolutions, EGM notices, explanatory statements, board report disclosure.

Company secretaries in India—whether you are a member of ICSI (PCS), in-house CS, or part of a multi-disciplinary firm—carry the same burden: translate board decisions into compliant documents, maintain registers, and meet MCA timelines without rework. Related Party Transactions (Section 188) in CoSecOffice mirrors how experienced teams already work, but removes copy-paste between Word files, email threads, and spreadsheets.

Related party transactions need identification of related parties, board approval, member approval when thresholds apply, and disclosure in the board report.

When traffic to your practice website drops, prospects are usually comparing tools or searching for how work is actually done—not generic feature lists. This guide explains the statutory context and the exact generation flow inside CoSecOffice so you can evaluate fit against your current process.

Why this matters for company secretaries

Manual drafting for "RPT Compliance Software for Company Secretaries" work consumes senior time that should go to advisory and governance. Errors in resolutions, missing explanatory statements, or inconsistent registers create MCA queries and client escalations. Software only helps when it follows the real sequence: master data → event capture → board/GM papers → registers → filing.

CoSecOffice is built for every company secretary role—including PCS in practice, in-house secretarial departments, and compliance teams at startups and large corporates—not a narrow "PCS only" tool. The same modules support multi-client practices and single-entity in-house use with role-based access.

How CoSecOffice generates documents for this work

Open Related Party Transactions (Section 188) from the dashboard (/dashboard/documents/rpt-compliance) after sign-in. Master data from the company or LLP profile flows into notices, resolutions, and forms.

The platform stores generated Word files in your document library, supports your letterhead and formatting preferences, and lets you regenerate when facts change—without rebuilding from a blank template.

Step-by-step workflow in the application

Sync related parties from directors, shareholders, KMP, and group structure.
Document the transaction; generate board and GM resolutions with recitals.
Produce explanatory statement and board report disclosure paragraphs.

Documents the module typically produces

Board resolution
GM notice
Explanatory statement
Disclosure note

MCA forms and filings to coordinate

MGT-14 when required — prepared in your review pack; filed on MCA portal with data validated against the same client file

In-house secretarial departments vs practice firms

Corporate secretarial departments need RBAC, audit trails, and consistent templates across subsidiaries—CoSecOffice supports sub-users, circulation exports, and group entity mapping. Practice firms need speed across many CINs—the same modules scale with director import and compliance calendars per client.

For large corporates requiring dedicated onboarding, SSO planning, and implementation playbooks, see our Enterprise Solutions plan with in-house implementation support.

Conclusion

Strong related party transactions (section 188) discipline reduces penalty risk and improves board confidence. CoSecOffice aligns generation with Companies Act 2013 and Secretarial Standards where applicable—so your team spends time on judgment, not retyping.

Start a free trial with one live client, run this workflow end-to-end, and compare hours saved against your current Word-and-email process.

Estimated read time: 6 min read

Related resources

RPT Compliance Software for Company Secretaries: Related Party Transactions – Section 188