Fixed quote after a free call

Accounting client onboarding with engagement letters and due diligence built in

We build an onboarding workflow that starts the moment a proposal is accepted: it sends the right engagement letter for e-signature, requests identity, ownership and prior-adviser details through your portal, pulls public company records where they exist, compares them with what the client provided and assembles one file for the partner to review. A typical build costs $1,000 to $2,500 per workflow and takes about four to five weeks.

The problem

Why accounting client onboarding stalls

Onboarding is where a firm's checklist meets real life. The engagement letter sits unsigned, the identity documents arrive as phone photos in an email thread, and nobody is sure whether the previous accountant was ever contacted. Work starts anyway, because the client needs a return filed.

The obligations differ by country. In the UK, many accountancy services fall under the Money Laundering Regulations, which require identifying and verifying the client and any beneficial owners and understanding the purpose of the relationship. US firms face different rules, but still need a signed engagement and a defensible record of who the client is. Either way, the evidence needs to live in one place.

What we build

What our accounting client onboarding software includes

Onboarding triggered by the signature

An accepted proposal starts a tailored request based on client type: individual, sole proprietor, company, partnership or trust.

Engagement letter for e-signature

The right letter from your approved templates, sent through DocuSign or your proposal tool, with signed copies filed automatically.

Identity and ownership requests

Clear requests for ID and ownership details through your portal or the identity verification service you already use.

Public record comparison

For UK companies, officers and persons with significant control pulled from Companies House and differences highlighted.

Prior adviser hand-over

A drafted professional clearance or hand-over request for the partner to approve and send.

One file for review

Evidence, gaps and a draft risk summary in one place, with reminders on anything missing and an escalation if the file stalls.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Proposal accepted

    The signed proposal starts the onboarding request for that client type.

  2. 02 Automated

    Letter and requests sent

    The engagement letter goes for e-signature and ID and ownership details are requested.

  3. 03 Automated

    Evidence compared

    Uploads are matched to the checklist and compared with public records where available.

  4. 04 Staff review

    Admin checks the file

    The administrator chases gaps and confirms the file is complete.

  5. 05 Accountant or partner decides

    Client acceptance

    A responsible partner sets the risk rating and decides whether the firm takes the client on.

How it behaves

How engagement letters and onboarding behave

What each person sees and what runs in the background, including what happens when something goes wrong.

What the client sees

  • An engagement letter to sign on their phone or laptop
  • One clear list of what to upload and why
  • A reminder or two, then a call from the firm if they are stuck

What staff see

  • One file per new client with evidence and gaps listed
  • Mismatches with public records highlighted
  • An escalation when a file stalls

What the automation does

  • Picks the right letter and checklist for the client type
  • Files signed letters and uploads in the right place
  • Never sets a risk rating or accepts a client

Edge cases and fallbacks

Client signs the proposal but not the letter
Work items stay blocked and the partner is told.
Ownership details differ from the public register
Flagged for the partner; nothing is overwritten.
Client cannot upload documents
The checklist switches to a call or office visit and staff log the evidence.
E-signature or registry service unavailable
Requests are queued and retried, and the administrator gets an alert.

Architecture

Client onboarding for an accounting firm at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Signed proposal Services agreed n8n workflow By client type Engagement letter DocuSign ID and ownership Portal requests Public records Companies House Evidence check Gaps and mismatches Partner Risk and accept Client file Practice system
  • Input
  • Logic and services
  • Output
  • AI step
  • People
  • Data

How it flows

  1. 1 An accepted proposal tells the workflow which client type and services to onboard.
  2. 2 The engagement letter goes out for e-signature while identity and ownership details are requested through the portal.
  3. 3 Uploads and public records are compared, and gaps or mismatches are listed rather than resolved automatically.
  4. 4 The partner reviews the evidence, sets the risk rating and approves acceptance; the file is saved to the practice system.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Client onboarding, engagement letters & due diligence project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Client types, engagement templates, current checks, identity provider and where files are kept.

  2. 02

    Design

    About 1 week

    Checklists per client type, letter selection rules, comparison logic, escalation timings and retention.

  3. 03

    Build

    1 to 2 weeks

    E-signature, portal requests, public record lookups, evidence check and file assembly.

  4. 04

    Shadow run

    About 1 week

    New clients onboard through both routes while the partner compares the files.

  5. 05

    Launch

    1 to 2 days

    Switch on for all new clients and train the administrator.

  6. 06

    Support

    Ongoing

    New letter templates, rule changes and periodic review reminders.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n DocuSign eSignature REST API and Connect webhooks Companies House public data API (UK) Your client portal (TaxDome, Canopy, SmartVault or similar) Your identity verification provider Karbon, TaxDome or Canopy for the client record

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Client types, checklists, letter rules and retention.

    $250 – $500

  • Build

    Requests, evidence check, file assembly and escalations.

    $450 – $1,200

  • Integrations

    E-signature, portal, registry and practice system.

    $150 – $450

  • Testing and shadow run

    QA and parallel onboarding with partner review.

    $100 – $250

  • Launch and training

    Switch-on and administrator training.

    $50 – $100

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. E-signature, identity verification and portal subscriptions are billed to you by each vendor.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • E-signature: DocuSign or your proposal tool's own plan.
  • Identity verification: Your provider's per-check or subscription pricing.
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually) or €50 (Pro).

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

UK: customer due diligence

Regulation 28 of the Money Laundering Regulations 2017 requires identifying and verifying the customer and beneficial owners, understanding the purpose of the relationship and ongoing monitoring, scaled to risk. The firm decides; the workflow gathers evidence.

Source: www.legislation.gov.uk

US: electronic engagement letters

Under the E-SIGN Act a contract or signature cannot be denied effect solely because it is electronic; where consumer disclosures must be in writing, consent to electronic delivery is required first.

Source: www.law.cornell.edu

US: protecting client data

Firms that prepare tax returns are covered by the FTC Safeguards Rule and need a written information security plan, including oversight of service providers such as onboarding tools.

Source: www.irs.gov

EU and UK: identity documents are personal data

Every processor in the onboarding chain needs an Article 28 GDPR contract, and documents are kept only as long as your retention policy allows.

Source: gdpr-info.eu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Client onboarding, engagement letters & due diligence questions, answered.

Typically a signed engagement letter, identity details for the client and anyone acting for them, ownership details for companies, prior-accountant contact, access to the ledger and bank feeds, and the information each service needs. We build your checklist per client type so nothing is skipped.

No. It gathers and compares evidence and drafts a summary. A responsible partner sets the risk rating, decides on any extra checks and approves acceptance.

In the US the E-SIGN Act gives electronic signatures legal effect, and DocuSign has a documented API with webhooks for status. Rules elsewhere differ, so we follow what your professional body and local law expect.

No. We connect the provider you already use, or help you choose one, and file its results with the rest of the evidence.

Yes. Bookkeeping clients get their own checklist and questionnaire, such as bank feed access, chart of accounts preferences and payroll details, and the same file structure.

Days from signed proposal to complete file, share of files complete before work starts, and how many files stall waiting on the client.

Free 20-minute call

Want this for your accountant?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call