<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:media="http://search.yahoo.com/mrss/"><channel><title><![CDATA[Suade Labs]]></title><description><![CDATA[Technology to prevent the next financial crisis]]></description><link>https://suade.org/</link><image><url>https://suade.org/favicon.png</url><title>Suade Labs</title><link>https://suade.org/</link></image><generator>Ghost 5.79</generator><lastBuildDate>Thu, 22 Oct 2026 11:52:39 GMT</lastBuildDate><atom:link href="https://suade.org/rss/" rel="self" type="application/rss+xml"/><ttl>60</ttl><item><title><![CDATA[Suade’s London RegTech Forum 2026 highlights responsible AI and the future of regulatory reporting]]></title><description><![CDATA[<p><strong>LONDON, 6 October 2026 &#x2013; </strong>Suade held its fifth annual RegTech Forum at Guildhall in the City of London. The Forum featured speakers from the Bank of England, FCA, ECB and EBA, alongside senior representatives from financial institutions including JPMorganChase, Goldman Sachs and Standard Chartered, as well as technology leaders</p>]]></description><link>https://suade.org/regtech-forum-2026-2/</link><guid isPermaLink="false">6accb9d884bb68095b84ef0b</guid><category><![CDATA[News]]></category><dc:creator><![CDATA[Bernice Nkoy]]></dc:creator><pubDate>Thu, 22 Oct 2026 11:48:19 GMT</pubDate><media:content url="https://suade.org/content/images/2026/10/ShapeVideo_RS1_2766_VS1-copy.jpg" medium="image"/><content:encoded><![CDATA[<img src="https://suade.org/content/images/2026/10/ShapeVideo_RS1_2766_VS1-copy.jpg" alt="Suade&#x2019;s London RegTech Forum 2026 highlights responsible AI and the future of regulatory reporting"><p><strong>LONDON, 6 October 2026 &#x2013; </strong>Suade held its fifth annual RegTech Forum at Guildhall in the City of London. The Forum featured speakers from the Bank of England, FCA, ECB and EBA, alongside senior representatives from financial institutions including JPMorganChase, Goldman Sachs and Standard Chartered, as well as technology leaders and regulatory experts.&#xA0;</p><p>Diana Paredes, co-founder and CEO of Suade, said: <em>&#x201C;The RegTech Forum 2026 once again demonstrated the importance of collaboration in shaping the future of financial regulation.&#x201D;</em>&#xA0;</p><p>The programme centred on one question: how can firms adopt AI in regulatory reporting while keeping people in the loop and accountable for the results? Over the course of the event, speakers set out what needs to be in place first, from shared data standards and well-engineered systems to clear human oversight and ownership of AI-assisted outputs.&#xA0;</p><p>The discussions highlighted a shared challenge for the industry: how to embrace innovation without compromising the accuracy, transparency and accountability that effective regulation requires.&#xA0;<br>&#xA0;</p><p><strong>Building the foundations for responsible AI</strong>&#xA0;</p><p>Opening the Forum, <strong>Sushil Saluja, Alderman at the City of London Corporation and former CIO of the Bank of England</strong>, highlighted the importance of collaboration between regulators and industry in establishing common standards and improving the quality of regulatory data.&#xA0;</p><p>Drawing parallels between the historic hallmarking system and the need for trusted data standards today, Saluja emphasised that technological progress must be underpinned by strong foundations.&#xA0;</p><p>&#x201C;<em>AI is pivotal, but we also know that AI on its own is not enough. We have to use the right tools for the job,&#x201D;</em> said Saluja.&#xA0;</p><p>He added: <em>&#x201C;Innovation will only be as strong as the data and the controls underneath it.&#x201D;</em>&#xA0;</p><p>His remarks reinforced the importance of addressing data quality and interoperability as financial institutions explore new applications for AI, while ensuring regulatory reporting remains reliable and auditable. They also underscored that better tools and data do not remove the need for people to exercise judgement and remain accountable for the results. For further context, see the <a href="https://www.bankofengland.co.uk/prudential-regulation/publication/2023/october/artificial-intelligence-and-machine-learning?ref=suade.org">Bank of England and FCA&#x2019;s review of AI and machine learning in UK financial services</a>.&#xA0;<br>&#xA0;</p><p><strong>Moving beyond the AI hype</strong>&#xA0;</p><p>In his presentation, <em>How I Learned to Stop Worrying and Love AI</em>, <strong>Murat Abur, Co-founder and CIO at Suade</strong>, examined the practical implications of AI for regulatory reporting.&#xA0;</p><p>Drawing on Suade&#x2019;s experience developing regulatory reporting technology since 2014, Abur challenged the notion that AI will simply replace existing software or human expertise. He argued that AI&#x2019;s potential lies instead in building on reliable, well-engineered systems that can deliver precise results in highly regulated environments. In regulatory reporting, where errors can compound across complex processes, AI must be supported by dependable tools, structured data and systems designed to make information accessible and actionable.&#xA0;</p><p>Murat&#xA0;also highlighted the importance of keeping people at the centre of technological progress. Rather than replacing human expertise, AI should act as a powerful tool to help professionals work more efficiently and productively. As he argued during his presentation, AI will need us more than we need it.&#xA0;</p><p>For Suade, this means developing technology that enables firms to take advantage of emerging AI capabilities while retaining flexibility over the models they use and where they deploy them. Whatever tools or models a firm chooses, responsibility for the use of AI and the resulting regulatory outputs must remain clear and firmly with the firm.&#xA0;<br></p><p><strong>Why standardisation matters more in an AI-driven world</strong>&#xA0;</p><p>Closing the Forum, <strong>Lyndon Nelson, Senior Technical Expert and Visiting Scholar at the IMF, former Deputy CEO of the PRA and advisor to Suade</strong>, offered a regulatory perspective on AI adoption, human oversight and accountability.&#xA0;</p><p>Nelson used the analogy of containerisation to illustrate why standardisation is essential to technological progress. Just as standardised shipping containers transformed global trade, common data structures and interoperable systems can make complex regulatory reporting environments more accessible to AI. The ECB&#x2019;s <a href="https://bird.ecb.europa.eu/?ref=suade.org">Banks&#x2019; Integrated Reporting Dictionary (BIRD)</a> provides an example of collaborative work on common data models for regulatory reporting.&#xA0;</p><p><em>&#x201C;Open data models, common definitions, and open interfaces matter more in an AI world, not less,&#x201D;</em> said Nelson.&#xA0;</p><p>He also highlighted the risks of relying on AI without meaningful human oversight, stressing that people must retain the expertise and authority to challenge automated outputs. In regulatory reporting, accountability cannot be delegated to technology. The Bank of England has also explored these challenges in its discussion of <a href="https://www.bis.org/speeches/20241104-engaging-machine-ai-and-financial-stability?ref=suade.org">AI and financial stability</a>.&#xA0;</p><p>Nelson argued that across the AI value chain - model provider, software vendor, integrator and bank - accountability can slip through the gaps. Speaking in a personal capacity and as an advisor to Suade, he said the bring-your-own-AI approach was, for now, the right one because it leaves no doubt that the bank owns the AI and so owns the whole.&#xA0;</p><p><em>&#x201C;Everyone owns a part. Someone must own the whole,&#x201D;</em> he said.&#xA0;<br>&#xA0;</p><p><strong>A connected, trustworthy reporting ecosystem</strong>&#xA0;</p><p>From open data standards to AI-enabled reporting, the path forward depends on collaboration between regulators, financial institutions and technology providers. By improving the foundations of regulatory data and building systems designed for interoperability, the industry can reduce operational complexity and unlock new opportunities for innovation.&#xA0;</p><p>The Forum concluded with a clear message: in an AI-driven world, the future of RegTech is not simply about automating existing processes. It is about building a connected, trustworthy reporting ecosystem in which people stay in the loop, and ownership and accountability are never in doubt.&#xA0;</p><p>Reflecting on the event, Paredes added: <em>&#x201C;By bringing together leading voices from across financial services, regulation and technology, we explored how stronger data foundations, responsible AI and innovation can help address the industry&#x2019;s evolving challenges and build a more effective future for regulatory reporting.&#x201D;</em>&#xA0;</p><hr><p><strong>About Suade</strong>&#xA0;</p><p>Suade has been developing regulatory reporting technology since 2014. Suade remains committed to advancing the transformation of regulatory reporting, helping financial institutions modernise through technology designed to support accuracy, efficiency and adaptability in a changing regulatory landscape.&#xA0;</p><p><br><strong>Media contact:</strong>&#xA0;<br><strong>marketing@suade.org</strong>&#xA0;<br><strong>020 3923 7049</strong>&#xA0;</p>]]></content:encoded></item><item><title><![CDATA[RegTech Forum 2026 - Panel: Navigating a more fragmented global banking landscape]]></title><description><![CDATA[<p>As geopolitical pressures intensify and regulatory requirements diverge across jurisdictions, global banks face growing challenges in managing cross-border compliance. The <em>Navigating a More Fragmented Global Banking Landscape</em> panel explored how financial institutions can respond to this complexity by building more flexible regulatory infrastructure, strengthening data foundations and balancing global consistency</p>]]></description><link>https://suade.org/navigating-a-more-fragmented-global-banking-landscape/</link><guid isPermaLink="false">6acf3c3384bb68095b84efc1</guid><category><![CDATA[Insights]]></category><dc:creator><![CDATA[Bernice Nkoy]]></dc:creator><pubDate>Wed, 21 Oct 2026 10:18:32 GMT</pubDate><media:content url="https://suade.org/content/images/2026/10/Untitled-design--13-.png" medium="image"/><content:encoded><![CDATA[<img src="https://suade.org/content/images/2026/10/Untitled-design--13-.png" alt="RegTech Forum 2026 - Panel: Navigating a more fragmented global banking landscape"><p>As geopolitical pressures intensify and regulatory requirements diverge across jurisdictions, global banks face growing challenges in managing cross-border compliance. The <em>Navigating a More Fragmented Global Banking Landscape</em> panel explored how financial institutions can respond to this complexity by building more flexible regulatory infrastructure, strengthening data foundations and balancing global consistency with local requirements.</p><p><strong>Regulatory fragmentation is becoming a strategic challenge.</strong> Differences in rules, supervisory expectations and national priorities are making cross-border compliance increasingly complex and costly. While perfectly harmonised global standards may be unrealistic, firms can reduce unnecessary divergence by reusing established definitions, standards and reporting approaches wherever possible.</p><p><strong>Global consistency should be the starting point, with flexibility for local differences.</strong> Shared data models, platforms and processes can reduce duplication and improve efficiency across international operations. However, these systems must also accommodate genuine jurisdiction-specific requirements. A flexible approach allows firms to maintain consistency without overlooking local regulatory obligations.</p><p><strong>Effective regulatory reporting starts with strong data architecture.</strong> Data must be captured accurately and at sufficient granularity from the outset. Attempting to resolve missing information or inconsistent classifications at the reporting stage can be expensive and difficult. Building robust data foundations early helps firms meet reporting requirements more efficiently and adapt to future changes.</p><p><strong>Data should be treated as a strategic business asset.</strong> High-quality, well-governed and accessible data supports far more than regulatory compliance. It can strengthen risk management, improve capital planning and inform broader business decisions. Designing data infrastructure around the needs of risk, finance and the wider business can deliver more sustainable outcomes than building separate systems for individual reporting templates.</p><p><strong>Proportionality must reflect the realities of different institutions.</strong> Global banks and smaller international firms operate with different levels of complexity, resources and technological capability. Regulatory requirements and implementation approaches should account for these differences while maintaining appropriate standards of oversight and risk management.</p><p><strong>Technology can accelerate transformation, but strong foundations remain essential.</strong> Automation, cloud infrastructure and AI offer opportunities to improve efficiency and shorten transformation timelines. However, technology cannot compensate for weak data quality, fragmented architecture or unclear governance. Firms must first understand the problem they are trying to solve and select tools that address it effectively. Not every process requires AI, and where AI is appropriate, clear accountability and suitable safeguards remain critical.</p><p><strong>Data sharing requires careful navigation of geopolitical and legal constraints.</strong> As institutions seek to make information more accessible across their operations, differences in data protection laws, national security priorities and cross-border restrictions can create additional challenges. Firms must balance the benefits of data sharing with their obligations around privacy, security and local regulation.</p><p><strong>Collaboration between regulators and industry is vital.</strong> Sustained dialogue and early engagement can help identify implementation challenges, improve understanding of firms&#x2019; operational realities and reduce unnecessary complexity. Closer collaboration can also support regulatory frameworks that keep pace with technological innovation while remaining practical to implement.</p><p>Ultimately, <strong>navigating regulatory fragmentation requires long-term investment, adaptable infrastructure and a culture that recognises the value of data.</strong> Modernising regulatory reporting is not simply a technology project; it requires careful planning, cross-functional collaboration, the right skills and sustained commitment. By combining consistent global foundations with the flexibility to meet local requirements, financial institutions can manage regulatory complexity more effectively and build capabilities that support both compliance and wider business objectives.<br><br>Panellists:</p><ul><li>David Covey, Director, Suade (Moderator)</li><li>Lauren Dixon, Chief Data Officer, Financial Conduct Authority</li><li>Giles French, Chief Executive, Association of Foreign Banks</li><li>Tom Morrisey, Managing Director, Goldman Sachs</li><li>Helen Bex-Vigoureux, Global Head Regulatory Change, Standard Chartered</li></ul><p><em>This summary captures key themes from the discussion. Individual contributions have not been attributed to participants, in accordance with the Chatham House Rule.</em></p>]]></content:encoded></item><item><title><![CDATA[RegTech Forum 2026 - Panel: Staying future-proof - Basel 3.1, FRTB, IReF and future regulatory change]]></title><description><![CDATA[<p>As regulatory requirements continue to evolve, financial institutions must prepare for more than the next implementation deadline. Basel 3.1, the Fundamental Review of the Trading Book (FRTB) and the Integrated Reporting Framework (IReF) reflect the ongoing need for firms to adapt their data, systems and reporting processes. The <em>Staying</em></p>]]></description><link>https://suade.org/staying-future-proof-basel-3-1-frtb-iref-and-future-regulatory-change/</link><guid isPermaLink="false">6acf3e7884bb68095b84efc8</guid><category><![CDATA[Insights]]></category><dc:creator><![CDATA[Bernice Nkoy]]></dc:creator><pubDate>Wed, 21 Oct 2026 10:18:09 GMT</pubDate><media:content url="https://suade.org/content/images/2026/10/ShapeVideo_RS1_3297_VS4.jpg" medium="image"/><content:encoded><![CDATA[<img src="https://suade.org/content/images/2026/10/ShapeVideo_RS1_3297_VS4.jpg" alt="RegTech Forum 2026 - Panel: Staying future-proof - Basel 3.1, FRTB, IReF and future regulatory change"><p>As regulatory requirements continue to evolve, financial institutions must prepare for more than the next implementation deadline. Basel 3.1, the Fundamental Review of the Trading Book (FRTB) and the Integrated Reporting Framework (IReF) reflect the ongoing need for firms to adapt their data, systems and reporting processes. The <em>Staying Future-Proof &#x2013; Basel 3.1, FRTB, IReF and Future Regulatory Change</em> panel explored how organisations can manage these demands while building capabilities that make future regulatory change easier to implement.</p><p><strong>Regulatory change should be a long-term strategic priority.</strong> Rather than treating each new requirement as an isolated project, firms have an opportunity to strengthen their data foundations, improve processes and develop reusable capabilities. Each implementation should leave the organisation better prepared for the next change, rather than adding another layer of complexity.</p><p><strong>Granular, high-quality data is essential for future readiness.</strong> As reporting requirements become more detailed, firms need reliable, well-classified data that can support new calculations and disclosures without repeatedly rebuilding their systems. Standardised data models, reusable capabilities and a clear separation between core data and reporting-specific calculations can make implementation more efficient and adaptable.</p><p><strong>Data governance must be an ongoing discipline.</strong> Maintaining data quality, lineage, controls and clear ownership requires continuous attention. Effective governance cannot sit solely with technology or data teams; it depends on shared accountability across business, data and technology functions, supported by an organisation-wide culture that recognises the importance of reliable data.</p><p><strong>Breaking down data silos creates opportunities for greater consistency and reuse.</strong> Combining accounting, statistical and other datasets where appropriate can help firms reduce duplication and respond more effectively to different regulatory requirements. Initiatives such as IReF and the development of common data dictionaries offer opportunities to support greater harmonisation, although differences in national requirements and regulatory objectives must still be considered.</p><p><strong>Continuous improvement and automation can make reporting more resilient.</strong> Automated testing, frequent releases and more regular reporting runs can help firms identify issues earlier, reduce month-end surprises and improve the reliability of regulatory processes. Even when immediate deadlines require a focused delivery, organisations should look for opportunities to strengthen their wider data environment and create capabilities that can be reused.</p><p><strong>Simplification and collaboration remain important to effective regulatory change.</strong> Reducing duplicated returns, unnecessary detail and unclear instructions can deliver practical benefits in the near term, while longer-term investment supports more integrated, data-led reporting. Early engagement with regulators, practical industry feedback and shared technical work can help ensure requirements are clearly defined, implementable and aligned with genuine regulatory needs.</p><p><strong>AI can accelerate implementation, but human accountability remains essential.</strong> AI offers opportunities to support regulatory interpretation, code development, data lineage analysis and anomaly detection. However, firms must retain responsibility for interpreting requirements, validating outputs and maintaining effective controls. As regulatory processes become more automated, teams will also need broader skills spanning AI, data, regulatory expertise and commercial understanding.</p><p>Ultimately, <strong>future-proofing means building the foundations to adapt continuously, rather than simply meeting the next deadline.</strong> By investing in reusable data capabilities, embedding effective governance and adopting a culture of continuous improvement, financial institutions can make regulatory change more manageable and sustainable. The goal is to create flexible, reliable reporting infrastructure that meets today&apos;s obligations while preparing the organisation for requirements that have yet to emerge.</p><p>Panellists:</p><ul><li>Kira Snow, Regulatory Change, Suade (Moderator)</li><li>Dan Waites, Head of Finance Transformation, Starling</li><li>Helen Terry, Chief Data and Analytics Officer, Bank of Ireland</li><li>Tanja Loman, Team Lead, European Central Bank</li></ul><p><em>This summary captures key themes from the discussion. Individual contributions have not been attributed to participants, in accordance with the Chatham House Rule. </em></p>]]></content:encoded></item><item><title><![CDATA[EU & US Reg Roundup 20/10/26]]></title><description><![CDATA[<p><strong>Europe</strong></p><p><strong>European Banking Authority</strong></p><p><strong>Final technical package for reporting and Pillar 3 framework 4.4</strong></p><p>12 October 2026</p><p>The EBA released Phase 1 of reporting framework 4.4, including updated data models, validation rules and XBRL taxonomies. The package covers IFRS 18-aligned FINREP reporting, Pillar 3 disclosures on ESG, equity</p>]]></description><link>https://suade.org/uk-eu-reg-roundup-28-09-26-2/</link><guid isPermaLink="false">6ad8714b84bb68095b84f156</guid><category><![CDATA[Regulatory Updates]]></category><category><![CDATA[🇪🇺]]></category><category><![CDATA[🇺🇸]]></category><dc:creator><![CDATA[Bernice Nkoy]]></dc:creator><pubDate>Wed, 21 Oct 2026 08:03:03 GMT</pubDate><content:encoded><![CDATA[<p><strong>Europe</strong></p><p><strong>European Banking Authority</strong></p><p><strong>Final technical package for reporting and Pillar 3 framework 4.4</strong></p><p>12 October 2026</p><p>The EBA released Phase 1 of reporting framework 4.4, including updated data models, validation rules and XBRL taxonomies. The package covers IFRS 18-aligned FINREP reporting, Pillar 3 disclosures on ESG, equity and shadow-banking exposures, and amendments relating to resolution planning, MREL, third-country branch liquidity reporting and AMLA data collections. A second phase addressing the supervisory reporting simplification package is expected in early 2027.&#xA0;</p><p><a href="https://www.eba.europa.eu/publications-and-media/press-releases/eba-releases-final-technical-package-release-44-its-reporting-and-pillar-3-disclosure-framework?utm_source=openai">Original announcement</a></p><p><strong>Final draft amendments to prudential standards for central securities depositories</strong></p><p>12 October 2026</p><p>The EBA published its final report proposing amendments to prudential technical standards for central securities depositories and designated credit institutions providing banking-type ancillary services. The changes respond to the CSDR Refit, including arrangements allowing banking CSDs to provide these services to other CSDs. The standards have been submitted to the European Commission and are <strong>not yet applicable</strong>, making this a forward-looking implementation item rather than an immediately effective requirement.&#xA0;</p><p><a href="https://www.eba.europa.eu/activities/single-rulebook/regulatory-activities/market-infrastructures/regulatory-technical-standards-prudential-requirements-central-securities-depositories-csds?version=2025&amp;utm_source=openai">Original EBA publication page</a></p><p><strong>CRR3/CRD6 dashboard highlights the increasing impact of the output floor</strong></p><p>9 October 2026</p><p>The EBA&#x2019;s updated dashboard projects a fully loaded average CET1 ratio of <strong>15.1%</strong> across 129 EU/EEA banks. The estimated increase in Tier 1 minimum required capital rises to 6.0%, principally reflecting a larger output-floor impact. Under static balance-sheet assumptions, no capital shortfalls are projected before 2030, but shortfalls reach &#x20AC;18.5 billion under the fully loaded framework in 2033. The findings are relevant to medium-term capital planning and output-floor assessments.&#xA0;</p><p><a href="https://www.eba.europa.eu/publications-and-media/press-releases/eba-crr3crd6-dashboard-shows-banks-maintain-capital-levels-well-above-minimum-requirements-under?utm_source=openai">Original announcement</a></p><p><strong>Consultation on joint decisions for institution-specific capital and liquidity requirements</strong></p><p>25 September 2026</p><p>The EBA proposed revised implementing technical standards to simplify how supervisory colleges reach joint prudential decisions. Changes include an integrated risk-assessment report, closer alignment with the revised SREP framework, clearer treatment of qualitative measures, and inclusion of Pillar 2 Guidance and leverage-ratio-related Pillar 2 requirements and guidance. <strong>Comments close on 4 January 2027.</strong></p><p><a href="https://www.eba.europa.eu/publications-and-media/press-releases/eba-consults-revised-technical-standards-joint-decisions-institution-specific-capital-and-liquidity?trk=article-ssr-frontend-pulse_little-text-block&amp;utm_source=openai">Original announcement</a></p><p><strong>Final Guidelines on third-party risk management</strong></p><p>18 September 2026</p><p>The EBA published final Guidelines focusing on third-party arrangements supporting critical or important functions. They address the full arrangement lifecycle, including due diligence, contracting, subcontracting, monitoring and exit strategies, while promoting consistency with DORA and international standards. A two-year transitional period is intended to support proportionate implementation. The Guidelines are particularly relevant to outsourcing governance and operational-resilience programmes.&#xA0;</p><p><a href="https://eba.europa.eu/publications-and-media/press-releases/eba-publishes-its-final-guidelines-management-third-party-risk-delivering-more-proportionate-and?trk=article-ssr-frontend-pulse_little-text-block&amp;utm_source=openai">Original announcement</a></p><p><strong>European Securities and Markets Authority</strong></p><p><strong>T+1 settlement framework completed ahead of implementation</strong></p><p>16 October 2026</p><p>ESMA announced that the regulatory framework supporting the EU&#x2019;s move to T+1 settlement is complete following publication of technical standards and revised Guidelines on standardised procedures and messaging protocols. The EU transition is scheduled for <strong>11 October 2027</strong>, with an earlier <strong>7 December 2026</strong> deadline for investment firms and clients to meet new allocation and confirmation requirements. This is an important operational-readiness item for securities businesses.&#xA0;</p><p><a href="https://www.esma.europa.eu/press-news/esma-news/one-year-go-t1-settlement-regulatory-framework-complete-now-lets-make-it?ref=suade.org">Original announcement</a></p><p><strong>ESMA sets out its 2027 work programme and simplification priorities</strong></p><p>28 September 2026</p><p>ESMA&#x2019;s 2027 programme includes reviewing the impact of EMIR 3 on clearing-market resilience, supporting T+1 implementation and progressing the European Single Access Point. It also advances simplification initiatives covering transaction reporting, fund reporting and risk-based supervision. The programme signals continued attention to clearing dependencies, reporting efficiency, cybersecurity and technological innovation.</p><p><a href="https://www.esma.europa.eu/press-news/esma-news/esma-sets-2027-priorities-stronger-simpler-and-more-integrated-eu-capital?ref=suade.org">Original announcement</a></p><p><strong>BaFin</strong></p><p><strong>BaFin simplifies communication of its adoption of ESA and AMLA Guidelines</strong></p><p>1 October 2026 &#x2014; German publication; English listing dated 5 October 2026</p><p>BaFin announced that a consolidated overview will show which ESA and AMLA Guidelines it adopts into its administrative practice, replacing the publication of individual circulars for this purpose. This changes how firms monitor the domestic application of European Guidelines; it should not be interpreted as withdrawing the underlying supervisory expectations. The German date differs from the English listing supplied in your source material.&#xA0;</p><p><a href="https://www.bafin.de/SharedDocs/Veroeffentlichungen/DE/Meldung/2026/meldung_2026_10_01_leitlinien_esas_amla_bafin_reduziert_rundschreiben.html?ref=suade.org">Original announcement &#x2014; German</a></p><p><strong>North America</strong></p><p><strong>Federal Reserve Board</strong></p><p><strong>Bowman outlines supervisory modernisation following the Silicon Valley Bank review</strong></p><p>14 October 2026</p><p>Vice Chair for Supervision Michelle Bowman described proposed improvements to supervisory accountability, decision-making authority and escalation channels following an independent review of Silicon Valley Bank&#x2019;s failure. She emphasised timely intervention on material financial risks, particularly interest-rate and liquidity exposures, and proportionate supervision. The speech provides supervisory direction; it does not itself establish new capital or liquidity requirements.&#xA0;</p><p><a href="https://www.federalreserve.gov/newsevents/speech/bowman20261014a.htm">Original speech</a></p><p><strong>Bowman discusses modernising regulation and supervision</strong></p><p>6 October 2026</p><p>Bowman outlined the Federal Reserve&#x2019;s continuing modernisation agenda, including updating asset thresholds, making supervisory ratings more reflective of financial condition and risk, and streamlining regulatory reporting. She also discussed coordination with other banking agencies and a greater focus on matters capable of causing material financial impairment. The speech is relevant to supervisory planning, but references to earlier reforms should not be treated as new rules issued on this date.&#xA0;</p><p><a href="https://www.federalreserve.gov/newsevents/speech/bowman20261006a.htm">Original speech</a></p><p><strong>U.S. Securities and Exchange Commission</strong></p><p><strong>Proposed expansion of cross-trading by registered funds</strong></p><p>9 October 2026</p><p>The SEC proposed amendments expanding the securities eligible for cross-trading between registered funds and affiliates, including restoring the ability to cross-trade most fixed-income securities. The proposal also modernises pricing and oversight conditions, seeking to reduce transaction costs while maintaining investor protections. This is relevant to fund governance, valuation and affiliated-transaction controls, rather than bank capital regulation.&#xA0;</p><p><a href="https://www.sec.gov/newsroom/press-releases/2026-104-sec-proposes-expanding-securities-eligible-cross-trading-registered-funds?ref=suade.org">Original announcement</a></p><p><strong>Proposed custody framework for crypto assets</strong></p><p>1 October 2026</p><p>The SEC proposed a tailored crypto-asset custody framework for registered investment advisers and regulated funds. The proposals would permit self-custody in specified circumstances, allow state trust companies to act as crypto custodians, and amend related audit and broker-dealer custody provisions. Comments are due <strong>60 days after Federal Register publication</strong>. These remain proposals, not permissions that firms can assume are already effective.</p><p><a href="https://www.sec.gov/newsroom/press-releases/2026-100-sec-proposal-would-address-how-investment-advisers-funds-can-custody-crypto-assets-under-federal?ref=suade.org">Original announcement</a></p><p><strong>New examination handbook clarifies supervisory engagement</strong></p><p>1 October 2026</p><p>The SEC&#x2019;s Division of Examinations published a handbook explaining the examination process from initial risk assessment through to the disposition letter. Replacing the previous brochure, it provides practical preparation guidance and explains channels for questions and feedback. The publication is relevant to examination readiness and regulatory engagement, rather than introducing new substantive prudential obligations.&#xA0;</p><p><a href="https://www.sec.gov/newsroom/press-releases/2026-99-secs-division-examinations-announces-new-exam-handbook?ref=suade.org">Original announcement</a></p><p><strong>Office of the Superintendent of Financial Institutions (Canada)</strong></p><p></p><p><strong>Fall risk outlook focuses on frontier AI</strong></p><p>8 October 2026</p><p>OSFI&#x2019;s Semi-Annual Risk Outlook highlights how frontier AI can amplify cyber, technology, third-party and reputational risks. It calls on institutions to strengthen governance, controls and testing, with boards and senior management remaining accountable. OSFI also plans to strengthen its assessment of technology concentration and critical third-party dependencies. This is a supervisory risk update rather than a new capital standard.</p><p><a href="https://www.osfi-bsif.gc.ca/en/news/osfi-releases-fall-risk-update-focused-frontier-ai?ref=suade.org">Original announcement</a></p><p><strong>Clarification on use of the Bank of Canada&#x2019;s Standing Liquidity Facility</strong></p><p>29 September 2026</p><p>OSFI and the Bank of Canada clarified that overnight Standing Liquidity Facility advances to Lynx participants are a normal part of daily payment-system activity. Such drawings are consistent with routine liquidity management and are not, in themselves, signs of liquidity stress or exceptional liquidity measures. The statement is directly relevant to liquidity contingency planning and the treatment of central-bank facility usage.</p><p><a href="https://www.osfi-bsif.gc.ca/en/news/bank-canada-osfi-issue-joint-statement-use-banks-standing-liquidity-facility?ref=suade.org">Original joint statement</a></p><p><strong>Rest of World</strong></p><p><strong>Monetary Authority of Singapore</strong></p><p><strong>Final Guidelines on AI risk management for financial institutions</strong></p><p>7 October 2026</p><p>MAS published Guidelines setting supervisory expectations for managing risks arising from AI use across financial institutions and all forms of AI technology. Institutions may tailor their approaches to their risk profiles and the scale and nature of their AI activities. The publication states that the Guidelines take effect on <strong>7 October 2027</strong>, making AI governance and implementation planning a forward-looking priority.&#xA0;</p><p><a href="https://www.mas.gov.sg/regulation/guidelines/guidelines-on-artificial-intelligence-risk-management-for-financial-institutions?utm_source=openai">Original publication</a></p>]]></content:encoded></item><item><title><![CDATA[RegTech Forum 2026: Key takeaways]]></title><description><![CDATA[<p>This year&#x2019;s event saw insights from across the industry, with regulators, banks and technology leaders coming together at Guildhall, London on 6 October to discuss the future of regulatory reporting. From building trust in AI and keeping human judgement at the centre, to managing constant regulatory change and</p>]]></description><link>https://suade.org/regtech-forum-2026-key-insights-and-takeaways/</link><guid isPermaLink="false">6ac7974784bb68095b84eeea</guid><dc:creator><![CDATA[Corinne Jones]]></dc:creator><pubDate>Tue, 20 Oct 2026 09:38:25 GMT</pubDate><media:content url="https://images.unsplash.com/photo-1573720312427-5dd97ff39791?crop=entropy&amp;cs=tinysrgb&amp;fit=max&amp;fm=jpg&amp;ixid=M3wxMTc3M3wwfDF8c2VhcmNofDM4fHxsb25kb24lMjBhcmNoaXRlY3R1cmV8ZW58MHx8fHwxNzkxOTgxOTY2fDA&amp;ixlib=rb-4.1.0&amp;q=80&amp;w=2000" medium="image"/><content:encoded><![CDATA[<img src="https://images.unsplash.com/photo-1573720312427-5dd97ff39791?crop=entropy&amp;cs=tinysrgb&amp;fit=max&amp;fm=jpg&amp;ixid=M3wxMTc3M3wwfDF8c2VhcmNofDM4fHxsb25kb24lMjBhcmNoaXRlY3R1cmV8ZW58MHx8fHwxNzkxOTgxOTY2fDA&amp;ixlib=rb-4.1.0&amp;q=80&amp;w=2000" alt="RegTech Forum 2026: Key takeaways"><p>This year&#x2019;s event saw insights from across the industry, with regulators, banks and technology leaders coming together at Guildhall, London on 6 October to discuss the future of regulatory reporting. From building trust in AI and keeping human judgement at the centre, to managing constant regulatory change and an increasingly fragmented global landscape, the conversations went well beyond the headlines.</p><p>Our key takeaways bring together the main themes, insights and points of debate from the day, including perspectives from our opening and closing keynote speakers. Download the PDF to see what the industry is thinking and what to prepare for next.</p><div class="kg-card kg-product-card">
            <div class="kg-product-card-container">
                <img src="https://suade.org/content/images/2026/10/RTF-2026---Key-takeaways-cover--1-.png" width="1080" height="1080" class="kg-product-card-image" loading="lazy" alt="RegTech Forum 2026: Key takeaways">
                <div class="kg-product-card-title-container">
                    <h4 class="kg-product-card-title"></h4>
                </div>
                

                <div class="kg-product-card-description"><p><span style="white-space: pre-wrap;">Read the full summary of the Forum, including the key takeaways from across the day.</span></p></div>
                
                    <a href="https://suade.org/filehosting/resources/Suade_RegTech_Forum_2026_Takeaways.pdf" class="kg-product-card-button kg-product-card-btn-accent" target="_blank" rel="noopener noreferrer"><span>Access key takeaways</span></a>
                
            </div>
        </div>]]></content:encoded></item><item><title><![CDATA[Webinar: Navigating Canada’s evolving regulatory landscape: The latest OSFI updates]]></title><description><![CDATA[<p><strong>Date</strong>: Thursday 12th November 2026<br><strong>Time: </strong>11:30AM - 12:15PM ET<br><strong>Duration</strong>: 45 minutes<br><strong>Format</strong>: Live Webinar</p><p>Join Suade&apos;s expert, Greg Goodall and Lindsay Fortnum, Senior Manager at Deloitte for a practical look at the latest developments from OSFI, what has changed in Canada&apos;s regulatory</p>]]></description><link>https://suade.org/2026-11-12-webinar-canada-latest-osfi-update/</link><guid isPermaLink="false">6ad63e0b84bb68095b84f0fa</guid><category><![CDATA[Events]]></category><dc:creator><![CDATA[Bernice Nkoy]]></dc:creator><pubDate>Mon, 19 Oct 2026 16:33:56 GMT</pubDate><media:content url="https://suade.org/content/images/2026/10/yogesh-pedamkar-7l__1mzzkwQ-unsplash-1.jpg" medium="image"/><content:encoded><![CDATA[<img src="https://suade.org/content/images/2026/10/yogesh-pedamkar-7l__1mzzkwQ-unsplash-1.jpg" alt="Webinar: Navigating Canada&#x2019;s evolving regulatory landscape: The latest OSFI updates"><p><strong>Date</strong>: Thursday 12th November 2026<br><strong>Time: </strong>11:30AM - 12:15PM ET<br><strong>Duration</strong>: 45 minutes<br><strong>Format</strong>: Live Webinar</p><p>Join Suade&apos;s expert, Greg Goodall and Lindsay Fortnum, Senior Manager at Deloitte for a practical look at the latest developments from OSFI, what has changed in Canada&apos;s regulatory landscape, and what it means for disclosure, reporting and data processes at financial institutions.</p><h3 id="the-session-will-cover">The session will cover</h3><ul><li>Recent developments in the Canadian regulatory landscape, and the key shifts in supervisory priorities</li><li>OSFI&apos;s updated Pillar 3 disclosure guidelines, including IRRBB requirements and the expected implementation timeline</li><li>Lessons from the first year of regulatory return assurance, and where reporting processes can improve</li><li>Recent changes to the Domestic Stability Buffer and what they mean for institutions</li><li>How to strengthen data quality and controls, and streamline reporting to reduce administrative burden</li></ul><p>This session is designed for regulatory reporting, risk and finance professionals at Canadian financial institutions.<br></p>
