Skip to content
English - Australia
  • There are no suggestions because the search field is empty.

Update: 30/08/2026

easyAML Updates

easyAML - Version 1.0.73, 1.0.74, 1.0.75 Release Notes

New features

  • Charities, associations and not-for-profits can sign up. Organisations with an ABN but no ACN (incorporated associations, charities, co-ops) get their own "Association / Not-for-profit" business structure in onboarding; they list their office bearers manually instead of a company search. Indigenous corporations (registered with ORIC) are a new dedicated entity type with their ORIC registration number and a Rule Book document slot. Charity (ACNC) registration can be recorded on any entity via the API for now — no screen for it yet — and is reflected in risk.
  • Where did this party come from? Every person or entity on a company structure now shows a Source pill — Registry (the government register), Document (read from a trust deed or company extract) or Manual — with a details panel showing the document, date, confidence and who confirmed it. Support note: records created before this release show it after a one-off data backfill is run per environment.
  • Refreshing registry data no longer overwrites document-sourced details. If the register disagrees with information that came from a deed or extract, the record is flagged as a "source conflict" instead of being silently overwritten. (Resolving the conflict in-app is behind a switch.)
  • Documents are protected once used. A document that produced extracted parties can't be removed or replaced while those parties exist — the user is told how many and can exclude/archive the parties first. Archiving any document now requires a reason, shown in the record's timeline.
  • Trust summary pages now use the same layout as other entities, and a trust with unreviewed screening matches now shows a "review required" banner (previously only sanctions/adverse-media hits did).
  • Labels management in Settings. Admins can see how many records use each label, rename or recolour it, and delete a label while moving its records to another. Applying labels day-to-day is unchanged.
  • Training reminders. Compliance officers get a "Remind" button on the Training Dashboard to nudge a staff member with overdue modules (email + in-app), limited to one reminder per person per day.
  • Custom transaction roles now save correctly when linking an entity to a transaction (this used to error). Custom roles need a plan that includes them.
  • Country risk expanded (1.0.75). Russia and 45 other previously unranked countries now score High (sanctioned/conflict countries such as Russia, Iran, North Korea, Syria) or Medium (offshore centres such as the Cayman Islands, Jersey, Bermuda). Applies to new and re-assessed records — existing ratings don't change by themselves until that person/entity/transaction is next refreshed or re-screened.
  • Smaller improvements: "New KYC" is a prominent button for people who haven't been verified yet; tidier spacing in the transaction edit form; the AI "Ask Amelie" industry helper now appears on sole-trader, partnership, SMSF and trust creation screens.

Fixes

  • Parties vanishing after sign-off. Shareholders/officeholders added after a transaction was signed off could disappear, and "Dismiss potential trust" could fail with an error — both fixed. Past signed-off versions are now clearly read-only.
  • "Pending" that should have been "Verified". People verified after a transaction sign-off now show Verified everywhere, including for firms searching to rely on that verification.
  • Screening that never started. Some people whose ID check completed were never screened (stuck on "Pending"). Refreshing the verification now runs screening; support has a bulk repair for existing cases.
  • Source of Wealth / Source of Funds documents. Files uploaded by clients during ID verification weren't displaying (after a change on our ID-check provider's side) or showed as raw file references — fixed. Cancelling a verification request now also cancels an attached SoW/SoF questionnaire, so it no longer shows as outstanding. Support: already-affected verifications need a refresh to pull the files; in some older cases the file can't be recovered and the client must re-upload.
  • Wrong number of ID documents requested (the client picked one document but was asked for the full set) — fixed. Verifications raised without an explicit choice now follow the account's defaults for documents, billing mode and question sets.
  • Notification scope. Some users received notifications for records outside their role's default scope (e.g. records they don't own). Delivery now follows the role default unless the user explicitly chose "all records". Expect "I'm getting fewer notifications" — intended.
  • Actionstep disconnects. Connections were being dropped by a timing issue or a temporary Actionstep outage; fixed, and a genuinely broken connection now shows a clear "Reconnect" on the Apps page. Firms already disconnected must click Reconnect once.
  • Company structures: a billing conflict during unwrap now produces a clearly "Blocked" task instead of a silent failure; the paid "Refresh registry data" button is disabled while a refresh is already running; "Cancelled" added to the task filter.
  • Split billing tab no longer appears for enterprise customers who don't use split billing.
  • Police-check wording: results with disclosable court outcomes now read "Disclosable Court Outcomes / Review required" (amber) rather than "Not Passed" (red) — it's information for the officer to review, not a failed check.