Synthetic report

Navkaar Moonloom Demo Components record

This report mirrors the Parakh report journey, but every source and business fact is synthetic.

Demo reference
DEMO-2026-0002
Report ID
PRK-SYN-DELAY-002

DEMO REFERENCE DEMO-2026-0002 · Maharashtra

Navkaar Moonloom Demo Components Private Limited

SPECIMEN
IDENTITY
Synthetic profile found
CLEAR
FILING
Repeated filing delay pattern
FLAG
RECORDS
No synthetic public-record signal in this fixture
NOTE
LIMITS
3 unavailable source area(s) disclosed
NOTE

Could not find: Live GST portal confirmation, Whether delays were cured after the synthetic data snapshot, Underlying tax-office notices, if any.

No candidate record to compare

This fixture supplies no candidate records. That does not establish that no records exist.

Try the identity check example
Synthetic-data disclosure: This public synthetic demo uses fictional data only. It does not access live government systems, private records, real GSTINs, PANs, Aadhaar numbers, OTPs, payments, or production Parakh data.
CICRA 2005 note: This synthetic demonstration is not a credit information report, legal opinion, or automated credit decision.

SYNTHETIC DEMO - NOT A REAL REGISTRATION

AI Summary

Thinking

Reviewing the synthetic evidence and record attributions…

The synthetic findings remain available while AI synthesis is pending or unavailable.

Who you are dealing with

Identity and structure

Legal name
Navkaar Moonloom Demo Components Private Limited
Trade name
Navkaar Moonloom Demo Components
Constitution
Private Limited Company
State
Maharashtra
Status
Active in synthetic registry
Synthetic registry since
12 Jan 2026
Address
Unit 302, Trade Link Corporate Hub, Senapati Bapat Marg, Lower Parel, Mumbai, Maharashtra 400013 (Fictional commercial address)
Source
Local synthetic fixture, generated for Parakh demo

Statutory returns & timing compliance

GST return filing

Filing history shows delays

Available filing data covers 5 fixture periods. GSTR-1 and GSTR-3B filings are evaluated against standard statutory due dates.

FLAG
ReturnPublishedOn timeLateSource unavailable
GSTR-15230
GSTR-3B5220
GSTR-1MAR 26 – JUL 26
MAR26
APR26
MAY26
JUN26
JUL26
GSTR-3BMAR 26 – JUL 26
MAR26
APR26
MAY26
JUN26
JUL26
On timeLateNot available from source
PeriodGSTR-1GSTR-3BFiled on
Mar 2026delayedfiled25 Apr 2026
Apr 2026delayeddelayed29 May 2026
May 2026fileddelayed27 Jun 2026
Jun 2026delayedmissingNot available in fixture
Jul 2026filedfiled11 Aug 2026

Court and record examples

Public-record signals

No synthetic public-record signal is present in this fixture.

Evidence, not rating

Observations

CLEARSynthetic profile found

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

FLAGRepeated filing delay pattern

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

NOTERead with demo limitations

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 scenario

SYN-GSTIN-CLEAR-001Clean trading partner · Mostly clear businessSYN-GSTIN-DELAY-002Delayed filings · Delayed filing patternSYN-GSTIN-MISMATCH-003Name mismatch · Identity/name mismatchSYN-GSTIN-COURT-004Public-record signal · Public-record/court-signal exampleSYN-GSTIN-PARTIAL-005Partial data · Partial or insufficient data

How this report was generated

  1. 01Accept only an obvious synthetic identifier
  2. 02Load local synthetic profile, filing, and public-record fixtures
  3. 03Normalize names, dates, filing periods, and record parties
  4. 04Create observations with FLAG, CLEAR, and NOTE labels only
  5. 05Run server-side AI attribution reasoning for each returned public-record signal
  6. 06Render model decision, confidence, justification, or fixture-grade fallback
  7. 07Synthesize the resolved attribution results and filing evidence into one descriptive AI Summary
  8. 08Attach 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.

Back to search