COMPLY Statutory Notices Management System
AI & Accounting

COMPLY Statutory Notices Management System

Author : CA Jeetendra Vadnere

Watch on Youtube


1. Introduction

COMPLY is a web based application designed to help large companies and financial institutions manage the flood of regulatory and statutory notices they receive every day. These notices come from government and regulatory bodies (for example, Income Tax, GST, SEBI, labour authorities) and can arrive by portal, emails of various employees of organisation, or physical post/ hand delivery at corporate office and branches. COMPLY turns this chaotic inflow into a single, trackable, auditable workflow so compliance teams can act quickly, consistently, and with full evidence for audits and senior management.


2. Problem Statement — Why COMPLY Is Needed?

Large organizations face three practical problems when statutory notices arrive:

a) Scattered intake: Notices come from many places — authority websites, to multiple email accounts, and physical post and/hand delivery at multiple location. Different people in the same company may receive the same notice, or some notices may be missed entirely.

b) Manual tracking and duplication: People forward notices by email or print them; duplicates and missed actions are common. It is hard to know which notices have been replied to, who is responsible, and when replies were sent.

c) Regulatory risk and governance gaps: If a notice is missed or not replied to on time, the company can face fines, legal exposure, and negative findings in internal or external audits. The Chief Compliance Officer needs a reliable, auditable way to show that notices were captured and handled.

COMPLY addresses these problems by automating capture, removing duplicates, assigning responsibility, enforcing timelines, and producing audit-ready records.


3. Solution Overview — What COMPLY Does?

At a high level, COMPLY does five things:

1. Collects notices automatically from three places: registered government portals, configured email inboxes, and a folder where scanned paper notices are stored.

2. Reads and understands the notice using Optical Character Recognition (OCR) so the system can extract dates, reference numbers, and keywords.

3. Creates a Service Request (SR) for every unique notice. Each SR has a unique number, the original notice attached, a due date, and an assigned to person as per role defined in the App as Direct taxes, Indirect taxes, Secretarial etc.

4. Tracks actions taken by users (reply, adjourn, close) and stores the reply documents with the SR.

5. Escalates and reports automatically when SRs are overdue and provides dashboards and exportable reports for management and auditors.


4. Walkthrough - How COMPLY Works Step by Step?


4.1 Setup and Onboarding


a) Sign up: A user registers with name, designation, email, and password. For security purpose the system sends a verification link to the email to confirm identity. Password is kept alphanumeric as per industry standard which is hard to decode.

b) Role assignment: The administrator assigns roles — Admin (full rights) and User (limited rights). Admins configure master data.

c) Master data entry: Admins fill four key masters:

1) Company Master — Name, address, registration numbers etc

2) Authority Master — list of names of government/regulatory authorities from whom notices are generally coming with their portals, portal URLs, and credentials.

3) User Master — list of employees who will receive SRs, their roles (specified in tool can be choose by drop down), and reporting lines.

4) Email Master — email accounts from which notices should be automatically collected (IMAP host, port, credentials).


4.2 Collection and SR Creation


a) Trigger RUN: The admin presses the RUN button (or a scheduled job runs). COMPLY begins collecting notices.

b) Three sources scanned:

1) Authority portals listed in Authority Master.

2) Configured email inboxes listed in Email Master.

3) Specified folder on a local or network drive where scanned paper notices are stored.

c) Filtering: The system looks for files or emails that contain keywords such as “Notice”, “Notices” etc in the subject, body, or filename.

d) Download and OCR: Attachments are downloaded and OCR is used to extract text from images or scanned PDFs.

e) Deduplication: If the same notice appears multiple times (for example, sent to several people), COMPLY keeps one copy and ignores duplicates.

f) Service Request creation: For each unique notice, COMPLY creates an SR with:

1) Unique SR number

2) Creation date and time

3) Due date (default 72 hours from creation or the notice’s stated due date, whichever is earlier)

4) Assigned user or role (based on type of notice)

5) Brief description and original attachment


4.3 User Action and Tracking


a) User receives SR: The assigned user logs in, opens the SR, and reviews the attached notice.

b) Take action: The user records the action taken — Reply, Adjourn, or Close — and uploads any reply documents. If adjourned, the new date is recorded.

c) Status updates: The SR status is updated to Open, Adjourned, or Closed. All actions are logged.


4.4 Monitoring and Escalation


a) Dashboard monitoring: Admins see live counts of SRs, open vs closed, overdue items, and charts showing trends. Overdue SRs are color-coded for quick attention.

