All products
Audit & Assurance
CA Audit
AboutContactSupportSign InBook a Demo →
IRDAI Returns · NL forms · public disclosures

Load the ledger dump. The return is there.

Every figure in an IRDAI NL return is derived in the database from your general-ledger dump — no seeded numbers, no hard-coded figures, no workbook re-opened. The sign rule, period scopes and segment mapping are applied server-side, a whole filing computes in about two seconds, and every version, assignment and four-eyes sign-off is on record for the inspector who asks about one cell eighteen months later.

✓ NL-1 → NL-48✓ Derived in Postgres✓ 67,226 lines → 734 buckets in ~1s✓ Versioned filings✓ Four-eyes sign-off✓ Cell-level audit
48
NL forms in scope, including multi-part and FRB forms
~2s
A seven-form filing computed from a 67,226-line ledger
0
Seeded or hard-coded figures — the dump is the only source
1
Analysis code per account — your mapping, ingested as evidence
The problem

NL returns are built in a workbook that nobody can re-derive.

Each quarter someone re-cuts the ledger into forty-odd templates. A year later, the question ‘where did this cell come from?’ has no answer.

Re-keyed each quarter

Ledger to pivot to template — every step a chance to drift.

No versioning

A re-cut overwrites the filed number.

No cell lineage

An inspector's question about one cell becomes a week of reconstruction.

What others can't do

What a template pack cannot do.

The return is a function of the ledger — rerun it and you get the same number.

ONLY HERE · 01

Your mapping, as evidence

The IRDA analysis code on every journal line is ingested, not re-derived.

ONLY HERE · 02

A reversal is not a disposal

Fixed-asset movements read line by line so reclassifications and CWIP transfers are not misread.

ONLY HERE · 03

Refuses edits to a signed filing

Once signed, cells are locked; a re-cut creates a new version.

ONLY HERE · 04

Cost flat as the ledger grows

Aggregation happens in the database; buckets, not lines, cross the wire.

What is inside

What is inside.

Ingest, derive, review, sign, publish.

INGLedger intakePin a return to one dump and one reporting cut.
DRVDerivationSign rules, period scopes and segment mapping server-side.
FRMFormsRevenue, P&L, balance sheet, schedules, investments, solvency, ratios and business forms.
CTLControlsCross-form tie-outs and benchmark checks.
WFWorkflowAssignments, four-eyes and versioned filings.
EXPExportFiling-ready workbooks and public-disclosure output.
AI roadmap

Where AI will help.

Figures stay derived. AI helps reviewers.

Variance commentary

Roadmap

Quarter-on-quarter movements explained from the derived buckets.

Unmapped-account suggestions

Roadmap

New accounts proposed an analysis code from their postings.

The boundary

Across every FinIFRS product the rule is the same: a deterministic, tested engine computes and stores every figure first. AI reads documents, drafts sentences and answers questions over what is already stored — it never computes, posts or approves an amount.

Highly configurable

Configured to your ledger.

Masters and mappings are data, per entity and per year.

Account-to-analysis-code mapping.
Segment mapping.
Period and fiscal-calendar rules.
Form layouts and multi-part grouping.
Neck and neck

Side by side.

Against the template workbook.

CapabilityTemplate workbookConsultant packFinIFRS
Every figure derived from the ledgerPastedPasted✓ In the database
Versioned filings——✓ Native
Cell-level audit——✓ Native
The questions the room actually asks

Next year?

Load the new dump, open a filing, and the return is there.

Beyond the product lines

We build the AI-native finance automation you can't buy.

A regulator's bespoke return, a partner settlement, a reconciliation between two systems only you run. We build it to your requirement on the same engines, audit trail and AI boundary our products run on — in weeks, with golden tests, and handed over as configuration your team owns.

01Deterministic where money movesEvery figure is computed by a tested engine — never by a model.
02AI where documents and questions areExtraction, narrative and Q&A over stored facts, with validation.
03Governance from day oneHash-chained audit, maker-checker and tenant isolation, inherited.
04Yours to changeRules as versioned configuration your controllers edit after go-live.