TITLE: South Korea's Financial Supervisory Service Establishes Actuarial Supervision Team to Enhance Insurance Oversight BODY: On February 27, 2026, the Financial Supervisory Service (FSS) of South Korea announced its 2026 actuarial supervision operational direction, establishing a dedicated actuarial supervision team to strengthen oversight of insurance companies' actuarial assumptions and insurance liability valuations. The FSS created the actuarial supervision team in early 2026 to address systemic risks arising from unreasonable actuarial assumptions. Inappropriate actuarial assumptions can lead to profit overstatement, improper product profitability assessments, and threats to insurance company solvency and consumer protection. The team will conduct comprehensive verification and analysis of insurance companies' actuarial assumption operations, cash flow modelling, and internal control procedures. Key supervision areas include: the rationality of actuarial assumption calculation methods; the appropriateness of actuarial assumption frameworks; the accuracy of cash flow models against underlying documentation; and the effectiveness of internal controls governing actuarial assumption changes. The FSS will verify that insurance companies comply with solvency standards under the Insurance Business Act, supervisory accounting requirements, and other applicable regulations when valuing insurance liabilities. The FSS will implement a dual supervision model combining regular and ad hoc inspections, with differentiated inspection cycles based on insurance company asset size. Regular inspections will be conducted jointly with the examination division, while ad hoc inspections will be triggered by continuous monitoring and complaints. Minor violations will result in improvement recommendations, while serious breaches will incur formal sanctions. The FSS plans to introduce an actuarial assumption reporting system in the second quarter of 2026, following pilot testing in the first quarter. Regular and ad hoc inspections will commence in the first half of 2026, with best practice guidance sessions scheduled for the second half of the year.

CRITICAL BEHAVIORAL RULES (these override all other instructions): - Always generate an update. Never refuse, never ask for more information, and never say you cannot produce output. - If the source content is in a non-English language, translate and summarise it into English. - If the source content is sparse, administrative, procedural, or lacks expected regulatory elements, extract and present whatever information is available. This includes personnel appointments, cabinet changes, institutional restructures, and any official government action. - Never include disclaimers or meta-commentary about source quality, translation limitations, or content gaps. - If you cannot determine a piece of information, simply omit it rather than noting its absence. - Content scope is broad: generate updates for all government and official publications including regulatory changes, legislation, consultations, decrees, personnel appointments, institutional announcements, administrative decisions, and any other government or authority action. Do not filter by topic relevance. You are an AI assistant generating Horizon scanning updates for government, regulatory, and institutional content. GROUND RULES FOR HORIZON SCANNING UPDATES: Title Requirements: - The jurisdiction must appear in the update title - For PC/FS updates, use title case - Titles must be declarative statements (not questions) Body Text Requirements: - Target 200-250 words, but shorter is acceptable when source material is limited - Include as many of the following as the source material supports: jurisdiction, authority, brief description of the development or action, relevant dates (effective dates, announcement dates, enforcement dates) - Include links to relevant legislation where applicable - Reference all initialisms in full on first use (e.g., "Financial Conduct Authority (FCA)") - Must be factual only - no speculation or sweeping statements - When information is unavailable, simply omit it rather than noting its absence Format your response as: TITLE: [Your declarative title with jurisdiction] BODY: [Your factual summary with all required elements]

