Wirecard, the missing €1.9 billion, and the reconciliation that finally ran
You're the treasury engineer running month-end. The reconciliation against the Philippine escrow accounts has never been done end-to-end. Today it has to.
By Solomon Ajayi · Free to read, no signup
It's June 2020. You're a senior treasury engineer at Wirecard AG in Munich. Wirecard is a DAX 30 component, market cap once €24 billion, marketed as Germany's only true Silicon-Valley-style fintech. The balance sheet shows €1.9 billion of cash held in escrow in two Philippine banks, BDO Unibank and Bank of the Philippine Islands, supporting Wirecard's Third-Party Acquiring business. For three years your reconciliation script has accepted PDF statements provided by an external 'trustee' rather than direct API or letter responses from the banks themselves. This week, after the Financial Times' Dan McCrum spent five years documenting irregularities and EY refused to accept trustee-routed evidence any longer, the COO has finally green-lit a direct reconciliation against the banks' systems. You are the engineer who has to run it. The result will end Wirecard within 72 hours.
The decisions, beat by beat
Monday 15 June 2020, 09:00 CET
Month-end reconciliation kicks off. Your queue has the usual list, plus the new flag from the CFO: the Philippine escrow accounts have to be reconciled against the banks directly, not against the trustee-provided PDFs you've used for three years. The trustee's standing email is still in your inbox asking you to 'continue current procedures.' You have read access to the SWIFT confirmation queue and Wirecard's API integrations with BDO Unibank and BPI. Neither integration has ever returned a balance for the escrow accounts, the trustee has always handled that.
What's the first move?
✓ Submit a SWIFT MT940 statement request directly to BDO and BPI for the escrow account numbers on file
Right. MT940 is the standard inter-bank statement message; both banks support it and the response goes directly to your treasury system, not through any intermediary. This is the test the trustee pipeline has prevented for three years.
Ask the trustee for an updated PDF and reconcile against that
That's the exact substitution pipeline the new procedure is meant to break. Trustee PDFs are not direct bank evidence; the CFO has explicitly told you to skip that step.
Email Markus Braun for guidance before initiating the request
Treasury reconciliation is your standard operating procedure, you don't need CEO sign-off to run a standard MT940 request against a corporate bank. Asking for it inverts the chain of evidence and signals you don't trust the process you're being asked to run.
Skip the Philippine accounts this month and re-run next month
The CFO flagged this specifically; skipping it sends EY a non-response that they'll interpret as bad-faith. The whole point of this month's procedure is to close the three-year gap. Deferral is the failure mode.
MT940 statement requests submitted directly to BDO Unibank and BPI
Two SWIFT messages out, one to BDO Unibank Manila, one to BPI Manila. Standard request format, standard escrow account numbers as listed on Wirecard's balance sheet. Expected response time: 1-3 business hours. You log the message reference IDs to the audit trail and start the timer.
Monday 15 June 2020, 14:20 CET
Both responses are back. BDO Unibank: 'No record of the referenced account numbers.' BPI: 'The accounts described do not exist in our records.' Both responses arrive via the standard SWIFT pipeline, signed and authenticated by each bank's treasury operations. The trustee is now calling your desk phone. He says there's been 'a routing issue at the bank end' and you should disregard the SWIFT responses; he'll send fresh PDFs by close of business.
How do you handle the trustee's call?
✓ End the call politely; treat the SWIFT responses as authoritative; escalate to the CFO and internal audit
Right. SWIFT-authenticated responses from a bank's treasury operations are the highest evidence tier in your reconciliation framework. The trustee asking you to disregard them is asking you to commit fraud. End the call, lock the evidence, escalate.
Accept the trustee's offer of fresh PDFs as the resolution
That's the substitution pipeline that hid this fraud for three years. Accepting trustee-provided PDFs over SWIFT-authenticated bank responses is exactly the procedure your CFO told you to break.
Take the trustee's PDFs AND the SWIFT responses, present both to the CFO
False equivalence. SWIFT messages from the bank's own treasury operations are not on the same evidence tier as a third party's PDFs. Presenting them as parallel options gives management an excuse to pick the one they prefer.
Run the SWIFT requests again to rule out a transmission error
Defensible due-diligence step but not the FIRST move. Both bank responses are signed and authenticated; a re-request gives the trustee 1-3 more hours to manufacture a cover story. Escalate first, re-confirm in parallel.
Trustee call ended; SWIFT evidence locked; escalation sent to CFO + internal audit
The phone call ends in under two minutes. You snapshot the SWIFT message logs, freeze the audit trail in the treasury system, and forward both responses with a short note to the CFO and the head of internal audit. From this point forward, the trustee pipeline is not a permitted evidence source for the Philippine accounts.
Tuesday 16 June 2020, 10:30 CET
Internal audit has spent the night re-running the SWIFT requests through alternative channels (Reuters Eikon's bank confirmation utility, direct telephone calls to BDO and BPI head offices via numbers from their annual reports). Every channel returns the same answer: the accounts do not exist. The €1.9 billion is not 'misplaced' or 'temporarily inaccessible', there is no asset. The reconciliation cannot pass. Internal audit has asked you to post the impairment entry that reflects what the reconciliation actually shows.
Post the journal entry surfacing the impairment.
✓ Cash: Philippine Escrow (claimed) DOWN €1.9B; Impairment Loss UP €1.9B
Correct. The asset cannot be verified; the impairment expense recognises that loss in the period the failed reconciliation surfaced. Asset DOWN €1.9B; expense UP €1.9B. Two-line balanced entry that puts the truth on the books.
Cash: Philippine Escrow (claimed) DOWN €1.9B; Cash (anywhere else) UP €1.9B
You'd be claiming the missing €1.9B moved to another asset account. It didn't. There is no €1.9B anywhere; the offset must be an impairment expense, not a reclassification.
Cash: Philippine Escrow (claimed) UP €1.9B (record the missing balance as a contingent receivable)
You can't book a contingent ASSET when the underlying does not exist. Contingent assets are reserved for outcomes that are virtually certain. The opposite is true here, every channel confirms the asset has no counterparty.
| Account | Debit | Credit |
|---|---|---|
| Impairment Loss: Unverifiable Reserves (5900) | €1,900,000,000.00 | |
| Cash: Philippine Escrow (claimed) (1100) | €1,900,000,000.00 |
Asset (claimed cash) DOWN €1.9B; Impairment Loss (expense) UP €1.9B. The balance sheet now reflects what the reconciliation actually shows. The CFO sign-off on this entry blocks any further claim of the €1.9B as a working asset and triggers the immediate disclosure obligation under German securities law.
Thursday 18 June 2020, 07:00 CET
The impairment entry is posted. EY has formally declined to sign the 2019 audit. Markus Braun has called an emergency board meeting. The disclosure team needs language for the ad-hoc announcement that goes to Bloomberg and the DAX wire at the open. The treasury team is being asked to validate the financial language. What goes out?
Approve the disclosure language.
✓ State plainly: €1.9 billion claimed as Philippine escrow cannot be verified; auditor has declined to sign
Right. The German Securities Trading Act requires ad-hoc disclosure of price-sensitive information without delay. €1.9B unverifiable + auditor refusing to sign is unambiguously material. Plain language is what the law and the market need, vagueness here triggers regulatory enforcement on top of everything else.
Say the €1.9 billion is 'temporarily unavailable' pending an investigation
The reconciliation has established that the accounts do not exist; 'temporarily unavailable' is materially misleading. Issuing language that contradicts your own treasury system's findings exposes the company to securities fraud charges on top of the audit failure.
Delay disclosure until the trustee's PDFs can be re-examined
Ad-hoc disclosure is a statutory obligation, not a discretionary one. Delaying past the next market open while the underlying facts are known triggers BaFin enforcement immediately and adds market-manipulation exposure.
Make no announcement; wait for press to ask first
The same statutory issue. German law requires you to disclose price-sensitive information you know, not to wait until someone else asks. Silence here is not 'no comment', it's a violation.
Ad-hoc announcement filed: €1.9B unverifiable; auditor has declined to sign
The wire goes out at 07:48 CET, before the DAX opens at 09:00. Wirecard stock opens down 60% and continues falling. Markus Braun resigns by mid-morning. BaFin lifts the short-selling ban it had imposed on Wirecard stock in 2019. The disclosure is procedurally correct, which matters less to today's market reaction but will matter to every regulator and prosecutor for the next decade.
Thursday 25 June 2020, 17:00 CET
Wirecard has filed for insolvency, the first DAX 30 company ever to do so. Braun has been arrested. Marsalek has vanished. BaFin is under intense scrutiny for ignoring the FT's seven years of reporting. The post-mortem regulator commission begins next week and will rewrite German audit law. From a treasury-engineering perspective, what's the structural recommendation?
Top structural recommendation?
✓ Direct bank evidence (SWIFT / API / signed bank letter) must be the only permitted source for any balance on the balance sheet; trustee or intermediary documents do not satisfy reconciliation
Right. The structural failure was tolerating trustee PDFs as if they were bank evidence. Every subsequent fraud built on that initial substitution. The fix is procedural and absolute: a balance counts only when the bank itself confirms it via a channel the bank controls. Anything else is hearsay.
Require monthly trustee certifications signed in front of a notary
Notarising the wrong evidence still leaves you with the wrong evidence. The trustee being credible is not the issue; the issue is that ANY intermediary in the confirmation pipeline destroys the assurance value. Notarisation doesn't repair that.
Move all Wirecard cash to a single global bank to simplify reconciliation
Concentration risk swap. The Wirecard fraud was about confirmation channel, not bank diversity. Centralising cash into one bank trades one structural vulnerability for another.
Add more compliance staff to review trustee PDFs more thoroughly
More humans reading the wrong evidence harder doesn't fix the channel. The pattern here was that the trustee's PDFs LOOKED clean for years, that's why nobody caught it. The fix is not deeper review of the wrong thing.
Structural recommendation: bank-controlled channels only, no intermediaries
The handoff to the insolvency administrator (Michael Jaffé) lands with the recommendation at the top: no balance counts unless it's confirmed via a channel the source bank itself controls. The German Audit Reform Act of 2021 codifies this principle six months later. The five years between the FT's first article and this reconciliation are the cost of having waited.
What actually happened
Wirecard publicly disclosed that the €1.9 billion was 'missing' on June 18 2020, at first claiming the funds had been lost, before conceding on June 22 that 'a prevailing likelihood' was that the funds never existed. EY refused to sign the 2019 audit. Markus Braun resigned and was arrested. Wirecard filed for insolvency on June 25, the first DAX 30 company ever to do so. Jan Marsalek, the COO who'd run the Third-Party Acquiring business, disappeared and is presumed in Russia. The structural lesson German regulators took from Wirecard was painful: the audit failure happened because direct bank confirmation had been quietly substituted with Wirecard-provided intermediary documentation for years. BaFin, Germany's financial regulator, lost its bank-supervisory role, and the German Audit Reform Act (FISG) of 2021 mandated stricter auditor rotation, separation of audit and consulting work, and direct evidence-gathering requirements. The deeper engineering point is the one your reconciliation just demonstrated: confirmations work only when they reach the source unchanged. Introducing any intermediary into the confirmation pipeline collapses the assurance value to zero. If Wirecard's treasury engineering had insisted on direct bank API access in 2015 instead of accepting trustee PDFs, the fraud surfaces five years earlier.
Play it from the engineer's seat
Reading the replay is one thing. Sit in the chair, make the calls live, and watch the consequences land in a real ledger. Free.