<!--kg-card-begin: html-->
<div style="max-width:640px; margin:0 auto; background:#e9f0ff; border:1px solid #dbe4ff; border-radius:8px; padding:22px; font-family: var(--first-font-type), sans-serif; color:#111827;"> <!-- Success message (hidden until submit succeeds) --><div id="successBox" style="display:none; margin-top:4px;"><h2 style="margin:0 0 18px; font-size:22px; font-weight:700;">Thank you for registering</h2><div style="border-left:4px solid #4d67e6; padding-left:12px; line-height:1.5;">We&#x2019;ve received your details and are reviewing your submission. We&#x2019;ll contact you shortly with the next steps.</div></div><form id="regForm" novalidate><h2 style="margin:0 0 18px; font-size:22px; font-weight:700;">Registration open</h2> <input type="hidden" id="field_12" value="701QB000018L4gNYAS"> <!-- Salesforce campaign --> <input type="hidden" id="field_13" value="Registered"> <!-- Salesforce Status --> <input type="hidden" id="field_17" value="Marketing - webinar registration"> <!-- Salesforce source --> <input type="hidden" id="field_14" value="Ghost"> <!-- WP post id used by WS Form --> <input type="hidden" id="field_15" value="840 4552 2599"> <!-- Zoom webinar ID --> <!-- --> <!-- First / Last --><div style="display:flex; gap:16px; margin-bottom:14px; flex-wrap:wrap;"><div style="flex:1; min-width:220px;"> <label for="field_1" style="display:block; font-size:14px; margin:0 0 6px;">First name <span style="color:#dc2626;">*</span></label> <input id="field_1" required autocomplete="given-name" style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;"></div><div style="flex:1; min-width:220px;"> <label for="field_2" style="display:block; font-size:14px; margin:0 0 6px;">Last name <span style="color:#dc2626;">*</span></label> <input id="field_2" required autocomplete="family-name" style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;"></div></div> <!-- Title --><div style="margin-bottom:14px;"> <label for="field_8" style="display:block; font-size:14px; margin:0 0 6px;">Job title <span style="color:#dc2626;">*</span></label> <input id="field_8" required style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;"></div> <!-- Company --><div style="margin-bottom:14px;"> <label for="field_9" style="display:block; font-size:14px; margin:0 0 6px;">Company <span style="color:#dc2626;">*</span></label> <input id="field_9" required autocomplete="organization" style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;"></div> <!-- Email --><div style="margin-bottom:14px;"> <label for="field_3" style="display:block; font-size:14px; margin:0 0 6px;">Email <span style="color:#dc2626;">*</span></label> <input id="field_3" type="email" required autocomplete="email" inputmode="email" style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;"></div><div id="emailError" style="display:none; color:#b91c1c; font-size:13px; margin:0 0 10px 0;">Please enter a valid work email address.</div>  <!-- Message --><div id="messageContainer" style="margin-bottom:14px; display:none"> <label for="field_5" style>Message <span>*</span></label><textarea id="field_5" rows="6"></textarea></div><div style="margin-bottom:18px;"> <label for="field_10" style="display:block; font-size:14px; margin:0 0 6px;">Country <span style="color:#dc2626;">*</span></label> <select id="field_10" name="field_10[]" required autocomplete="country" style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;"><option value selected disabled>Select...</option><option value="AF">Afghanistan</option><option value="AL">Albania</option><option value="DZ">Algeria</option><option value="AD">Andorra</option><option value="AO">Angola</option><option value="AG">Antigua and Barbuda</option><option value="AR">Argentina</option><option value="AM">Armenia</option><option value="AU">Australia</option><option value="AT">Austria</option><option value="AZ">Azerbaijan</option><option value="BS">Bahamas</option><option value="BH">Bahrain</option><option value="BD">Bangladesh</option><option value="BB">Barbados</option><option value="BY">Belarus</option><option value="BE">Belgium</option><option value="BZ">Belize</option><option value="BJ">Benin</option><option value="BT">Bhutan</option><option value="BO">Bolivia</option><option value="BA">Bosnia and Herzegovina</option><option value="BW">Botswana</option><option value="BR">Brazil</option><option value="BN">Brunei</option><option value="BG">Bulgaria</option><option value="BF">Burkina Faso</option><option value="BI">Burundi</option><option value="CV">Cabo Verde</option><option value="KH">Cambodia</option><option value="CM">Cameroon</option><option value="CA">Canada</option><option value="CF">Central African Republic</option><option value="TD">Chad</option><option value="CL">Chile</option><option value="CN">China</option><option value="CO">Colombia</option><option value="KM">Comoros</option><option value="CG">Congo</option><option value="CD">Congo, Democratic Republic of the</option><option value="CR">Costa Rica</option><option value="CI">C&#xF4;te d&#x2019;Ivoire</option><option value="HR">Croatia</option><option value="CU">Cuba</option><option value="CY">Cyprus</option><option value="CZ">Czechia</option><option value="DK">Denmark</option><option value="DJ">Djibouti</option><option value="DM">Dominica</option><option value="DO">Dominican Republic</option><option value="EC">Ecuador</option><option value="EG">Egypt</option><option value="SV">El Salvador</option><option value="GQ">Equatorial Guinea</option><option value="ER">Eritrea</option><option value="EE">Estonia</option><option value="SZ">Eswatini</option><option value="ET">Ethiopia</option><option value="FJ">Fiji</option><option value="FI">Finland</option><option value="FR">France</option><option value="GA">Gabon</option><option value="GM">Gambia</option><option value="GE">Georgia</option><option value="DE">Germany</option><option value="GH">Ghana</option><option value="GI">Gibraltar</option><option value="GR">Greece</option><option value="GD">Grenada</option><option value="GT">Guatemala</option><option value="GN">Guinea</option><option value="GW">Guinea-Bissau</option><option value="GY">Guyana</option><option value="HT">Haiti</option><option value="HN">Honduras</option><option value="HK">Hong Kong</option><option value="HU">Hungary</option><option value="IS">Iceland</option><option value="IN">India</option><option value="ID">Indonesia</option><option value="IQ">Iraq</option><option value="IE">Ireland</option><option value="IM">Isle of Man</option><option value="IL">Israel</option><option value="IT">Italy</option><option value="JM">Jamaica</option><option value="JP">Japan</option><option value="JE">Jersey</option><option value="JO">Jordan</option><option value="KZ">Kazakhstan</option><option value="KE">Kenya</option><option value="KI">Kiribati</option><option value="KR">Korea</option><option value="KW">Kuwait</option><option value="KG">Kyrgyzstan</option><option value="LA">Laos</option><option value="LV">Latvia</option><option value="LB">Lebanon</option><option value="LS">Lesotho</option><option value="LR">Liberia</option><option value="LY">Libya</option><option value="LI">Liechtenstein</option><option value="LT">Lithuania</option><option value="LU">Luxembourg</option><option value="MG">Madagascar</option><option value="MW">Malawi</option><option value="MY">Malaysia</option><option value="MV">Maldives</option><option value="ML">Mali</option><option value="MT">Malta</option><option value="MR">Mauritania</option><option value="MU">Mauritius</option><option value="MX">Mexico</option><option value="FM">Micronesia (Federated States of)</option><option value="MD">Moldova</option><option value="MC">Monaco</option><option value="MN">Mongolia</option><option value="ME">Montenegro</option><option value="MA">Morocco</option><option value="MZ">Mozambique</option><option value="MM">Myanmar</option><option value="NA">Namibia</option><option value="NR">Nauru</option><option value="NP">Nepal</option><option value="NL">Netherlands</option><option value="NZ">New Zealand</option><option value="NI">Nicaragua</option><option value="NE">Niger</option><option value="NG">Nigeria</option><option value="MK">North Macedonia</option><option value="NO">Norway</option><option value="OM">Oman</option><option value="PK">Pakistan</option><option value="PW">Palau</option><option value="PA">Panama</option><option value="PG">Papua New Guinea</option><option value="PY">Paraguay</option><option value="PE">Peru</option><option value="PH">Philippines</option><option value="PL">Poland</option><option value="PT">Portugal</option><option value="QA">Qatar</option><option value="RO">Romania</option><option value="RU">Russian Federation</option><option value="RW">Rwanda</option><option value="KN">Saint Kitts and Nevis</option><option value="LC">Saint Lucia</option><option value="VC">Saint Vincent and the Grenadines</option><option value="WS">Samoa</option><option value="SM">San Marino</option><option value="ST">Sao Tome and Principe</option><option value="SA">Saudi Arabia</option><option value="SN">Senegal</option><option value="RS">Serbia</option><option value="SC">Seychelles</option><option value="SL">Sierra Leone</option><option value="SG">Singapore</option><option value="SK">Slovakia</option><option value="SI">Slovenia</option><option value="SB">Solomon Islands</option><option value="SO">Somalia</option><option value="ZA">South Africa</option><option value="SS">South Sudan</option><option value="ES">Spain</option><option value="LK">Sri Lanka</option><option value="SD">Sudan</option><option value="SR">Suriname</option><option value="SE">Sweden</option><option value="CH">Switzerland</option><option value="SY">Syria</option><option value="TW">Taiwan</option><option value="TJ">Tajikistan</option><option value="TZ">Tanzania</option><option value="TH">Thailand</option><option value="TL">Timor-Leste</option><option value="TG">Togo</option><option value="TO">Tonga</option><option value="TT">Trinidad and Tobago</option><option value="TN">Tunisia</option><option value="TR">Turkey (T&#xFC;rkiye)</option><option value="TM">Turkmenistan</option><option value="TV">Tuvalu</option><option value="UG">Uganda</option><option value="UA">Ukraine</option><option value="AE">United Arab Emirates</option><option value="GB">United Kingdom</option><option value="US">United States</option><option value="UY">Uruguay</option><option value="UZ">Uzbekistan</option><option value="VU">Vanuatu</option><option value="VE">Venezuela</option><option value="VN">Viet Nam</option><option value="YE">Yemen</option><option value="ZM">Zambia</option><option value="ZW">Zimbabwe</option> </select></div> <!-- Submit --> <button type="submit" style="font-family: IBM Plex Sans, sans-serif; width:100%; padding:12px 16px; border:0; border-radius:8px; background:#4d67e6; color:#fff; font-size:16px; font-weight:600; cursor:pointer;"> Submit </button> <input type="hidden" id="g-recaptcha-response" value><p>By submitting this form to Suade you hereby agree that any personal information you provide can be processed according to Suade&#x2019;s <a href="https://suade.org/privacy-policy/">Privacy policy</a>.</p></form><div id="status" style="margin-top:12px; font-size:14px;" aria-live="polite"></div> <script> (function () {
 console.log("script start");
 const messageContainer = document.getElementById("messageContainer");
 const messageField = document.getElementById("field_5"); 
 const emailInput = document.getElementById('field_3');
 const errEl = document.getElementById('emailError');
 // Base providers (compare against the "second-level" label like gmail, yahoo, outlook, etc.)
 const BLOCKED_SLD = new Set([
 'gmail',
 'yahoo',
 'hotmail',
 'live',
 'outlook',
 'aol',
 'msn',
 'icloud',
 'me',
 'mac',
 'btinternet',
 'talktalk',
 'virginmedia',
 'comcast',
 'verizon',
 'sky',
 ]);
 function baseLabel(host) {
 const parts = host.split('.').filter(Boolean);
 if (parts.length < 2) return host;
 const tld = parts[parts.length - 1];
 // ccTLD heuristic (e.g., .co.uk, .com.au)
 if (tld.length === 2 && parts.length >= 3) {
 return parts[parts.length - 3]; // label before .co.uk/.com.au
 }
 return parts[parts.length - 2];
 }
 function isPersonalEmail(email) {
 const m = String(email).toLowerCase().match(/^[^@\s]+@([^@\s]+)$/);
 if (!m) return false; // let type=email handle malformed addresses
 const host = m[1];
 const sld = baseLabel(host);
 return BLOCKED_SLD.has(sld);
 }
 function showWorkEmailError(show) {
 if (show) {
 emailInput.setCustomValidity('Please enter a valid work email address.');
 errEl.style.display = 'block';
 } else {
 emailInput.setCustomValidity('');
 errEl.style.display = 'none';
 }
 }
 function validateEmail() {
 const val = emailInput.value.trim();
 const block = val && isPersonalEmail(val);
 showWorkEmailError(block);
 return !block;
 }
 emailInput.addEventListener('input', validateEmail);
 emailInput.addEventListener('blur', validateEmail);  const ENDPOINT = 'https://harrya10.sg-host.com/wp-json/ws-form/v1/submit'; // remote WP site
 const $ = (id) => document.getElementById(id);
 function buildFormData(nonce) {
 const fd = new FormData();
 // Main fields (must match cURL exactly)
 fd.append('field_1',  $('field_1').value.trim());
 fd.append('field_2',  $('field_2').value.trim());
 fd.append('field_8',  $('field_8').value.trim());
 fd.append('field_9',  $('field_9').value.trim());
 fd.append('field_3',  $('field_3').value.trim());
 fd.append('field_5',  $('field_5').value.trim());
 fd.append('field_10[]', $('field_10').value); // ISO alpha-2
 // Hidden fields/constants
 fd.append('field_12', $('field_12').value);
 fd.append('field_13', $('field_13').value);
 fd.append('field_17', $('field_17').value);
 fd.append('field_15', $('field_15').value);
 fd.append('field_14', $('field_14').value);
 // reCAPTCHA token (optional but often required on receiver)
 // fd.append('g-recaptcha-response', $('g-recaptcha-response').value || '');
 // WS Form meta (match cURL)
 fd.append('wsf_form_id', '1');
 fd.append('wsf_hash', '');
 fd.append('wsf_nonce', nonce);
 fd.append('wsf_post_id', $('field_14').value);
 fd.append('wsf_post_mode', 'submit');
 fd.append('wsf_hidden', '');
 fd.append('wsf_bypass_required', '');
 console.table([...fd]); //
 return fd;
 }  // 2) submit to WS Form REST endpoint
 const sleep = ms => new Promise(r => setTimeout(r, ms));
 async function fetchRetry(url, opts = {}, tries = 3) {
 try {
 const res = await fetch(url, { ...opts, signal: AbortSignal.timeout(8000) });
 if (!res.ok) throw Object.assign(new Error('HTTP ' + res.status), { res });
 return res;
 } catch (e) {
 if (tries <= 1) throw e;
 await sleep(400 * (4 - tries));
 return fetchRetry(url, opts, tries - 1);
 }
 } 
 async function submitRemote(fd) {
 console.log("form submit");
 const res = await fetchRetry(ENDPOINT, {
 method: 'POST',
 body: fd,
 mode: 'cors',
 credentials: 'omit'
 });
 return res;
 }
 const form = $('regForm');
 const statusEl = $('status');
 const success = $('successBox');
 form.addEventListener('submit', async (e) => {
 e.preventDefault();
 if (!form.checkValidity()) { form.reportValidity(); return; }
 const btn = form.querySelector('button[type="submit"]');
 console.log("button clicked");
 btn.disabled = true;
 statusEl.style.color = '#111827';
 statusEl.textContent = 'Submitting…'; 
 let res; 
 try {
 const { nonce } = await fetchRetry('https://harrya10.sg-host.com/wp-json/custom/v1/nonce', {
 credentials: 'omit' 
 }).then(r => r.json());  const fd = buildFormData(nonce);
 const res = await submitRemote(fd);
 if (res.ok) {
 form.style.display = 'none';
 success.style.display = 'block';
 statusEl.textContent = '';
 console.log("submission OK");
 } else {
 const t = await res.text().catch(() => '');
 statusEl.style.color = '#b91c1c';
 statusEl.textContent = 'Submission failed. Please try again.';
 console.error('WS Form error', res.status, t);
 }
 } catch (err) {
 statusEl.style.color = '#b91c1c';
 statusEl.textContent = 'Network error. Please try again in a minute.';
 console.error(err); 
 } finally {
 btn.disabled = false;
 console.log(res);
 }
 });
 })(); </script></div>
