Corporate portal — file and track
Submit the route and the documents for your entity. Watch the file clear, live.
This is the treasury-side desk. Register the filing, confirm the route the law gives you, attach each annexure against the statute that demands it, and then follow the ticket through all ten stages as they clear in real time. Filings stay on this device under their reference, so you can leave and come back.
In plain words — this is the online counter where a company hands in its paperwork to send money abroad, and a tracking screen that shows exactly where the file has reached, like parcel tracking.
AD Category-I bank — live processing tape
0 eventsNo filing on the rail yet. File one from the Corporate Application desk and every bank action appears here as it happens.
Qwen · reasoning
Statutory reasoning model reads the rule and the filing together, and writes the conclusion with the rule quoted.
LangChain · orchestration
Chains the retrieval, tool calls and checks in a fixed order so every filing is examined the same way.
Alibaba Cloud · compute
Runs the heavy document and screening workloads in an India-resident region.
Federated ledger
Each result is hash-chained into a block every regulator node holds a copy of.
Human desk
A named officer signs this off. The machine only prepares the file.
Your AD Category-I bank is working the file above. The supervisory side of the same filing — including who must sign an Approval-route case — is on the Regulator Approval desk.
Step 1 — register the filing
Company universe
Ranked by audited net worth; Rule 7 ceiling is 400% of that net worth.
Indian party (483 entities in this universe)
Target hub (52 centres)
Amount to be sent abroad (INR crore)
Authorised signatory
Notification address
Route submitted
Inside the Rule 7 ceiling, unrestricted sector
Audited net worth
₹3,27,080 Cr
400% ceiling (Rule 7)
₹13,08,320 Cr
Headroom after this filing
₹7,16,086 Cr
Value leaving India
₹12,40,00,00,000 · SGD
Step 2 — documentation for the submitted route
Documentation checklist — Automatic route vs Approval route
Automatic route · 0/6 attachedIn plain words
Both routes need the same six core papers. The Approval route asks for three more, because a human regulator has to be persuaded before the money may leave — not merely informed after.
Filing readiness
0/6
In plain words — the counter only accepts a complete file on the correct route, because an incomplete or wrongly routed file is exactly what causes months of delay.
Step 3 — live status tracking
Track by reference
Search
Status
Hub
Current stage
No filings yet. Register one above and it will appear here with a live status.
Select or file an application to open its live tracker.
In plain words — each row is one checkpoint the file must pass. The bar under a row fills while that checkpoint is working, and a fingerprint is written when it finishes — so nobody can later claim a step was skipped.
Step 4 — live ledger sync and action timeline
Federated ledger sync · corporate view
6 member nodes · All proofs verified
0 ms
Checkpoint ingestion latency
Time from a desk clearing a step to every node holding the block.
—
Last confirmed block
No block committed yet on this device.
0
Confirmed checkpoints
0 checkpoints currently in flight.
0 / 0
Retries / failed proofs
Re-broadcasts and rejected proofs, both regenerated before commit.
Retry and proof-failure log
No retries and no failed proofs on the checkpoints committed so far.
In plain words
This panel shows how quickly each cleared step reaches every regulator's copy of the record, when the last one landed, and whether any had to be sent again before it was accepted.
Select one of your filings above to open its checkpoint-by-checkpoint timeline.
Step 5 — audit log and evidence hash explorer
Select a filing above to open its audit log and evidence chain.
Audit console — corporate desk
0 of 0 blocks
Corporate
Checkpoint stage
Officer / designation
Status
From (UTC)
To (UTC)
| Reference | Corporate | Checkpoint | Cleared by | Timestamp (UTC) | Digest | Status |
|---|---|---|---|---|---|---|
| Nothing matches these filters. Widen the stage, officer or UTC window. | ||||||
In plain words
Narrow the record to one company, one checkpoint, one officer or one window of clock time, switch between the blockchain checkpoints and the human action trail — who did what, when, and from which page — and download exactly that selection as a spreadsheet or a PDF. You only ever see the filings your role permits.
In plain words — this is the permanent record of the file: what happened, exactly when, who signed it, and the fingerprint of the paper they signed. Click any checkpoint to read its fingerprint, the documents behind it and the full chain back to the first block, or export the whole history as a spreadsheet or a signed-looking PDF for your auditor.
Step 5 — notifications at every stage
In-app notifications
0 unreadNo alerts yet. File an application and every checkpoint will report here the moment it clears.
Email notifications dispatched
0 sentStage notices addressed to the filing's notification address will appear here as they go out.
In plain words — the moment a checkpoint is signed off, a pop-up alert appears on screen, the alert is logged in the feed on the left, and a written notice addressed to the treasury contact is raised on the right — each one naming the officer or engine that cleared the step, the node they sit on, and the fingerprint of the evidence they produced. Nothing clears silently.