Desk access — role-based
Two sides of the rail. Nobody sees both.
A corporate treasury reaches only the application desk, and only the filings raised under its own identity. A regulator officer reaches only the approvals queue, and may sign only for the authority they serve — the other five desks stay read-only.
In plain words
Pick who you are. The site then hides everything that is not your business — a company cannot read another company's file, and an officer cannot sign in someone else's name.
Corporate treasury
File and track your own entity
Registers the filing, attaches the annexures and follows the ten stages. Sees no other company's reference, and cannot open the approvals queue.
Regulator officer
Hold office at one authority
Sees the approvals queue for every filing on the rail, but the approve and query actions unlock only on the desk of the authority signed in below.
Corporate treasury desk — 3D simulation of one application
What the application actually does after you press send.
Before you sign in, watch a demonstration file run the full corridor: the treasury desk, the reasoning engine that fixes the route, the AD Category-I bank that is the only lawful door out of India, the GIFT IFSC ledger the six regulators read, and the overseas bank finally credited.
The moment the treasury clicks
- 01running
Field validation as you type
Entity, hub, amount and AD bank are bound to the audited net-worth record before the button is even live. Nothing incomplete can be submitted.
- 02queued
Route decided in the same second
The commitment is tested against the Rule 7 ceiling and the sector conditions. The engine returns Automatic or Approval with the rule quoted, not a queue ticket.
- 03queued
Annexures hashed and bound
Every attachment is digested and the digests are bound to the reference, so no page can be swapped after filing.
- 04queued
One write to the ledger
The packet is written once to the append-only ledger. There is no second copy for the bank and a third for the regulator.
- 05queued
Six desks attach in parallel
All six authorities read the same line while the transaction is still forming, each running its own queue at once.
In plain words: one click starts everything. The company keys the file once, and the bank and the regulators are looking at that same file within seconds.
Regulator desk — automated work queues in parallel
Six authorities. Six queues. One window of seconds.
Choose an authority from the dropdown to see exactly what it has to approve on an approval-route file, how many of those checks the engine clears on its own, and which few still need a named officer's signature.
Desks signed
0 / 6
Checks automated
81% of 16
Quorum ETA
1m 02s
Approval ETA, desk by desk — seconds on the rail against the legacy queue
Why manual intervention is small
Of the 16 statutory checks the six authorities owe on this filing, 13 are pure rule tests — a ceiling, a list, a rate, a form pair — and the engine can complete them the second the packet lands. Only 3 carry discretion, and those are the ones a named officer signs. Run one after another the queue would take 204s; read in parallel off the same ledger line it closes in 59s, a saving of 145s on this filing alone.
Observer and operator desks — evidence permissions
Investor / observer
Read the file, change nothing
Diligence access to the rail, the evidence checklist and the audit trail. By default no status button is live — the administrator may grant specific statuses per step.
Platform administrator
Set who may update what
Opens the role permission matrix on every route step: allow or withdraw Outstanding, Prepared, Submitted and Validated for each desk, globally or step by step.