> ## Documentation Index
> Fetch the complete documentation index at: https://docs.frankieone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Trust Analyzer

> Extract trust structures from trust deeds and produce audit-ready, structured output for complex KYB onboarding using the FrankieOne Trust Analyzer.

<Callout icon="flask" color="#1A6CFF" iconType="regular">
  ##### Preview feature

  The Trust Analyzer is available through the API today. Portal screens for running, reviewing, and confirming a trust analysis are still being built, so drive the flow through the API for now. The endpoints below are stable, but response details may still change as the feature is finalised.
</Callout>

## Overview

Trusts are one of the harder entity types to onboard. The information you need lives in a trust deed, a long, free-form legal document that varies in layout from one trust to the next, and reading it by hand is slow and easy to get wrong. The Trust Analyzer does that reading for you.

It ingests a trust deed PDF, classifies the trust type, extracts the named parties (trustees, settlors, beneficiaries, appointors, protectors, SMSF members), and normalises their roles into a consistent structure. Every extracted value carries a reference back to the page of the deed it came from, so your compliance team can trace and verify each field.

The result is structured, audit-ready data you can review, correct, and feed into your KYB and KYC workflows. It lets you onboard trusts, and businesses that hold assets through trusts, at scale without adding the manual review effort that deeds normally demand.

<Callout icon="thumbtack" color="#1A6CFF" iconType="regular">
  ##### Access

  The Trust Analyzer runs as the `GLB-Trust-Analysis` workflow on the V2 platform. Contact your FrankieOne representative to have it enabled for your environment.
</Callout>

***

## How it Works

The Trust Analyzer runs as a step inside the `GLB-Trust-Analysis` KYB workflow rather than as a standalone endpoint. You upload the trust deed against an organization, execute the workflow, then retrieve, review, and confirm the extracted data. The flow follows a familiar analyze, review, confirm pattern, with a human confirmation step so a person signs off on the extracted structure before it is used for compliance.

<Steps>
  <Step title="Upload the trust deed">
    Upload the trust deed PDF as a `TRUST_DEED` document against the organization entity and keep the returned `documentId`. This is the document the workflow will analyse.
  </Step>

  <Step title="Execute the Trust Analysis workflow">
    Execute `GLB-Trust-Analysis` for the organization, passing the `documentId` via `executionVariables`. The trust type is detected from the document, so you do not supply it.
  </Step>

  <Step title="Track progress">
    The workflow runs asynchronously. Track the execution result until it reaches `REVIEW`, which signals that analysis has completed and the extracted data is ready to look at.
  </Step>

  <Step title="Retrieve and review the analysis">
    Fetch the analyses for the document. Each analysis includes the detected trust type and the extracted parties, with `references` that point back to the page in the deed each value came from.
  </Step>

  <Step title="Confirm, with corrections if needed">
    Review the extracted data, correct any field that needs it, then confirm. Confirmation records your accepted version while keeping the original analysis as an audit trail.
  </Step>

  <Step title="Associate the parties">
    Link the extracted parties to the focus organization so they form part of its ownership and control structure.
  </Step>
</Steps>

<Callout icon="code" color="#1A6CFF" iconType="regular">
  Ready to integrate? The [Trust Analyzer Implementation Guide](/docs/kyb/trust-analyzer-implementation) walks the full API flow step by step, with request and response examples for each stage.
</Callout>

***

## Supported Trust Types

| Trust Type                              | Detected value            |
| --------------------------------------- | ------------------------- |
| Discretionary (family) trust            | `DISCRETIONARY`           |
| Unit trust                              | `UNIT`                    |
| Self-managed superannuation fund (SMSF) | `SELF_MANAGED_SUPER_FUND` |
| Could not be classified                 | `UNKNOWN`                 |

Every analysis returns the details common to any trust (name, establishment, certification, and execution dates, trustees, and settlors). On top of that, the shape of `typeInformation` depends on the detected type:

* **Discretionary** (`discretionary`): specified beneficiaries, general beneficiaries, appointors, and protectors.
* **Unit** (`unit`): unit holders with their holdings (as a percentage or a unit count) and the total units on issue.
* **SMSF** (`selfManagedSuperFund`): the fund's members.
* **Unknown** (`unknown`): the reasons the trust could not be classified. Resolve these and set the correct type as part of your correction before confirming.

***

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="What document format is accepted?">
    The trust deed must be a PDF, uploaded as a `TRUST_DEED` document. Use a text-based (machine-readable) PDF: extraction reads the document text directly, so scanned or image-only deeds may not extract reliably. Documents are also subject to a page limit.
  </Accordion>

  <Accordion title="How long does analysis take?">
    Analysis is asynchronous and usually takes a couple of minutes. After executing the workflow, wait and poll the workflow result periodically until the analysis is ready; complex multi-schedule deeds can take a little longer.
  </Accordion>

  <Accordion title="Do I pass the trust type when I execute the workflow?">
    No. The only execution variable the workflow needs is `documentId`. The trust type is detected from the deed and returned in `type.detected`.
  </Accordion>

  <Accordion title="What happens if the trust type cannot be detected?">
    `type.detected` is returned as `UNKNOWN`, with the reasons under `typeInformation.unknown`. A trust type must be identified before you can confirm, so review the deed and set the correct type as part of your correction before confirming.
  </Accordion>

  <Accordion title="Can I correct the extracted data?">
    Yes. Send the corrected `documentInformation` to the [analysis confirm endpoint](/api-reference/organization/document-analysis-result-confirmation). The original analysis is retained as an audit trail and your confirmed version becomes the valid result. You can re-confirm later if further corrections are needed.
  </Accordion>
</AccordionGroup>

***

## Next Steps

* [Trust Analyzer Implementation Guide](/docs/kyb/trust-analyzer-implementation) — the full API walkthrough: upload, execute, retrieve, confirm, and associate parties.
* [Executing Workflows](/docs/kyb/executing-workflows) — how `executionVariables` are passed when executing a workflow.
* [Interpreting Workflow Results](/docs/kyb/interpreting-workflows-v2) — parse the full `workflowResult` object.
* [Managing Organizations](/docs/kyb/managing-organizations) — create and manage the organization entity before running the workflow.
* [Anti-Money Laundering](/docs/kyb/anti-money-laundering) — screen the parties extracted from the trust deed.