Digital bookkeeping has become the default for most Indian businesses over the last decade, whether through Tally, Zoho Books, QuickBooks, SAP, or a custom ERP. Until now, where that data physically sat was largely a matter of convenience and vendor architecture. That has changed.

With effect from 1 April 2026, Rule 46(8) of the Income-tax Rules, 2026, framed under the Income-tax Act, 2025, requires every person who maintains books of account in electronic form to keep those records accessible in India at all times, and to take a daily backup of them on a server physically located within the country. This is no longer a good governance practice left to internal IT policy; it is a statutory compliance obligation, tied directly into the redesigned tax audit report, Form No. 26.

This article walks through what Rule 46(8) actually requires, who it covers, how it links to the new tax audit disclosures, what happens if a business does not comply, and the practical steps a finance or compliance team should be taking right now.

•      Rule 46(8) of the Income-tax Rules, 2026 requires electronic books of account to remain accessible in India at all times and to be backed up daily on India-located servers, effective 1 April 2026.

•      The requirement applies to persons covered under Section 62 (books of account) and Section 63 (tax audit) of the Income-tax Act, 2025, including businesses using cloud platforms hosted overseas.

•      The backup must be a genuine, recoverable copy taken at the close of each business day; irregular or occasional backups do not satisfy the rule.

•      Form No. 26, the consolidated tax audit report replacing Forms 3CA/3CB/3CD, now requires auditors to disclose the accounting software used, the server's IP address and country, and the address of the India-based backup server.

•      Non-compliance can attract a penalty of Rs. 25,000 on the taxpayer, with an additional Rs. 10,000 penalty on an auditor who certifies compliance incorrectly.

•      Businesses running cloud accounting on platforms such as Tally on Cloud, Zoho Books, QuickBooks Online, or SAP hosted outside India need to set up a parallel India-based backup mechanism before their next tax audit.

Rule 46 of the Income-tax Rules, 2026 deals with the manner in which books of account and other documents must be maintained, including in electronic form. Sub-rule (8) adds a data-localisation layer to this requirement. In substance, it provides that books of account and documents maintained electronically must remain accessible in India at all times, and that a backup of such records must be kept on a daily basis on a server physically located in India.

The shift in framing is significant. Earlier rules focused on what records had to be kept and for how long. Rule 46(8) instead focuses on where the electronic version of those records physically lives, and how often a recoverable copy is created. Tax officers examining a case no longer need to depend on a taxpayer's cooperation, or on a foreign cloud vendor's response time, to access electronic records during scrutiny or search proceedings.

The rule attaches to two categories of persons under the Income-tax Act, 2025:

•      Persons required to maintain books of account under Section 62, which covers most businesses and specified professionals above prescribed income or turnover thresholds.

•      Persons whose accounts are subject to tax audit under Section 63, broadly businesses with turnover exceeding Rs. 1 crore and professionals with gross receipts exceeding Rs. 50 lakh, subject to the presumptive taxation carve-outs that already exist under the Act.

If your organisation falls in either bucket and keeps its books electronically, in an accounting package, an ERP, or a cloud platform, Rule 46(8) applies. Paper-based bookkeeping is not covered, but very few businesses of any meaningful size operate that way today.

Note: The ₹1 crore / ₹50 lakh figures are the basic thresholds, not the only ones

Section 63 also carries enhanced thresholds tied to digital-transaction compliance. For businesses, the audit threshold rises from ₹1 crore to ₹10 crore where cash receipts and cash payments each do not exceed 5% of the total. For professionals, the threshold rises from ₹50 lakh to ₹75 lakh under a similar cash-transaction condition. A business or professional operating largely through banking channels may therefore fall outside Section 63 — and, by extension, outside Rule 46(8) — well above the basic figures quoted here. Applicability should be checked against actual cash-versus-digital transaction proportions each year, not against the basic thresholds alone.

Two elements sit at the core of the rule, and both need to be read strictly.

Daily backup

A backup must be taken at the close of each business day. A backup taken on Monday does not stand in for Tuesday's records, and skipping a day because "nothing much changed" is not a defence. For entities that run 24-hour operations or operate across time zones, the practical approach is to fix a consistent day-end cut-off time, document it as internal policy, and back up at that interval without exception.

India-based storage

