Summarize know-your-customer documents for a compliance review

Summarize the know-your-customer (KYC) file below against our procedure, for {{reviewer}}, so that they can see in one place what the documents establish about the customer's identity, ownership and source of funds, what is missing and what does not match, before they make the onboarding decision. This summary records what the documents show; it does not decide whether to onboard the customer or what risk rating to give.

Our KYC procedure for this type of customer (required documents, ownership threshold, risk factors, escalation rules):
"""
{{procedure}}
"""

The customer file (application details and the content of each document, with document names and dates):
"""
{{customer_file}}
"""

Screening results from our tools (sanctions, politically exposed persons, adverse media), as reported: {{screening}}
Customer type and the product applied for: {{customer_type}}
Expected account activity, as stated by the customer: {{expected_activity}}

Produce:
1. Requirements table: one row for each requirement in our procedure, with the columns Requirement, Document provided, What it shows (names, dates and figures exactly as written), Status (met, partly met, missing, discrepancy).
2. Identity: names, dates of birth and addresses as they appear in each document, side by side, with any difference marked.
3. Ownership and control, for companies and other entities: each owner or controller named in the documents, their percentage and how it is held, against our procedure's threshold, and any link in the ownership chain with no document behind it.
4. Source of funds and wealth: what the customer says and what the documents show, kept apart, with each point marked "as documented" or "stated only".
5. Discrepancies: each one, with both versions and their documents.
6. Missing documents: what our procedure requires that the file lacks.
7. Risk factors: only factors listed in our procedure that the file shows, each quoted from the procedure with the evidence.
8. Screening: each hit as reported, and any information in the file that may help the analyst assess it, without deciding whether it is a true match.

For example, a discrepancy line might read: "Address: utility bill dated [date] shows [address A]; application form shows [address B]." That example shows the form only.

Keep the text outside the tables under 600 words. A good summary lets the analyst check every statement against a named document.

Rules:
- State only what the documents show. Do not infer source of wealth, a business purpose or the reason for a discrepancy.
- Use only the last four characters of any ID, passport, tax or account number.
- Do not treat ethnicity, religion, the sound or origin of a name, or other personal characteristics as risk factors. Apply country or nationality factors only where our procedure lists them, exactly as it defines them.
- Do not give an overall risk rating or recommend approval or rejection; that is the analyst's decision under our procedure.

If a document is unreadable, expired, or its date or issuer is not shown, mark it so in the requirements table rather than treating it as met. If the procedure does not cover this customer type, say so at the top and stop.