Synthetic report
Navkaar Metro Demo record
This report mirrors the Parakh report journey, but every source and business fact is synthetic.
- Demo reference
- DEMO-2026-0002
- Report ID
- PRK-DEMO-2026-0002
Demo reference DEMO-2026-0002 · Maharashtra
Parakh Demo Entity Navkaar Metro Components Private Limited
Could not find: Live GST portal confirmation, Whether delays were cured after the synthetic data snapshot, Underlying tax-office notices, if any.
SYNTHETIC DEMO - NOT A REAL REGISTRATION
Who you are dealing with
Identity and structure
Recent return behaviour
Filing pattern
| Period | GSTR-1 | GSTR-3B | Filed on |
|---|---|---|---|
| Mar 2026 | delayed | filed | 25 Apr 2026 |
| Apr 2026 | delayed | delayed | 29 May 2026 |
| May 2026 | filed | delayed | 27 Jun 2026 |
| Jun 2026 | delayed | missing | Not available in fixture |
| Jul 2026 | filed | filed | 11 Aug 2026 |
Court and record examples
Public-record signals
Evidence, not rating
Observations
The searched identifier resolves to a local synthetic business profile with a legal name, trade name, state, and registration marker.
Confidence High · Synthetic business profile lookup
4 recent synthetic periods include delayed or missing return markers. This is an operational follow-up signal, not a credit or trust verdict.
Confidence High · Derived from synthetic GST filing fixture rows
This demo explains what the evidence says and what it cannot say. It does not score, rate, or clear a counterparty.
Confidence Medium · Report methodology note
Limits
What we could not find
- Live GST portal confirmation
- Whether delays were cured after the synthetic data snapshot
- Underlying tax-office notices, if any
Demo scenarios
Try another demo reference
How this report was generated
- Accept only an obvious synthetic identifier
- Load local synthetic profile, filing, and public-record fixtures
- Run fixture-only V4-style normalization and court-candidate resolution
- Create observations with FLAG, CLEAR, and NOTE labels only
- Attach confidence, attribution, provenance, limits, and synthetic disclosure
Production use would require authorized APIs, consent-aware handling, audit logs, rate limits, data provenance, retention limits, security controls, and human-readable limitations.