iterate

for accountants · onboarding

Proposal accepted. Everything else just happens.

Onboarding a client takes most practices eleven manual steps across five systems: the AML check, the engagement letter, the ID verification, the practice manager, the folders. Connected properly, it runs itself - from "yes" to filed evidence in minutes of oversight, for every client you ever take on.

in plain terms

iterate connects your client onboarding end to end. A new client accepts your proposal, and from there the AML check starts itself, clearance sends the engagement letter for e-signature with ID verification, signing creates the client and jobs in your practice manager, and the folder structure and evidence file themselves in your document system. Your tools, your templates, your rules about what a human signs off. Every step logged.

See it on your stack → Everything else we do for accountants

the chain

Five systems. One flow.

01

Proposal accepted

From Ignition or your website. The trigger - the only manual part is the client saying yes.

02

AML check runs

The CDD case opens itself. When it clears, the chain moves on - and the report is already saved for the auditor.

03

Letter signed, identity verified

The engagement letter goes out for e-signature with ID verification, generated from your template with the right services in it.

04

Client & jobs created

The client appears in XPM or Karbon with the engaged jobs open - no re-typing, nothing missed.

05

Folders & evidence filed

The folder structure is created and the CDD report and signed letter land exactly where your auditor will look.

common questions

Answered straight.

Why doesn't our software just do this already?
Because onboarding crosses five different vendors - proposals, AML, e-signing, practice management, documents - and each one stops at its own edge. No single vendor sells the whole chain, so in most firms a person is the chain. Connecting it end to end is a build, and it only has to be built once.
Which tools does the chain work with?
The usual NZ practice stack: Ignition or a website form for the accepted proposal, First AML or your AML platform for the check, Annature for the engagement letter and ID verification, XPM or Karbon for the client and jobs, FYI or SuiteFiles (via its SharePoint) for the folders and evidence. Different stack? The chain is configured per firm - that's the point.
What does 'the evidence files itself' mean for our AML audit?
The CDD report and the signed engagement letter land in the client's folder, in the structure your auditor expects, the moment they exist - not when someone remembers. When the DIA review comes around, the trail is already where it should be.
How long does it take to set up, and what does it cost?
Fixed price, configured to your tools and templates, with your rules about what needs a human sign-off. Typically days of focused work. Every step is logged, and a person approves anything that matters - automation runs the admin, not the judgment.
Can we see it working before we commit?
Yes - we've built a working prototype of the full chain against sandbox versions of the tools, and we're happy to walk you through it live. It's clearly labelled as a prototype: the orchestration is real, the vendor accounts are stand-ins, and your version gets wired to your actual stack.

start here

How many clients did you onboard last month?

Multiply by an hour of admin each - that's the leak. A conversation costs nothing, and we'll show you the working prototype on the call.

Start a conversation →