SEBI bars GDR issuer for 10 years after it pledged its own GDR proceeds
Maars Software International Limited · Listed software company
The case in brief
Visible before detection
Checks that could have surfaced it, on hindsight
Third-party confirmation
Bank confirmation would show the GDR proceeds were pledged to the subscriber's lender.
Can mislead when: Counterparties can collude or ignore requests. A non-response is logged as a gap, never as a pass.
Ownership / related-party links
Ownership links would connect the subscriber to the placing agent.
Can mislead when: Nominee directors and offshore layers hide links. Name matching throws up false positives, so every flag shows its evidence path.
End-use tracing of funds
End-use tracing would show no free funds from the issue.
Can mislead when: Kubr sees only the company's own accounts. Once money reaches a third party's bank, Kubr can flag the payee but cannot see the next hop without that party's consent.
Where Kubr services would have helped
Valuation context
Offered in India- Peer multiples and the exit-multiple bridge would have shown how much of the story relied on valuation holding.
Borrower monitor
Offered in India- C3 Ownership links would connect the subscriber to the placing agent.
- C6 End-use tracing would show no free funds from the issue.
Proceeds tracer
Offered in India- C3 Ownership links would connect the subscriber to the placing agent.
- C6 End-use tracing would show no free funds from the issue.
Verified Snapshot
Offered in India- C3 Ownership links would connect the subscriber to the placing agent.
Mapped from the checks each service runs. A hindsight reading of public records, not a promise that the failure would have been found.
Same pattern
A summary of public documents. It reports what the sources say. It is not Kubr's finding and not a statement of guilt.