Does our accounting software legally need an audit trail in India?

If your company keeps its books electronically, the Companies (Accounts) Rules require accounting software with an audit trail that records each change to an accounting entry with the date of that change, cannot be disabled, and is preserved with the books. Your auditor must separately report on whether the feature was enabled and operated all year. Software permitting untraceable back-dated edits is therefore a reporting exposure, not a preference.

Where is input tax credit actually lost, and how do we stop it?

Almost always in the gap between your purchase register and GSTR-2B. A supplier has not filed, has filed against the wrong GSTIN, or has raised the document in a period you did not expect. If you match monthly, it is a phone call to the supplier while the credit can still be corrected. If you match at the annual return, the same item is usually unrecoverable. The cadence matters more than the tooling.

Why does our month-end close take two weeks?

Usually unreconciled sub-ledgers rather than slow people. The recurring four are GR/IR, bank, inter-company and stock valuation against the ledger. Each is a reconciliation that could have happened continuously but was deferred to the close, so finance spends the first fortnight reconstructing rather than reviewing. Notably, most of these originate in purchasing, stores or treasury, and are only discovered in finance.

Can a group run each entity in a separate Tally file and still consolidate?

It can produce a consolidation, but not quickly and not with an audit path. Separate files mean different charts, unmatched inter-company postings, and elimination performed by hand in a workbook, so no group figure traces back to a posting. The fix is one chart of accounts and one master data regime with consolidation derived in the ledger — which is an architecture change, not a reporting change.

Do we need SAP or Oracle, or is Business Central enough?

It depends on entity count, currencies and reporting complexity rather than turnover. A single-entity business with one functional currency and straightforward operations does not need a tier-one platform and will resent its run cost. Business Central, Xtreme Industry ERP or WorkSuite Finance fits there. S/4HANA Finance and Oracle Fusion earn their keep with many legal entities, multiple functional currencies and Ind AS alongside local books.

What does segregation of duties mean in practice for payments?

That the person who creates or amends a vendor cannot approve payments to it, enforced by the system rather than noticed in review. The related control is bank-detail changes: treat them as high-risk, verify by independent call-back to a previously held number, attach the evidence, and log the change. Most payment fraud we are asked about afterwards turned on one of those two gaps.

Why do fixed assets need two depreciation registers?

Because two statutes require different calculations on the same assets. The Companies Act register works from useful life and residual value per asset, with component accounting where parts have materially different lives. The Income Tax register uses the written-down-value block-of-assets method, applied to the block rather than the individual asset. Maintaining one and adjusting the other manually is a common source of deferred tax error.

Why can our finance team not just handle Ind AS adjustments at period end?

Because the adjustments need data the transaction system must capture at source. Revenue recognised over time needs performance-obligation and progress data from the contract or project system. Lease accounting needs term, options, discount rate and payment schedule held as data so modifications can be re-measured. Expected credit loss needs retained loss history by segment. Without those inputs, the adjustment becomes an estimate an auditor will challenge.

Finance Software: Accounting Software for Business

Finance software that can survive an audit and close in days

Most finance software pages sell dashboards. Indian finance teams are not short of dashboards; they are short of a general ledger that can prove who changed what. Since the audit trail requirement entered the Companies (Accounts) Rules, accounting software for business in India has had a legal specification, not just a feature list — every change logged, the log impossible to switch off, and the auditor obliged to report on it. A great many companies are non-compliant and have not been told. That is where this page starts, because it is the reason most of the finance replacements we are asked to run actually begin.

Edit log

Statutory, and it cannot be disabled

GSTR-2B

Reconciled monthly, not at year end

2 registers

Fixed assets under two separate statutes

ISO 27001

Certified, CMMI Level 3 appraised

Audit trail accounting software: what the log has to actually do

An edit log that an administrator can switch off, or that records only the final state of a record, does not meet the requirement. The test is whether an auditor can reconstruct a change without your help.

Every create, modify and delete on an accounting entry captured with user, timestamp and the before and after values
Logging enforced at database or application level so it cannot be disabled by a privileged user, and any attempt is itself recorded
Period locking that makes back-dated posting an explicit, logged, approved exception rather than a silent edit
Retention of the log for the same period as the books, and a means of producing it for an auditor as evidence rather than as a screen

GST e-invoicing software, GSTR-2B and the credit you are losing

E-invoicing is the easy half — the IRN and signed QR come back from the portal and sit against the invoice. Reconciliation is the half that costs money.

