KUBR

Diamond Foods shifted walnut grower payments between years to hit earnings targets

Diamond Foods · Snack foods (listed)

Revenue inflationGovernance failure

The case in brief

Visible before detection

    Checks that could have surfaced it, on hindsight

    1

    Third-party confirmation

    Would have confirmed with growers what the payments were for.

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

    2

    Books edit log

    Would have shown payments recorded in a later period.

    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.

    3

    Bank credits vs books

    Would have matched cash paid to growers against the crop cost booked.

    Can mislead when: AA only sees the accounts the company links, so an undisclosed account stays invisible. Cash-heavy businesses and timing differences create false flags.

    Where Kubr services would have helped

    Financial diligence

    Offered in India
    • C1 Would have matched cash paid to growers against the crop cost booked.
    • C12 Would have shown payments recorded in a later period.

    Valuation context

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

    Model check

    Offered in India
    • C1 Would have matched cash paid to growers against the crop cost booked.

    Portfolio monitor

    Offered in India
    • C1 Would have matched cash paid to growers against the crop cost booked.

    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.