Annature changelog
AML & CTF Custom fields — XPM and FYI Elite
During our AML/CTF webinar series earlier this month, we ran a poll asking whether we should design our own custom fields to record AML/CTF status back into Xero Practice Manager and FYI Elite, or wait until these vendors themselves released a structured scheme for this data. The overwhelming majority of you asked us to move ahead now rather than wait.
Based on that feedback, we’ve drafted a set of custom fields that Annature will sync back into your Xero Practice Manager & FYI Elite client records. Before we start building the integration, we want to share what we’ve come up with and get your input - because you’re the ones who’ll be looking at these fields every day.
What we’re proposing to sync
The Verification fields already exist and are being used today. What's new are the AML & CTF fields. All fields are prefixed with [A] to make them easy to identify as Annature-synced fields in XPM.
Field | Description |
|---|---|
[A] AML & CTF Checked | Whether AML & CTF screening has been run for this client |
[A] AML & CTF Date | The date AML & CTF screening was most recently run |
[A] AML & CTF Outcome | The result of the screening check — Pass or Flagged |
[A] AML & CTF Outcome Notes | Details of any matches identified during screening (e.g. PEP, sanctions, adverse media) |
[A] AML & CTF PEP | Whether the client has been identified as a Politically Exposed Person, including PEP level |
[A] AML & CTF Risk Assessment | Whether a risk assessment has been completed and recorded for this client |
[A] AML & CTF Risk Rating | The client's assigned risk rating — Low, Medium, or High |
[A] Verified | Whether the client has been successfully identity-verified through Annature |
[A] Verified By | The Annature user who initiated the verification request |
[A] Verified Date | The date the verification was completed |
[A] Verification Method | The method used to verify the client's identity (e.g. Document Check) |
[A] Verification Notes | Notes recorded against the verification (e.g. Verified by Annature) |
[A] Verification Link | A direct link to the verification record in Annature |
A few things to know about the field names
The [A] prefix is new. Existing verification fields on your XPM connection don't have it, and we're not changing those — automations and reporting rules built on the current field names will keep working as they do today.
Going forward, the [A] prefix is the default for any new custom field we create — including the AML & CTF fields when you create them. If you'd rather not use the prefix, you can turn it off in your integration settings before creating the new fields. New connections created after this build will have the prefix on by default.
You can rename any of these fields in XPM to whatever suits your firm. When our integration creates a field in XPM, we store an internal ID against it — meaning we always know which field is which, regardless of what you rename it to. If you'd prefer "Client PEP status" over "[A] AML & CTF PEP", rename it. If your team has an internal naming convention, use it. We won't lose track of the field, and syncing will keep working exactly as expected.
To make this concrete, here's how the fields would appear on a client record — a clean pass on the left, and a flagged result on the right:
We want your feedback
Before we start building, we want to know what you think of the proposed fields — and whether we're missing anything.
Head over to our Feature Requests page and you'll find AML & CTF Custom Fields.
Upvote if the proposed field set looks right to you, or leave a comment if you'd like to see something added, removed, or reworked. The specific questions we're keen to hear on:
Are there fields here that don't make sense to you, or that you wouldn't use?
Are there fields missing that you'd want to see synced?
For the "Outcome Notes" field on flagged results — is the format we're showing useful, or would you prefer something more structured?
We'll be collecting feedback until 07 August before making a decision and starting the build.
— Corey