IRN and signed QR obtained at the point of invoicing, stored against the document, with cancellation and amendment windows respected
GSTR-2B matched against the purchase register every month, split into matched, in-your-books-not-in-2B, and in-2B-not-in-your-books
Supplier non-filing surfaced as a name and an amount, so procurement can chase it while the credit is still recoverable
E-way bills generated from the despatch document with transporter and vehicle details, and GSTR-1 and 3B built from posted documents rather than reassembled

TDS and TCS: deduction at source, not reconstruction at quarter end

The recurring failure is TDS decided by a person at payment time rather than by the system at voucher entry. By the time Form 26AS disagrees with your ledger, the correction is a revised return.

Section-wise rates and thresholds held against the vendor master, with lower-deduction certificates and PAN status driving the rate applied
Challan-to-deduction mapping maintained as payments are made, so each deduction is traceable to the challan that remitted it
Form 26Q and 27Q populated from ledger data, with non-resident deductions carrying the detail that Form 27Q and Form 15CA/15CB work require
Periodic reconciliation of your deduction ledger against Form 26AS, and of TCS collected against the corresponding return, treated as a monthly control

Multi-entity accounting and financial consolidation software

A group running each entity as a separate accounting file cannot close quickly, because the group figure is assembled rather than posted. Consolidation belongs in the ledger.

One chart of accounts and one master data regime across entities, with local statutory requirements handled as attributes rather than as separate charts
Inter-company transactions posted as matched pairs so elimination is derived from the ledger, not typed into a consolidation workbook
Different functional currencies per entity, with translation to the group presentation currency and translation reserve movements traceable to source
Common control transactions and group restructurings modelled deliberately, since the accounting treatment differs from an ordinary acquisition

Month-end close automation: close is a process, not an event

Close takes two weeks because sub-ledgers are unreconciled, not because finance is slow. Naming the specific blockers is most of the fix.

Goods-received-against-invoice-received cleared continuously, so the GR/IR account is a working queue rather than a year-end mystery
Bank and inter-company reconciliations run daily or weekly, which converts the close from a reconciliation exercise into a review
Stock valuation agreed against the inventory ledger before the period closes, with variances explained rather than posted to a suspense account
A close calendar with named owners, dependencies and a task status anyone can see, so the bottleneck is visible on day three rather than day eleven

Accounts payable automation with real segregation of duties

The classic control failure is one person creating a vendor and approving its payment. Automation without segregation just makes the failure faster.

Vendor creation, amendment and payment approval held in separate roles, with the conflict blocked by the system rather than noticed in review
Bank-detail changes treated as a high-risk event: independent call-back verification to a previously held number, evidence attached, change logged
Three-way match of purchase order, goods receipt and invoice, with tolerances set deliberately and exceptions routed rather than auto-passed
Ageing that distinguishes dues to micro and small suppliers, since statutory payment terms and the related disclosure depend on that classification

Fixed assets: two parallel depreciation registers, by design

Block-of-assets depreciation under the Income Tax Act and component-level depreciation under the Companies Act are different calculations on the same assets. Running one and adjusting the other by hand is where deferred tax errors originate.

Companies Act register with useful life and residual value per asset, and component accounting where parts have materially different lives
Income Tax register on the written-down-value block method, with additions, deletions and the part-year rule applied to the block rather than the asset
Capital work in progress capitalised on a defined trigger, with borrowing costs and directly attributable expenditure included consistently
Deferred tax derived from the difference between the two registers automatically, and asset disposals writing back both consistently

Ind AS compliance: the data has to be captured at source

Ind AS treatments are the clearest example of an accounting requirement that cannot be solved in the accounting team. If the transaction system never captured the input, the adjustment becomes an estimate.

Revenue recognised over time needs performance-obligation and progress data from the contract and project system, not a period-end judgement
Lease accounting needs the lease term, extension options, discount rate and payment schedule held as data, with modifications re-measured rather than re-keyed
Expected credit loss needs receivable ageing by customer segment and actual loss history, which means the history must have been retained
Where Ind AS and tax or local books diverge, parallel ledgers or accounting principles held in the same system, so neither set is a manual derivation

