KUBR

Software firm paid $12.5M to settle SEC charges after $190M revenue restatement

Synchronoss Technologies, Inc. · Cloud and messaging software

Revenue inflationForged documentsGovernance failure

The case in brief

Visible before detection

    Checks that could have surfaced it, on hindsight

    1

    Document authenticity / direct pull

    A direct pull of contracts and side letters from sales staff would show payment contingent on future events.

    Can mislead when: The company can refuse consent, and a refusal is itself a flag. Some banks and co-op banks are not on AA yet.

    2

    Third-party confirmation

    Customer confirmations would reveal conditions not in the contract file.

    Can mislead when: Counterparties can collude or ignore requests. A non-response is logged as a gap, never as a pass.

    3

    Books edit log

    Revenue entries and their timing would show upfront recognition.

    Can mislead when: Logs can be disabled at database level (auditors qualified this in year one) or tampered with on export. Kubr needs the company to cooperate.

    Where Kubr services would have helped

    Financial diligence

    Offered in India
    • C5 A direct pull of contracts and side letters from sales staff would show payment contingent on future events.
    • C12 Revenue entries and their timing would show upfront recognition.

    Valuation context

    Offered in India
    • Peer multiples and the exit-multiple bridge would have shown how much of the story relied on valuation holding.

    IC note

    Offered in India
    • C5 A direct pull of contracts and side letters from sales staff would show payment contingent on future events.

    Mapped from the checks each service runs. A hindsight reading of public records, not a promise that the failure would have been found.

    A summary of public documents. It reports what the sources say. It is not Kubr's finding and not a statement of guilt.