A practical compliance calendar for RBI-regulated entities, and how to keep up with circulars

How to build a compliance calendar that holds up in an inspection: list every obligation, give each an owner and a reviewer, file the evidence, and catch the circulars that change the rules.

Ask the compliance head of any NBFC, small bank or payments company how they track what is due, and the honest answer is often a spreadsheet. One tab per department, a column for due dates, colour coding that only one person fully understands, and a long trail of emails asking whether something was filed.

It works until it does not. Someone leaves, a circular quietly amends an earlier one, or an inspector asks for proof of a review done eight months ago. This guide sets out a practical way to build a compliance calendar for an RBI-regulated entity, and a routine for keeping up with the circulars that keep changing it.

Why the spreadsheet stops working

The Reserve Bank of India issues a steady stream of circulars, notifications and master directions, and often amends or replaces earlier ones. A team that misses an amendment can go on following a version of a rule that no longer exists.

RBI has also said plainly that it expects better than spreadsheets. In its circular RBI/2023-24/117 dated 31 January 2024, it asked supervised entities to put in place integrated, enterprise-wide technology solutions for compliance monitoring. Its supervisory review had found monitoring methods ranging from spreadsheets to workflow tools with heavy manual work.

There is also the evidence problem. Work that was done but cannot be shown to have been done still counts against you in an audit. A calendar that only records "done" without the proof behind it does not help much when the question comes.

Step 1: Build the obligation list

A compliance calendar is only as good as the list underneath it. Start with every obligation that applies to each legal entity in your group, drawn from the master directions, circulars and notifications relevant to your entity type.

For each obligation, record:

  • What it requires, in one plain sentence.
  • The source: the document, the paragraph and the exact wording. When someone later asks why you do this, the answer should be one click away.
  • Who it applies to: which entity, and why. An obligation for upper layer NBFCs, for example, does not bind a base layer NBFC.
  • How often it recurs: one time, monthly, quarterly, half-yearly, annual, or only when an event happens.
  • The deadline wording from the source text.
  • What evidence proves it: a filed return, a board resolution, a signed policy, a review note.

Group entities if you have more than one. A housing finance company and an NBFC in the same group will share some obligations and not others.

Step 2: Turn obligations into dates

Now convert each recurring obligation into a schedule. Two settings cover most cases: the day of the month the item is due, and how many months after the period ends. A quarterly item due 15 days after the quarter closes is "due day 15, one month after the period ends".

A few points that trip teams up:

  • Use the Indian financial year. Quarters run April to June, July to September, October to December and January to March. Label periods clearly, such as Q3 FY27, so nobody confuses calendar and financial quarters.
  • Watch short months. An item due on the 31st needs a rule for months that end on the 30th or 28th.
  • Do not assume holidays move the date. Unless the source says otherwise, plan as though the due date stands even if it falls on a weekend or holiday.
  • Event-driven items need a trigger. Some obligations arise only when something happens, such as a change in directors or a new product launch. List them anyway, with a note on what starts the clock.

Step 3: Give every item an owner and a reviewer

Each item needs one named owner who does the work, and a different person who reviews it. This is the maker-checker principle, and it matters for two reasons. It catches mistakes before they reach the regulator, and it shows an inspector that the work was checked, not just done.

The owner and the reviewer should never be the same person. The person who submits a piece of work should not be the one who approves it.

Set reminders before each due date, for example seven days and one day before, and agree what happens when something is overdue. An escalation that reaches the compliance head the morning after a missed date is far better than finding out at quarter end.

Step 4: File the evidence where the work is

When an owner finishes a task, the evidence should be attached to that item and period, not saved in a shared drive or an email thread. Record who uploaded it and when. Once a period is submitted for review, lock the evidence so it cannot be swapped afterwards.

If something went wrong, record that too: what went wrong and the date it will be fixed. A recorded deviation with a remediation plan reads very differently in an inspection from a gap nobody mentioned.

Step 5: A routine for new circulars

The calendar is a living thing. Every new circular or notification can add an obligation, change a deadline or retire an old requirement. A simple routine keeps it current:

  1. Check daily. Review new RBI circulars, notifications and master directions every working day. A daily digest by email helps.
  2. Read the relationships. Note whether each new document supersedes, amends, clarifies or corrects an earlier one. Follow the chain back so you know which version is current.
  3. Confirm the status at source. Before relying on any older document, confirm on RBI's website that it has not been withdrawn.
  4. Decide applicability. Have a person decide, with a written reason, whether the change applies to each entity.
  5. Update the register. Add new obligations, change affected schedules and retire items that no longer apply. Keep the history of retired items for audit.

The step that most often fails is the second one. A circular that amends a paragraph of a master direction is easy to read and file without changing anything in the calendar.

How Orbit by JuriCloud helps

Orbit by JuriCloud runs this whole process in one place. It covers RBI, GST, SEBI, IRDAI, MCA and Income Tax. For RBI, it collects new circulars, notifications and master directions twice a day, writes a short AI-assisted summary of each circular and notification, and maps what each document supersedes, amends, clarifies or corrects.

Obligations are extracted with the exact source quote and paragraph. Every quote must match the source word for word, and only obligations verified by JuriCloud experts can enter your register. Orbit offers an applicability status with its reason for each entity, for your team to confirm.

Your register then works as the calendar described above: schedules on the Indian financial year, a named owner and a different reviewer for each item, reminders and escalation, evidence stored with a SHA-256 fingerprint, maker-checker approval and a tamper-evident audit trail. Due dates can also appear in Outlook or Google Calendar through a calendar feed.

The AI drafts and summarises. People decide and approve. If your team still runs compliance on spreadsheets, book a demo or visit orbit.juricloud.co.

This article is general information, not legal advice. For advice on your own situation, speak to a qualified lawyer.

Orbit by JuriCloud

All your compliance, in one orbit.

More from the blog