Skip to content
Modules

One ledger, read five different ways.

Most ERPs bolt a compliance report onto an operational database and call it reporting. Profinlex is arranged the other way round: the operational modules post into a ledger that is already being verified, and each module is a different lens on that same verified record.

Modules
Five, on one ledger
Frameworks applied
Ind AS, GST, income tax, Companies Act, SEBI, RBI
Verification point
At posting, not at period end
How the modules relate

Three layers, and every module sits across all three.

This is why a compliance product cannot be added later. Verification needs the transaction, the document and the authority at the same moment they are created.

The operating layer records what happened

Orders, receipts, stock, payroll. Nothing is verified here - things are simply recorded accurately and immediately, with their supporting document attached.

The verification layer decides whether it holds

Recognition, presentation, credit eligibility, deduction rate, approval requirement, clause compliance. Each test names the standard it is applying and the entry it applied to.

The evidence layer makes it provable later

The edit log, the document linkage, the approval history and the retention rules - so a question asked two years from now has an answer that does not depend on anyone's memory.

The five modules

What each one owns, and what it will not let you do.

01

Financial Reporting & Statutory Compliance

Ledger, close and statutory reporting in one place - with Schedule III presentation, Ind AS recognition rules and control-account reconciliation applied continuously instead of at year end.

Verified against

  • Ind AS and AS
  • Schedule III, Division II & III
  • Companies Act 2013, s.128 & s.129
  • CARO 2020
  • AOC-4 / AOC-4 XBRL
Open Financial Reporting

What it raises on its own

  • A control account that no longer agrees with its sub-ledger
  • Revenue posted without the performance obligation being satisfied
  • A lease payment expensed where Ind AS 116 requires recognition
  • Depreciation on a life that departs from Schedule II without a technical justification on record
02

Audit Trail & Documentation

A complete, time-stamped record of every financial and legal action, with source documents linked to the entries they support and export packs an auditor can work from directly.

Verified against

  • Rule 3(1), Companies (Accounts) Rules 2014 - edit log
  • Companies Act 2013, s.128 - books and eight-year retention
  • SA 230 - audit documentation
  • SA 500 - audit evidence
  • ICFR documentation under s.134(5)(e)
Open Audit Trail

What it raises on its own

  • A back-dated entry posted into a period already reported
  • An entry approved above the approver's authority limit
  • A voucher with no supporting document attached past the policy window
  • A document replaced after the entry was approved
03

Tax & Regulatory Filing

GST, TDS, TCS, direct tax and sector-specific returns prepared from source data, with a per-registration filing calendar, reconciliation against government statements, and a notice register.

Verified against

  • CGST Act 2017 - GSTR-1, 3B, 9, 9C
  • GSTR-2B matching and s.16 ITC conditions
  • E-invoicing and e-way bill rules
  • Income-tax Act - Chapter XVII-B and XVII-BB
  • Form 26Q / 24Q / 27EQ, Form 16 and 16A
Open Tax & Filing

What it raises on its own

  • Input tax credit claimed on an invoice not appearing in GSTR-2B
  • An outward supply invoiced without an IRN generated
  • TDS deducted at a rate below the section rate with no certificate on record
  • An MSME payable crossing the 45-day window
04

Legal, Contract & Entity Management

Contract repository with obligations extracted, related-party and entity registers mapped to statute, and continuous reconciliation between agreed terms and recorded transactions.

Verified against

  • Companies Act 2013, s.188 - related-party transactions
  • Companies Act 2013, s.185 & s.186 - loans and investments
  • Ind AS 24 - related-party disclosures
  • Statutory registers under s.85, s.88, s.170
  • SEBI LODR Reg. 23 - RPT approvals
Open Legal & Entity

What it raises on its own

  • An invoice raised at a rate the contract does not support
  • A contractual escalation due but never billed
  • A related-party transaction recorded before its approval date
  • A renewal or notice window closing inside the next quarter
05

Core Operations

Sales, procurement, inventory, production and payroll, with every confirmed document posting its accounting entry at the moment of confirmation.

Verified against

  • Ind AS 2 - inventory measurement
  • Ind AS 115 - revenue and contract balances
  • Ind AS 16 - property, plant and equipment
  • E-invoicing under Rule 48(4)
  • E-way bill under Rule 138
Open Core Operations

What it raises on its own

  • A dispatch made without an e-way bill where one is required
  • An invoice raised above the customer's approved credit limit
  • A goods receipt with no purchase order behind it
  • Stock ageing past the provisioning threshold with no provision made
Working session

Bring one messy period and we will walk it through the five modules.

Pick a quarter you know had problems - an ITC mismatch, a late filing, a related-party approval out of sequence. We will show you where each one would have been caught, and what the record would have looked like when the auditor arrived.

  • Your own chart of accounts, mapped to Schedule III presentation
  • Your registrations turned into a filing calendar with owners
  • One contract read against its own invoices