Synthetic report

Dakshin Papercloud Demo Works record

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

Demo reference: DEMO-2026-0003
Report ID: PRK-SYN-MISMATCH-003

DEMO REFERENCE DEMO-2026-0003 · Tamil Nadu

Dakshin Papercloud Demo Works Limited

SPECIMEN

IDENTITY

Synthetic profile found

CLEAR

FILING

Recent filing pattern is consistent

CLEAR

RECORDS

2 synthetic registry record(s) found

FLAG

LIMITS

3 unavailable source area(s) disclosed

NOTE

Could not find: Beneficial ownership confirmation, Live registry certificate, Consent-backed document upload from the counterparty.

AI identity check

Fictional evidence · runtime AI

Does this record belong to the same business?

A similar name is a reason to check, not a confirmed identity. Compare the source fields with the model’s explanation.

[E1] BUSINESS YOU ARE CHECKING

Dakshin Papercloud Demo Works Limited

Trade name: Dakshin Papercloud Demo Works

Synthetic entity marker: DEMO-ENTITY-MISMATCH

[R1] NAME ON THE RECORD

Dakshin Papercloud Demo Traders

DEMO-RECORD-0027 · Fictional registry entry

Synthetic entity marker: Not supplied

AI Attribution ReasoningDEMO-RECORD-0027THINKING

Reviewing the synthetic entity and candidate record…

See the exact evidence sent to AI

These fields are fictional. The model is not given the fixture’s expected decision, confidence, or match explanation. Identity markers are invented tokens, not PANs.

{
  "synthetic": true,
  "mode": "full",
  "E1": {
    "source": "Fictional business profile",
    "legalName": "Dakshin Papercloud Demo Works Limited",
    "tradeName": "Dakshin Papercloud Demo Works",
    "aliases": [
      "Dakshin Papercloud Demos Works Ltd",
      "Dakshin Papercloud Demo Traders",
      "Dakshin Papercloud Demo"
    ],
    "entityMarker": "DEMO-ENTITY-MISMATCH"
  },
  "R1": {
    "source": "Registrar of Companies / Trade Registry (Demo Ledger)",
    "reference": "DEMO-RECORD-0027",
    "category": "registry",
    "namedParty": "Dakshin Papercloud Demo Traders",
    "parties": [
      "Dakshin Papercloud Demo Works Limited",
      "Dakshin Papercloud Demo Traders"
    ],
    "entityMarker": null
  }
}

What changes when evidence is missing?

Remove both identity markers and ask AI again using the same names. The result below is a separate live experiment; it does not replace your report.

Your next step: ask the business for a document showing its registered legal name and identifier. Compare it with the original record before linking the two. No documents are uploaded in this demo.

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

Dakshin Papercloud Demo Works Limited

Trade name

Dakshin Papercloud Demo Works

Constitution

Public Limited Company

State

Tamil Nadu

Status

Active in synthetic registry

Synthetic registry since

12 Jan 2026

Address

Works No. 54, SIDCO Industrial Complex, Ambattur, Chennai, Tamil Nadu 600058 (Fictional commercial address)

Source

Local synthetic fixture, generated for Parakh demo

Statutory returns & timing compliance

GST return filing

Returns filed on time

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

CLEAR

Return	Published	On time	Late	Source unavailable
GSTR-1	4	4	0	0
GSTR-3B	4	4	0	0

GSTR-1MAR 26 – JUN 26

MAR26

APR26

MAY26

JUN26

GSTR-3BMAR 26 – JUN 26

MAR26

APR26

MAY26

JUN26

On timeLateNot available from source

Period	GSTR-1	GSTR-3B	Filed on
Mar 2026	filed	filed	10 Apr 2026
Apr 2026	filed	filed	09 May 2026
May 2026	filed	filed	10 Jun 2026
Jun 2026	filed	filed	11 Jul 2026

Court and record examples

Public-record signals

FLAGSYN-REG-MISMATCH-027

20 Jul 2026

Commercial invoice alias "Dakshin Papercloud Demo Traders" closely resembles the registered legal name, but lacks formal corporate entity documentation.

DEMO-RECORD-0027 · Registrar of Companies / Trade Registry (Demo Ledger)

Parties: DAKSHIN PAPERCLOUD DEMO WORKS LTD · DAKSHIN PAPERCLOUD DEMO TRADERS

Side: alias-party · Fixture descriptor: Similar synthetic alias; legal name is not exact

Fixture confidence Medium · Local synthetic fixture, generated for Parakh demo

AI Attribution ReasoningSYN-REG-MISMATCH-027THINKING

Reviewing the synthetic entity and candidate record…

NOTESYN-REG-MISMATCH-028

22 Jul 2026

A separate fictional legal entity shares the words Dakshin Papercloud Demo, but the searched synthetic entity is not named in this record.

DEMO-RECORD-0028 · Registrar of Companies / Trade Registry (Demo Ledger)

Parties: DAKSHIN PAPERCLOUD DEMO TRADERS PVT LTD

Side: not-applicable · Fixture descriptor: Similar words only; different synthetic legal entity

Fixture confidence High · Local synthetic fixture, generated for Parakh demo

AI Attribution ReasoningSYN-REG-MISMATCH-028THINKING

Reviewing the synthetic entity and candidate record…

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

CLEARRecent filing pattern is consistent

Available synthetic returns show regular filing markers across the recent periods included in this demo.

Confidence High · Derived from synthetic GST filing fixture rows

FLAGPublic-record signal needs review

Commercial invoice alias "Dakshin Papercloud Demo Traders" closely resembles the registered legal name, but lacks formal corporate entity documentation.

Confidence Medium · registry record SYN-REG-MISMATCH-027

NOTEPossible alias record

A separate fictional legal entity shares the words Dakshin Papercloud Demo, but the searched synthetic entity is not named in this record.

Confidence High · registry record SYN-REG-MISMATCH-028

FLAGName variants require confirmation

The synthetic fixture includes similar names that should be resolved before onboarding or payment release.

Confidence Medium · Normalized legal name and alias comparison

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

Beneficial ownership confirmation
Live registry certificate
Consent-backed document upload from the counterparty

Demo scenarios

Try another demo scenario

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

How this report was generated

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