← All use cases

New client setup · planned workflow

Accounting client onboarding that starts with the right information

Accounting client onboarding turns an agreed engagement into a usable client record. Apraxo is designing a guided way to gather service details, contacts, prior records, and open questions, then hand the reviewed information to the people who will do the work.

Request pilot access

The problem

A client record needs more than a name.

A new business client may send entity details in a form, prior statements by email, and an urgent deadline in a phone call. The team then has to reconstruct what it knows and what it still needs. The planned onboarding request gives each answer and file a place in the client record instead of leaving it scattered across channels.

How the planned flow works

From request to review

01

Identify the client and work

The firm creates an individual or organization client, chooses the service and staff assignment, and invites the appropriate contact. Apraxo’s requirements include linked contacts when one person represents several clients.

02

Collect setup information

The planned request can ask for business details, records, and service-specific questions. A signed-in client can complete the request over several visits.

03

Resolve open items

Staff review the returned answers and files, ask for missing information, and keep accepted material under the right client before a job proceeds.

Example request

What a new-client request could include

A firm can adapt this example to its engagement and its own security process:

  • Client and contact details, including the people who should receive requests
  • Services requested and the starting period
  • Prior-year returns or existing financial records when relevant
  • Entity details and bookkeeping system information for a business client
  • A question about outstanding notices, deadlines, or open items

A working example

A new business client

Illustrative status before the kickoff. This example shows how a firm could distinguish a document that has arrived from one it has actually reviewed.

The example covers information gathering. Engagement acceptance, identity checks, secure access to outside systems, and the firm’s compliance decisions remain separate steps.

ILLUSTRATIVE REQUESTA new business client
  • Entity and contact detailsAnswered by the client contact
    Received
  • Prior financial statementsRequested for the agreed starting period
    Missing
  • Prior-year returnUploaded; assignment needs staff review
    Review
  • Open notices or deadlinesFirm needs a yes-or-no answer
    Question
CLIENT VIEW

The contact sees only the setup items still assigned to them. If they return later, the planned portal preserves their progress and shows which questions remain.

FIRM VIEW

The assigned staff member sees the missing statements, the return awaiting review, and the unanswered deadline question before scheduling the next step.

The handoff

Give the assigned team a starting point.

The value is the handoff after collection: the reviewed answers and files stay attached to the right client, where staff can begin the actual engagement. The first pilot is tax-firm focused; broader practice workflows will follow the product roadmap.

Pilot scope

A clear view of what is planned.

Apraxo is recruiting a small tax and accounting pilot. Onboarding screens here describe the planned experience, not an already available public feature set. A firm should continue using its existing engagement and compliance process until pilot readiness is verified.

How we are approaching security →

Questions firms ask

Before you join

Can this replace an engagement letter?

No. This page covers collecting setup information. The firm should use its normal engagement-letter process; signing workflows are a separate part of the product plan.

Can one contact represent multiple clients?

The product requirements include linked contacts and a client switcher. We will confirm which parts are ready with each pilot firm.

Should clients send system passwords in the request?

No. This illustrative onboarding request does not ask for passwords or access codes. Firms should use their own secure connection or authorization process.