New Omni documentation is now available — policy-driven document verification and API reference. Explore Omni → · Custom Theme for KYC liveform: Learn more →
New Omni documentation is now available — policy-driven document verification and API reference. Explore Omni → · Custom Theme for KYC liveform: Learn more →
정책은 Omni 워크플로우에서 가장 중요한 부분입니다. AI 에이전트에게 무엇을 확인하고, 문서를 어떻게 평가하며, 언제 승인 또는 거부할지 정확히 알려줍니다. 잘 작성된 정책은 정확하고 일관된 결과를 생성합니다. 모호한 정책은 신뢰할 수 없는 출력을 생성합니다.이 가이드는 효과적인 정책 작성의 원칙을 다루고, 일반적인 사용 사례에 대한 템플릿을 제공하며, 정책 문구가 엔진 선택에 어떻게 영향을 미치는지 설명합니다.
[Objective]Verify the submitted [document type(s)] for [purpose].[Input Documents]Expected documents: [list of document types][Verification Steps]1. Extract [specific fields] from [specific document]2. Verify that [condition A]3. Check that [condition B]4. Cross-validate [field X] against [field Y]5. Screen [person/entity name] against [database/list][Decision Criteria]- APPROVE if [all success conditions]- REJECT if [any failure conditions]- FLAG for manual review if [ambiguous conditions]
이러한 정확한 섹션 헤더를 사용할 필요는 없습니다. 중요한 것은 정책이 네 가지 영역(목적, 입력, 단계, 결정)을 모두 다루는 것입니다. Omni는 서식이 아니라 의미를 분석합니다.
Verify the submitted business registration documents for corporate entity validation.Expected documents: business registration certificate, corporate registry extractVerification steps:1. Extract company name, registration number, incorporation date, registered address, and representative name from the business registration certificate2. If a corporate registry extract is provided, cross-validate company name and registration number between both documents3. Verify that the incorporation date is in the past and the registration has not expired4. Check that the registered address includes street, city, and country5. Screen the representative name against AML/sanctions watchlists6. Verify that all required fields are present and non-emptyDecision criteria:- APPROVE if all fields are consistent across documents, no AML matches found, and registration is valid and not expired- REJECT if AML screening returns a high-risk match (SAN-CURRENT, PEP-CURRENT) or the registration is expired- FLAG for manual review if AML returns a partial or medium-risk match, or if fields are inconsistent between documents
활성화되는 엔진: Text Verifier - Glove, AML Search - Person
인보이스 검증
Verify the submitted invoice for payment processing approval.Expected documents: invoice (PDF or image)Verification steps:1. Extract vendor name, vendor address, invoice number, invoice date, payment due date, line items (description, quantity, unit price, amount), subtotal, tax amount, and total amount2. Verify that all required fields are present: vendor name, invoice number, invoice date, at least one line item, and total amount3. Calculate the expected subtotal from line items (quantity x unit price for each) and check it matches the stated subtotal4. Verify that tax is calculated correctly based on the subtotal5. Check that the total equals subtotal plus tax6. Validate that the invoice date is not in the future7. Validate that the payment due date is after the invoice dateDecision criteria:- APPROVE if all required fields are present, all calculations are correct, and dates are valid- REJECT if required fields are missing, amounts do not add up, or the invoice date is in the future- FLAG for manual review if minor discrepancies exist (e.g., rounding differences less than 1%) or if any field is partially unreadable
활성화되는 엔진: Text Verifier - Glove
컴플라이언스 문서 확인
Review the submitted compliance document to verify regulatory requirements are met.Expected documents: regulatory license, compliance certificate, or permit documentVerification steps:1. Extract document type, issuing authority, issue date, expiration date, license/permit number, entity name, and scope of authorization2. Verify that all required sections are present: document header with issuing authority, body with license details, signature block, and date fields3. Check that the expiration date is in the future (document is currently valid)4. Verify that the entity name on the document matches the expected entity name5. Confirm that the license/permit number follows the expected format6. Check that the issuing authority is a recognized regulatory bodyDecision criteria:- APPROVE if all required sections are present, the document is not expired, entity names match, and the license number format is valid- REJECT if the document is expired, required sections are missing, or entity names do not match- FLAG for manual review if the entity name is a close but not exact match, or if the issuing authority cannot be verified
활성화되는 엔진: Text Verifier - Glove
문서 추출을 포함한 AML 심사
Screen individuals referenced in the submitted documents against AML/sanctions databases.Expected documents: any document containing person names (contracts, corporate filings,partnership agreements, board resolutions)Verification steps:1. Extract all person names mentioned in the submitted documents, along with any available identifying information (date of birth, nationality, role/title)2. For each extracted person, perform AML/sanctions watchlist screening3. Classify screening results by risk level: - High risk: current sanctions (SAN-CURRENT), current PEP (PEP-CURRENT), regulatory enforcement (REL) - Medium risk: linked to PEP (PEP-LINKED), former PEP (PEP-FORMER), former sanctions (SAN-FORMER) - Low risk: media reports (RRE), insolvency (INS)4. Summarize all screening results with person name, match status, and risk levelDecision criteria:- APPROVE if no AML/sanctions matches are found for any screened individual- REJECT if any individual has a high-risk match- FLAG for manual review if any individual has a medium-risk or low-risk match
활성화되는 엔진: Text Verifier - Glove (이름 추출용), AML Search - Person (심사용)
문제: Omni가 무엇을 검증해야 할지 알 수 없습니다. “Verify the document”는 어떤 필드를 확인해야 하는지, 무엇이 통과 조건인지에 대한 정보를 제공하지 않습니다.해결: 확인할 항목을 명시적으로 작성하세요.
# BadVerify the document and check if it is valid.# GoodExtract the company name, registration number, and incorporation date from thebusiness registration certificate. Verify that all fields are present, theregistration number follows a valid format, and the incorporation date is in the past.
결정 기준 누락
문제: 명확한 승인/거부 규칙이 없으면 AI 에이전트가 무엇이 통과 결과인지 추측해야 합니다.해결: 항상 정책 끝에 명시적인 결정 기준을 포함하세요.
# BadExtract invoice details and check the amounts.# GoodExtract invoice details and check the amounts.- APPROVE if all line item amounts sum to the stated total and all required fields are present- REJECT if amounts do not match or required fields are missing- FLAG for manual review if amounts match but optional fields are missing
문서 유형 미언급
문제: Omni는 예상되는 문서 유형을 알 때 더 나은 성능을 발휘합니다. 이 컨텍스트가 없으면 추출 정확도가 저하될 수 있습니다.해결: 정책 시작 부분에 예상 문서 유형을 지정하세요.
# BadCheck the submitted files for compliance.# GoodReview the submitted business registration certificate (PDF or scanned image)for corporate compliance requirements.
단일 정책의 과도한 복잡성
문제: 하나의 정책에 서로 관련 없는 너무 많은 검증 작업을 넣으면 AI 에이전트가 깔끔하게 실행하기 어렵습니다. 결과의 신뢰성이 떨어집니다.해결: 프로세스에 근본적으로 다른 유형의 확인이 포함되어 있다면 (예: 인보이스 검증과 직원 배경 심사) 별도의 워크플로우로 분리하세요.
# Bad - one policy doing everythingVerify the vendor invoice, check the vendor's business registration,screen all directors against AML lists, validate the vendor's insurancecertificate, and confirm their bank account details.# Good - split into focused workflowsWorkflow 1 (Invoice): Verify invoice amounts, dates, and required fieldsWorkflow 2 (Vendor KYB): Validate business registration and screen directorsWorkflow 3 (Vendor Compliance): Check insurance certificate and bank details
이 엔진은 정책에 제재 및 감시 목록 심사와 관련된 키워드가 포함된 경우 제안됩니다.트리거 키워드:
“AML”, “anti-money laundering”
“sanctions”, “sanctioned”
“watchlist”, “watch list”
“screening”, “screen against”
“PEP”, “politically exposed”
AML Search를 활성화하는 예시 문구:
"Screen the representative name against AML/sanctions watchlists""Perform AML screening on all directors""Check individuals against sanctions databases"
이 엔진은 정책이 문서 분석, 데이터 추출 또는 필드 검증 작업을 설명할 때 제안됩니다.트리거 키워드:
“extract”, “extraction”
“verify”, “validate”, “validation”
“check”, “compare”, “cross-check”
“match”, “consistency”
“present”, “missing”, “required fields”
Text Verifier를 활성화하는 예시 문구:
"Extract the company name and registration number from the certificate""Verify that all required fields are present""Cross-validate the address between the two documents""Check that the invoice total matches the sum of line items"
두 엔진을 동시에 활성화할 수 있습니다. 예를 들어, “extract company details” (Text Verifier)와 “screen directors against AML watchlists” (AML Search)를 모두 언급하는 KYB 정책은 두 엔진을 모두 올바르게 제안합니다. 워크플로우 생성 3단계에서 제안을 언제든지 수동으로 변경할 수 있습니다.