Blocker	Root cause	The fix	Where it lives
GR/IR account full of unexplained items	Goods received without invoices, or invoices matched to the wrong receipt, cleared only when someone investigates at year end	Clear GR/IR as a weekly working queue with an owner, and tighten receipt discipline at the gate rather than in finance	Purchase-to-pay process, not the ledger
Bank reconciliation done once a month	Statements imported manually, unmatched items parked, and the reconciliation attempted only when the close demands it	Automated statement import with rule-based matching, reconciled daily or weekly so only genuine exceptions reach the close	Treasury and bank integration
Inter-company balances that never agree	Each entity posts its own side independently, with different dates, amounts or exchange rates, and no matching key	Post inter-company as matched pairs with a shared reference, agree balances before the period closes, and derive elimination from the ledger	Group accounting design
Stock value in the ledger differs from the stock system	Valuation run separately from inventory movements, with adjustments, rejections and job-work stock treated inconsistently	Agree the inventory sub-ledger to the general ledger before close, and investigate variances rather than posting them to suspense	Inventory and costing, upstream of finance
Input tax credit reconciled at annual return	GSTR-2B matched only when the annual return forces it, by which point non-filing suppliers cannot be corrected	Monthly three-way match of purchase register, GSTR-2B and payments, with supplier non-filing escalated to procurement by name	GST compliance cadence
TDS corrected through revised returns	Deduction decided by a person at payment time instead of by the system at voucher entry, then found wrong against Form 26AS	Drive rates from the vendor master with certificate and PAN status, map challans as remittances are made, reconcile to 26AS monthly	Vendor master and voucher configuration
Consolidation rebuilt in a workbook each period	Separate accounting files per entity, with different charts and no shared master data, so the group figure is assembled by hand	One chart and one master data regime, ledger-level consolidation, and translation handled in the system with an audit path to source	Platform architecture — the expensive one to fix late
Journals appearing after the period is closed	No period lock, or a lock that a privileged user can lift without leaving a record	Hard period close with reopening as an approved, logged exception, and the audit trail enforced below the application layer	Controls and the audit trail itself

Blocker

Root cause

The fix

Where it lives

GR/IR account full of unexplained items

Goods received without invoices, or invoices matched to the wrong receipt, cleared only when someone investigates at year end

Clear GR/IR as a weekly working queue with an owner, and tighten receipt discipline at the gate rather than in finance

Purchase-to-pay process, not the ledger

Bank reconciliation done once a month

Statements imported manually, unmatched items parked, and the reconciliation attempted only when the close demands it

Automated statement import with rule-based matching, reconciled daily or weekly so only genuine exceptions reach the close

Treasury and bank integration

Inter-company balances that never agree

Each entity posts its own side independently, with different dates, amounts or exchange rates, and no matching key

Post inter-company as matched pairs with a shared reference, agree balances before the period closes, and derive elimination from the ledger

Group accounting design

Stock value in the ledger differs from the stock system

Valuation run separately from inventory movements, with adjustments, rejections and job-work stock treated inconsistently

Agree the inventory sub-ledger to the general ledger before close, and investigate variances rather than posting them to suspense

Inventory and costing, upstream of finance

Input tax credit reconciled at annual return

GSTR-2B matched only when the annual return forces it, by which point non-filing suppliers cannot be corrected

Monthly three-way match of purchase register, GSTR-2B and payments, with supplier non-filing escalated to procurement by name

GST compliance cadence

TDS corrected through revised returns

Deduction decided by a person at payment time instead of by the system at voucher entry, then found wrong against Form 26AS

Drive rates from the vendor master with certificate and PAN status, map challans as remittances are made, reconcile to 26AS monthly

Vendor master and voucher configuration

Consolidation rebuilt in a workbook each period

Separate accounting files per entity, with different charts and no shared master data, so the group figure is assembled by hand

One chart and one master data regime, ledger-level consolidation, and translation handled in the system with an audit path to source

Platform architecture — the expensive one to fix late

Journals appearing after the period is closed

No period lock, or a lock that a privileged user can lift without leaving a record

Hard period close with reopening as an approved, logged exception, and the audit trail enforced below the application layer

Controls and the audit trail itself

Finance software that can survive an audit and close in days

Symptoms we are usually called about

The audit trail rule changed what counts as acceptable accounting software

The eight areas that decide whether your finance system holds

Audit trail accounting software: what the log has to actually do

GST e-invoicing software, GSTR-2B and the credit you are losing

TDS and TCS: deduction at source, not reconstruction at quarter end

Multi-entity accounting and financial consolidation software

Month-end close automation: close is a process, not an event

Accounts payable automation with real segregation of duties

Fixed assets: two parallel depreciation registers, by design

Ind AS compliance: the data has to be captured at source

What actually stops a fast close — and where each fix lives

How we run a finance implementation

Compliance and control baseline

Chart of accounts, entity model and statutory design

Platform fit and configuration to standard

Migration, controls testing and a rehearsed cutover

Supported first close, then a controls handover

Where to go next

Finance software questions we are asked most often

Let's build what's next — together.