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

# Changelog

> See the latest ezyshield updates, improvements, and platform changes.

<Update label="June 24, 2026" tags={["Feature"]}>
  ## Import your contacts in bulk

  Bring your existing payees into ezyshield in one step. Upload a CSV of contacts during onboarding or at any time from the contacts list, and ezyshield creates and queues them for verification automatically — no manual entry, no row-by-row setup. New customers can be fully operational minutes after signing up.

  ## Invoices without a valid ABN are automatically blocked

  Invoices that arrive without a valid ABN are now flagged as **Invalid** and stopped before any contact is created. Fraudulent and malformed invoices are caught at the door, keeping unverifiable payees out of your payment workflow rather than surfacing the risk only after the fact.
</Update>

<Update label="June 18, 2026" tags={["Feature"]}>
  ## Auto-correct recurring payee details

  When an invoice arrives with a name that differs from a contact you've already verified, ezyshield offers to auto-correct it. Opt in with one click and future invoices for that contact are aligned to the verified details for you — so recurring suppliers stop tripping the same avoidable mismatch. Turn it off again whenever you like.

  ## Re-verify a failed contact in one click

  When a contact fails verification, an **Auto-verify** option appears. One click updates the business and account name to the ABN's registered entity and re-runs the check — clearing common name mismatches without editing anything by hand.
</Update>

<Update label="June 1, 2026" tags={["Improvement"]}>
  ## Choose when to contact a payee for identity verification

  Adding or importing a contact no longer automatically texts the contact person to verify their identity. By default, only the account name check runs, confirming the bank account name matches the business or individual on the contact — without involving the contact person.

  A new **Verify identity** toggle on the contact person section puts you in control. When enabled, the contact person is asked to verify their identity with a government-issued ID and is notified by email and/or SMS to complete the process. This unlocks ongoing monitoring for AML, PEP screening, and sanction checks so you can confirm the individual is safe to pay and work with.
</Update>

<Update label="May 28, 2026" tags={["Feature"]}>
  ## Set how long verifications stay valid

  Set a verification expiry period for your organization. Once a verification reaches that age it's marked expired and your team is notified, so stale payee details surface for a fresh check instead of being trusted indefinitely.
</Update>

<Update label="May 26, 2026" tags={["Feature"]}>
  ## Account-only verifications (Confirmation of Payee)

  Create [verifications](/api-reference/verifications) with only bank account details when business or individual identity verification and correlation is not required.

  This gives API integrations a lighter Confirmation of Payee path for checking an account name, BSB, and account number, while keeping business and individual verification flows available when stronger payee correlation is needed.
</Update>

<Update label="May 20, 2026" tags={["Breaking Change"]}>
  ## Renamed Verification `checks` to `check_results` <Badge color="red">Breaking Change</Badge>

  The `checks` attribute on the [Verification](/api-reference/verifications) object has been renamed to `check_results` to reduce naming ambiguity between automated check logs and user-initiated [Check](/api-reference/checks) objects.

  ### Concept Clarification

  * `verification.check_results` is a historical record of the automated background checks run by the system during the initial verification process.
  * The [Check](/api-reference/checks) object represents a separate, ongoing monitoring check that you trigger after completion to ensure details haven't maliciously diverged.

  <Note>
    Make sure to update references from `checks` to `check_results`.
  </Note>
</Update>

<Update label="May 14, 2026" tags={["Feature"]}>
  ## Customize confirmation flow branding

  Upload your organization's logo in settings to align confirmation screens and portal pages with your company's branding.

  Featuring your brand identity during verification checks increases payee completion rates and establishes immediate trust, while maintaining a clean "Powered by ezyshield" footer.
</Update>