Managing Regulatory Relationships – Meetings
We have had many meetings with regulators while working in financial services. We’ve found that using a standard meeting approach significantly improves the process and the results. In our experience, being well-prepared for a meeting leads to successful outcomes for both you and your regulator.
Depending on the regulatory regime under which you operate, there may be several reasons you need to meet with your regulator. It may be one of a series of regular meetings specific to your business. It may be part of a thematic theme review, where the regulator meets with several regulated entities in a particular type of regulated activity to compare best practices across the industry. There may also be a potential compliance issue that you need to address. No matter the reason for the meeting, using a standard approach will smooth the process internally and at the meeting.
The Board of Directors and senior management should be advised of the visit, including the proposed dates, type of review, and scope. Representatives of each should be available to assist and answer questions during the meetings and to review any output being provided as part of the meeting outcomes. A standard preparation process ensures you are prepared for the discussion and any follow-up required. Knowing your regulatory requirements and anticipating your regulator visit schedule will also help manage the process.
Initial Information Request
Receiving a request for a meeting with your regulatory supervisor should prompt an internal discussion to review the request. This meeting should include your regulatory liaison officer, compliance team and senior management.
Things to discuss should include:
Creating a plan for organising and preparing the information is vital. Assign tasks to specific people with due dates to review and confirm that the data is complete.
You may well experience difficulties in meeting the deadlines for the provision of some information. If so, don’t leave it to the last minute before informing your regulator. Hopefully, you can agree on a realistic alternative timeframe well before the original deadline or agree to partial responses with the balance available at the meeting.
Planning the meeting
While planning, be clear about what the regulator is asking for and your objectives for the meeting. This is your opportunity to gather information and guidance from the regulatory supervisor while answering their questions with relevant but not extraneous information. Agree on who will be your internal lead for the meeting, and have them coordinate all actions with your regulator.
Offer to draft the agenda and send it to your regulatory contact. Agreeing on the content, order, and material required before or at the meeting will allow for a focused and productive meeting. Deciding on an agenda with the regulator will help focus the session. Both parties will know what is being discussed and can have the right people at the meeting, saving time and ensuring you can discuss with the right level of detail.
Once the agenda is agreed upon, plan who should participate in meetings and which items they will discuss. Gather that group and brainstorm what questions might come up and who should answer them. It’s also good to discuss how best to answer those questions. Having a chance to discuss potential questions that might be asked and appropriate responses will help the team be confident and prepared for the meeting. During that meeting, you should also review output from previous regulatory visits to have a consistent and thorough approach to the meeting.
Day of the visit
Offer to have someone from your team take minutes to be shared and agreed upon after the meeting. Also, take note of actions in an action tracker. During the meeting, agree on who is responsible for the activity and when it is due. This includes actions from the regulator as well as your team. Send the draft action tracker with the draft minutes so both parties have input and can confirm realistic due dates.
If you are aware of shortcomings or areas you are working on, have a plan for how these will be addressed and be transparent about the timeframe and outcome of those plans. Validating that the approach will meet requirements and confirming that your timelines are acceptable with the regulator will clarify your process and allow the regulator to make any further recommendations while you can still make changes.
What to do when things go wrong
No matter how prepared you are, something may come up that you aren’t prepared for. Don’t feel you have to give an immediate response. Asking for more details and agreeing to provide information to respond more fully after the meeting will allow you to provide the correct information that benefits both parties.
Be prepared to say “I don’t know” or “I will need to confirm those details”. Regulators understand that you may not have every detail at your fingertips. Being honest and asking for some time to gather the information so as not to waste time in the meeting is the most efficient way to deal with it and ensure you don’t unintentionally provide incorrect or unhelpful information.
Post-visit management
Hold a lessons-learned session after the meeting, so you are better prepared for next time and share information with management and team members who weren’t at the meeting. Be sure to complete the following:
If shortcomings are identified during the review, don’t wait until you receive the Regulatory Body’s written report before taking steps to address them. If you take prompt action, you will be able to demonstrate that matters are taken seriously and have either been addressed or are being progressed.
There are many tools available for action trackers. We used to use an excel spreadsheet to track and manage our regulatory liaison activities.
Now that we have the Phundex Platform, we manage all of our regulatory liaison activities on Phundex. With Phundex, you can plan and follow up on meetings, requests and action points in one central spot. You can even invite the regulator to see published documents on the Platform, reducing email risk.
To download the entire document, please click on the link below.
For more information, see the article we published earlier this year on managing regulatory liaisons using Phundex, which you can find here: Regulatory Liaison – How Phundex Can Help
You can find more articles on our website, at Phundex Resources, on LinkedIn at Phundex LinkedIn, or for other questions, please email us at: hello@phundex.com.
To book a demo or a trial, you can either use the link on our website or email support@phundex.com, and they will be happy to set it up for you.
Get a one-to-one demo
Discover how Phundex can streamline your transactions and processes
Your transactions…
simplified
Streamline business processes, reduce operational risk and increase efficiency.
Copyright Phundex 2023
PHUNDEX UK LIMITED
Registered Office :
128 City Road, London, UK, EC1V 2NX
Trading Office :
68 Summers Road, Godalming, Surrey, UK, GU7 3BE
Phundex Limited is registered in Jersey, Channel Islands, No 131447, Registered with the Information Commissioner’s Office in the UK in compliance with the Data Protection (Charges and Information) Regulations 2018 under registration ZA839762 and in Jersey in compliance with Regulation 4(1) of the Data Protection (Registration and Charges) (Jersey) Regulations 2018 under registration 68186
Phundex UK Ltd is registered in England & Wales No. 12207772, Registered with the Information Commissioner’s Office in the UK in compliance with the Data Protection (Charges and Information) Regulations 2018 under registration ZB285669
Cookie | Duration | Description |
---|---|---|
_GRECAPTCHA | 5 months 27 days | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
ajs_anonymous_id | 1 year | This cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before. |
ajs_user_id | never | This cookie is set by Segment to help track visitor usage, events, target marketing, and also measure application performance and stability. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
Cookie | Duration | Description |
---|---|---|
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
Cookie | Duration | Description |
---|---|---|
__tld__ | session | No description |