Skip to main content
Security control 7/10 Locked periods or years are protected from silent change with governance and evidence.
ASSETREGISTER360
Start Free Trial
Security control 7

Locked periods.
Protected data.
Review-ready always.

Prevent silent changes, apply credible governance and maintain a controlled fixed asset register with separate statutory working, physical verification and review-ready reports.

  • Controlled fixed asset register
  • Separate books and Income-tax depreciation
  • Physical verification with human approval
  • Review-ready reports and attributed history
Designed for controlled finance workflowsRole-scoped accessPrivate report deliveryDocumented controls
Governed financial records inside a secure vault with a controller desk sign

Governance that protects what matters

Once a period is closed and locked, ordinary changes are blocked. Any governed change requires approval, reason and evidence.

  1. 1Create & review

    Capture records, calculate and prepare balances

  2. 2Close period

    Complete the period after review and approval

  3. 3Lock period

    Block ordinary changes after closure

  4. 4Change with approval

    Route governed changes with reason and evidence

  5. 5Immutable history

    Retain attributed application events

Why locked periods matter

No silent changesBlocks unintended edits.Stronger controlsSeparates duties and approvals.Review assuranceRetains time-stamped history.Statutory alignmentKeeps books and tax distinct.

Security controls built for trust

1. Access control

Role-scoped access, organisation and branch scope, restricted private documents and optional MFA.

2. Audit history

Create, update, delete, approval and lock events retain actor, time, action and record context.

3. Evidence & approvals

Reasons, documents and reviewer decisions remain attached to governed changes and exceptions.

4. Data validation

Useful-life, rate, date and classification checks stop invalid changes from silently entering reports.

Calculate depreciation accurately. Keep books and tax separate.

Companies Act (Schedule II) — Books DepreciationFY 2025-26
Total assets12,843Gross block1,256.48 CrDepreciation126.74 CrClosing WDV428.71 Cr
Income-tax Act — Block DepreciationFY 2025-26
Total assets12,843Gross block1,256.48 CrDepreciation126.74 CrClosing WDV428.71 Cr

Run physical verification. Reconcile with confidence.

Plan the scope, capture signed evidence, classify exceptions and approve the closeout before the controlled register changes.

  1. 1Plan

    Define scope, locations, teams and dates

  2. 2Verify

    Capture signed field evidence

  3. 3Reconcile

    Classify matches and variances

  4. 4Approve

    Review exceptions and close out

ScopeDefinedField evidenceAttachedComparisonReconciledCloseoutApprovedHistoryRetained

Review-ready reports. On demand.

Asset Register

Complete controlled register

Books Depreciation

Schedule II statement

Tax Depreciation

Block-wise statement

Verification

Status and evidence report

Variance Report

Reconciliation and closeout

Audit Trail

Attributed application events

Privacy & data handling

Your data remains private

Authenticated access and signed public verification links.

Encrypted transport

Production delivery is expected to use HTTPS and secure storage controls.

Scoped files

Private reports and documents use controlled download paths.

Retention control

Audit retention follows the selected plan and documented policy.

Right to remove

Authorised users can process deletion within application constraints.

Roles, responsibilities and review controls

Clear roles reduce accidental changes and preserve reviewer independence.

Asset creator

Create and maintain records without approving governed changes.

Reviewer

Review calculations, imports and exception work.

Approver

Approve governed changes and verification closeout.

Finance controller

Oversee books, tax and reporting outcomes.

Auditor

Read-only access to evidence and history when granted.

Assurance FAQ

Can ordinary data be changed in a locked financial year?+

Ordinary changes are blocked. Governed corrections must follow the authorised unlock or approval process available to the organisation.

Are books and Income-tax calculations kept separate?+

Yes. They share asset identity and lifecycle source data while retaining independent methods, rates, balances and outputs.

Is the audit trail tamper-proof?+

Application events are retained as controlled history. Infrastructure-level immutability depends on the production deployment and backup policy.

Who can approve a verification closeout?+

Only an authenticated user with the required organisation, branch and role scope can complete authorised closeout actions.

How are reports delivered?+

Reports are generated as private artifacts and downloaded through authenticated or otherwise scoped delivery paths.

How is physical verification controlled?+

Signed links capture evidence; reconciliation and register changes remain subject to authenticated human review.

Lock periods. Strengthen controls. Stay review-ready.

  • Book a controlled product walkthrough
  • Start a workspace in minutes
Book a DemoStart Free Trial