<!--kg-card-end: html-->
]]></content:encoded></item><item><title><![CDATA[A Little Suade Christmas]]></title><description><![CDATA[<!--kg-card-begin: html-->
<p style="font-family: Georgia, serif; font-size: 20px; line-height: 1.6; color: #990F2B; font-style: italic; margin-top: 0;">
 Tuesday 24 November 2026 | Bank, London
</p>

<!--kg-card-end: html-->
<p>Celebrate the Season with Suade and join us for an evening of drinks, festive food and great company as we bring together peers from across the regulatory reporting community.</p><p>As the year draws to a close, it&#x2019;s a chance to catch up</p>]]></description><link>https://suade.org/2026-11-24_a-little-suade-christmas/</link><guid isPermaLink="false">6ace474484bb68095b84ef7d</guid><category><![CDATA[Events]]></category><dc:creator><![CDATA[Phoebe Regnault]]></dc:creator><pubDate>Tue, 13 Oct 2026 15:16:00 GMT</pubDate><media:content url="https://images.unsplash.com/photo-1512474932049-78ac69ede12c?crop=entropy&amp;cs=tinysrgb&amp;fit=max&amp;fm=jpg&amp;ixid=M3wxMTc3M3wwfDF8c2VhcmNofDIxfHxjaHJpc3RtYXN8ZW58MHx8fHwxNzkxOTA0MDg5fDA&amp;ixlib=rb-4.1.0&amp;q=80&amp;w=2000" medium="image"/><content:encoded><![CDATA[
<!--kg-card-begin: html-->
<img src="https://images.unsplash.com/photo-1512474932049-78ac69ede12c?crop=entropy&amp;cs=tinysrgb&amp;fit=max&amp;fm=jpg&amp;ixid=M3wxMTc3M3wwfDF8c2VhcmNofDIxfHxjaHJpc3RtYXN8ZW58MHx8fHwxNzkxOTA0MDg5fDA&amp;ixlib=rb-4.1.0&amp;q=80&amp;w=2000" alt="A Little Suade Christmas"><p style="font-family: Georgia, serif; font-size: 20px; line-height: 1.6; color: #990F2B; font-style: italic; margin-top: 0;">
 Tuesday 24 November 2026 | Bank, London
</p>

<!--kg-card-end: html-->
<p>Celebrate the Season with Suade and join us for an evening of drinks, festive food and great company as we bring together peers from across the regulatory reporting community.</p><p>As the year draws to a close, it&#x2019;s a chance to catch up with familiar faces, make new connections and celebrate another year in the industry. And, of course, you&#x2019;ll leave with a little Christmas gift from Suade!</p>
<!--kg-card-begin: html-->

<p style="font-family: Georgia, serif; font-size: 20px; line-height: 1.6; color: #990F2B; font-style: italic; margin-top: 0;">
  Register your interest:
</p>

<!--kg-card-end: html-->

<!--kg-card-begin: html-->
<div style="max-width:640px; margin:0 auto; background:#e9f0ff; border:1px solid #dbe4ff; border-radius:8px; padding:22px; font-family: var(--first-font-type), sans-serif; color:#111827;">

    <!-- Success message (hidden until submit succeeds) -->
    <div id="successBox" style="display:none; margin-top:4px;">
        
        <h2 style="margin:0 0 18px; font-size:22px; font-weight:700;">Thank you for registering</h2>
      <div style="border-left:4px solid #4d67e6; padding-left:12px; line-height:1.5;">We&#x2019;ve received your details and are reviewing your submission. We&#x2019;ll contact you shortly with the next steps.
        </div>
    </div>

    <form id="regForm" novalidate>

          <h2 style="margin:0 0 18px; font-size:22px; font-weight:700;">Registration open</h2>
        
        <input type="hidden" id="field_12" value="701QB00000qWSPrYAO">  <!-- Salesforce campaign -->
        <input type="hidden" id="field_13" value="Registered"> <!-- Salesforce Status -->
              <input type="hidden" id="field_17" value="Marketing - event registration"> <!-- Salesforce source -->
        <input type="hidden" id="field_14" value="Ghost"> <!-- utm campaign -->
        <input type="hidden" id="field_15" value> <!-- Zoom webinar ID -->


        <!-- -->
     
        <!-- First / Last -->
        <div style="display:flex; gap:16px; margin-bottom:14px; flex-wrap:wrap;">
            <div style="flex:1; min-width:220px;">
                <label for="field_1" style="display:block; font-size:14px; margin:0 0 6px;">First name <span style="color:#dc2626;">*</span></label>
                <input id="field_1" required autocomplete="given-name" style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;">
            </div>
            <div style="flex:1; min-width:220px;">
                <label for="field_2" style="display:block; font-size:14px; margin:0 0 6px;">Last name <span style="color:#dc2626;">*</span></label>
                <input id="field_2" required autocomplete="family-name" style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;">
            </div>
        </div>

        <!-- Title -->
        <div style="margin-bottom:14px;">
            <label for="field_8" style="display:block; font-size:14px; margin:0 0 6px;">Job title <span style="color:#dc2626;">*</span></label>
            <input id="field_8" required style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;">
        </div>

        <!-- Company -->
        <div style="margin-bottom:14px;">
            <label for="field_9" style="display:block; font-size:14px; margin:0 0 6px;">Company <span style="color:#dc2626;">*</span></label>
            <input id="field_9" required autocomplete="organization" style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;">
        </div>

        <!-- Email -->
        <div style="margin-bottom:14px;">
            <label for="field_3" style="display:block; font-size:14px; margin:0 0 6px;">Email <span style="color:#dc2626;">*</span></label>
            <input id="field_3" type="email" required autocomplete="email" inputmode="email" style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;">
        </div>
        <div id="emailError" style="display:none; color:#b91c1c; font-size:13px; margin:0 0 10px 0;">Please enter a valid work email address.</div>
<!-- Message -->
      
        <div id="messageContainer" style="margin-bottom:14px; display:none">
            <label for="field_5" style>Message <span>*</span></label>
            <textarea id="field_5" rows="6"></textarea>
        </div>
<div style="margin-bottom:18px;">
            <label for="field_10" style="display:block; font-size:14px; margin:0 0 6px;">Country <span style="color:#dc2626;">*</span></label>
            <select id="field_10" name="field_10[]" required autocomplete="country" style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;">
                <option value selected disabled>Select...</option>
                <option value="AF">Afghanistan</option>
<option value="AL">Albania</option>
<option value="DZ">Algeria</option>
<option value="AD">Andorra</option>
<option value="AO">Angola</option>
<option value="AG">Antigua and Barbuda</option>
<option value="AR">Argentina</option>
<option value="AM">Armenia</option>
<option value="AU">Australia</option>
<option value="AT">Austria</option>
<option value="AZ">Azerbaijan</option>
<option value="BS">Bahamas</option>
<option value="BH">Bahrain</option>
<option value="BD">Bangladesh</option>
<option value="BB">Barbados</option>
<option value="BE">Belgium</option>
<option value="BZ">Belize</option>
<option value="BJ">Benin</option>
<option value="BT">Bhutan</option>
<option value="BO">Bolivia</option>
<option value="BA">Bosnia and Herzegovina</option>
<option value="BW">Botswana</option>
<option value="BR">Brazil</option>
<option value="BN">Brunei</option>
<option value="BG">Bulgaria</option>
<option value="BF">Burkina Faso</option>
<option value="BI">Burundi</option>
<option value="CV">Cabo Verde</option>
<option value="KH">Cambodia</option>
<option value="CM">Cameroon</option>
<option value="CA">Canada</option>
<option value="CF">Central African Republic</option>
<option value="TD">Chad</option>
<option value="CL">Chile</option>
<option value="CN">China</option>
<option value="CO">Colombia</option>
<option value="KM">Comoros</option>
<option value="CG">Congo</option>
<option value="CD">Congo, Democratic Republic of the</option>
<option value="CR">Costa Rica</option>
<option value="CI">C&#xF4;te d&#x2019;Ivoire</option>
<option value="HR">Croatia</option>
<option value="CU">Cuba</option>
<option value="CY">Cyprus</option>
<option value="CZ">Czechia</option>
<option value="DK">Denmark</option>
<option value="DJ">Djibouti</option>
<option value="DM">Dominica</option>
<option value="DO">Dominican Republic</option>
<option value="EC">Ecuador</option>
<option value="EG">Egypt</option>
<option value="SV">El Salvador</option>
<option value="GQ">Equatorial Guinea</option>
<option value="ER">Eritrea</option>
<option value="EE">Estonia</option>
<option value="SZ">Eswatini</option>
<option value="ET">Ethiopia</option>
<option value="FJ">Fiji</option>
<option value="FI">Finland</option>
<option value="FR">France</option>
<option value="GA">Gabon</option>
<option value="GM">Gambia</option>
<option value="GE">Georgia</option>
<option value="DE">Germany</option>
<option value="GH">Ghana</option>
<option value="GI">Gibraltar</option>
<option value="GR">Greece</option>
<option value="GD">Grenada</option>
<option value="GT">Guatemala</option>
<option value="GN">Guinea</option>
<option value="GW">Guinea-Bissau</option>
<option value="GY">Guyana</option>
<option value="HT">Haiti</option>
<option value="HN">Honduras</option>
<option value="HK">Hong Kong</option>
<option value="HU">Hungary</option>
<option value="IS">Iceland</option>
<option value="IN">India</option>
<option value="ID">Indonesia</option>
<option value="IQ">Iraq</option>
<option value="IE">Ireland</option>
<option value="IM">Isle of Man</option>
<option value="IL">Israel</option>
<option value="IT">Italy</option>
<option value="JM">Jamaica</option>
<option value="JP">Japan</option>
<option value="JE">Jersey</option>
<option value="JO">Jordan</option>
<option value="KZ">Kazakhstan</option>
<option value="KE">Kenya</option>
<option value="KI">Kiribati</option>
<option value="KR">Korea</option>
<option value="KW">Kuwait</option>
<option value="KG">Kyrgyzstan</option>
<option value="LA">Laos</option>
<option value="LV">Latvia</option>
<option value="LB">Lebanon</option>
<option value="LS">Lesotho</option>
<option value="LR">Liberia</option>
<option value="LY">Libya</option>
<option value="LI">Liechtenstein</option>
<option value="LT">Lithuania</option>
<option value="LU">Luxembourg</option>
<option value="MG">Madagascar</option>
<option value="MW">Malawi</option>
<option value="MY">Malaysia</option>
<option value="MV">Maldives</option>
<option value="ML">Mali</option>
<option value="MT">Malta</option>
<option value="MR">Mauritania</option>
<option value="MU">Mauritius</option>
<option value="MX">Mexico</option>
<option value="FM">Micronesia (Federated States of)</option>
<option value="MD">Moldova</option>
<option value="MC">Monaco</option>
<option value="MN">Mongolia</option>
<option value="ME">Montenegro</option>
<option value="MA">Morocco</option>
<option value="MZ">Mozambique</option>
<option value="MM">Myanmar</option>
<option value="NA">Namibia</option>
<option value="NR">Nauru</option>
<option value="NP">Nepal</option>
<option value="NL">Netherlands</option>
<option value="NZ">New Zealand</option>
<option value="NI">Nicaragua</option>
<option value="NE">Niger</option>
<option value="NG">Nigeria</option>
<option value="MK">North Macedonia</option>
<option value="NO">Norway</option>
<option value="OM">Oman</option>
<option value="PK">Pakistan</option>
<option value="PW">Palau</option>
<option value="PA">Panama</option>
<option value="PG">Papua New Guinea</option>
<option value="PY">Paraguay</option>
<option value="PE">Peru</option>
<option value="PH">Philippines</option>
<option value="PL">Poland</option>
<option value="PT">Portugal</option>
<option value="QA">Qatar</option>
<option value="RO">Romania</option>
<option value="RW">Rwanda</option>
<option value="KN">Saint Kitts and Nevis</option>
<option value="LC">Saint Lucia</option>
<option value="VC">Saint Vincent and the Grenadines</option>
<option value="WS">Samoa</option>
<option value="SM">San Marino</option>
<option value="ST">Sao Tome and Principe</option>
<option value="SA">Saudi Arabia</option>
<option value="SN">Senegal</option>
<option value="RS">Serbia</option>
<option value="SC">Seychelles</option>
<option value="SL">Sierra Leone</option>
<option value="SG">Singapore</option>
<option value="SK">Slovakia</option>
<option value="SI">Slovenia</option>
<option value="SB">Solomon Islands</option>
<option value="SO">Somalia</option>
<option value="ZA">South Africa</option>
<option value="SS">South Sudan</option>
<option value="ES">Spain</option>
<option value="LK">Sri Lanka</option>
<option value="SD">Sudan</option>
<option value="SR">Suriname</option>
<option value="SE">Sweden</option>
<option value="CH">Switzerland</option>
<option value="SY">Syria</option>
<option value="TW">Taiwan</option>
<option value="TJ">Tajikistan</option>
<option value="TZ">Tanzania</option>
<option value="TH">Thailand</option>
<option value="TL">Timor-Leste</option>
<option value="TG">Togo</option>
<option value="TO">Tonga</option>
<option value="TT">Trinidad and Tobago</option>
<option value="TN">Tunisia</option>
<option value="TR">Turkey (T&#xFC;rkiye)</option>
<option value="TM">Turkmenistan</option>
<option value="TV">Tuvalu</option>
<option value="UG">Uganda</option>
<option value="UA">Ukraine</option>
<option value="AE">United Arab Emirates</option>
<option value="GB">United Kingdom</option>
<option value="US">United States</option>
<option value="UY">Uruguay</option>
<option value="UZ">Uzbekistan</option>
<option value="VU">Vanuatu</option>
<option value="VE">Venezuela</option>
<option value="VN">Viet Nam</option>
<option value="ZM">Zambia</option>
<option value="ZW">Zimbabwe</option>
            </select>
        </div>

        <!-- Submit -->
        <button type="submit" style="font-family: IBM Plex Sans, sans-serif; width:100%; padding:12px 16px; border:0; border-radius:8px; background:#4d67e6; color:#fff; font-size:16px; font-weight:600; cursor:pointer;">
            Submit
        </button>
   
    
        <input type="hidden" id="g-recaptcha-response" value>
    
           <p>By submitting this form to Suade you hereby agree that any personal information you provide can be processed according to Suade&#x2019;s <a href="https://suade.org/privacy-policy/">Privacy policy</a>.</p>
    
    </form>

    <div id="status" style="margin-top:12px; font-size:14px;" aria-live="polite"></div>
<script>
(function () {

  console.log("script start");

  const messageContainer = document.getElementById("messageContainer");
  const messageField = document.getElementById("field_5");
  const emailInput = document.getElementById("field_3");
  const errEl = document.getElementById("emailError");
  const utm_field = document.getElementById('field_14');
  if (utm_field) {
    utm_field.value =
      new URLSearchParams(window.location.search).get('utm_campaign') || 'Ghost';
  }

  const BLOCKED_SLD = new Set([
    'gmail',
    'yahoo',
    'hotmail',
    'live',
    'outlook',
    'aol',
    'msn',
    'icloud',
    'me',
    'mac',
    'btinternet',
    'talktalk',
    'virginmedia',
    'comcast',
    'verizon',
    'sky'
  ]);

  function baseLabel(host) {
    const parts = host.split('.').filter(Boolean);

    if (parts.length < 2) {
      return host;
    }

    const tld = parts[parts.length - 1];

    if (tld.length === 2 && parts.length >= 3) {
      return parts[parts.length - 3];
    }

    return parts[parts.length - 2];
  }

  function isPersonalEmail(email) {
    const m = String(email)
      .toLowerCase()
      .match(/^[^@\s]+@([^@\s]+)$/);

    if (!m) {
      return false;
    }

    const host = m[1];
    const sld = baseLabel(host);

    return BLOCKED_SLD.has(sld);
  }

  function showWorkEmailError(show) {
    if (show) {
      emailInput.setCustomValidity(
        'Please enter a valid work email address.'
      );

      errEl.style.display = 'block';
    } else {
      emailInput.setCustomValidity('');
      errEl.style.display = 'none';
    }
  }

  function validateEmail() {
    const val = emailInput.value.trim();
    const block = val && isPersonalEmail(val);

    showWorkEmailError(block);

    return !block;
  }

  emailInput.addEventListener('input', validateEmail);
  emailInput.addEventListener('blur', validateEmail);


  const $ = (id) => document.getElementById(id);

  const SALESFORCE_ENDPOINT =
    'https://webto.salesforce.com/servlet/servlet.WebToLead?encoding=UTF-8';
  const ZOOM_ENDPOINT = 'https://applications.zoom.us/api/v1/pardot/registration/Nh8FHOozT0uoLb9XrHGOAg?state=VkVSU046MDAwlEtstTrtQnaPm6-F1cYhzo180QIO0fZmXBfv55996eHVuPaCHIEBHQ1aJOUPO9L7GT4'
  
  const salesforceIframe = document.createElement('iframe');

  salesforceIframe.name = 'salesforceTarget';
  salesforceIframe.id = 'salesforceTarget';
  salesforceIframe.style.display = 'none';

  document.body.appendChild(salesforceIframe);

  const zoomIframe = document.createElement('iframe');

  zoomIframe.name = 'zoomTarget';
  zoomIframe.id = 'zoomTarget';
  zoomIframe.style.display = 'none';
  
  document.body.appendChild(zoomIframe);

  function addField(form, name, value) {
    const input = document.createElement('input');

    input.type = 'hidden';
    input.name = name;
    input.value = value || '';

    form.appendChild(input);
  }

  function submitToSalesforce() {

    const sfForm = document.createElement('form');

    sfForm.method = 'POST';
    sfForm.action = SALESFORCE_ENDPOINT;
    sfForm.target = 'salesforceTarget';
    sfForm.style.display = 'none';

    addField(
      sfForm,
      'oid',
      '00D1t000000vUFQ'
    );

    addField(
      sfForm,
      '00NQB00000H9wKx',
      $('field_3').value.trim()
    );

    addField(
      sfForm,
      'first_name',
      $('field_1').value.trim()
    );

    addField(
      sfForm,
      'last_name',
      $('field_2').value.trim()
    );

    addField(
      sfForm,
      'company',
      $('field_9').value.trim()
    );

    addField(
      sfForm,
      'title',
      $('field_8').value.trim()
    );

    addField(
      sfForm,
      'country_code',
      $('field_10').value
    );

    addField(
      sfForm,
      '00N3Y00000H76Kw',
      $('field_12').value
    );

    addField(
      sfForm,
      '00NQB0000051EZ7',
      $('field_13').value
    );

    addField(
      sfForm,
      '00NQB00000Uy1rC',
      $('field_14').value
    );

    addField(
      sfForm,
      'description',
      $('field_5').value.trim()
    );

    addField(
      sfForm,
      'lead_source',
      $('field_17').value
    );

    document.body.appendChild(sfForm);

    console.log('Submitting directly to Salesforce');

    sfForm.submit();

    setTimeout(function () {
      sfForm.remove();
    }, 1000);
  }

  function submitToZoom() {

  const webinarId = $('field_15').value.trim();

  // Don't attempt Zoom registration if this event has no webinar ID.
  if (!webinarId) {
    console.log('No Zoom webinar ID configured - skipping Zoom registration');
    return;
  }

  const zoomForm = document.createElement('form');

  zoomForm.method = 'POST';
  zoomForm.action = ZOOM_ENDPOINT;
  zoomForm.target = 'zoomTarget';
  zoomForm.style.display = 'none';

  addField(
    zoomForm,
    'first_name',
    $('field_1').value.trim()
  );

  addField(
    zoomForm,
    'last_name',
    $('field_2').value.trim()
  );

  addField(
    zoomForm,
    'org',
    $('field_9').value.trim()
  );

  addField(
    zoomForm,
    'job_title',
    $('field_8').value.trim()
  );

  addField(
    zoomForm,
    'email',
    $('field_3').value.trim()
  );

  addField(
    zoomForm,
    'webinarId',
    webinarId
  );

  document.body.appendChild(zoomForm);

  console.log(
    'Submitting directly to Zoom webinar:',
    webinarId
  );

  zoomForm.submit();

  setTimeout(function () {
    zoomForm.remove();
  }, 1000);
}

  const form = $('regForm');
  const statusEl = $('status');
  const success = $('successBox');

  form.addEventListener('submit', function (e) {

    e.preventDefault();

    validateEmail();

    if (!form.checkValidity()) {
      form.reportValidity();
      return;
    }

    const btn =
      form.querySelector('button[type="submit"]');

    console.log("button clicked");

    btn.disabled = true;

    statusEl.style.color = '#111827';
    statusEl.textContent = 'Submitting…';

    try {

      submitToSalesforce();
      submitToZoom();


      form.style.display = 'none';
      success.style.display = 'block';

      statusEl.textContent = '';

      console.log('Salesforce and Zoom submissions sent');

    } catch (err) {

      statusEl.style.color = '#b91c1c';

      statusEl.textContent =
        'Submission failed. Please try again.';

      console.error(err);

      btn.disabled = false;
    }

  });

})();
</script>
</div>
<!--kg-card-end: html-->
]]></content:encoded></item><item><title><![CDATA[RegTech Forum 2026 - Fireside chat: How to use the best tool for the job]]></title><description><![CDATA[<p>As financial institutions explore new ways to improve efficiency and modernise regulatory reporting, choosing the right technology for the task has become increasingly important. The <em>How to Use the Best Tool for the Job</em> panel examined how automation and artificial intelligence can deliver meaningful benefits, while highlighting the importance of</p>]]></description><link>https://suade.org/fireside-chat-how-to-use-the-best-tool-for-the-job/</link><guid isPermaLink="false">6acf3c0784bb68095b84efba</guid><category><![CDATA[Insights]]></category><dc:creator><![CDATA[Bernice Nkoy]]></dc:creator><pubDate>Tue, 13 Oct 2026 11:12:00 GMT</pubDate><media:content url="https://suade.org/content/images/2026/10/Untitled-design--22-.png" medium="image"/><content:encoded><![CDATA[<img src="https://suade.org/content/images/2026/10/Untitled-design--22-.png" alt="RegTech Forum 2026 - Fireside chat: How to use the best tool for the job"><p>As financial institutions explore new ways to improve efficiency and modernise regulatory reporting, choosing the right technology for the task has become increasingly important. The <em>How to Use the Best Tool for the Job</em> panel examined how automation and artificial intelligence can deliver meaningful benefits, while highlighting the importance of reliable data, effective controls and human accountability.</p><p><strong>Automation creates value when it frees people to focus on higher-value work.</strong> Replacing repetitive manual processes with more effective tools can improve speed and efficiency, allowing specialists to dedicate more time to investigating risks, analysing data and supporting better decisions. However, these benefits depend on selecting technology that addresses a genuine business need.</p><p><strong>Strong data foundations remain essential for reliable AI.</strong> Legacy systems, inconsistent data definitions and poor data lineage continue to present challenges for financial institutions. AI cannot compensate for fundamental weaknesses in the information it relies on. Investing in data quality, integration and consistent definitions is therefore critical to producing trustworthy outputs.</p><p><strong>Accuracy requires more than generating an answer.</strong> Producing a report or recommendation does not guarantee that it is correct. Reconciliation, validation and robust controls are essential to ensure outputs are accurate, consistent and suitable for regulatory use. As AI becomes more capable, firms must retain the ability to verify its work rather than assume its results are reliable.</p><p><strong>AI governance must be embedded into the technology itself.</strong> As AI agents become more autonomous and operate at greater speed and scale, relying solely on human oversight may not be sufficient. Firms need clearly defined permissions, preventative controls and mechanisms to identify and stop inappropriate actions. The level of control should reflect the risks associated with each application.</p><p><strong>Human accountability remains central to responsible adoption.</strong> Organisations must be able to explain why they trust a system, demonstrate the checks applied to its outputs and identify who is responsible when something goes wrong. AI can support decision-making, but it does not remove the need for professional judgement or clear ownership of outcomes.</p><p><strong>The right tool depends on the task and its potential impact.</strong> AI can be particularly valuable for improving productivity, scrutinising data and interpreting complex regulatory requirements. Applications with greater autonomy or significant financial or customer consequences require more rigorous testing and stronger safeguards. The objective should not be to deploy the most advanced technology available, but to choose the solution best suited to the problem.</p><p><strong>Technology should strengthen expertise, not replace it.</strong> Making information and answers more accessible can support learning and collaboration across teams. However, employees must continue to develop the knowledge and judgement needed to challenge AI-generated outputs and recognise when results may be incomplete or incorrect. Effective adoption combines technological capability with human understanding.</p><p><strong>Effective oversight starts with asking the right questions.</strong> Boards and senior leaders do not need to become technical specialists, but they must understand the potential impact of AI, the scenarios in which systems could fail and the safeguards in place. Clear accountability, credible contingency plans and informed challenge are essential to maintaining effective governance.</p><p>Looking ahead, legacy infrastructure and fragmented systems remain significant barriers to progress. Modern tools can help connect information and improve reporting processes, but sustained investment in underlying technology and data capabilities is still required. As lending, payments and other financial activities become faster and increasingly real-time, regulatory reporting and risk management will also need to become more responsive.</p><p>Ultimately, <strong>successful technology adoption is about combining innovation with control.</strong> By choosing the right tools, strengthening data foundations and embedding effective governance, financial institutions can turn efficiency gains into better decisions and stronger risk management. The goal is not simply to automate more, but to ensure that technology delivers reliable, measurable value while preserving the expertise and accountability on which the industry depends.<br><br>Panellists:</p><ul><li>Oliver Margetts, Chief Technology Officer, Suade (Moderator)</li><li>Zachary Anderson, Chief Data &amp; Analytics Officer, Global Banking &amp; Payments, JP Morgan</li><li>Jonathan Taylor, Head of Quantitative Analysis &amp; Model Risk Management, PRA, Bank of England</li><li>Nick Wilson, Liquidity Reporting Senior Manager, Lloyds</li></ul><p><em>This summary captures key themes from the discussion. Individual contributions have not been attributed to participants, in accordance with the Chatham House Rule.</em></p>]]></content:encoded></item><item><title><![CDATA[RegTech Forum 2026 - Panel: Living in a world of constant regulatory change]]></title><description><![CDATA[<p>As financial institutions navigate an increasingly complex regulatory environment, adapting to evolving requirements across jurisdictions remains a significant challenge. The <em>Living in a World of Constant Regulatory Change</em> panel explored how firms can manage regulatory divergence, strengthen data governance and modernise reporting processes while balancing compliance obligations with operational efficiency</p>]]></description><link>https://suade.org/living-in-a-world-of-constant-regulatory-change/</link><guid isPermaLink="false">6acf3bde84bb68095b84efb3</guid><category><![CDATA[Insights]]></category><dc:creator><![CDATA[Bernice Nkoy]]></dc:creator><pubDate>Tue, 13 Oct 2026 11:09:00 GMT</pubDate><media:content url="https://suade.org/content/images/2026/10/ShapeVideo_RS1_3115_VS4.jpg" medium="image"/><content:encoded><![CDATA[<img src="https://suade.org/content/images/2026/10/ShapeVideo_RS1_3115_VS4.jpg" alt="RegTech Forum 2026 - Panel: Living in a world of constant regulatory change"><p>As financial institutions navigate an increasingly complex regulatory environment, adapting to evolving requirements across jurisdictions remains a significant challenge. The <em>Living in a World of Constant Regulatory Change</em> panel explored how firms can manage regulatory divergence, strengthen data governance and modernise reporting processes while balancing compliance obligations with operational efficiency and commercial priorities.</p><p><strong>International alignment must account for local differences.</strong> Global regulatory standards provide a common foundation, but differences in legislation, market structures and domestic priorities mean that requirements are not always implemented consistently. Firms operating across multiple jurisdictions must understand these local nuances and ensure their reporting frameworks can accommodate different interpretations and obligations.</p><p><strong>Strong data governance is fundamental to consistent reporting.</strong> Clear data definitions, standardised data dictionaries and traceable data lineage help ensure information can be interpreted accurately across jurisdictions and reporting requirements. As regulatory expectations evolve, firms need robust data foundations to maintain consistency, accuracy and confidence in their submissions.</p><p><strong>Proportionality and simplicity must deliver practical benefits.</strong> Simplifying regulatory requirements can reduce unnecessary reporting burdens, but frameworks must reflect the size, complexity and risk profiles of individual firms. Similarly, more granular rules can improve risk sensitivity, yet introduce additional operational complexity. Effective regulation must strike a balance between meaningful oversight and manageable implementation.</p><p><strong>Granular reporting increases the importance of data quality and accountability.</strong> As regulators request more detailed information, firms need stronger reconciliation processes to connect granular submissions with existing regulatory returns, investigate discrepancies and explain reported figures. Clear ownership, senior oversight and effective governance are essential to maintaining accuracy and accountability as reporting obligations expand.</p><p><strong>Successful implementation depends on communication and collaboration.</strong> Translating complex regulatory requirements into practical business language is critical to ensuring teams understand what needs to change and why. Training and collaboration across regulatory, risk, technology and customer-facing functions can help embed new requirements effectively. Ongoing dialogue between firms and regulators is equally important, enabling unintended consequences to be identified and helping ensure policy remains workable in practice.</p><p><strong>Automation can help firms manage growing reporting demands.</strong> Modernising legacy systems and automating manual submissions offers opportunities to reduce repetitive work, improve efficiency and free up resources for higher-value activities. However, firms must also maintain the flexibility and expertise needed to respond to changing requirements without compromising data quality or control.</p><p>Ultimately, <strong>managing constant regulatory change requires adaptability, forward planning and a strong data foundation.</strong> By investing in flexible reporting systems, clear accountability and effective collaboration, financial institutions can respond more effectively to evolving regulatory expectations across jurisdictions. The challenge is not simply to keep pace with new rules, but to implement them in a way that supports accurate reporting, proportionate compliance and sustainable business outcomes.</p><p><br>Panellists:</p><ul><li>Max Gerard, Solutions Consultant, Suade (Moderator)</li><li>Ian Warren, Chief Financial Officer, iFast</li><li>Tamiko Bayliss, Head of Banking Capital Policy, Bank of England</li><li>Judy Zhu, Head of Regulatory Reporting; Bank of China</li><li>Jina Kim, Head of Financial &amp; Regulatory Reporting, Redwood Bank</li></ul><p><em>This summary captures key themes from the discussion. Individual contributions have not been attributed to participants, in accordance with the Chatham House Rule.</em></p>]]></content:encoded></item><item><title><![CDATA[RegTech Forum 2026 - Panel: Building trust in AI]]></title><description><![CDATA[<p>As artificial intelligence becomes increasingly embedded in financial services, building trust in its use is essential. The <em>Building Trust in AI</em> panel explored how organisations can realise the benefits of AI while ensuring its deployment remains safe, responsible and reliable. The discussion highlighted the importance of strong governance, high-quality data</p>]]></description><link>https://suade.org/building-trust-in-ai/</link><guid isPermaLink="false">6acf3b5a84bb68095b84efaa</guid><category><![CDATA[Insights]]></category><dc:creator><![CDATA[Bernice Nkoy]]></dc:creator><pubDate>Tue, 13 Oct 2026 10:52:00 GMT</pubDate><media:content url="https://suade.org/content/images/2026/10/ShapeVideo_RS1_2984_VS4.jpg" medium="image"/><content:encoded><![CDATA[<img src="https://suade.org/content/images/2026/10/ShapeVideo_RS1_2984_VS4.jpg" alt="RegTech Forum 2026 - Panel: Building trust in AI"><p>As artificial intelligence becomes increasingly embedded in financial services, building trust in its use is essential. The <em>Building Trust in AI</em> panel explored how organisations can realise the benefits of AI while ensuring its deployment remains safe, responsible and reliable. The discussion highlighted the importance of strong governance, high-quality data and clear accountability in managing the risks associated with increasingly capable AI systems.</p><p><strong>Strong governance is the foundation of trust.</strong> Organisations need clear accountability, effective oversight and robust controls to ensure AI is deployed responsibly. These safeguards should be integrated into existing risk management frameworks, taking into account potential challenges such as bias, data privacy, security and operational resilience.</p><p><strong>Reliable AI depends on reliable data.</strong> The quality of AI-generated outputs is directly linked to the accuracy of the underlying data, the clarity of data lineage and the explainability of the processes involved. While AI can deliver significant efficiencies, speed must not come at the expense of accuracy, transparency or trust.</p><p><strong>Controls must reflect the level of risk.</strong> Not all AI applications carry the same potential impact. Organisations should adopt a proportionate approach to governance, validation and monitoring, applying more rigorous safeguards where AI decisions could have significant business or customer consequences.</p><p><strong>Trust requires continuous monitoring.</strong> As AI systems evolve and become more widely accessible, organisations must maintain visibility over how they are used and regularly assess emerging risks. Ongoing monitoring is essential to ensure controls remain effective and that AI continues to operate within appropriate boundaries.</p><p><strong>Human accountability cannot be delegated to AI.</strong> Although AI can support decision-making and improve operational efficiency, organisations must retain responsibility for its outcomes. Decisions and outputs should remain open to scrutiny, challenge and explanation, with appropriate human oversight in place.</p><p>Ultimately, <strong>responsible AI adoption requires a balance between innovation and control.</strong> Financial institutions have opportunities to use AI to improve efficiency and customer outcomes, but realising this potential depends on understanding its limitations and maintaining appropriate safeguards. By prioritising strong governance, reliable data and human accountability, organisations can build the trust needed to adopt AI responsibly and sustainably. The <em>Building Trust in AI</em> panel explored how organisations can realise the benefits of AI while ensuring its deployment remains safe, responsible and reliable. The discussion highlighted the importance of strong governance, high-quality data and clear accountability in managing the risks associated with increasingly capable AI systems.</p><p><strong>Strong governance is the foundation of trust.</strong> Organisations need clear accountability, effective oversight and robust controls to ensure AI is deployed responsibly. These safeguards should be integrated into existing risk management frameworks, taking into account potential challenges such as bias, data privacy, security and operational resilience.</p><p><strong>Reliable AI depends on reliable data.</strong> The quality of AI-generated outputs is directly linked to the accuracy of the underlying data, the clarity of data lineage and the explainability of the processes involved. While AI can deliver significant efficiencies, speed must not come at the expense of accuracy, transparency or trust.</p><p><strong>Controls must reflect the level of risk.</strong> Not all AI applications carry the same potential impact. Organisations should adopt a proportionate approach to governance, validation and monitoring, applying more rigorous safeguards where AI decisions could have significant business or customer consequences.</p><p><strong>Trust requires continuous monitoring.</strong> As AI systems evolve and become more widely accessible, organisations must maintain visibility over how they are used and regularly assess emerging risks. Ongoing monitoring is essential to ensure controls remain effective and that AI continues to operate within appropriate boundaries.</p><p><strong>Human accountability cannot be delegated to AI.</strong> Although AI can support decision-making and improve operational efficiency, organisations must retain responsibility for its outcomes. Decisions and outputs should remain open to scrutiny, challenge and explanation, with appropriate human oversight in place.</p><p>Ultimately, <strong>responsible AI adoption requires a balance between innovation and control.</strong> Financial institutions have opportunities to use AI to improve efficiency and customer outcomes, but realising this potential depends on understanding its limitations and maintaining appropriate safeguards. By prioritising strong governance, reliable data and human accountability, organisations can build the trust needed to adopt AI responsibly and sustainably.<br><br>Panellists:</p><ul><li>Murat Abur, Co-founder &amp; CIO, Suade (Moderator)</li><li>Gaetano Chionsini, Head of Statistics, European Banking Authority</li><li>Vicki Jordan, Policy Manager - AI, Remuneration, and Policy Profession, Financial Conduct Authority</li><li>Nick Talbot, Head of Climate &amp; Nature Risk; Head of AI Risk Framework Programme at NatWest</li></ul><p><em>This summary captures key themes from the discussion. Individual contributions have not been attributed to participants, in accordance with the Chatham House Rule.</em></p>]]></content:encoded></item><item><title><![CDATA[Thresholds on autopilot: what the PRA's CP13/26 means for regulatory reporting]]></title><description><![CDATA[<p>On the 7th October 2026, the PRA published Consultation Paper 13/26 (CP13/26), &quot;Updating regulatory thresholds: An autopilot approach&quot;. It proposes that 128 thresholds across banking, insurance and credit unions are updated automatically, in line with UK nominal GDP, every five years.</p><p>The day before, Federal Reserve</p>]]></description><link>https://suade.org/pras-cp13-26/</link><guid isPermaLink="false">6acf3f7484bb68095b84efcf</guid><category><![CDATA[Insights]]></category><dc:creator><![CDATA[Bernice Nkoy]]></dc:creator><pubDate>Tue, 13 Oct 2026 10:00:00 GMT</pubDate><content:encoded><![CDATA[<p>On the 7th October 2026, the PRA published Consultation Paper 13/26 (CP13/26), &quot;Updating regulatory thresholds: An autopilot approach&quot;. It proposes that 128 thresholds across banking, insurance and credit unions are updated automatically, in line with UK nominal GDP, every five years.</p><p>The day before, Federal Reserve Vice Chair for Supervision Michelle Bowman set out a similar direction for US bank regulation. The two announcements differ in detail and in maturity, but the design is the same: fixed thresholds, indexed to economic growth, refreshed every five years.</p><h2 id="why-thresholds-matter">Why thresholds matter</h2><p>Thresholds determine which rules apply to a firm, how they apply, and what the firm is required to report. Most are fixed nominal figures set at a point in time. As the economy grows, firms move towards and across them without any change in their risk profile. Until now, the fix has been a manual, ad hoc change to the rules.</p><p>Bowman made the same point in her speech, citing Regulation O, which governs lending to bank insiders and has not been comprehensively updated since 1979, and the $10 billion community bank definition, which has stood for around 15 years.</p><h2 id="what-the-pra-proposes">What the PRA proposes</h2><p>1.&#xA0;<strong>Indexation metric.</strong> UK nominal GDP, published by the ONS. The PRA chose it because it captures both price changes and real economic growth, which CPI or real GDP alone would not.</p><p>2.&#xA0;<strong>Frequency and timing.</strong> The first update takes effect on 1 July 2031, then every five years. The PRA&apos;s worked illustration retains unrounded values, with changes taking effect in July of the second calendar year after the reference year.</p><p>3.&#xA0;<strong>Implementation.</strong> The CP includes draft PRA Rulebook changes, a draft indexation statement of policy and the lists of in-scope thresholds. The PRA intends to implement the framework before the first update.</p><p>4.&#xA0;<strong>Cost-benefit.</strong> The PRA&apos;s analysis compares five-yearly automatic indexation with a baseline of manual indexation every ten years.</p><p>The consultation closes on 7 February 2027.</p><h2 id="what-bowman-announced">What Bowman announced</h2><p>Speaking at the 2026 Community Banking Research Conference in St. Louis on the 6th October, Bowman said:</p><p>&#x2022;&#xA0;&#xA0;The Board will consider, later this year, updates to the fixed-dollar asset thresholds in its regulations to account for inflation and economic growth.</p><p>&#x2022;&#xA0;&#xA0;The proposal will increase static thresholds, with a mechanism to update them every five years.</p><p>&#x2022;&#xA0;&#xA0;Broader structural reforms to bank portfolios defined by asset size, and updates to the large bank tailoring framework, will follow later this year.</p><p>The speech does not name an index or list the thresholds in scope. Those details will come with the Board&apos;s proposal. It also sits alongside the Regulation O proposal issued in July 2026 and the FFIEC&apos;s December 2025 request for information on streamlining the call report.</p><h2 id="what-this-means-for-regulatory-reporting">What this means for regulatory reporting</h2><p>In a reporting environment, a threshold is an input. Where it decides whether a return applies, or at what level of detail, a change to the threshold changes the scope of what a firm submits.</p><p>1.&#xA0;<strong>Thresholds become dated parameters.</strong> The value in force depends on the reference date and the indexation methodology. Firms need to show which value applied to which submission.</p><p>2.&#xA0;<strong>Scope needs re-testing at each update.</strong> Firms close to a threshold should model where an update leaves them, and which returns that affects.</p><p>3.&#xA0;<strong>Two jurisdictions, two cycles.</strong> Banks reporting in both the UK and the US will manage indexed thresholds with different metrics, dates and scope.</p><p>4.&#xA0;<strong>Hard-coded values become a maintenance burden.</strong> A threshold held in a spreadsheet or buried in report logic has to be found and changed by hand every time it moves.</p><h2 id="how-suade-approaches-this">How Suade approaches this</h2><p>Suade separates regulatory logic from a firm&apos;s own data. Firm data is mapped once into FIRE, our open-source Financial Regulatory data standard, and regulatory rules and calculations are applied on top of it. When a threshold or rule changes, it is updated once in the regulatory content and applied across the reports it affects, rather than being rebuilt in each firm&apos;s reporting process.</p><p>Because every figure is traceable back to its source data, firms can evidence which threshold applied to which submission, and why. We will track CP13/26 and the Fed&apos;s forthcoming proposal as they develop, and cover them in our Regulatory Updates.</p><p>To discuss how threshold changes could affect your reporting scope, <a href="https://suade.org/book-a-demo/">book a demo with our team</a>.</p><h2 id="key-dates">Key dates</h2>
<!--kg-card-begin: html-->
<table class="MsoTableGrid" border="1" cellspacing="0" cellpadding="0" style="border-collapse:collapse;mso-table-layout-alt:fixed;border:none;
 mso-border-alt:solid windowtext .5pt;mso-yfti-tbllook:1056;mso-padding-alt:
 0cm 5.4pt 0cm 5.4pt">
 <thead>
  <tr style="mso-yfti-irow:0;mso-yfti-firstrow:yes">
   <td width="312" valign="top" style="width:234.0pt;border:solid windowtext 1.0pt;
   mso-border-alt:solid windowtext .5pt;background:#F2F2F2;padding:0cm 5.4pt 0cm 5.4pt">
   <p class="MsoNormal"><span lang="EN-US" style="color:black;mso-color-alt:windowtext">Date</span><span lang="EN-US"><o:p></o:p></span></p>
   </td>
   <td width="312" valign="top" style="width:234.0pt;border:solid windowtext 1.0pt;
   border-left:none;mso-border-left-alt:solid windowtext .5pt;mso-border-alt:
   solid windowtext .5pt;background:#F2F2F2;padding:0cm 5.4pt 0cm 5.4pt">
   <p class="MsoNormal"><span lang="EN-US" style="color:black;mso-color-alt:windowtext">Event</span><span lang="EN-US"><o:p></o:p></span></p>
   </td>
  </tr>
 </thead>
 <tbody><tr style="mso-yfti-irow:1">
  <td width="312" valign="top" style="width:234.0pt;border:solid windowtext 1.0pt;
  border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt;
  padding:0cm 5.4pt 0cm 5.4pt">
  <p class="MsoNormal"><span lang="EN-US">7 October 2026<o:p></o:p></span></p>
  </td>
  <td width="312" valign="top" style="width:234.0pt;border-top:none;border-left:
  none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt;
  mso-border-alt:solid windowtext .5pt;padding:0cm 5.4pt 0cm 5.4pt">
  <p class="MsoNormal"><span lang="EN-US">CP13/26 published, consultation opens<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style="mso-yfti-irow:2">
  <td width="312" valign="top" style="width:234.0pt;border:solid windowtext 1.0pt;
  border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt;
  padding:0cm 5.4pt 0cm 5.4pt">
  <p class="MsoNormal"><span lang="EN-US">Later in 2026<o:p></o:p></span></p>
  </td>
  <td width="312" valign="top" style="width:234.0pt;border-top:none;border-left:
  none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt;
  mso-border-alt:solid windowtext .5pt;padding:0cm 5.4pt 0cm 5.4pt">
  <p class="MsoNormal"><span lang="EN-US">Federal Reserve Board expected to
  consider its threshold proposal<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style="mso-yfti-irow:3">
  <td width="312" valign="top" style="width:234.0pt;border:solid windowtext 1.0pt;
  border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt;
  padding:0cm 5.4pt 0cm 5.4pt">
  <p class="MsoNormal"><span lang="EN-US">7 February 2027<o:p></o:p></span></p>
  </td>
  <td width="312" valign="top" style="width:234.0pt;border-top:none;border-left:
  none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt;
  mso-border-alt:solid windowtext .5pt;padding:0cm 5.4pt 0cm 5.4pt">
  <p class="MsoNormal"><span lang="EN-US">CP13/26 consultation closes<o:p></o:p></span></p>
  </td>
 </tr>
 <tr style="mso-yfti-irow:4;mso-yfti-lastrow:yes">
  <td width="312" valign="top" style="width:234.0pt;border:solid windowtext 1.0pt;
  border-top:none;mso-border-top-alt:solid windowtext .5pt;mso-border-alt:solid windowtext .5pt;
  padding:0cm 5.4pt 0cm 5.4pt">
  <p class="MsoNormal"><span lang="EN-US">1 July 2031<o:p></o:p></span></p>
  </td>
  <td width="312" valign="top" style="width:234.0pt;border-top:none;border-left:
  none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  mso-border-top-alt:solid windowtext .5pt;mso-border-left-alt:solid windowtext .5pt;
  mso-border-alt:solid windowtext .5pt;padding:0cm 5.4pt 0cm 5.4pt">
  <p class="MsoNormal"><span lang="EN-US">First proposed automatic PRA update, then
  every five years<o:p></o:p></span></p>
  </td>
 </tr>
</tbody></table>
<!--kg-card-end: html-->
<h2 id="sources">Sources</h2><p>&#x2022;&#xA0;<a href="https://www.bankofengland.co.uk/prudential-regulation/publication/2026/october/updating-regulatory-thresholds-consultation-paper?ref=suade.org">CP13/26: Updating regulatory thresholds: An autopilot approach</a>, PRA, 7 October 2026</p><p>&#x2022;&#xA0;<a href="https://www.bankofengland.co.uk/news/2026/october/regulatory-thresholds-set-to-shift-to-automatic-increases?ref=suade.org">Regulatory thresholds set to shift to automatic increases</a>, Bank of England news release, 7 October 2026</p><p>&#x2022;&#xA0;<a href="https://www.federalreserve.gov/newsevents/speech/bowman20261006a.htm">Modernizing the Regulatory and Supervisory Landscape</a>, speech by Vice Chair for Supervision Bowman, 6 October 2026</p>]]></content:encoded></item><item><title><![CDATA[UK & EU Reg Roundup 28/09/26]]></title><description><![CDATA[<p><strong>The EBA consults on revised technical standards for joint decisions on institution-specific capital and liquidity requirements</strong></p><p>25 September 2026</p><p>The EBA has launched a consultation on revised technical standards for<em> </em><a href="https://www.eba.europa.eu/publications-and-media/press-releases/eba-consults-revised-technical-standards-joint-decisions-institution-specific-capital-and-liquidity?ref=suade.org"><em><strong>institution-specific capital and liquidity requirements</strong>,</em></a> aiming to simplify the joint decision process and align it with current supervisory practices.<br><br><strong>Key</strong></p>]]></description><link>https://suade.org/eu-uk-ca-reg-roundup-10-09-26/</link><guid isPermaLink="false">6abb99bb84bb68095b84eea4</guid><category><![CDATA[Regulatory Updates]]></category><category><![CDATA[🇪🇺]]></category><dc:creator><![CDATA[Bernice Nkoy]]></dc:creator><pubDate>Tue, 29 Sep 2026 11:00:36 GMT</pubDate><content:encoded><![CDATA[<p><strong>The EBA consults on revised technical standards for joint decisions on institution-specific capital and liquidity requirements</strong></p><p>25 September 2026</p><p>The EBA has launched a consultation on revised technical standards for<em> </em><a href="https://www.eba.europa.eu/publications-and-media/press-releases/eba-consults-revised-technical-standards-joint-decisions-institution-specific-capital-and-liquidity?ref=suade.org"><em><strong>institution-specific capital and liquidity requirements</strong>,</em></a> aiming to simplify the joint decision process and align it with current supervisory practices.<br><br><strong>Key Changes</strong></p><ul><li><strong>Simplified process:</strong> Introduces a single, more streamlined risk assessment report.</li><li><strong>SREP alignment:</strong> Updates the process to reflect the revised SREP framework and supervisory practices.</li><li><strong>Broader scope:</strong> Includes <strong>Pillar 2 Guidance</strong> and leverage ratio-related requirements and guidance.</li><li><strong>Supervisory measures:</strong> Better incorporates qualitative supervisory measures into joint decisions.</li><li><strong>Greater consistency:</strong> Aims to improve coordination and consistency in supervisory assessments.</li></ul><p><strong>Key Dates</strong></p><ul><li><strong>Consultation deadline:</strong> 4 January 2027</li><li><strong>Public hearing:</strong> 10 November 2026</li><li><a href="https://www.eba.europa.eu/sites/default/files/2026-09/65dc7659-0fc5-4ec3-99ae-0baf47dd5671/Consultation%20Paper%20on%20revised%20ITS%20on%20conditions%20of%20application%20of%20the%20joint%20decision%20process%20for%20institution-specific%20prudential%20requirements.pdf?ref=suade.org"><strong><em>CP ON DRAFT ITS ON THE JOINT DECISION PROCESS FOR INSTITUTION-SPECIFIC PRUDENTIAL REQUIREMENTS</em></strong></a></li><li><a href="https://www.eba.europa.eu/sites/default/files/2026-09/aabaf235-3595-424f-8ca1-35d7d451dd62/Revised%20ITS%20on%20joint%20Decisions%20EU%20No%20710-2014%20Annex.pdf?ref=suade.org"><strong><em>Revised ITS on joint Decisions EU No 710-2014 Annex.</em></strong></a></li></ul><p></p><p><strong>The EBA identifies priorities for the review of MiCA</strong></p><p>24 September 2026</p><p>The EBA has outlined key areas for strengthening and clarifying the<a href="https://www.eba.europa.eu/publications-and-media/press-releases/eba-identifies-priorities-review-mica?ref=suade.org"> <strong><em>Markets in Crypto-assets Regulation (MiCA)</em></strong></a> to keep the framework proportionate, consistent and responsive to the rapidly evolving crypto-asset sector.</p><p><strong>Key Changes</strong></p><ul><li><strong>Stablecoins:</strong> Strengthen rules for third-country multi-issuer schemes and review reserve requirements.</li><li><strong>Scope and definitions:</strong> Clarify the classification of crypto-assets to reduce uncertainty, costs and delays.</li><li><strong>Crypto-asset lending:</strong> Consider bringing crypto lending, including <strong>DeFi-related activities</strong>, within the regulatory framework.</li><li><strong>Reporting:</strong> Review reporting requirements for issuers and crypto-asset service providers to improve supervision and risk monitoring.</li><li><a href="https://www.eba.europa.eu/sites/default/files/2026-09/12cb4f01-0d51-46bf-a561-165ac486698f/EBA%20response%20to%20EC%20targeted%20consultation%20on%20MiCA%20review.pdf?ref=suade.org"><strong><em>EBA response to EC targeted consultation on MiCA review</em></strong></a></li></ul><p><br><strong>The EBA publishes its final Guidelines on the management of third-party risk, delivering a more proportionate and consistent framework aligned with DORA</strong></p><p>18 September 2026</p><p>The EBA has <a href="https://www.eba.europa.eu/publications-and-media/press-releases/eba-publishes-its-final-guidelines-management-third-party-risk-delivering-more-proportionate-and?ref=suade.org"><strong><em>published its final Guidelines on managing third-party risk</em></strong></a><em>,</em> introducing a more proportionate and consistent framework aligned with <strong>DORA</strong>. The Guidelines focus primarily on third-party arrangements supporting <strong>critical or important functions (CIFs)</strong>, reducing unnecessary requirements for lower-risk arrangements while maintaining effective risk management.</p><p><strong>Key Changes</strong></p><ul><li><strong>Risk-based approach:</strong> Greater focus on third-party arrangements supporting CIFs.</li><li><strong>Full lifecycle coverage:</strong> Includes due diligence, contracts, subcontracting, monitoring, documentation and exit strategies.</li><li><strong>ICT and non-ICT services:</strong> Applies a holistic approach across both types of third-party arrangements.</li><li><strong>Alignment:</strong> Takes account of DORA and international standards, including <strong>BCBS principles</strong>.</li><li><strong>Implementation:</strong> A <strong>two-year transitional period</strong> will allow firms to implement the Guidelines proportionately.</li></ul><p><br><strong>The EBA publishes updated list of validation rules as part of its regular quarterly reporting frameworks update</strong></p><p>14 September 2026</p><p>The European Banking Authority (EBA) has <a href="https://www.eba.europa.eu/publications-and-media/press-releases/eba-publishes-updated-list-validation-rules-part-its-regular-quarterly-reporting-frameworks-update?ref=suade.org"><strong><em>published</em></strong></a> its quarterly update to the validation rules, with changes aimed at improving the accuracy and consistency of regulatory reporting.</p><p><strong>Key Changes</strong></p><ul><li><strong>Validation rules:</strong> Some rules have been deactivated due to inaccuracies or IT issues, while others have been reactivated.</li><li><strong>Release 4.0:</strong> New taxonomy and DPM update packages have been introduced.</li><li><strong>DPM 2.0:</strong> Validation rules are now embedded directly in the taxonomy and DPM, improving consistency and traceability.</li></ul><p><a href="https://www.eba.europa.eu/risk-and-data-analysis/reporting/reporting-frameworks/validation-rules-packages?ref=suade.org"><strong><em>Validation rules packages</em></strong></a></p><p><strong>Bank of England&#xA0;</strong></p><p></p><p><strong>Statistical Notice 2026/08 - Changes to the criteria for monthly form BT reporting</strong></p><p>15 September 2026</p><p>The Bank of England has revised the criteria for determining which firms must submit <a href="https://www.bankofengland.co.uk/statistics/notice/2026/statistical-notice-2026-08?ref=suade.org"><strong><em>Form BT monthly</em></strong></a>, with the aim of keeping reporting requirements proportionate while maintaining statistical quality.</p><p><strong>Key Changes</strong></p><ul><li><strong>Monthly reporting:</strong> Firms required to submit <strong>BE, BN, GT or ER</strong> returns will generally also submit Form BT monthly.</li><li><strong>Quarterly reporting:</strong> Firms not submitting any of these returns will generally submit Form BT quarterly.</li><li><strong>Discretionary requirement:</strong> The Bank may still require individual firms to report Form BT monthly.</li><li><strong>Affected firms:</strong> The Bank will contact firms directly where their reporting frequency changes.</li></ul><p><br><strong>European Securities and Markets AuthorityESMA sets 2027 priorities for stronger, simpler and more integrated EU capital markets</strong></p><p>28 September 2026</p><p><a href="https://www.esma.europa.eu/press-news/esma-news/esma-sets-2027-priorities-stronger-simpler-and-more-integrated-eu-capital?ref=suade.org"><strong><em>ESMA has published its 2027 Work Programme</em></strong></a>, focusing on strengthening and simplifying<strong> EU capital markets</strong> while moving several major regulatory and supervisory initiatives into the delivery phase.<strong>Key Changes</strong></p><ul><li><strong>Supervision:</strong> Expanded oversight of<strong> ESG ratings,</strong> benchmarks, consolidated tape providers, EU Green Bonds and critical ICT third-party providers.</li><li><strong>Market resilience:</strong> Review of <strong>EMIR 3</strong> and continued work on stronger EU clearing markets.</li><li><strong>Simplification:</strong> Further work to reduce reporting and supervisory burdens, including transaction and funds reporting.</li><li><strong>Digital transformation:</strong> Development of ESMA&#x2019;s <strong>Data Platform</strong> and greater use of AI and technology in supervision.</li><li><strong>Capital market integration:</strong> Implementation of initiatives such as the European Single Access Point and transition to T+1 settlement.</li><li><strong>Crypto and innovation:</strong> Continued work on <strong>MiCA, crypto-assets, tokenisation and AI-related risks</strong>.</li></ul><p><strong>Key Takeaway</strong>ESMA&#x2019;s 2027 priorities combine <strong>regulatory simplification, stronger supervision and greater use of technology</strong>, while supporting more integrated and resilient EU capital markets.</p>]]></content:encoded></item><item><title><![CDATA[EU, UK & CA Reg Roundup 10/09/26]]></title><description><![CDATA[<p><strong>European Banking Authority</strong></p><p><strong>The EBA consults on draft technical standards on institutions&#x2019; operational risk management</strong></p><p>26 August 2026</p><p>The European Banking Authority (EBA) has launched a consultation on draft Regulatory Technical Standards (RTS) specifying the operational risk management framework institutions must maintain under Article 323 of the Capital Requirements</p>]]></description><link>https://suade.org/eu-uk-ca-reg-roundup-25-08-26/</link><guid isPermaLink="false">6aa976f284bb68095b84ee2a</guid><category><![CDATA[Regulatory Updates]]></category><category><![CDATA[🇪🇺]]></category><dc:creator><![CDATA[Bernice Nkoy]]></dc:creator><pubDate>Tue, 15 Sep 2026 16:53:20 GMT</pubDate><content:encoded><![CDATA[<p><strong>European Banking Authority</strong></p><p><strong>The EBA consults on draft technical standards on institutions&#x2019; operational risk management</strong></p><p>26 August 2026</p><p>The European Banking Authority (EBA) has launched a consultation on draft Regulatory Technical Standards (RTS) specifying the operational risk management framework institutions must maintain under Article 323 of the Capital Requirements Regulation (CRR), as amended by CRR3.</p><p>The proposals set out harmonised and proportionate requirements covering three key areas:</p><ol><li>governance arrangements;</li><li>the operational risk management process; and</li><li>the operational risk assessment system.</li></ol><p>The draft RTS clarify the responsibilities of management bodies, senior management and independent operational risk management functions. They also establish requirements for operational risk data and taxonomy, the business indicator component, reporting, validation and audit. ICT risk requirements are addressed through the Digital Operational Resilience Act (DORA).</p><p>Proportionality is a key feature of the proposals. Institutions with a business indicator below EUR 750 million would benefit from less frequent reviews and reporting, alongside simplified requirements concerning data granularity, loss thresholds and operational risk taxonomy.</p><p>The consultation is open until 31 December 2026. A virtual public hearing will take place on 29 September 2026, with registration closing on 25 September 2026. Following the consultation, the EBA will finalise the draft RTS and submit them to the European Commission for adoption.</p><p>Please find the whole consultation&#xA0;<a href="https://www.eba.europa.eu/publications-and-media/press-releases/eba-consults-draft-technical-standards-institutions-operational-risk-management?ref=suade.org"><u>here</u></a>.</p><p></p><p></p><p><strong>Bank of England</strong></p><p><strong>Andrew Bailey emphasises regulatory independence and accountability in safeguarding financial stability</strong></p><p>4 September 2026</p><p>Bank of England Governor Andrew Bailey delivered a speech at the LSE TRIUM Anniversary Conference examining central bank independence, including its importance for financial regulation and financial stability.</p><p>The speech highlighted two major themes relevant to banking regulation:</p><ol><li>Independence from industry and political pressure: Bailey argued that central banks must avoid becoming aligned with particular financial sectors or political movements. Protecting financial stability can require resisting pressure from concentrated financial interests, including calls arguing that regulation has gone too far.</li><li>The distributional effects of regulation: Bailey acknowledged that financial stability policies can affect institutions and sectors differently. He stressed that their purpose is not to favour particular groups, but to safeguard stable money and a resilient financial system for society as a whole.</li></ol><p>Please find the whole speech&#xA0;<a href="https://www.bankofengland.co.uk/speech/2026/september/andrew-bailey-keynote-speech-at-lse-trium-anniversary-conference?ref=suade.org"><u>here</u></a>.</p><p></p><p></p><p><strong>Office of the Superintendent of Financial Institutions</strong></p><p><strong>OSFI updates its policy release schedule</strong></p><p>3 September 2026</p><p>The Office of the Superintendent of Financial Institutions (OSFI) has published a letter to federally regulated financial institutions outlining changes to its planned policy releases and announcements, as set out in its spring Annual Risk Outlook.</p><p>The revised schedule covers three quarterly releases:</p><ol><li>10 September 2026: The draft Guideline B-6 Liquidity Principles is deferred to February 2027, while the final Pillar 3 Disclosures for Interest Rate Risk is deferred to November 2026.</li><li>19 November 2026: OSFI plans to publish the final Pillar 3 Disclosures for Interest Rate Risk, the final Guideline B-2 Large Exposure Limits for Property and Casualty and Life and Fraternal insurers, and the Credit Risk Management &#x201C;What We Heard&#x201D; consultation report. The draft chapters of the Credit Risk Management Guideline are deferred to February 2027.</li><li>12 February 2027: OSFI plans to publish the draft chapters of the Credit Risk Management Guideline and the draft Guideline B-6 Liquidity Principles.</li></ol><p>OSFI notes that publication timelines and planned releases remain subject to change in response to developments in financial institutions&#x2019; risk and operating environment. Updates will be reflected in its policy releases and announcements schedule.</p><p>Please find the whole letter&#xA0;<a href="https://www.osfi-bsif.gc.ca/en/guidance/guidance-library/letter-industry-updates-osfis-policy-plan?ref=suade.org"><u>here</u></a>.</p>]]></content:encoded></item><item><title><![CDATA[Your invitation to RegTech Forum 2026]]></title><description><![CDATA[<h3 id="tuesday-6th-october-from-1130am-guildhall-london"><strong>Tuesday 6th October | From 11:30am | Guildhall, London</strong></h3><h3 id="400-senior-leaders-25-high-profile-speakers-networking"><strong>400+ Senior Leaders | 25+ High Profile Speakers | Networking </strong></h3><p>We&#x2019;ve reserved a place for you at this year&#x2019;s RegTech Forum. We&#x2019;d be delighted to have you join us at Guildhall on 6 October.</p><p>This invitation gives you</p>]]></description><link>https://suade.org/regtech-forum-2026-ticket/</link><guid isPermaLink="false">6aa954ca84bb68095b84ee10</guid><dc:creator><![CDATA[Phoebe Regnault]]></dc:creator><pubDate>Tue, 15 Sep 2026 14:28:57 GMT</pubDate><media:content url="https://suade.org/content/images/2026/09/RTF-2026-email-banner--mailchimp-.svg" medium="image"/><content:encoded><![CDATA[<h3 id="tuesday-6th-october-from-1130am-guildhall-london"><strong>Tuesday 6th October | From 11:30am | Guildhall, London</strong></h3><h3 id="400-senior-leaders-25-high-profile-speakers-networking"><strong>400+ Senior Leaders | 25+ High Profile Speakers | Networking </strong></h3><img src="https://suade.org/content/images/2026/09/RTF-2026-email-banner--mailchimp-.svg" alt="Your invitation to RegTech Forum 2026"><p>We&#x2019;ve reserved a place for you at this year&#x2019;s RegTech Forum. We&#x2019;d be delighted to have you join us at Guildhall on 6 October.</p><p>This invitation gives you access to our 2026 RegTech Forum, bringing together senior leaders from across banking, regulation and technology.</p><p><strong>Please confirm your attendance below.</strong></p><h3 id="about">About</h3><p>A senior forum bringing together leaders from banking, regulation and technology to explore how regulatory reporting is evolving in practice, and what it takes to build scalable, data-driven and resilient reporting frameworks in an era of rapid change.</p><h3 id="key-themes">Key themes</h3><p>This year&#x2019;s forum will explore how regulatory reporting is evolving in practice, as banks respond to rapid advances in AI, increasing data complexity, and continued regulatory divergence across jurisdictions. Discussions will focus on how firms are operationalising change across data, technology, controls and capital frameworks.</p><h3 id="agenda"><strong>Agenda</strong></h3>
<!--kg-card-begin: html-->
<table class="agenda-table" style="margin: 0px; width: 1200.8px; border-radius: 16px; border-collapse: collapse; padding: 8px; background-color: rgb(255, 255, 255); border: none; vertical-align: top; table-layout: fixed !important; color: rgb(50, 50, 50); font-family: " ibm plex sans", sans-serif; font-size: medium; font-style: normal; font-variant-ligatures: font-variant-caps: font-weight: 400; letter-spacing: orphans: 2; text-align: start; text-transform: none; widows: word-spacing: 0px; -webkit-text-stroke-width: white-space: text-decoration-thickness: initial; text-decoration-style: text-decoration-color: initial;">

<thead>
<tr style="font-size: 20px; color: rgb(37, 76, 184); font-weight: bold; border-bottom: 0.8px solid rgb(37, 76, 184); padding-top: 24px;">
<th style="text-align: left; font-weight: bold; padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; border-radius: 16px; width: 80px !important;">Time</th>
<th style="text-align: left; font-weight: bold; padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; border-radius: 16px;">Session</th>
</tr>
</thead>

<tbody>

<tr style="border-bottom: 0.8px dotted rgb(229, 229, 229); vertical-align: top;">
<th class="time" style="text-align: left; font-weight: bold; padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; width: 80px !important; min-width: 80px !important; white-space: nowrap !important; border-radius: 16px;">11:30</th>
<td style="padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; border-radius: 16px;">Registration and networking lunch</td>
</tr>

<tr style="border-bottom: 0.8px dotted rgb(229, 229, 229); vertical-align: top;">
<th class="time" style="text-align: left; font-weight: bold; padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; width: 80px !important; min-width: 80px !important; white-space: nowrap !important; border-radius: 16px;">12:45</th>
<td class="session" style="padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; border-radius: 16px;"><b style="color: rgb(37, 76, 184);">Welcome from Diana Paredes, CEO of Suade</b></td>
</tr>

<tr style="border-bottom: 0.8px dotted rgb(229, 229, 229); vertical-align: top;">
<th class="time" style="text-align: left; font-weight: bold; padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; width: 80px !important; min-width: 80px !important; white-space: nowrap !important; border-radius: 16px;">12:50</th>
<td class="session" style="padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; border-radius: 16px;"><span>Opening keynote: </span><b style="color: rgb(37, 76, 184);">Shaping tomorrow - The UK&#x2019;s evolution in RegTech and collaborative innovation</b></td>
</tr>

<tr style="border-bottom: 0.8px dotted rgb(229, 229, 229); vertical-align: top;">
<th class="time" style="text-align: left; font-weight: bold; padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; width: 80px !important; min-width: 80px !important; white-space: nowrap !important; border-radius: 16px;">13:00</th>
<td class="session" style="padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; border-radius: 16px;"><span>Panel: </span><b style="color: rgb(37, 76, 184);">Building trusted data foundations for AI in regulatory reporting</b></td>
</tr>

<tr style="border-bottom: 0.8px dotted rgb(229, 229, 229); vertical-align: top;">
<th class="time" style="text-align: left; font-weight: bold; padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; width: 80px !important; min-width: 80px !important; white-space: nowrap !important; border-radius: 16px;">13:45</th>
<td style="padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; border-radius: 16px;">Networking break</td>
</tr>

<tr style="border-bottom: 0.8px dotted rgb(229, 229, 229); vertical-align: top;">
<th class="time" style="text-align: left; font-weight: bold; padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; width: 80px !important; min-width: 80px !important; white-space: nowrap !important; border-radius: 16px;">14:15</th>
<td class="session" style="padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; border-radius: 16px;"><span>Panel: </span><b style="color: rgb(37, 76, 184);">Living a world of regulatory divergence and proportionality</b></td>
</tr>

<tr style="border-bottom: 0.8px dotted rgb(229, 229, 229); vertical-align: top;">
<th class="time" style="text-align: left; font-weight: bold; padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; width: 80px !important; min-width: 80px !important; white-space: nowrap !important; border-radius: 16px;">15:00</th>
<td class="session" style="padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; border-radius: 16px;"><span>Fireside chat: </span><b style="color: rgb(37, 76, 184);">Getting the job done</b></td>
</tr>

<tr style="border-bottom: 0.8px dotted rgb(229, 229, 229); vertical-align: top;">
<th class="time" style="text-align: left; font-weight: bold; padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; width: 80px !important; min-width: 80px !important; white-space: nowrap !important; border-radius: 16px;">15:30</th>
<td class="session" style="padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; border-radius: 16px;"><span>Presentation: </span><b style="color: rgb(37, 76, 184);">What is the future of regulatory reporting?</b></td>
</tr>

<tr style="border-bottom: 0.8px dotted rgb(229, 229, 229); vertical-align: top;">
<th class="time" style="text-align: left; font-weight: bold; padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; width: 80px !important; min-width: 80px !important; white-space: nowrap !important; border-radius: 16px;">15:45</th>
<td style="padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; border-radius: 16px;">Networking break</td>
</tr>

<tr style="border-bottom: 0.8px dotted rgb(229, 229, 229); vertical-align: top;">
<th class="time" style="text-align: left; font-weight: bold; padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; width: 80px !important; min-width: 80px !important; white-space: nowrap !important; border-radius: 16px;">16:15</th>
<td class="session" style="padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; border-radius: 16px;"><span>Panel: </span><b style="color: rgb(37, 76, 184);">Staying future proof and being ready for Basel 3.1, FRTB, IReF and future regulatory changes</b></td>
</tr>

<tr style="border-bottom: 0.8px dotted rgb(229, 229, 229); vertical-align: top;">
<th class="time" style="text-align: left; font-weight: bold; padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; width: 80px !important; min-width: 80px !important; white-space: nowrap !important; border-radius: 16px;">17:00</th>
<td class="session" style="padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; border-radius: 16px;"><span>Panel: </span><b style="color: rgb(37, 76, 184);">Challenges of a global world</b></td>
</tr>

<tr style="border-bottom: 0.8px dotted rgb(229, 229, 229); vertical-align: top;">
<th class="time" style="text-align: left; font-weight: bold; padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; width: 80px !important; min-width: 80px !important; white-space: nowrap !important; border-radius: 16px;">17:45</th>
<td class="session" style="padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; border-radius: 16px;"><span>Closing keynote: </span><b style="color: rgb(37, 76, 184);">Simplifying regulatory reporting by design</b></td>
</tr>

<tr>
<th class="time" style="text-align: left; font-weight: bold; padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; width: 80px !important; min-width: 80px !important; white-space: nowrap !important; border-radius: 16px;">18:00</th>
<td style="padding: 8px 12px; vertical-align: middle !important; box-sizing: border-box !important; line-height: initial; border-radius: 16px;">Drinks &amp; canap&#xE9;s</td>
</tr>

</tbody>
</table>
<!--kg-card-end: html-->
<h3 id="confirm-your-place"><strong>Confirm your place:</strong></h3>
<!--kg-card-begin: html-->
<div style="max-width:640px; margin:0 auto; background:#e9f0ff; border:1px solid #dbe4ff; border-radius:8px; padding:22px; font-family: var(--first-font-type), sans-serif; color:#111827;"> <!-- Success message (hidden until submit succeeds) --><div id="successBox" style="display:none; margin-top:4px;"><h2 style="margin:0 0 18px; font-size:22px; font-weight:700;">Thank you for registering</h2><div style="border-left:4px solid #4d67e6; padding-left:12px; line-height:1.5;">We&#x2019;ve received your details and are reviewing your submission. We&#x2019;ll contact you shortly with the next steps.</div></div><form id="regForm" novalidate><h2 style="margin:0 0 18px; font-size:22px; font-weight:700;">Registration open</h2> <input type="hidden" id="field_12" value="701QB00000yRy43YAC"> <!-- Salesforce campaign --> <input type="hidden" id="field_13" value="Registered"> <!-- Salesforce Status --> <input type="hidden" id="field_17" value="Marketing - event registration"> <!-- Salesforce source --> <input type="hidden" id="field_14" value="Ghost"> <!-- WP post id used by WS Form --> <input type="hidden" id="field_15" value> <!-- Zoom webinar ID --> <!-- --> <!-- First / Last --><div style="display:flex; gap:16px; margin-bottom:14px; flex-wrap:wrap;"><div style="flex:1; min-width:220px;"> <label for="field_1" style="display:block; font-size:14px; margin:0 0 6px;">First name <span style="color:#dc2626;">*</span></label> <input id="field_1" required autocomplete="given-name" style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;"></div><div style="flex:1; min-width:220px;"> <label for="field_2" style="display:block; font-size:14px; margin:0 0 6px;">Last name <span style="color:#dc2626;">*</span></label> <input id="field_2" required autocomplete="family-name" style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;"></div></div> <!-- Title --><div style="margin-bottom:14px;"> <label for="field_8" style="display:block; font-size:14px; margin:0 0 6px;">Job title <span style="color:#dc2626;">*</span></label> <input id="field_8" required style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;"></div> <!-- Company --><div style="margin-bottom:14px;"> <label for="field_9" style="display:block; font-size:14px; margin:0 0 6px;">Company <span style="color:#dc2626;">*</span></label> <input id="field_9" required autocomplete="organization" style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;"></div> <!-- Email --><div style="margin-bottom:14px;"> <label for="field_3" style="display:block; font-size:14px; margin:0 0 6px;">Email <span style="color:#dc2626;">*</span></label> <input id="field_3" type="email" required autocomplete="email" inputmode="email" style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;"></div><div id="emailError" style="display:none; color:#b91c1c; font-size:13px; margin:0 0 10px 0;">Please enter a valid work email address.</div>  <!-- Message --><div id="messageContainer" style="margin-bottom:14px; display:none"> <label for="field_5" style>Message <span>*</span></label><textarea id="field_5" rows="6"></textarea></div><div style="margin-bottom:18px;"> <label for="field_10" style="display:block; font-size:14px; margin:0 0 6px;">Country <span style="color:#dc2626;">*</span></label> <select id="field_10" name="field_10[]" required autocomplete="country" style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;"><option value selected disabled>Select...</option><option value="AF">Afghanistan</option><option value="AL">Albania</option><option value="DZ">Algeria</option><option value="AD">Andorra</option><option value="AO">Angola</option><option value="AG">Antigua and Barbuda</option><option value="AR">Argentina</option><option value="AM">Armenia</option><option value="AU">Australia</option><option value="AT">Austria</option><option value="AZ">Azerbaijan</option><option value="BS">Bahamas</option><option value="BH">Bahrain</option><option value="BD">Bangladesh</option><option value="BB">Barbados</option><option value="BY">Belarus</option><option value="BE">Belgium</option><option value="BZ">Belize</option><option value="BJ">Benin</option><option value="BT">Bhutan</option><option value="BO">Bolivia</option><option value="BA">Bosnia and Herzegovina</option><option value="BW">Botswana</option><option value="BR">Brazil</option><option value="BN">Brunei</option><option value="BG">Bulgaria</option><option value="BF">Burkina Faso</option><option value="BI">Burundi</option><option value="CV">Cabo Verde</option><option value="KH">Cambodia</option><option value="CM">Cameroon</option><option value="CA">Canada</option><option value="CF">Central African Republic</option><option value="TD">Chad</option><option value="CL">Chile</option><option value="CN">China</option><option value="CO">Colombia</option><option value="KM">Comoros</option><option value="CG">Congo</option><option value="CD">Congo, Democratic Republic of the</option><option value="CR">Costa Rica</option><option value="CI">C&#xF4;te d&#x2019;Ivoire</option><option value="HR">Croatia</option><option value="CU">Cuba</option><option value="CY">Cyprus</option><option value="CZ">Czechia</option><option value="DK">Denmark</option><option value="DJ">Djibouti</option><option value="DM">Dominica</option><option value="DO">Dominican Republic</option><option value="EC">Ecuador</option><option value="EG">Egypt</option><option value="SV">El Salvador</option><option value="GQ">Equatorial Guinea</option><option value="ER">Eritrea</option><option value="EE">Estonia</option><option value="SZ">Eswatini</option><option value="ET">Ethiopia</option><option value="FJ">Fiji</option><option value="FI">Finland</option><option value="FR">France</option><option value="GA">Gabon</option><option value="GM">Gambia</option><option value="GE">Georgia</option><option value="DE">Germany</option><option value="GH">Ghana</option><option value="GI">Gibraltar</option><option value="GR">Greece</option><option value="GD">Grenada</option><option value="GT">Guatemala</option><option value="GN">Guinea</option><option value="GW">Guinea-Bissau</option><option value="GY">Guyana</option><option value="HT">Haiti</option><option value="HN">Honduras</option><option value="HK">Hong Kong</option><option value="HU">Hungary</option><option value="IS">Iceland</option><option value="IN">India</option><option value="ID">Indonesia</option><option value="IQ">Iraq</option><option value="IE">Ireland</option><option value="IM">Isle of Man</option><option value="IL">Israel</option><option value="IT">Italy</option><option value="JM">Jamaica</option><option value="JP">Japan</option><option value="JE">Jersey</option><option value="JO">Jordan</option><option value="KZ">Kazakhstan</option><option value="KE">Kenya</option><option value="KI">Kiribati</option><option value="KR">Korea</option><option value="KW">Kuwait</option><option value="KG">Kyrgyzstan</option><option value="LA">Laos</option><option value="LV">Latvia</option><option value="LB">Lebanon</option><option value="LS">Lesotho</option><option value="LR">Liberia</option><option value="LY">Libya</option><option value="LI">Liechtenstein</option><option value="LT">Lithuania</option><option value="LU">Luxembourg</option><option value="MG">Madagascar</option><option value="MW">Malawi</option><option value="MY">Malaysia</option><option value="MV">Maldives</option><option value="ML">Mali</option><option value="MT">Malta</option><option value="MR">Mauritania</option><option value="MU">Mauritius</option><option value="MX">Mexico</option><option value="FM">Micronesia (Federated States of)</option><option value="MD">Moldova</option><option value="MC">Monaco</option><option value="MN">Mongolia</option><option value="ME">Montenegro</option><option value="MA">Morocco</option><option value="MZ">Mozambique</option><option value="MM">Myanmar</option><option value="NA">Namibia</option><option value="NR">Nauru</option><option value="NP">Nepal</option><option value="NL">Netherlands</option><option value="NZ">New Zealand</option><option value="NI">Nicaragua</option><option value="NE">Niger</option><option value="NG">Nigeria</option><option value="MK">North Macedonia</option><option value="NO">Norway</option><option value="OM">Oman</option><option value="PK">Pakistan</option><option value="PW">Palau</option><option value="PA">Panama</option><option value="PG">Papua New Guinea</option><option value="PY">Paraguay</option><option value="PE">Peru</option><option value="PH">Philippines</option><option value="PL">Poland</option><option value="PT">Portugal</option><option value="QA">Qatar</option><option value="RO">Romania</option><option value="RU">Russian Federation</option><option value="RW">Rwanda</option><option value="KN">Saint Kitts and Nevis</option><option value="LC">Saint Lucia</option><option value="VC">Saint Vincent and the Grenadines</option><option value="WS">Samoa</option><option value="SM">San Marino</option><option value="ST">Sao Tome and Principe</option><option value="SA">Saudi Arabia</option><option value="SN">Senegal</option><option value="RS">Serbia</option><option value="SC">Seychelles</option><option value="SL">Sierra Leone</option><option value="SG">Singapore</option><option value="SK">Slovakia</option><option value="SI">Slovenia</option><option value="SB">Solomon Islands</option><option value="SO">Somalia</option><option value="ZA">South Africa</option><option value="SS">South Sudan</option><option value="ES">Spain</option><option value="LK">Sri Lanka</option><option value="SD">Sudan</option><option value="SR">Suriname</option><option value="SE">Sweden</option><option value="CH">Switzerland</option><option value="SY">Syria</option><option value="TW">Taiwan</option><option value="TJ">Tajikistan</option><option value="TZ">Tanzania</option><option value="TH">Thailand</option><option value="TL">Timor-Leste</option><option value="TG">Togo</option><option value="TO">Tonga</option><option value="TT">Trinidad and Tobago</option><option value="TN">Tunisia</option><option value="TR">Turkey (T&#xFC;rkiye)</option><option value="TM">Turkmenistan</option><option value="TV">Tuvalu</option><option value="UG">Uganda</option><option value="UA">Ukraine</option><option value="AE">United Arab Emirates</option><option value="GB">United Kingdom</option><option value="US">United States</option><option value="UY">Uruguay</option><option value="UZ">Uzbekistan</option><option value="VU">Vanuatu</option><option value="VE">Venezuela</option><option value="VN">Viet Nam</option><option value="YE">Yemen</option><option value="ZM">Zambia</option><option value="ZW">Zimbabwe</option> </select></div> <!-- Submit --> <button type="submit" style="font-family: IBM Plex Sans, sans-serif; width:100%; padding:12px 16px; border:0; border-radius:8px; background:#4d67e6; color:#fff; font-size:16px; font-weight:600; cursor:pointer;"> Submit </button> <input type="hidden" id="g-recaptcha-response" value><p>By submitting this form to Suade you hereby agree that any personal information you provide can be processed according to Suade&#x2019;s <a href="https://suade.org/privacy-policy/">Privacy policy</a>.</p></form><div id="status" style="margin-top:12px; font-size:14px;" aria-live="polite"></div> <script> (function () {
 console.log("script start");
 const messageContainer = document.getElementById("messageContainer");
 const messageField = document.getElementById("field_5"); 
 const emailInput = document.getElementById('field_3');
 const errEl = document.getElementById('emailError');
 // Base providers (compare against the "second-level" label like gmail, yahoo, outlook, etc.)
 const BLOCKED_SLD = new Set([
 'gmail',
 'yahoo',
 'hotmail',
 'live',
 'outlook',
 'aol',
 'msn',
 'icloud',
 'me',
 'mac',
 'btinternet',
 'talktalk',
 'virginmedia',
 'comcast',
 'verizon',
 'sky',
 ]);
 function baseLabel(host) {
 const parts = host.split('.').filter(Boolean);
 if (parts.length < 2) return host;
 const tld = parts[parts.length - 1];
 // ccTLD heuristic (e.g., .co.uk, .com.au)
 if (tld.length === 2 && parts.length >= 3) {
 return parts[parts.length - 3]; // label before .co.uk/.com.au
 }
 return parts[parts.length - 2];
 }
 function isPersonalEmail(email) {
 const m = String(email).toLowerCase().match(/^[^@\s]+@([^@\s]+)$/);
 if (!m) return false; // let type=email handle malformed addresses
 const host = m[1];
 const sld = baseLabel(host);
 return BLOCKED_SLD.has(sld);
 }
 function showWorkEmailError(show) {
 if (show) {
 emailInput.setCustomValidity('Please enter a valid work email address.');
 errEl.style.display = 'block';
 } else {
 emailInput.setCustomValidity('');
 errEl.style.display = 'none';
 }
 }
 function validateEmail() {
 const val = emailInput.value.trim();
 const block = val && isPersonalEmail(val);
 showWorkEmailError(block);
 return !block;
 }
 emailInput.addEventListener('input', validateEmail);
 emailInput.addEventListener('blur', validateEmail);  const ENDPOINT = 'https://harrya10.sg-host.com/wp-json/ws-form/v1/submit'; // remote WP site
 const $ = (id) => document.getElementById(id);
 function buildFormData(nonce) {
 const fd = new FormData();
 // Main fields (must match cURL exactly)
 fd.append('field_1',  $('field_1').value.trim());
 fd.append('field_2',  $('field_2').value.trim());
 fd.append('field_8',  $('field_8').value.trim());
 fd.append('field_9',  $('field_9').value.trim());
 fd.append('field_3',  $('field_3').value.trim());
 fd.append('field_5',  $('field_5').value.trim());
 fd.append('field_10[]', $('field_10').value); // ISO alpha-2
 // Hidden fields/constants
 fd.append('field_12', $('field_12').value);
 fd.append('field_13', $('field_13').value);
 fd.append('field_17', $('field_17').value);
 fd.append('field_15', $('field_15').value);
 fd.append('field_14', $('field_14').value);
 // reCAPTCHA token (optional but often required on receiver)
 // fd.append('g-recaptcha-response', $('g-recaptcha-response').value || '');
 // WS Form meta (match cURL)
 fd.append('wsf_form_id', '1');
 fd.append('wsf_hash', '');
 fd.append('wsf_nonce', nonce);
 fd.append('wsf_post_id', $('field_14').value);
 fd.append('wsf_post_mode', 'submit');
 fd.append('wsf_hidden', '');
 fd.append('wsf_bypass_required', '');
 console.table([...fd]); //
 return fd;
 }  // 2) submit to WS Form REST endpoint
 const sleep = ms => new Promise(r => setTimeout(r, ms));
 async function fetchRetry(url, opts = {}, tries = 3) {
 try {
 const res = await fetch(url, { ...opts, signal: AbortSignal.timeout(8000) });
 if (!res.ok) throw Object.assign(new Error('HTTP ' + res.status), { res });
 return res;
 } catch (e) {
 if (tries <= 1) throw e;
 await sleep(400 * (4 - tries));
 return fetchRetry(url, opts, tries - 1);
 }
 } 
 async function submitRemote(fd) {
 console.log("form submit");
 const res = await fetchRetry(ENDPOINT, {
 method: 'POST',
 body: fd,
 mode: 'cors',
 credentials: 'omit'
 });
 return res;
 }
 const form = $('regForm');
 const statusEl = $('status');
 const success = $('successBox');
 form.addEventListener('submit', async (e) => {
 e.preventDefault();
 if (!form.checkValidity()) { form.reportValidity(); return; }
 const btn = form.querySelector('button[type="submit"]');
 console.log("button clicked");
 btn.disabled = true;
 statusEl.style.color = '#111827';
 statusEl.textContent = 'Submitting…'; 
 let res; 
 try {
 const { nonce } = await fetchRetry('https://harrya10.sg-host.com/wp-json/custom/v1/nonce', {
 credentials: 'omit' 
 }).then(r => r.json());  const fd = buildFormData(nonce);
 const res = await submitRemote(fd);
 if (res.ok) {
 form.style.display = 'none';
 success.style.display = 'block';
 statusEl.textContent = '';
 console.log("submission OK");
 } else {
 const t = await res.text().catch(() => '');
 statusEl.style.color = '#b91c1c';
 statusEl.textContent = 'Submission failed. Please try again.';
 console.error('WS Form error', res.status, t);
 }
 } catch (err) {
 statusEl.style.color = '#b91c1c';
 statusEl.textContent = 'Network error. Please try again in a minute.';
 console.error(err); 
 } finally {
 btn.disabled = false;
 console.log(res);
 }
 });
 })(); </script></div>
