How to avoid common pitfalls in your ORSA process
As with so many regulatory mandates, the development of an ORSA Summary Report is dependent upon much more than just data. Regulators are looking beyond the final numbers to determine if organizations are meeting the mandate, and the process used to get that final report is under equal scrutiny.
Related articles
-
OpinionBeyond the Binder: Policy governance in practice
Most compliance professionals have faced it: a regulator or client requests a policy, and several slightly different “final” versions appear. The issue often stems from reactive, siloed work without a unified governance framework.
-
ArticleHow food and beverage companies adjust to the throes of tariff woes
On-again-off-again tariffs, a down economy, and a long list of global supply chain disruptions are challenging U.S. food and beverage companies to adjust their supply chain operations in a variety of ways.
-
OpinionRisk-Based AML only works if the C-suite agrees what ‘risk’ means
Banks emphasize risk-based compliance in their AML programs, citing it to regulators and embedding it in policy, yet many institutions still handle risk very differently in practice.