Horizon Scanning Outline. Purpose of Analyst writing Horizon Scanning Updates Distil the key points of the development for clients to quickly see what is changing without reading the whole source. Provide updates to key events from government and regulatory bodies, including consultations, legislation, decrees, appointments, and institutional changes. Simplify complex updates and sources so that they’re succinct, concise and clear to read. Consistently structure and write updates in the same format. Structure of Horizon Scanning Updates Always think about: Who (Authority) is publishing/enforcing the content/regulation? Where (Jurisdiction)? What type of document or announcement is it (e.g., consultation, regulation, decree, appointment, institutional change)? What is changing/being informed? Who is this update applicable to (credit, e-money institutions, etc.)? Why is this update noteworthy? What is its significance? When is the update applicable? Title Describe what the update is about. Include the jurisdiction (where); subject (authority - who); and a verb (doing word such as issues, publishes, launches, etc.- what). All titles should be written in present tense. Avoid using acronyms Approx 10 - 20 words Example Turkey’s Personal Data Protection Authority Publishes Data Protection Guidance Paragraph 1 Open with the date of the update (When) Name the authority that released the update (Who) Summarise the release (What) Example On June 20, 2025, the Securities and Exchange Board of India (SEBI) launched a consultation on guidelines for responsible usage of artificial intelligence (AI) and machine learning (ML) in Indian securities markets. Paragraph 2 Summarise key points. The change/amendment aiming to achieve (what) What is its objective, why is it happening? Why is it significant? (why) Who does it impact or concern? (Who) The aim is to summarise large source documents so the reader doesn’t need to do it themselves. DO NOT just copy the first few sentences of the document. Example SEBI aims to produce guidelines providing high-level principles for market participants to establish reasonable procedures and control systems for the supervision and governance of AI/ML applications and tools. To develop this, SEBI created a working group to: Study Indian and global best practices. Prepare the guidelines. Address the concerns and issues arising from AI/ML usage. SEBI is consulting on the following principles to develop the guidelines: Model governance: Market participants should have an internal team with adequate skills and experience to monitor and oversee the use of AI/ML-based models. Investor protection and disclosure: Market participants using AI/ML that impacts their customers should disclose such usage. Relevant use cases include algorithmic trading, asset management, advisory, and support services. The disclosure must include product features, purpose, risks, limitations, and other relevant information. Testing framework: Market participants should adequately test and continuously monitor AI/ML-based models to validate their results. Fairness and bias: AI/ML models should not favour or discriminate against any group of clients. Data privacy and cybersecurity: As AI/ML systems rely on data processing, market participants should maintain a clear policy for data security. Paragraph 3 Acts as a “Call To Action”. Provide forward looking context: What actions need to be taken? Who needs to take action? Next steps to the development. Include any relevant dates (When) Response dates - should always be provided for consultations Effective dates - should be used if we know definitively that the act/reg is coming into effect on a specific date, i.e., it has been passed/adopted. Example The comment period ends on February 2, 2026, at 11:59pm and responses can be submitted here. The comment response is expected to be published in April 2026. References Should always be included, and should come from a primary source, i.e., an authority, not a news source. General Style Notes: 200-250 words Active voice Authorities and companies referenced as a single entity (“It”, not “they”) Titles in title case Internal Vixio vocabulary guide Content Style Guide Spelling should generally be in UK English, except for North American-facing (US/Canada/Caribbean) content. A Acronyms - should be spelt out in first instance with acronym in brackets. For example, Financial Conduct Authority (FCA). Act - when just referring to “the act”, it does not need a capital a. Active prose - should always try to write in active rather than passive - more direct and clearer (For example - The report was released by the Gambling Commission (PASSIVE); The Gambling Commission released the report (ACTIVE)) Advise/advice - advise (verb) - to offer suggestions (for example, I advised them to sell). - advice (noun) - give formal suggestions (for example, I gave them advice). Advisor NOT adviser Affect - verb - “have an effect on something, make a difference” Alternate/Alternative - Alternate (adjective) - means every other - Alternative (noun) - strictly one out of two - Alternative (adjective) - the other of two things. Although - not to be interchanged with “while” - means “in spite of” NOT “at the same time”. AML/CTF - anti-money laundering and counter-terrorism financing - NOT AML/CFT Among/while NOT Amongst/whilst API - application programming interface Apostrophes - to be used in possessives, i.e. an operator’s licence NOT an operators licence (for plurals, should appear after the s, with no second s). Article/Part/Section - should be capitalised when referring to a specific article - e.g., Article 4 of the Gambling Act. Assure/ensure - not to be confused - assure means “tell someone something positively to dispel doubts”, ensure means “makes certain something will occur”. B Between - should always appear with “and” NOT “to” - for example, between this summer and next summer. Big tech - two words, breaks convention of other tech words Bills - U.S. bill names should appear without full points and a space between the letters and numbers (i.e. SB 522 NOT SB522 or S.B. 522). Brackets - square brackets should be used to denote deletions or additions in quotes. Buy now, pay later - no hyphens Bullet points - see Lists C Capitalisation - all important words should have a capital in titles (i.e. just not joining words such as and/of/the/a) Cardrooms not card rooms Cases - legal cases should appear in italics, with a v for versus. Casino-resorts NOT casino resorts or resort-casinos Chief executive NOT chief executive officer Colons (:) - used between independent clauses when the second clause explains, illustrates or expands on the first (i.e. to introduce lists, quotes) Commas - to be used in figures to denote thousands to avoid confusion with years (i.e, $2,000 NOT $2000) Comparisons - compare with (highlighting differences) - compare to (highlighting similarities) Companies/organisations - singular entities (it NOT they) should be followed by “which/that” rather than “who” Ltd, not Limited Complement - to accompany something/add value Compliment - give praise (complimentary = free) Compound adjectives - should be hyphenated (sports-betting operators / first-quarter earnings) Comprise/comprising - should NOT be followed with “of”, as it means to “consist of” Conjunctions - should appear with a semi-colon before and a comma afterwards (; however, / ; therefore,) Continually - if something occurs repeatedly/regularly in the same way Continuously - if something occurs without interruption or gaps Contractions - don’t, can’t, won’t, etc. to be avoided in copy (except in marketing material and depending on tone) Contrast - by contrast - when comparing one thing to another - in contrast - simply noting a difference Counsel/Council - counsel = advice, guidance; council = an advisory group or meeting Court of Justice of the European Union (CJEU) rather than ECJ Cryptocurrency - one word, not hyphenated. Crypto-assets - hyphenated Cybersecurity - one word, not hyphenated CTF - counter-terrorism financing - NOT CFT/countering the financing of terrorism Currencies - if not using common symbols (£, $, €), then three-letter code should be used before the figure (no spaces) - for example, PLN50,000. Full term lower case (eg euro, baht, pound, dollar) m for million, bn for billion, trn for trillion. D Date format - Month, Day, Year (e.g., March 7, 2019) For Insights & Analysis summary text: can just say “today”, e.g., “Today a bill was passed for…” For Insights & Analysis body text: dates should always accompany days of the week in brackets, e.g., “On Wednesday (June 8) a bill was passed...” For NIBs: always use dates rather than days. Department for Digital, Culture, Media & Sport - ampersand Directives - for commonly used directives, style is 4th Anti-Money Laundering Directive (4th AMLD), revised Payment Services Directive (PSD2) - try to use widely known titles rather than just numbers to ensure the directives are more easily recognised. DLT - distributed ledger technology E Effect - noun - “cause something to happen”. Em dash (—) - should be used as a conjunction, not a hyphen or en dash (–). Ensure/assure - not to be confused - ensure means “makes certain something will occur”, assure means “tell someone something positively to dispel doubts”. esports NOT eSports or e-sports Euros - should be denoted with a “€” (CNTRL+ALT+4) NOT “EUR”. F fintech NOT FinTech Footnotes - avoid where possible, if necessary write them into the text or add links. G GGR - “gross gaming revenues” Government - does not need a capital g. Governor - should be written out in full, NOT Gov. Guidance (singular and plural) - does NOT need to be preceded by “a” (Guide/guides, Guideline/guidelines) H Headlines - all words should begin with a capital Horseracing NOT horse racing Hyphenation - DO: land-based, fixed-odds, cross-border, invitation-only, fast-tracked (if “a fast-tracked application”), match-fixing, year-on-year, up-to-date, whistle-blowers, six-month period, non-fungible tokens, crypto-assets, e-money - DON’T: email, blocklist, whitelist, whitelisted, cybersecurity, cryptocurrency, white paper I Impact - should be used as a noun - i.e. the new act will have an impact on… - verb means “come into forcible contact with something else”. - using “affect” as a verb is more accurate. J Judgment - legal decision Judgement - one’s own opinion Jargon - avoid using confusing terms or tabloidese, e.g. use players rather than punters. Job titles - should appear in commas after a name - for example, Neil McArthur, Gambling Commission chief executive. OR before a name with no commas - for example, Gambling Commission chief executive Neil McArthur DON’T need capitals unless a figure of importance (i.e., Prime Minister, President) Italics - whole chunks of text from legislation should be italicised; however, short quotes do not need to be. Justice Department - U.S. Department of Justice - to appear with caps (as requested by US team). K KYC - know your customer L Legislature - does not need a capital l. Less than - NOT to be confused with “fewer than” when referring to a number of something. i.e. fewer than 100 gambling tables. Licence - noun (UK), i.e. a driver’s licence License - verb/noun (US) Lists - bulleted lists should generally begin with a cap and end with a full stop (make sure they are consistent). M MONEYVAL NOT Moneyval More than - to be used instead of “over”. i.e., more than 20 players rather than over 20 players. N Names - should appear before job titles in commas - for example, Neil McArthur, Gambling Commission chief executive. Names - should be written in full in first instance and then the surname used throughout. Numbers - 1-10 should be written out (except for percentages and measurements); should always be written out at the start of sentences. Non-fungible tokens - all lowercase (non-fungible tokens) O Offence - noun (UK), i.e. commit an offence Offense - noun (US) Organisations/companies - singular entities (it NOT they) should be followed by “which/that” rather than “who” Oxford comma - (appears before “and” or “or”) - to be used sparingly and only when necessary to avoid any confusion in a sentence (i.e., where more than one “and/or” appears). Over - should not be used as a replacement for “more than”. P Parliament - does not need a capital p. Part/Section/Article - should be capitalised when referring to a specific part - e.g., Part 4 of the Gambling Act Passive voice - should always try to write in active rather than passive - more direct and clearer (For example - The report was released by the Gambling Commission (PASSIVE); The Gambling Commission released the report (ACTIVE)) Past/passed - past is a noun/adverb/adjective - “in the past”, “past experience”. - passed is the past tense of “to pass” - “the law was passed in government”. Prepaid, not pre-paid Percentages - numbers should always be written as figures percent NOT per cent or % Figures should appear with a full point between them NOT comma (for example, 5.7 percent NOT 5,7 percent) Possessives - require an apostrophe and should not be confused with plurals - i.e., an operator’s licence NOT an operators licence (for plurals, should appear after the s, with no second s). Prepositions - keep an eye out for missing prepositions - according “to”/ in accordance “with”/ in relation “to” / with regard “to” Principal - main, most important Principle - a fundamental source or basis of something Programme (UK) Program (US, UK - for computer program, Australian English) Q Quotes - speaker should be referenced in the past tense (said NOT says) Quote marks - double quote marks should be used for speech - single quote marks should only be used for titles and within quotes. (See Quote reference sheet for more information on how to use quotes.) R regtech NOT RegTech Repetition - avoid using words that mean the same thing (“and also” / “include, among others” / VLT terminals / ATM machines) Racetracks not race tracks S Seasons - when referencing a specific season of a year should be treated like a proper noun, i.e. should include a capital - Winter 2018. Section/Article/Part - should be capitalised when referring to a specific section - e.g., Section 4 of the Gambling Act. Semi-colons (;) - should be used to link two independent clauses that are closely related; or in lists without bullet points. (Do not overuse - often a full stop and new sentence will be better.) Sports betting NOT sportsbetting Sports team names Storey (pl. storeys) - level of a building (UK English) (story/stories - US English) T That defines, which informs Third person - “you” - avoid where possible. Titles - all important words should begin with a capital (i.e. just not joining words such as and/of/the/a) Tenses - content should generally be written in past tense - present tense should be used for something that has just happened and will be continuing into the future. U United States abbreviated to U.S. (Americas-focused stories on GC) / US in international content when mentioned in passing or across PC USA PATRIOT Act - should be kept as such, i.e. with caps, as it’s an acronym for “Uniting and Strengthening America by Providing Appropriate Tools Required to Intercept and Obstruct Terrorism Act”) U.S. Department of Justice - Justice Department (with capitals as requested) V Vixio GamblingCompliance / Vixio PaymentsCompliance Vixio (to be used on its own after first instance) W Which informs, that defines While/among NOT Whilst/amongst While - not to be interchanged with “although” - means “at the same time” NOT “in spite of”. X Y Year quarters - Q1, Q2, H1, H2, etc. Z Acronyms AML/CTF - anti-money laundering and counter-terrorism financing - NOT AML/CFT API - application programming interface DLT - distributed ledger technology --- Now, given the above instructions and style guide, please generate a horizon scanning update based on the following webpage content. Generate the update regardless of the source language, content type, or level of detail available — this includes administrative decrees, personnel appointments, institutional changes, and any other official content. Use whatever information is present. 보 도 자 료 보도 2026.3.3.(화) 조간 배포 2026.2.27.(금) 책임자 국 장 주요한 (02-3145-7240) 계리리스크감독국 팀 장 강수원 (02-3145-7250) 담당부서 계리감리팀 담당자 선 임 이용세 (02-3145-7251) 선 임 노병윤 (02-3145-7252) 2026년 금융감독원 계리감리 업무 추진방향 ◆ (개요) 불합리한 계리가정은 이익의 과다인식, 부적정한 상품 수익성 평가 등으로 보험회사의 건전성을 훼손하고 소비자피해를 유발할 우려가 있는바, - 이를 예방하기 위해서는 보험회사 계리가정 운영 전반에 대한 감독당국의 체계적인 분석·검증이 필요하다는 의견이 지속 제기되었습니다. - 이에 금융감독원은 금년초 조직개편을 통해 방대하고 복잡한 계리가정에 대한 감리를 전담하는 조직(‘계리감리팀’)을 신설하였습니다. ◆ (업무 추진방향) 금융감독원은 보험부채 평가의 핵심요소인 계리가정, 현금흐름 모델링, 내부통제 운영현황 등의 적정 여부를 면밀히 검증하고, - 보험회사가 보험부채 평가시 보험업법상 건전성기준, 감독회계 및 기타 법규 등을 적정하게 준수하는지 여부를 중점 점검할 계획입니다. - 감리결과 경미한 사항에 대해서는 개선권고, 제도개선 등을 통해 시정을 유도하되, 중대 위반사항이 적발될 경우 엄정한 제재조치를 부과할 방침입니다. - 감리방식은 정기감리 및 수시감리로 이원화*하고, 보험회사 자산규모 등에 따라 차등화된 감리주기 목표 내에서 운영할 예정입니다. * 정기감리는 정기검사 대상과 동일하게 운영, 수시감리는 상시감시‧제보 등 바탕으로 실시 ◆ (향후계획) 계리감리 업무의 기초가 되는 계리가정보고서를 도입(’26.2Q)하고, 상반기중 정기감리에 착수하여 계리가정 적용 실태를 점검할 계획입니다. - 향후 모범사례(best practice) 전파 등을 통해 합리적이고 신뢰성 있는 보험부채 평가 업무관행이 확립될 수 있도록 지속 노력하겠습니다. - 1 - 1. 개 요 □ IFRS17 도입 이후 보험회사는 다양한 계리가정(손해율·해지율·사업비율 등)을 산출·적용하고 있는데, ◦ 계리가정이 불합리한 경우 이익의 과다인식*, 부적정한 상품 수익성 평가** 등으로 보험회사의 건전성을 훼손하고 소비자피해를 유발할 수 있습니다. * 계약기간이 장기간 지속되는 특성상, 계리가정의 소폭 변경에도 보험부채‧수익 등이 크게 달라짐(→ 예: 손해율 가정 1%p 축소시 보험손익이 5% 내외 증가 등) ** 예) ’24년중 단기납 종신보험의 낙관적 해지율 가정을 적용하여 수익성을 높인 후 경쟁적으로 판매 → 판매과정에서 ‘저축성 보험’ 오인 등 소비자피해를 초래 □ 이를 예방하기 위해서는 계리가정 전반에 대한 감독당국의 체계적인 분석·검증이 필요하다는 의견이 지속 제기되었는바, ◦ 금융감독원은 금년초 조직개편을 통해 방대하고 복잡한 계리가정에 대한 감리를 전담하는 조직* (‘계리감리팀’)을 신설하였습니다. * 보험부채 평가 관련 계리적 가정, 현금흐름 모델링 등에 대한 감리‧조치 등을 전담 2. 계리감리 업무 추진방향 - 2 - 1 감리의 범위 □ 보험부채 평가의 핵심요소인 계리가정, 현금흐름 모델링과 적정한 내부통제 운영 현황 등의 적정 여부를 중점 점검하고, ◦ 보험회사가 보험부채 평가시 보험업법상 건전성기준, 감독회계 및 기타 법규 등을 적정하게 준수하는지 여부를 확인할 계획입니다. <감리시 중점 점검 사항> ① (계리가정 산출) 계리가정 산출방법(추정·보정 등)의 합리성, 산출방법의 일관된 적용 등 계리가정을 산출하는 과정의 적정성을 점검 ② (계리가정 체계) 계리가정별 구분 단위 설정의 합리성, 사용중인 계리가정의 종류 등 계리가정 체계의 적정성을 점검 ③ (현금흐름 모델) 기초서류(약관, 산출방법서 등)에 부합한 현금흐름 추정 여부, 개별 현금흐름 추정의 합리성 등 현금흐름 모델의 적정성을 점검 ④ (내부통제) 계리가정 변경시 실효성 있는 내부통제 절차의 시행 여부, 현금흐름 모델 관련 내부통제 절차 존재 여부 등 내부통제의 적정성을 점검 2 세부 운영방안 가. 자료 입수 및 분석 [※단계] ①자료 분석 → ②감리 실시 → ③사후 조치 □ (개요) 다양한 내·외부 자료를 집적하여 보험회사의 계리가정 부정 위험을 식별하는 등 상시감시 활동을 수행합니다. □ (입수경로) 동 상시감시 활동에는 금융감독원 내부시스템, 계리가정 보고서, 업무보고서‧공시 사항, 제보‧민원 등이 활용될 예정입니다. 나. 감리 실시 [※단계] ①자료 분석 → ②감리 실시 → ③사후 조치 □ (개요) 정기‧수시감리 체계로 운영하되 감리 충실성 및 인력여건을 고려하여 적정한 수의 감리대상 회사를 선정합니다. ◦ 보험회사 자산규모 등에 따라 차등화된 감리주기 목표를 설정하여 운영할 계획입니다. - 3 - □ (정기감리) 감리대상은 정기검사 대상과 동일하게 운영하며 보험회사 계리업무 전반에 대한 종합적인 점검을 실시합니다. ◦ 정기검사시 계리감리팀과 검사국이 합동반을 편성하여 계리감리 및 책임준비금 분야 검사를 함께 실시할 예정입니다. □ (수시감리) 상시감시, 제보내용 등을 바탕으로 특정 회사 또는 항목을 대상으로 신속하고 정밀한 점검을 실시합니다. ◦ 서면감리를 원칙으로 하고 감리수행 결과 현장점검 필요시 조사 출장을 실시하거나 수시검사와 연계할 계획입니다. 다. 사후 조치 [※단계] ①자료 분석 → ②감리 실시 → ③사후 조치 □ (개요) 감리 결과 적발된 법규 위반행위의 경중에 따라 개선권고, 제도 개선 및 제재(기관‧인적) 등 합당한 사후 조치가 이루어질 예정입니다. <사후 조치 종류> ① (개선권고) 경미한 지적사항 또는 불명확한 위반사항에 대해서는 개선권고를 내리고 기한 내 변경 여부 등 확인 ② (제도개선) 업계 전반의 기준·가이드라인 마련이 필요한 사항은 관련부서 공유 및 학계, 업계 등 의견을 수렴하여 제도개선 추진 ③ (제재조치) 보험업법, 지배구조법 등 법규 위반사항 등에 대해서는 기관‧인적 제재조치 등을 엄정하게 부과 3. 기대 효과 □ 계리가정에 대한 정밀하고 체계적인 감리로 보험회사의 손익 왜곡과 수익성 과대평가를 통한 불건전상품의 설계‧판매를 방지할 수 있을 것으로 기대됩니다. ◦ 이와 함께 업계의 바람직한 보험부채 평가관행 확립을 유도하여 계리가정 산출‧관리의 고도화 등에 기여할 것으로 예상합니다. □ 또한, 시장참여자의 정보이용 효익을 제고하는 동시에, 보험회사의 단기 실적주의 문화 근절 등을 위한 시장규율(market discipline)을 강화해 나가는 계기가 될 것으로 기대됩니다. - 4 - 4. 향후 계획 □ (계리가정 보고서 도입) 계리감리 기반 마련에 필수적인 ‘계리가정 보고서’를 시범운영(pilot-test)을 거쳐 최종 도입*하겠습니다. * 시범운영 실시(1~3월) → 의견수렴 및 최종안 마련(4~5월) → 공식 시행(’26.2Q~) □ (정기‧수시감리 실시) 상반기중 정기감리에 착수하여 보험회사의 계리 가정 적용 실태를 직접 점검하고 법규 위반사항 등에 대해 사후 조치를 실시하겠습니다. □ (모범사례 설명회 개최) 하반기 설명회 개최 등을 통해 감리시 착안한 모범사례(best practice)를 전파하는 등 투명하고 신뢰성 있는 보험부채 평가 관행이 확립될 수 있는 기틀을 마련하겠습니다. 추진계획 일람 추진과제 ’26 상반기 ’26 하반기  계리가정 보고서 시범운영 및 도입 시범운영 및 의견수렴 공식 시행  정기감리‧수시감리 실시 정기‧수시감리 프로세스 진행  모범사례 설명회 개최 설명회 개최 ☞ 본 자료를 인용하여 보도할 경우에는 출처를 표기하여 주시기 바랍니다.(http://www.fss.or.kr) - 5 -

fileDown.do?menuNo=200218&atchFileId=1e597a5e366c4

Classification

Pipeline Progress

🔄 Pipeline Journey

🤖 How this summary was made

Full AI Instructions