<!--kg-card-end: html-->
<h3 id></h3>
<!--kg-card-begin: html-->
<section class="page-panel">
    <div class="page-content">
        <ul class="cards">
            <li class="card no-hr">
                <h4 class="card-title">Meet our 2026 speakers</h4>
                <div id="regtech-forum-speakers" class="card-content">
                    <ul class="box-list">
                        <li>
                            <img class="headshot" src="https://suade.org/content/images/2024/03/chimera_Tamiko-Bayliss.png" alt="Your invitation to RegTech Forum 2026">
                            <label class="name"><span style="text-transform: capitalize">Tamiko</span>&#xA0;<span style="text-transform: capitalize">Bayliss</span></label>
                            <label class="job-title">Head of Banking Capital Policy Division</label>
                            <img class="logo" src="https://suade.org/content/images/2024/03/chimera_Bank-of-England-.png" alt="Your invitation to RegTech Forum 2026">
                        </li>

                        <li>
                            <img class="headshot" src="https://suade.org/content/images/2024/06/chimera_Tom-Morrisey.png" alt="Your invitation to RegTech Forum 2026">
                            <label class="name"><span style="text-transform: capitalize">Tom</span>&#xA0;<span style="text-transform: capitalize">Morrissey</span></label>
                            <label class="job-title">Managing Director</label>
                            <img class="logo" src="https://suade.org/content/images/2024/06/chimera_Goldman.png" alt="Your invitation to RegTech Forum 2026">
                        </li>

                        <li>
                            <img class="headshot" src="https://suade.org/content/images/2026/09/chimera_TanjaLoman.png" alt="Your invitation to RegTech Forum 2026">
                            <label class="name"><span style="text-transform: capitalize">Tanja</span>&#xA0;<span style="text-transform: capitalize">Loman</span></label>
                            <label class="job-title">Integrated Reporting Framework (IReF) Programme Office</label>
                            <img class="logo" src="https://suade.org/content/images/2026/09/chimera_ECB2.png" alt="Your invitation to RegTech Forum 2026">
                        </li>

                        <li>
                            <img class="headshot" src="https://suade.org/content/images/2026/09/chimera_Giles-French.png" alt="Your invitation to RegTech Forum 2026">
                            <label class="name"><span style="text-transform: capitalize">Giles</span>&#xA0;<span style="text-transform: capitalize">French</span></label>
                            <label class="job-title">Chief Executive</label>
                            <img class="logo" src="https://suade.org/content/images/2026/09/chimera_AFB.png" alt="Your invitation to RegTech Forum 2026">
                        </li>

                        <li>
                            <img class="headshot" src="https://suade.org/content/images/2026/09/chimera_VickiJordan.png" alt="Your invitation to RegTech Forum 2026">
                            <label class="name"><span style="text-transform: capitalize">Vicki</span>&#xA0;<span style="text-transform: capitalize">Jordan</span></label>
                            <label class="job-title">Policy Manager - AI, Remuneration and Policy Profession</label>
                            <img class="logo" src="https://suade.org/content/images/2024/03/chimera_FCA.png" alt="Your invitation to RegTech Forum 2026">
                        </li>

                        <li>
                            <img class="headshot" src="https://suade.org/content/images/2026/09/chimera_helenterry2.png" alt="Your invitation to RegTech Forum 2026">
                            <label class="name"><span style="text-transform: capitalize">Helen</span>&#xA0;<span style="text-transform: capitalize">Terry</span></label>
                            <label class="job-title">Chief Data and Analytics Officer</label>
                            <img class="logo" src="https://suade.org/content/images/2026/09/chimera_BankofIreland.png" alt="Your invitation to RegTech Forum 2026">
                        </li>

                        <li>
                            <img class="headshot" src="https://suade.org/content/images/2026/09/chimera_Ian-Warren.png" alt="Your invitation to RegTech Forum 2026">
                            <label class="name"><span style="text-transform: capitalize">Ian</span>&#xA0;<span style="text-transform: capitalize">Warren</span></label>
                            <label class="job-title">Chief Financial Officer</label>
                            <img class="logo" src="https://suade.org/content/images/2026/09/chimera_IFast.png" alt="Your invitation to RegTech Forum 2026">
                        </li>

                        <li>
                            <img class="headshot" src="https://suade.org/content/images/2024/03/chimera_-10.png" alt="Your invitation to RegTech Forum 2026">
                            <label class="name"><span style="text-transform: capitalize">Diana</span>&#xA0;<span style="text-transform: capitalize">Paredes</span></label>
                            <label class="job-title">Founder &amp; Chief Executive Officer</label>
                            <img class="logo" src="https://suade.org/content/images/2024/03/chimera_Suade-Labs-.png" alt="Your invitation to RegTech Forum 2026">
                        </li>

                        <li>
                            <img class="headshot" src="https://suade.org/content/images/2026/09/chimera_JonathanTaylor.png" alt="Your invitation to RegTech Forum 2026">
                            <label class="name"><span style="text-transform: capitalize">Jonathan</span>&#xA0;<span style="text-transform: capitalize">Taylor</span></label>
                            <label class="job-title">Head of Quantitative Analysis &amp; Model Risk Management, PRA</label>
                            <img class="logo" src="https://suade.org/content/images/2024/03/chimera_Bank-of-England-.png" alt="Your invitation to RegTech Forum 2026">
                        </li>

                        <li>
                            <img class="headshot" src="https://suade.org/content/images/2026/09/chimera_JinaKim.png" alt="Your invitation to RegTech Forum 2026">
                            <label class="name"><span style="text-transform: capitalize">Jina</span>&#xA0;<span style="text-transform: capitalize">Kim</span></label>
                            <label class="job-title">Head of Financial and Regulatory Reporting</label>
                            <img class="logo" src="https://suade.org/content/images/2026/09/chimera_RedwoodBank.png" alt="Your invitation to RegTech Forum 2026">
                        </li>

                        <li>
                            <img class="headshot" src="https://suade.org/content/images/2026/09/chimera_DanWaites.png" alt="Your invitation to RegTech Forum 2026">
                            <label class="name"><span style="text-transform: capitalize">Dan</span>&#xA0;<span style="text-transform: capitalize">Waites</span></label>
                            <label class="job-title">Head of Regulatory Reporting</label>
                            <img class="logo" src="https://suade.org/content/images/2026/09/chimera_StarlingBank.png" alt="Your invitation to RegTech Forum 2026">
                        </li>

                        <li>
                            <img class="headshot" src="https://suade.org/content/images/2026/09/chimera_KiraSnow.png" alt="Your invitation to RegTech Forum 2026">
                            <label class="name"><span style="text-transform: capitalize">Kira</span>&#xA0;<span style="text-transform: capitalize">Snow</span></label>
                            <label class="job-title">Regulatory Change Implementation Specialist</label>
                            <img class="logo" src="https://suade.org/content/images/2024/03/chimera_Suade-Labs-.png" alt="Your invitation to RegTech Forum 2026">
                        </li>

                        <li>
                            <img class="headshot" src="https://suade.org/content/images/2026/09/chimera_GaetanoChionsini-1.png" alt="Your invitation to RegTech Forum 2026">
                            <label class="name"><span style="text-transform: capitalize">Gaetano</span>&#xA0;<span style="text-transform: capitalize">Chionsini</span></label>
                            <label class="job-title">Head of Statistics</label>
                            <img class="logo" src="ht" alt="Your invitation to RegTech Forum 2026">
                        </li>

                        <li>
                            <img class="headshot" src="https://suade.org/content/images/2026/09/chimera_JoeBrace.png" alt="Your invitation to RegTech Forum 2026">
                            <label class="name"><span style="text-transform: capitalize">Joe</span>&#xA0;<span style="text-transform: capitalize">Brace</span></label>
                            <label class="job-title">Head of Compliance</label>
                            <img class="logo" src="https://suade.org/content/images/2026/09/chimera_nationwide.png" alt="Your invitation to RegTech Forum 2026">
                        </li>

                        <li>
                            <img class="headshot" src="https://suade.org/content/images/2026/09/chimera_JudyZhu-1.png" alt="Your invitation to RegTech Forum 2026">
                            <label class="name"><span style="text-transform: capitalize">Judy</span>&#xA0;<span style="text-transform: capitalize">Zhu</span></label>
                            <label class="job-title">Head of Regulatory Reporting</label>
                            <img class="logo" src="https://suade.org/content/images/2026/09/chimera_bank-of-china-logo.png" alt="Your invitation to RegTech Forum 2026">
                        </li>

                        <li>
                            <img class="headshot" src="https://suade.org/content/images/2026/09/chimera_OliverMargetts.png" alt="Your invitation to RegTech Forum 2026">
                            <label class="name"><span style="text-transform: capitalize">Oliver</span>&#xA0;<span style="text-transform: capitalize">Margetts</span></label>
                            <label class="job-title">Chief Technology Officer</label>
                            <img class="logo" src="https://suade.org/content/images/2024/03/chimera_Suade-Labs-.png" alt="Your invitation to RegTech Forum 2026">
                        </li>

                        <li>
                            <img class="headshot" src="https://suade.org/content/images/2026/09/chimera_NickWilson.png" alt="Your invitation to RegTech Forum 2026">
                            <label class="name"><span style="text-transform: capitalize">Nick</span>&#xA0;<span style="text-transform: capitalize">Wilson</span></label>
                            <label class="job-title">Senior Manager Liquidity Reporting</label>
                            <img class="logo" src="https://suade.org/content/images/2024/09/chimera_Lloyds-Bank.png" alt="Your invitation to RegTech Forum 2026">
                        </li>

                        <li>
                            <img class="headshot" src="https://suade.org/content/images/2026/09/chimera_NickTalbot.png" alt="Your invitation to RegTech Forum 2026">
                            <label class="name"><span style="text-transform: capitalize">Nick</span>&#xA0;<span style="text-transform: capitalize">Talbot</span></label>
                            <label class="job-title">Head of AI Risk Framework Programme</label>
                            <img class="logo" src="https://suade.org/content/images/2026/09/chimera_natwest.png" alt="Your invitation to RegTech Forum 2026">
                        </li>

                    </ul>
                </div>
            </li>
        </ul>
    </div>