The backup destination must be a server physically located in India. This applies even where the primary accounting data is hosted on a global cloud platform, such as an AWS data centre in Singapore or an Azure region in the United States. Having your live data merely accessible from India through the internet does not satisfy the rule; a genuine, recoverable backup copy has to physically reside on Indian soil.

Example: A Mumbai-based trading company runs its books on a cloud ERP hosted on servers in Singapore. Under Rule 46(8), simply logging into that ERP from India every day is not compliance. The company needs a separate, automated process that pulls a full backup of the books each evening and stores it on an India-located server or data centre, in a form that can actually be restored if needed.

Form No. 26 is the new consolidated tax audit report under Section 63 of the Income-tax Act, 2025, read with Rule 47, replacing the earlier Forms 3CA, 3CB and 3CD from tax year 2026-27 onward. Where books are maintained electronically, the auditor is now required to disclose specific technical details rather than a generic statement that accounts are "computerised."

This effectively makes the auditor a checkpoint for Rule 46(8) compliance. An auditor who signs off on compliance without independently verifying the server location and backup logs takes on personal exposure under the incorrect-certification penalty discussed below.

The consequences of falling short of Rule 46(8) operate at two levels.

•      On the taxpayer: A penalty of Rs. 25,000 can be levied for failing to maintain the mandated daily, India-based backup.

•      On the auditor: An additional penalty of Rs. 10,000 applies where the tax auditor certifies Rule 46(8) compliance in Form No. 26 without it actually being satisfied.

These figures are a starting point rather than the full extent of the risk. Records that cannot be produced during a scrutiny assessment, search, or survey because they were never properly backed up in India can also weaken the taxpayer's position on unrelated factual disputes, since the burden of substantiating entries in the books ultimately falls on the assessee.

Getting ahead of Rule 46(8) is largely an IT and documentation exercise rather than a legal one, but it needs sign-off from both the finance team and whoever manages the accounting software.

1.   Map your data. Identify every system used to maintain books of account, and confirm where each one physically stores its data.

2.   Set up an India-located backup. If the primary system is hosted overseas, arrange a daily export or replication job to a server physically located in India, whether through the software vendor's Indian data centre option or an independent backup service.

3.   Fix a day-end cut-off and automate it. Manual, ad hoc backups are hard to defend under audit. An automated daily job with logs is far more robust evidence of compliance.

4.   Test restorability. A backup that cannot actually be restored is not a backup for this purpose. Periodically verify that the India-based copy can be opened and reconciled against the live books.

5.   Brief your tax auditor early. Since Form No. 26 now asks for specific IP addresses, server locations, and backup addresses, give your auditor this information well before the audit deadline rather than scrambling at the last minute.

6.   Document the policy. Keep a written internal policy stating the backup schedule, cut-off time, and responsible personnel, so that isolated technical failures can be explained and defended if questioned.

Does Rule 46(8) apply if I still maintain manual, paper-based books?

No. The rule applies only where books of account are maintained in electronic mode. However, given how widely accounting software is used even by small businesses today, very few taxpayers who are otherwise covered under Sections 62 or 63 will be able to claim a pure paper-based exemption.

What happens if the daily backup fails because of a genuine technical issue, such as an internet outage?

Maintain a log explaining the technical failure and take the backup as soon as systems are restored. A well-documented, isolated failure is more defensible than an undocumented gap, though repeated lapses are unlikely to be treated leniently.

Is a cloud platform with servers outside India automatically non-compliant?

Not automatically, provided a genuine daily backup is separately maintained on an India-located server. The rule targets the backup location specifically; it does not prohibit using an overseas platform for day-to-day operations.

Who is responsible for verifying Rule 46(8) compliance during a tax audit?

The tax auditor is required to independently confirm and disclose compliance in Form No. 26, including server IP addresses and the India-based backup address, and faces a separate penalty for incorrect certification.

From which tax year does this requirement apply?

Rule 46(8) and the corresponding disclosures in Form No. 26 apply from the tax year commencing on or after 1 April 2026, that is, Financial Year 2026-27.

This article has been prepared by the Taxflash Editorial Team solely for educational and informational purposes. While every effort has been made to ensure the accuracy of the information, readers are advised to refer to the relevant provisions of applicable laws, rules, notifications, circulars, judicial pronouncements, and official government publications before taking any decision. The contents of this article should not be construed as professional legal, tax, or financial advice. Taxflash Editorial Team shall not be responsible for any loss or liability arising from reliance on the information contained herein.

As amended up to the latest publicly available notification/circular at the time of writing.