b) Escalation matrix: If an SR remains open past configured thresholds (for example, 96, 120, 144 hours), COMPLY automatically sends escalation emails to the assigned user, their reporting authority, and any CC recipients defined in the matrix. These thresholds are configurable.

c) Reporting: Admins can export SR lists and filtered reports to Excel, CSV, or PDF for audit committees or management meetings.


5. Development - How COMPLY Was Built?


a) Design and planning: mapping the real-world process of receiving and responding to notices and designed a system that mirrors that workflow.

b) AI-assisted development: Modern AI tools Anthropic Opus 4.7 for code were used to help generate code and speed up development, especially for repetitive logic and for integrating OCR.

c) Development environment: The application was developed on Lovable. Dev and tested in a controlled development environment where features were repeatedly tested and improved until stable. The application was packaged as a web application which can run on desktop, laptop, mobile handset and tablet so can be access from anywhere.

d) Email connectors: COMPLY connects to specified email accounts (IMAP/Ports/App Password) and downloads attachments automatically.

e) Portal connectors: COMPLY can visit government or regulator websites (using stored credentials) and download notices posted there.

f) Reporting engine: Generates Excel, CSV, and PDF reports for management and auditors.


6. Security and Data Protection


a) Verified sign-up: Users must confirm their email address before they can use the system.

b) Role-based access: Only authorized people see or act on notices assigned to them. Admins have broader control; regular users see only what they need.

c) Strong passwords and secure storage: Alphanumeric Passwords are designed using industry-standard methods difficult to decode.

d) Attachment safety: Original notices and replies are stored with the SR so the evidence is preserved and cannot be altered without trace.


7. Roadmap and Further Improvements on the way


a) Document wallet: A local folder structure where each SR has its own subfolder containing the original notice and replies for offline backup.

b) Real-time alerts: SMS and WhatsApp notifications for SR creation, escalation, and closure so users get immediate awareness.

c) Calendar integration: Sync SR due dates with user calendars (Outlook/Google) so reminders appear in daily schedules.

d) Daily automation: Option to schedule COMPLY to run automatically at a set time each day to collect notices without manual intervention.


8. Alternative Uses with Minimal Modifications


COMPLY’s core capabilities—automated intake, OCR extraction, deduplication, SR creation, role routing, escalation, and reporting—make it adaptable to many related workflows with small configuration or UI changes. Key alternative uses include:

a) Legal Intake and Case Tracking — Capture legal notices, summons, and vendor disputes; create case files, assign lawyers, and track court dates.

b) Customer and Employee Complaints Management — Ingest complaints from email, portal forms, and scanned letters; route to HR, customer service, or legal; track resolution and SLA compliance.

c) Invoice and Bill Processing — Ingest vendor invoices and payment notices; create invoice SRs, route to accounts payable, and flag overdue payments for escalation.

d) Contract Renewal and Obligation Alerts — Monitor contract-related notices and expiry reminders; create SRs for renewals and compliance obligations.

Each alternative typically requires only: mapping new masters (roles/authority types), minor form changes to SR fields, and updated routing/escalation rules.


9. Ultimate Use Cases and Benefits


a) Who benefits

1) Chief Compliance Officer: Gains confidence that every notice is captured and tracked.

2) Department Heads and Users: Clear assignments and deadlines reduce confusion.

3) Audit and Legal Teams: Ready access to evidence and timelines for audits and legal reviews.

4) Senior Management and Board: Dashboards and reports provide concise oversight.

b) Concrete benefits

1) No missed notices: Automated collection reduces the chance of a notice being overlooked.

2) Less manual work: The system removes the need to forward emails, print documents, or manually track replies.

3) Faster response times: Due dates and escalations push timely action.

4) Clear evidence trail: Every notice and reply is stored with timestamps for audits.

5) Flexible use: With small changes, COMPLY can manage legal notices, vendor disputes, employee complaints, or invoice tracking.


10. Conclusion


COMPLY provides a simple, reliable solution by automatically consolidating notices from portals, emails and scanned documents into tracked Service Requests, enforcing timelines and escalating overdue items so nothing is missed; it also preserves a secure repository of original notices and reply documents for every SR—critical evidence for audits and investigations—thereby reducing the risk of penal action and strengthening corporate governance. COMPLY turns this chaotic inflow into a single, trackable, auditable workflow so compliance teams can act quickly, consistently, and with full evidence for audits and senior management. With minor configuration the same platform can be repurposed for legal intake, complaints management, invoice processing and other related workflows, delivering faster response times, clear ownership and audit ready records that give management the visibility needed to demonstrate control and accountability.