</section>
<!--kg-card-end: html-->
]]></content:encoded></item><item><title><![CDATA[Suade Client User Forum]]></title><description><![CDATA[<p><strong>Tuesday 6th October | 10am - 12pm | Guildhall, London</strong></p><p>We welcome our clients to join the Suade team for an morning of discussion, updates, and conversation with peers across the community.</p><p>During the forum, the Suade team presented a round-up of what has happened so far this year, what we have</p>]]></description><link>https://suade.org/2026-10-06-suade-client-user-forum/</link><guid isPermaLink="false">6a8c1b2584bb68095b84ec9f</guid><category><![CDATA[Events]]></category><dc:creator><![CDATA[Phoebe Regnault]]></dc:creator><pubDate>Wed, 02 Sep 2026 14:21:59 GMT</pubDate><media:content url="https://images.unsplash.com/photo-1554186649-01e761e07541?crop=entropy&amp;cs=tinysrgb&amp;fit=max&amp;fm=jpg&amp;ixid=M3wxMTc3M3wwfDF8c2VhcmNofDE3fHxhYnN0cmFjdCUyMGNpdHl8ZW58MHx8fHwxNzg3NTcwMjczfDA&amp;ixlib=rb-4.1.0&amp;q=80&amp;w=2000" medium="image"/><content:encoded><![CDATA[<img src="https://images.unsplash.com/photo-1554186649-01e761e07541?crop=entropy&amp;cs=tinysrgb&amp;fit=max&amp;fm=jpg&amp;ixid=M3wxMTc3M3wwfDF8c2VhcmNofDE3fHxhYnN0cmFjdCUyMGNpdHl8ZW58MHx8fHwxNzg3NTcwMjczfDA&amp;ixlib=rb-4.1.0&amp;q=80&amp;w=2000" alt="Suade Client User Forum"><p><strong>Tuesday 6th October | 10am - 12pm | Guildhall, London</strong></p><p>We welcome our clients to join the Suade team for an morning of discussion, updates, and conversation with peers across the community.</p><p>During the forum, the Suade team presented a round-up of what has happened so far this year, what we have been working on, and the product updates currently in the pipeline. </p><h2 id="speakers"><strong>Speakers: </strong></h2><p><strong>Kira Snow, </strong>Senior Implementation Specialist, Suade</p><p><strong>Florent Audigier,</strong> Head of Product, Suade</p>
<!--kg-card-begin: html-->
<div style="max-width:640px; margin:0 auto; background:#e9f0ff; border:1px solid #dbe4ff; border-radius:8px; padding:22px; font-family: var(--first-font-type), sans-serif; color:#111827;">

    <!-- Success message (hidden until submit succeeds) -->
    <div id="successBox" style="display:none; margin-top:4px;">
        
        <h2 style="margin:0 0 18px; font-size:22px; font-weight:700;">Thank you for registering</h2>
      <div style="border-left:4px solid #4d67e6; padding-left:12px; line-height:1.5;">We&#x2019;ve received your details and are reviewing your submission. We&#x2019;ll contact you shortly with the next steps.
        </div>
    </div>

    <form id="regForm" novalidate>

          <h2 style="margin:0 0 18px; font-size:22px; font-weight:700;">Registration open</h2>
        
        <input type="hidden" id="field_12" value="701QB00000npyR3YAI">  <!-- Salesforce campaign -->
        <input type="hidden" id="field_13" value="Registered"> <!-- Salesforce Status -->
              <input type="hidden" id="field_17" value="Marketing - event registration"> <!-- Salesforce source -->
        <input type="hidden" id="field_14" value="Ghost"> <!-- utm campaign -->
        <input type="hidden" id="field_15" value> <!-- Zoom webinar ID -->


        <!-- -->
     
        <!-- First / Last -->
        <div style="display:flex; gap:16px; margin-bottom:14px; flex-wrap:wrap;">
            <div style="flex:1; min-width:220px;">
                <label for="field_1" style="display:block; font-size:14px; margin:0 0 6px;">First name <span style="color:#dc2626;">*</span></label>
                <input id="field_1" required autocomplete="given-name" style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;">
            </div>
            <div style="flex:1; min-width:220px;">
                <label for="field_2" style="display:block; font-size:14px; margin:0 0 6px;">Last name <span style="color:#dc2626;">*</span></label>
                <input id="field_2" required autocomplete="family-name" style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;">
            </div>
        </div>

        <!-- Title -->
        <div style="margin-bottom:14px;">
            <label for="field_8" style="display:block; font-size:14px; margin:0 0 6px;">Job title <span style="color:#dc2626;">*</span></label>
            <input id="field_8" required style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;">
        </div>

        <!-- Company -->
        <div style="margin-bottom:14px;">
            <label for="field_9" style="display:block; font-size:14px; margin:0 0 6px;">Company <span style="color:#dc2626;">*</span></label>
            <input id="field_9" required autocomplete="organization" style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;">
        </div>

        <!-- Email -->
        <div style="margin-bottom:14px;">
            <label for="field_3" style="display:block; font-size:14px; margin:0 0 6px;">Email <span style="color:#dc2626;">*</span></label>
            <input id="field_3" type="email" required autocomplete="email" inputmode="email" style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;">
        </div>
        <div id="emailError" style="display:none; color:#b91c1c; font-size:13px; margin:0 0 10px 0;">Please enter a valid work email address.</div>
