Blockchain in Accounting

Blockchain in Accounting: A Working Guide for Indian CAs, Finance Heads, and Founders (2026)

Blockchain in Indian accounting has moved decisively from conference keynotes to live deployment. The RBI's e₹ (CBDC) is operational in retail and wholesale pilots, ICAI has issued updated guidance on auditing distributed-ledger environments, CBIC is piloting blockchain for export documentation, and Indian banks are processing live letters of credit on shared ledger platforms. For FY 2026-27, accountants need three things: a working model of how distributed ledgers change the texture of books and audits; clarity on how Ind AS classifies the digital assets that flow through those ledgers; and an airtight understanding of VDA tax obligations under Section 115BBH and Section 194S — with numbers. This guide delivers all three.

What Triple-Entry Accounting Actually Does to Your Reconciliation Problem

The phrase "triple-entry accounting" circulates freely but is rarely explained well. Here is the precise mechanics.

In conventional double-entry, Company A records a purchase (Dr. Purchases / Cr. Accounts Payable) and Company B records a corresponding sale (Dr. Accounts Receivable / Cr. Revenue). Both entries live on separate private ledgers. Neither party can see the other's record without sharing documents, which is why month-end intercompany reconciliation exists at all.

In a blockchain-enabled setup, a cryptographically verified third entry is written simultaneously to a shared distributed ledger that both parties — and any authorised third party such as a bank, statutory auditor, or regulator with appropriate read access — can inspect. That third entry is timestamped, hash-linked to every preceding transaction, and immutable. There is now only one version of the truth. Reconciliation does not disappear, but it shrinks to confirming that your ERP entry matches the on-chain record — a task that takes minutes rather than days.

