Outgrace, home
Governance & RiskCase lessons

What the Wirecard confirmations teach boards about auditor evidence

Two Singapore convictions show how false escrow letters reached the auditors. The questions boards should ask about who confirmed what, and how outside money is treated.

Two men were convicted in Singapore in September 2025 of falsifying accounts, and the case shows how a board can be handed false evidence that looks like the most reliable evidence an auditor can obtain. Thirteen confirmation letters, issued between March 2016 and April 2018, told Wirecard, its subsidiaries and its auditors that Citadelle Corporate Services Pte Ltd held more than €1.1bn of Wirecard funds in escrow accounts. According to the Singapore Police Force, the court found that Citadelle's director, R Shanmugaratnam, intended to deceive Wirecard, its subsidiaries and/or its auditors. He was sentenced to 10 years' imprisonment. His co-accused, James Henry O'Sullivan, was charged with abetting falsification in five of the letters and was sentenced to 6.5 years. Both men have said they will appeal, and the release reports no appeal outcome.

This article draws on two sources: the IFRS Foundation's page on IAS 24 and the Singapore Police Force's release of 8 January 2026. It does not draw on the German regulatory or parliamentary material on Wirecard, and it does not state any conclusion those bodies may have reached. Readers who need that material should read it directly before drawing conclusions about how Wirecard's own oversight worked.

  1. Mar 2016

    First confirmation letters

    The first of the thirteen letters is issued in this month. According to the police, the letters were addressed to the auditors themselves and relied on as audit evidence. The release does not describe who inside Wirecard saw them.

  2. Apr 2018

    Last letter issued

    The series ends. The police give March 2016 to April 2018 as the full span of the thirteen letters. Two years of letters is long enough for a pattern to form, and short enough that a single review would have caught it.

  3. 31 Jul 2023

    Joint trial begins

    The trial of Shanmugaratnam and O'Sullivan opens. It runs until 21 February 2025, and the police count 26 days of hearings within that period.

  4. 21 Feb 2025

    Trial period closes

    The hearings end. The court then reaches its verdict in September, which means the trial record was complete for more than seven months before the convictions were announced.

  5. 22 Sep 2025

    Both men convicted

    The court convicts both men. The police state that the court found Shanmugaratnam intended to deceive Wirecard, its subsidiaries and/or its auditors. The stated motive for the letters was to keep a business relationship going with O'Sullivan and with Wirecard executives Jan Marsalek and Oliver Bellenhaus.

  6. 6 Jan 2026

    Sentences passed

    Shanmugaratnam receives 10 years and O'Sullivan receives 6.5 years. Both men say they will appeal the convictions and sentences.

  7. 8 Jan 2026

    Police publish their account

    The Singapore Police Force issues its public release on the case, which is the source for every fact in this timeline. Any later appeal result will need its own check against the court record.

The decision that mattered

The decisive point is not the forgery itself but where the evidence came from. A confirmation letter is meant to be the piece of audit evidence the company cannot write for itself. In this case the police say the letters went to the auditors and were relied on as audit evidence. A board that accepts a summary of confirmations without asking who answered, by what route, and whether the answer can be checked against an independent record has accepted the same weakness the audit relied on. The question is not whether a letter looks professional. It is whether the person who signed it could have been anyone the company controlled.

The questions a board should have put, and can still put, are plain. Which balances were confirmed by a party outside the group? Who signed each reply, and how was that signature checked? Did any confirmation pass through the company's own staff or a service provider before it reached the auditor? Where an outside firm holds money, is that firm's own statement the only confirmation on file? In our experience the audit committee rarely asks the last question, because the answer seems obvious. In this case it was not obvious enough to stop the letters.

The police describe Citadelle as an accounting and auditing firm whose corporate secretarial services were used by Singapore-registered companies, including companies connected to O'Sullivan. A firm that does company secretarial work for several clients, and also holds money in escrow, sits where a board should ask whether its records are independent of the people it serves. Whether such a firm is a related party of the company under the reporting framework is a question for the auditors. This article cannot answer it from the sources it has, and it does not suggest an answer.

IAS 24 asks a different question from the one a confirmation letter answers. It asks whether a relationship could affect the financial statements. The standard treats a transfer of resources, services or obligations between a reporting entity and a related party as a related-party transaction, whether or not a price is charged. Where such transactions occurred in the period, the entity must disclose the nature of the relationship, the transactions and the outstanding balances, including commitments. The test the standard sets is that users should be able to understand the potential effect of the relationship on the financial statements. A board does not need to be a standard-setter to use that test. It needs a current list of its counterparties, a note of which of them hold company money, and a record of what the auditor was told about each.

The IFRS page sets the test. It does not say whether any particular firm in this case met it, and the police release describes a criminal case, not an audit outcome. The release does not say how the auditors handled the letters once they arrived, and this article does not say either. A reader who sees the escrow figure should resist the temptation to treat it as a verdict on the audit. What it does show is the size of a balance that can rest on a single document. That is the point at which an audit committee should slow down.

A related party transaction is a transfer of resources, services or obligations between a reporting entity and a related party, regardless of whether a price is charged.

IFRS Foundation, IAS 24 Related Party Disclosures, ifrs.org

Lessons

  • Ask who answered. The police say the escrow letters were addressed to the auditors and relied on as audit evidence. A board should ask the auditor to show how each external confirmation reached the audit team, not only that it arrived and was filed.
  • Treat outside money as a related-party question until it is answered. IAS 24 covers transfers of resources or services whether or not a price is charged. Ask whether any firm holding company funds has a relationship with the company or its people that would need to be disclosed.
  • Read a request to keep a relationship going as a reason for more evidence. The police state that the letters were issued to keep a business relationship going with O'Sullivan and with Marsalek and Bellenhaus. A counterparty who needs a relationship to continue is a reason to check the paper, not to relax about it.
  • Check the route every year, not only the total. The letters ran for two years. A committee that receives a schedule of confirmations, with the sending and receiving route recorded for each, can spot a change in pattern that a summary figure would hide.

A smaller company should borrow the question, not the scale. A company with one finance lead and a single bank does not hold €1.1bn in escrow through a service provider, and most boards will never face that exact arrangement. The lesson about route of evidence does scale down. A smaller board can ask its auditor for copies of every third-party confirmation addressed to the auditor, can ask that bank balances be confirmed through the bank's own channel rather than through a firm the company uses for other work, and can ask the auditor to say which related-party transactions it tested. What does not transfer is the Singapore case's specific arrangement, which a board of a smaller company is unlikely to recognise from the outside. Whether your auditor may share its correspondence, and what your committee may demand of it, are questions for the auditor and, where the answer is unclear, for a lawyer.

Newsletter

The Briefing

One email a week: the leaders we profiled, the ideas worth stealing, and nothing else.

Weekly, free, one click to leave. Read our privacy policy.