<!-- Message -->
      
        <div id="messageContainer" style="margin-bottom:14px; display:none">
            <label for="field_5" style>Message <span>*</span></label>
            <textarea id="field_5" rows="6"></textarea>
        </div>
<div style="margin-bottom:18px;">
            <label for="field_10" style="display:block; font-size:14px; margin:0 0 6px;">Country <span style="color:#dc2626;">*</span></label>
            <select id="field_10" name="field_10[]" required autocomplete="country" style="width:100%; box-sizing:border-box; padding:10px 12px; border:1px solid #c7d2fe; border-radius:6px; background:#fff; font-size:14px;">
                <option value selected disabled>Select...</option>
                <option value="AF">Afghanistan</option>
<option value="AL">Albania</option>
<option value="DZ">Algeria</option>
<option value="AD">Andorra</option>
<option value="AO">Angola</option>
<option value="AG">Antigua and Barbuda</option>
<option value="AR">Argentina</option>
<option value="AM">Armenia</option>
<option value="AU">Australia</option>
<option value="AT">Austria</option>
<option value="AZ">Azerbaijan</option>
<option value="BS">Bahamas</option>
<option value="BH">Bahrain</option>
<option value="BD">Bangladesh</option>
<option value="BB">Barbados</option>
<option value="BE">Belgium</option>
<option value="BZ">Belize</option>
<option value="BJ">Benin</option>
<option value="BT">Bhutan</option>
<option value="BO">Bolivia</option>
<option value="BA">Bosnia and Herzegovina</option>
<option value="BW">Botswana</option>
<option value="BR">Brazil</option>
<option value="BN">Brunei</option>
<option value="BG">Bulgaria</option>
<option value="BF">Burkina Faso</option>
<option value="BI">Burundi</option>
<option value="CV">Cabo Verde</option>
<option value="KH">Cambodia</option>
<option value="CM">Cameroon</option>
<option value="CA">Canada</option>
<option value="CF">Central African Republic</option>
<option value="TD">Chad</option>
<option value="CL">Chile</option>
<option value="CN">China</option>
<option value="CO">Colombia</option>
<option value="KM">Comoros</option>
<option value="CG">Congo</option>
<option value="CD">Congo, Democratic Republic of the</option>
<option value="CR">Costa Rica</option>
<option value="CI">C&#xF4;te d&#x2019;Ivoire</option>
<option value="HR">Croatia</option>
<option value="CU">Cuba</option>
<option value="CY">Cyprus</option>
<option value="CZ">Czechia</option>
<option value="DK">Denmark</option>
<option value="DJ">Djibouti</option>
<option value="DM">Dominica</option>
<option value="DO">Dominican Republic</option>
<option value="EC">Ecuador</option>
<option value="EG">Egypt</option>
<option value="SV">El Salvador</option>
<option value="GQ">Equatorial Guinea</option>
<option value="ER">Eritrea</option>
<option value="EE">Estonia</option>
<option value="SZ">Eswatini</option>
<option value="ET">Ethiopia</option>
<option value="FJ">Fiji</option>
<option value="FI">Finland</option>
<option value="FR">France</option>
<option value="GA">Gabon</option>
<option value="GM">Gambia</option>
<option value="GE">Georgia</option>
<option value="DE">Germany</option>
<option value="GH">Ghana</option>
<option value="GI">Gibraltar</option>
<option value="GR">Greece</option>
<option value="GD">Grenada</option>
<option value="GT">Guatemala</option>
<option value="GN">Guinea</option>
<option value="GW">Guinea-Bissau</option>
<option value="GY">Guyana</option>
<option value="HT">Haiti</option>
<option value="HN">Honduras</option>
<option value="HK">Hong Kong</option>
<option value="HU">Hungary</option>
<option value="IS">Iceland</option>
<option value="IN">India</option>
<option value="ID">Indonesia</option>
<option value="IQ">Iraq</option>
<option value="IE">Ireland</option>
<option value="IM">Isle of Man</option>
<option value="IL">Israel</option>
<option value="IT">Italy</option>
<option value="JM">Jamaica</option>
<option value="JP">Japan</option>
<option value="JE">Jersey</option>
<option value="JO">Jordan</option>
<option value="KZ">Kazakhstan</option>
<option value="KE">Kenya</option>
<option value="KI">Kiribati</option>
<option value="KR">Korea</option>
<option value="KW">Kuwait</option>
<option value="KG">Kyrgyzstan</option>
<option value="LA">Laos</option>
<option value="LV">Latvia</option>
<option value="LB">Lebanon</option>
<option value="LS">Lesotho</option>
<option value="LR">Liberia</option>
<option value="LY">Libya</option>
<option value="LI">Liechtenstein</option>
<option value="LT">Lithuania</option>
<option value="LU">Luxembourg</option>
<option value="MG">Madagascar</option>
<option value="MW">Malawi</option>
<option value="MY">Malaysia</option>
<option value="MV">Maldives</option>
<option value="ML">Mali</option>
<option value="MT">Malta</option>
<option value="MR">Mauritania</option>
<option value="MU">Mauritius</option>
<option value="MX">Mexico</option>
<option value="FM">Micronesia (Federated States of)</option>
<option value="MD">Moldova</option>
<option value="MC">Monaco</option>
<option value="MN">Mongolia</option>
<option value="ME">Montenegro</option>
<option value="MA">Morocco</option>
<option value="MZ">Mozambique</option>
<option value="MM">Myanmar</option>
<option value="NA">Namibia</option>
<option value="NR">Nauru</option>
<option value="NP">Nepal</option>
<option value="NL">Netherlands</option>
<option value="NZ">New Zealand</option>
<option value="NI">Nicaragua</option>
<option value="NE">Niger</option>
<option value="NG">Nigeria</option>
<option value="MK">North Macedonia</option>
<option value="NO">Norway</option>
<option value="OM">Oman</option>
<option value="PK">Pakistan</option>
<option value="PW">Palau</option>
<option value="PA">Panama</option>
<option value="PG">Papua New Guinea</option>
<option value="PY">Paraguay</option>
<option value="PE">Peru</option>
<option value="PH">Philippines</option>
<option value="PL">Poland</option>
<option value="PT">Portugal</option>
<option value="QA">Qatar</option>
<option value="RO">Romania</option>
<option value="RW">Rwanda</option>
<option value="KN">Saint Kitts and Nevis</option>
<option value="LC">Saint Lucia</option>
<option value="VC">Saint Vincent and the Grenadines</option>
<option value="WS">Samoa</option>
<option value="SM">San Marino</option>
<option value="ST">Sao Tome and Principe</option>
<option value="SA">Saudi Arabia</option>
<option value="SN">Senegal</option>
<option value="RS">Serbia</option>
<option value="SC">Seychelles</option>
<option value="SL">Sierra Leone</option>
<option value="SG">Singapore</option>
<option value="SK">Slovakia</option>
<option value="SI">Slovenia</option>
<option value="SB">Solomon Islands</option>
<option value="SO">Somalia</option>
<option value="ZA">South Africa</option>
<option value="SS">South Sudan</option>
<option value="ES">Spain</option>
<option value="LK">Sri Lanka</option>
<option value="SD">Sudan</option>
<option value="SR">Suriname</option>
<option value="SE">Sweden</option>
<option value="CH">Switzerland</option>
<option value="SY">Syria</option>
<option value="TW">Taiwan</option>
<option value="TJ">Tajikistan</option>
<option value="TZ">Tanzania</option>
<option value="TH">Thailand</option>
<option value="TL">Timor-Leste</option>
<option value="TG">Togo</option>
<option value="TO">Tonga</option>
<option value="TT">Trinidad and Tobago</option>
<option value="TN">Tunisia</option>
<option value="TR">Turkey (T&#xFC;rkiye)</option>
<option value="TM">Turkmenistan</option>
<option value="TV">Tuvalu</option>
<option value="UG">Uganda</option>
<option value="UA">Ukraine</option>
<option value="AE">United Arab Emirates</option>
<option value="GB">United Kingdom</option>
<option value="US">United States</option>
<option value="UY">Uruguay</option>
<option value="UZ">Uzbekistan</option>
<option value="VU">Vanuatu</option>
<option value="VE">Venezuela</option>
<option value="VN">Viet Nam</option>
<option value="ZM">Zambia</option>
<option value="ZW">Zimbabwe</option>
            </select>
        </div>

        <!-- Submit -->
        <button type="submit" style="font-family: IBM Plex Sans, sans-serif; width:100%; padding:12px 16px; border:0; border-radius:8px; background:#4d67e6; color:#fff; font-size:16px; font-weight:600; cursor:pointer;">
            Submit
        </button>
   
    
        <input type="hidden" id="g-recaptcha-response" value>
    
           <p>By submitting this form to Suade you hereby agree that any personal information you provide can be processed according to Suade&#x2019;s <a href="https://suade.org/privacy-policy/">Privacy policy</a>.</p>
    
    </form>

    <div id="status" style="margin-top:12px; font-size:14px;" aria-live="polite"></div>
<script>
(function () {

  console.log("script start");

  const messageContainer = document.getElementById("messageContainer");
  const messageField = document.getElementById("field_5");
  const emailInput = document.getElementById("field_3");
  const errEl = document.getElementById("emailError");
  const utm_field = document.getElementById('field_14');
  if (utm_field) {
    utm_field.value =
      new URLSearchParams(window.location.search).get('utm_campaign') || 'Ghost';
  }

  const BLOCKED_SLD = new Set([
    'gmail',
    'yahoo',
    'hotmail',
    'live',
    'outlook',
    'aol',
    'msn',
    'icloud',
    'me',
    'mac',
    'btinternet',
    'talktalk',
    'virginmedia',
    'comcast',
    'verizon',
    'sky'
  ]);

  function baseLabel(host) {
    const parts = host.split('.').filter(Boolean);

    if (parts.length < 2) {
      return host;
    }

    const tld = parts[parts.length - 1];

    if (tld.length === 2 && parts.length >= 3) {
      return parts[parts.length - 3];
    }

    return parts[parts.length - 2];
  }

  function isPersonalEmail(email) {
    const m = String(email)
      .toLowerCase()
      .match(/^[^@\s]+@([^@\s]+)$/);

    if (!m) {
      return false;
    }

    const host = m[1];
    const sld = baseLabel(host);

    return BLOCKED_SLD.has(sld);
  }

  function showWorkEmailError(show) {
    if (show) {
      emailInput.setCustomValidity(
        'Please enter a valid work email address.'
      );

      errEl.style.display = 'block';
    } else {
      emailInput.setCustomValidity('');
      errEl.style.display = 'none';
    }
  }

  function validateEmail() {
    const val = emailInput.value.trim();
    const block = val && isPersonalEmail(val);

    showWorkEmailError(block);

    return !block;
  }

  emailInput.addEventListener('input', validateEmail);
  emailInput.addEventListener('blur', validateEmail);


  const $ = (id) => document.getElementById(id);

  const SALESFORCE_ENDPOINT =
    'https://webto.salesforce.com/servlet/servlet.WebToLead?encoding=UTF-8';
  const ZOOM_ENDPOINT = 'https://applications.zoom.us/api/v1/pardot/registration/Nh8FHOozT0uoLb9XrHGOAg?state=VkVSU046MDAwlEtstTrtQnaPm6-F1cYhzo180QIO0fZmXBfv55996eHVuPaCHIEBHQ1aJOUPO9L7GT4'
  
  const salesforceIframe = document.createElement('iframe');

  salesforceIframe.name = 'salesforceTarget';
  salesforceIframe.id = 'salesforceTarget';
  salesforceIframe.style.display = 'none';

  document.body.appendChild(salesforceIframe);

  const zoomIframe = document.createElement('iframe');

  zoomIframe.name = 'zoomTarget';
  zoomIframe.id = 'zoomTarget';
  zoomIframe.style.display = 'none';
  
  document.body.appendChild(zoomIframe);

  function addField(form, name, value) {
    const input = document.createElement('input');

    input.type = 'hidden';
    input.name = name;
    input.value = value || '';

    form.appendChild(input);
  }

  function submitToSalesforce() {

    const sfForm = document.createElement('form');

    sfForm.method = 'POST';
    sfForm.action = SALESFORCE_ENDPOINT;
    sfForm.target = 'salesforceTarget';
    sfForm.style.display = 'none';

    addField(
      sfForm,
      'oid',
      '00D1t000000vUFQ'
    );

    addField(
      sfForm,
      '00NQB00000H9wKx',
      $('field_3').value.trim()
    );

    addField(
      sfForm,
      'first_name',
      $('field_1').value.trim()
    );

    addField(
      sfForm,
      'last_name',
      $('field_2').value.trim()
    );

    addField(
      sfForm,
      'company',
      $('field_9').value.trim()
    );

    addField(
      sfForm,
      'title',
      $('field_8').value.trim()
    );

    addField(
      sfForm,
      'country_code',
      $('field_10').value
    );

    addField(
      sfForm,
      '00N3Y00000H76Kw',
      $('field_12').value
    );

    addField(
      sfForm,
      '00NQB0000051EZ7',
      $('field_13').value
    );

    addField(
      sfForm,
      '00NQB00000Uy1rC',
      $('field_14').value
    );

    addField(
      sfForm,
      'description',
      $('field_5').value.trim()
    );

    addField(
      sfForm,
      'lead_source',
      $('field_17').value
    );

    document.body.appendChild(sfForm);

    console.log('Submitting directly to Salesforce');

    sfForm.submit();

    setTimeout(function () {
      sfForm.remove();
    }, 1000);
  }

  function submitToZoom() {

  const webinarId = $('field_15').value.trim();

  // Don't attempt Zoom registration if this event has no webinar ID.
  if (!webinarId) {
    console.log('No Zoom webinar ID configured - skipping Zoom registration');
    return;
  }

  const zoomForm = document.createElement('form');

  zoomForm.method = 'POST';
  zoomForm.action = ZOOM_ENDPOINT;
  zoomForm.target = 'zoomTarget';
  zoomForm.style.display = 'none';

  addField(
    zoomForm,
    'first_name',
    $('field_1').value.trim()
  );

  addField(
    zoomForm,
    'last_name',
    $('field_2').value.trim()
  );

  addField(
    zoomForm,
    'org',
    $('field_9').value.trim()
  );

  addField(
    zoomForm,
    'job_title',
    $('field_8').value.trim()
  );

  addField(
    zoomForm,
    'email',
    $('field_3').value.trim()
  );

  addField(
    zoomForm,
    'webinarId',
    webinarId
  );

  document.body.appendChild(zoomForm);

  console.log(
    'Submitting directly to Zoom webinar:',
    webinarId
  );

  zoomForm.submit();

  setTimeout(function () {
    zoomForm.remove();
  }, 1000);
}

  const form = $('regForm');
  const statusEl = $('status');
  const success = $('successBox');

  form.addEventListener('submit', function (e) {

    e.preventDefault();

    validateEmail();

    if (!form.checkValidity()) {
      form.reportValidity();
      return;
    }

    const btn =
      form.querySelector('button[type="submit"]');

    console.log("button clicked");

    btn.disabled = true;

    statusEl.style.color = '#111827';
    statusEl.textContent = 'Submitting…';

    try {

      submitToSalesforce();
      submitToZoom();


      form.style.display = 'none';
      success.style.display = 'block';

      statusEl.textContent = '';

      console.log('Salesforce and Zoom submissions sent');

    } catch (err) {

      statusEl.style.color = '#b91c1c';

      statusEl.textContent =
        'Submission failed. Please try again.';

      console.error(err);

      btn.disabled = false;
    }

  });

})();
</script>
</div>
<!--kg-card-end: html-->
]]></content:encoded></item></channel></rss>