To make this concrete: consider two subsidiaries of an Indian group with an intercompany payable of Rs. 50 crore settling monthly. Under the conventional process, the group CFO office typically allocates two finance staff for two to three days per quarter just confirming balances, chasing emails, and passing elimination entries at consolidation. On a permissioned private blockchain (such as Hyperledger Fabric deployed by the group's IT function), every transfer instruction and settlement confirmation is written simultaneously across nodes at each entity. Quarterly consolidation becomes a query against the shared ledger rather than a bilateral reconciliation exercise.

The accounting entry itself does not change — the debit-credit framework of Ind AS-compliant books remains fully intact. What changes is the source of evidence for that entry, the speed at which evidence is available, and the reliability of the audit trail.

Live Blockchain Deployments in India You Need to Know About

Trade Finance

SBI, HDFC Bank, and ICICI Bank participate on shared trade finance platforms for letters of credit, bank guarantees, and bill discounting. An auditor whose client uses these platforms will encounter on-chain documents as primary evidence for trade receivables. The existence and rights-and-obligations assertions are now substantiated by the ledger, not by a paper LC docket. Redesign your substantive procedures accordingly.

GST e-Invoicing and the IRP Architecture

India's Invoice Registration Portal (IRP) — now mandatory for taxpayers with aggregate annual turnover above Rs. 5 crore — generates an Invoice Reference Number (IRN) that is a SHA-256 hash of the invoice payload. Every signed IRN is a cryptographic proof of invoice authenticity. CBIC pilots are exploring a more fully distributed verification layer behind the IRP. For auditors, the IRN is already a testable on-chain proof that can be validated against the GST portal's API during completeness testing of GST output.

Supply Chain: Pharma, Agri-Exports, Gems and Jewellery

Drug Traceability regulations require large pharma companies to maintain end-to-end batch tracking. Several major manufacturers have implemented private blockchains to record production release, quality certification, and distributor receipt. For accountants, this creates on-chain provenance records that directly support:

• Inventory valuation (Ind AS 2): lot-level cost tracking with on-chain timestamps
• Revenue recognition (Ind AS 115): on-chain delivery confirmation from the distributor can serve as the objective trigger for recognising revenue — transfer of control is evidenced by a timestamped ledger entry, not a driver's signature on a paper POD
• Regulatory audit readiness: blockchain records satisfy drug authority audit trail requirements and reduce the documentation burden at inspection

The e₹ (CBDC) and Its Accounting Treatment

The RBI's e₹ operates in two forms: wholesale (e₹-W) for interbank settlement and retail (e₹-R) for general commerce. When your company receives or holds e₹, you face an immediate accounting question: is this cash or a financial asset?

The e₹ is a direct liability of the RBI, not a commercial bank deposit. Ind AS 7 (Statement of Cash Flows) defines cash as currency on hand and demand deposits. The e₹-R, redeemable on demand at face value without restriction, is appropriately classified as cash and cash equivalents under Ind AS 7. However, where the e₹ is purpose-bound (i.e., it can only be spent on specified categories — a feature the RBI is piloting for welfare disbursements), or where it carries programmatic restrictions on timing of use, classification as a financial asset under Ind AS 109 is more defensible. Document your classification rationale explicitly in the accounting policies note of your financial statements, particularly if material amounts are involved. Auditors will scrutinise this classification.

How to Classify Digital Assets Under Ind AS: A Decision Framework

There is no omnibus "crypto accounting" standard in India. Classification depends on the nature and business purpose of the specific asset held.

Practical note: If you are unsure whether a token is a security instrument, test whether it carries contractual rights to future cash flows arising from someone else's effort — the functional equivalent of the Howey test, which SEBI's evolving framework is incorporating. When classification is genuinely ambiguous, Ind AS 109 treatment is the most conservative and requires the most disclosure, which is usually the right default under the prudence concept.

VDA Tax Treatment Under Section 115BBH and Section 194S — With Actual Numbers

The Rate and Its Constraints

Under Section 115BBH of the Income-tax Act, 1961, applicable from Assessment Year 2023-24 and continuing without change for AY 2027-28, gains from transfer of any Virtual Digital Asset (VDA) are taxed at 30% flat, plus applicable surcharge and health and education cess at 4%.

Two constraints matter enormously in practice:

1. No deduction is allowed except the cost of acquisition. Business expenditure, administrative fees, platform charges, and interest on borrowings used to acquire the VDA cannot be deducted.
2. Losses from VDA cannot be set off against any other income — not against business income, not against capital gains, not against salary. They cannot be carried forward either.

Worked Example — VDA Gain (FY 2026-27 / AY 2027-28)

A founder acquired 2 Bitcoin in March 2024 at Rs. 28,00,000 each (total cost of acquisition: Rs. 56,00,000). In December 2026, she sells both for Rs. 45,00,000 each (total consideration: Rs. 90,00,000).

TDS under Section 194S: The buyer is obligated to deduct TDS at 1% of the sale consideration at the time of credit or payment, whichever is earlier. On Rs. 90,00,000, TDS = Rs. 90,000. This is available as a credit to the seller.

Advance tax alert: A common and expensive error is for founders to treat the Rs. 90,000 TDS as covering their liability. It covers less than 9% of the actual Rs. 10,60,800 due. VDA gains are subject to advance tax obligations on the standard four dates — 15 June, 15 September, 15 December, and 15 March of the relevant financial year. Interest under Sections 234B and 234C applies for shortfall. On a Rs. 10,60,800 liability, interest for a 9-month shortfall under Section 234C alone can reach approximately Rs. 19,000–22,000 — avoidable with a basic advance tax plan.

The 194S TDS Trap for Peer-to-Peer Transfers

When a VDA is sold peer-to-peer (outside an exchange), the buyer is the deductor. Many founders selling Bitcoin or other VDAs privately assume the obligation sits with the exchange. It does not, if there is no exchange involved. A buyer who fails to deduct TDS faces:

• Interest @ 1% per month from the date TDS was deductible to the date it was actually deducted (Section 201(1A))
• Potential disallowance of the cost as a deduction if the buyer is a business entity (Section 40(a)(ia))

Audit Implications: Redesigning Procedures for Blockchain-Enabled Clients

What SA 315 and SA 330 Require

SA 315 (Revised) — Identifying and Assessing the Risks of Material Misstatement — requires the auditor to understand the entity's information system, including the IT components that produce accounting information. A distributed ledger system is an IT component. You must document your understanding of the consensus mechanism, the node structure, the smart-contract logic that executes transactions, and the middleware that converts on-chain events into ERP journal entries.

SA 330 — The Auditor's Responses to Assessed Risks — requires that before you rely on system-generated information, you test the IT general controls (ITGCs) that ensure that information is complete and accurate. For a blockchain environment, ITGCs cover:

1. Node access controls — who can write to the ledger? Is private key management formally documented, segregated from operations, and backed by a hardware security module (HSM)?
2. Smart-contract version control — which version of the contract code was live during the audit period? Were upgrades reviewed, tested, and approved through a change management process?
3. Consensus mechanism reliability — does a single node failure or collusion scenario create a realistic integrity risk?
4. Oracle reliability — if the smart contract depends on external data feeds (commodity prices, IoT delivery sensors), is the oracle source independently auditable?

The Middleware Transformation Layer — the Highest-Risk Point Most Auditors Miss

Most enterprise blockchain deployments do not replace the ERP. A middleware API sits between the chain and SAP, Oracle, or Tally, reading on-chain events and posting journal entries. This layer is where errors concentrate. Middleware logic can aggregate transactions (masking individual amounts), net contra entries (violating Ind AS disclosure requirements), or apply incorrect account codes systematically.

Your audit procedure must include:

• Obtaining the middleware logic documentation and mapping
• Tracing a risk-stratified sample of on-chain transactions through the middleware to the final ERP posting
• Running an independent query on the blockchain node and reconciling the transaction count to ERP postings (testing completeness)
• Confirming that the middleware applies no unauthorised netting or aggregation

ICAI's Guidance Note on Audit in a Blockchain Environment and the updated Technical Guide on Audit of IT Systems — both current for the 2026 CPE cycle — provide the framework for designing these procedures.

Roadmap: Six Steps to Piloting Blockchain in Your Accounting Function

Step 1 — Define the problem before choosing a platform. Pick one high-volume, reconciliation-heavy process: intercompany payables, vendor invoice matching for a commodity supplier, or export documentation. Do not evaluate platforms until you have written down exactly what reconciliation pain you are solving and what "success" looks like in measurable terms (FTE hours saved, error rate reduction, reconciliation cycle time).

Step 2 — Select a permissioned blockchain. Public chains (Ethereum, Bitcoin) are unsuitable for enterprise accounting — gas cost volatility, public data exposure, and throughput limitations rule them out. Use Hyperledger Fabric, R3 Corda, or ConsenSys Quorum. These platforms offer controlled membership, private data collections, and throughput compatible with enterprise transaction volumes.

Step 3 — Separate on-chain and off-chain data before writing a line of code. The Digital Personal Data Protection Act, 2023 (DPDP Act) grants data principals the right to erasure of personal data. An immutable chain cannot comply with erasure requests. The rule is simple: store only a cryptographic hash of the document on-chain (proving the document existed and has not changed); store the actual document — with any personal data — in a DPDP-compliant, erasable off-chain repository.

Step 4 — Design the middleware mapping first. Your ERP journal entry structure, your chart of accounts mapping, and your GST input credit logic must all be defined before the middleware is built. Retrofitting accounting logic into middleware that is already processing live transactions is the single most common implementation failure.

Step 5 — Brief your statutory auditor before go-live. Auditors who encounter a live blockchain system for the first time during annual fieldwork face a steep learning curve and will invariably issue management letters on ITGC gaps. Engage your auditor at control-design stage. Share the smart-contract code, the key management policy, and the middleware mapping document. An auditor who has reviewed the design can issue a cleaner opinion and provide genuinely useful recommendations rather than generic observations.

Step 6 — Run a parallel period. Operate both the legacy reconciliation process and the new blockchain process side-by-side for one quarter. This lets you catch transformation errors in the middleware before they propagate into audited financial statements. At the end of the parallel period, the delta should be zero — any difference is a bug in the middleware or a gap in the chart of accounts mapping.

Common Mistakes and Pitfalls to Avoid

Treating blockchain as a substitute for accounting controls. Blockchain guarantees that what was recorded has not been altered. It does not guarantee that what was recorded was correct. A mis-coded journal entry posted on-chain is an immutable mis-coded journal entry.

Storing personal data on-chain. Supplier PAN, employee details, and customer contact information on an immutable ledger create an unfixable DPDP Act compliance gap. Design the separation at project inception.

Failing to document private key management. The entity that controls the private key controls asset access or ledger write access. Loss or compromise of a private key is equivalent to loss of the asset or a material ITGC failure. Your internal control documentation must specify: key generation environment, storage medium (HSM is the standard), access authorization matrix, rotation schedule, and disaster-recovery procedure.

Misclassifying VDA gains as speculative business income. Post Section 115BBH, VDA gains have their own dedicated tax head. Filing them under Business Income — even at similar effective rates — creates scrutiny risk and potentially incorrect loss set-off claims that trigger notices.

Ignoring advance tax on lumpy VDA gains. If the VDA position is large and concentrated in one quarter, advance tax defaults under Section 234B and 234C can be a five-to-six-digit liability in themselves.

Key Takeaways

• Triple-entry accounting reduces reconciliation, not accounting itself — distributed ledgers create a shared source of truth, but every on-chain event still requires a corresponding double-entry in your Ind AS-compliant ERP.
• Classify digital assets before you hold them — Ind AS 2, Ind AS 38, Ind AS 109, and Ind AS 7 give different answers for different asset types; the accounting policy note must document the rationale.
• VDA tax for AY 2027-28 is unambiguous — 30% under Section 115BBH on gains above cost of acquisition, no expense deduction, no loss set-off, 1% TDS under Section 194S, advance tax on the standard four due dates.
• The middleware layer between the blockchain and your ERP is the highest audit risk — trace a sample from chain to ledger; never rely solely on the ERP printout.
• DPDP Act 2023 mandates off-chain personal data — store hashes on-chain for integrity; keep all personally identifiable information in an erasable, DPDP-compliant system.
• Engage your statutory auditor at design stage — auditors involved in control design issue fewer qualifications and more useful recommendations than auditors who encounter the system live for the first time.
• Upskill deliberately and narrowly — ICAI's DISA qualification and ISA certification cover IT general controls, blockchain audit, and crypto-tax in an Indian regulatory context; targeted upskilling delivers measurable returns on the first engagement.