GF510 Unit 8 Citibank Payment Error Case Study Example

Three Approvals, One Wrong Box: A Unit 8 Operational Risk Case Study of Citibank's 2020 Revlon Payment

[Student Name]

Purdue University Global

GF510: Risk Analysis and Management

Unit 8 Operational Risk Case Study

[Instructor Name]

[Date]

The events, court decision, enforcement action and articles cited are real; figures are rounded, and the control analysis is the writer's own.

Background

Citibank served as administrative agent on a term loan of about $1.8 billion made to Revlon, the cosmetics company, in 2016. As agent, Citi collected Revlon's payments and passed them to the lenders, many of them investment funds. In August 2020 Revlon was refinancing part of the loan, and an interest payment was due to the lenders whose loans remained outstanding. An agent's job on such a loan is clerical rather than credit work: it moves other people's money on a schedule, which is why the bank's controls were built for routine payments rather than for a payment of unusual shape.

What Happened

To pay only interest while keeping the principal balance inside the bank, Citi's loan system required an operator to direct the principal portion to an internal account by setting several fields on the payment screen. The operator, working for a contractor that processed loan payments for Citi, set one of the required fields but not the others. The system therefore treated the principal as payable to the lenders.

The payment then went through what Citi called a six-eye review: the operator, a second reviewer at the contractor and a senior Citi employee all approved it. Each read the screen as showing an interest-only payment. The next morning, Citi discovered that it had paid out roughly the full outstanding principal of the loan, about $900 million, of its own money.

Citi asked the lenders to return the funds. Some did, returning roughly $400 million. A group of lenders holding about $500 million refused, arguing that Revlon owed them that principal anyway and that they were entitled to keep a payment they had no reason to think mistaken. In February 2021 a federal district court agreed with the lenders. In September 2022 the Court of Appeals for the Second Circuit reversed that ruling, holding that the lenders should have recognized the payment as a mistake and could not keep it (Citibank, N.A. v. Brigade Capital Management, LP, 2022). By then the money had been frozen for two years.

Separately, in October 2020 the bank's national regulator fined Citibank $400 million and ordered it to repair long-standing weaknesses in risk management, data governance and internal controls (Office of the Comptroller of the Currency [OCC], 2020). The order did not rest on the Revlon payment, but the payment was widely read as an example of the weaknesses it described.

The Failure Chain

Breaking the event into links shows where it could have been stopped.

Link 1: a screen that invited the error. The software required several fields to be set together to keep principal in-house, and nothing on the screen warned the user that setting only one would release the full balance. A design that relies on users remembering an unusual combination is a standing source of error.

Link 2: a review that checked the same view. The three approvals were not independent. All three reviewers looked at the same screen and accepted its display of the payment's purpose. None checked the amount about to leave the bank against the amount Revlon actually owed.

Link 3: no limit on the amount. No control compared the outgoing total against the expected interest payment or against a threshold for that loan. A payment more than a hundred times the expected size went out without a pause.

Link 4: a contract and a legal position, not a control. Recovery depended on persuading lenders to return the money and, when some refused, on litigation. Citi recovered in the end, but only after two years and a reversal on appeal.

Every approval in the six-eye process confirmed what the screen said rather than what the payment did, so three reviewers added the appearance of control without adding an independent check on the one number that mattered: the dollars leaving the bank.

Classifying the Event

The Basel framework sorts operational losses into seven event types. This loss falls under execution, delivery and process management, specifically transaction capture, execution and maintenance, the category for data entry errors and failed processing (Basel Committee on Banking Supervision, 2006). It was not fraud, not a system outage and not a product failure. That classification matters because the remedies for process errors are different from those for fraud: they lie in system design, independent verification and limits, not in surveillance of staff.

The Controls That Would Have Stopped Each Link

For Link 1, a preventive design control. A payment screen that required the user to confirm the outgoing principal amount in a separate step, or that blocked any principal payment not matched to a scheduled maturity or prepayment, would have stopped the error before approval.

For Link 2, an independent detective control. At least one reviewer should check the payment against a source outside the system, such as the borrower's payment notice, which showed only interest. Independence means checking a different piece of evidence, not looking at the same screen again.

For Link 3, a preventive limit. An automatic hold on any agency payment that exceeds the expected amount by a set margin would have stopped the transfer even after three approvals. Limits of this kind are cheap and act regardless of human judgment.

For Link 4, a response plan. Prewritten recall notices and an agreed legal route for agency payment errors would have shortened recovery, though the appeal decision now gives agents a stronger position than they had in 2020.

Why the Market Cared

Research on operational losses at banks and insurers finds that a firm's market value falls by more than the loss itself when an event is announced, which suggests investors read operational failures as signs of weak management (Cummins et al., 2006). The Revlon payment, coming alongside the OCC order, fed exactly that reading. The direct loss was eventually recovered; the reputational cost and the cost of the enforcement order were not.

Lessons for Any Firm That Moves Money

The lessons reach beyond banks. Any company that pays suppliers, employees or lenders by electronic transfer depends on screens, reviewers and limits. A treasury department can ask three questions of its own process: whether any screen allows a large payment through an unusual combination of settings, whether its approvals check independent evidence or the same display, and whether any automatic limit stops a payment far outside its expected size.

Conclusion

The Revlon payment was a small error with a large consequence because three controls that appeared to exist did not work independently. Better screen design, a check against outside evidence and an automatic amount limit would each have prevented it on its own.

References

Basel Committee on Banking Supervision. (2006). International convergence of capital measurement and capital standards: A revised framework (Comprehensive version). Bank for International Settlements.

Citibank, N.A. v. Brigade Capital Management, LP, 49 F.4th 42 (2d Cir. 2022).

Cummins, J. D., Lewis, C. M., & Wei, R. (2006). The market value impact of operational loss events for US banks and insurers. Journal of Banking & Finance, 30(10), 2605-2634. https://doi.org/10.1016/j.jbankfin.2005.09.015

Office of the Comptroller of the Currency. (2020). OCC assesses $400 million civil money penalty against Citibank [News release]. U.S. Department of the Treasury.