P
ProDeskCPA Docs
Help center for firms + clients
All articlesBack to appContact Support
DocsStandard Operating ProceduresOnboard a New Accounting Client
Onboard a New Accounting Client

PURPOSE

End-to-end procedure for onboarding a new monthly bookkeeping client through to "Go Live" — first regular monthly close. Onboarding is folded INTO the Monthly Close pipeline as 5 entry stages (per latest design intent), not a separate module.

WHEN TO USE

- New accounting client signs EL for monthly bookkeeping services - Client transitioning from another platform (TaxDome, Karbon, etc.) — use bulk import path - Firm taking over a client mid-year (cleanup phase preceded)

ROLES INVOLVED

- Primary owner: Accounting Manager - Bookkeeper: assigned to recurring monthly close - Engagement Partner: signs EL, signs off on cleanup if applicable - Client: provides accounting software access OR documents

PREREQUISITES

- EL signed (covered in main client onboarding flow); cleanup advance paid if applicable - QBO or Xero connected at firm level (M-021) — per-client OAuth happens during onboarding - Password Vault unlocked + master password set up for the bookkeeper (M-027) - Folder template ready (system auto-creates per Module 30 structure on engagement creation)

PROCEDURE

1. After EL signed, accounting engagement auto-created; lands in "Access to Accounting Software" stage (5-step onboarding folded into Monthly Close pipeline — M-020) 2. Stage 1 — Access to Accounting Software: ask client to connect QBO/Xero via OAuth, OR provide read-only login credentials 3. If OAuth: client clicks Connect → grants access → Realm ID / tenant ID stored on engagement; if credentials: bookkeeper adds login to Password Vault (M-027), tagged to this client + taskType "preclose" 4. Stage 2 — Initial Requirement List (IRL): bookkeeper builds IRL with 6 account types (Bank / Investment / CC / Loan / Payroll / POS Clearing) per the client's actual chart of accounts 5. For each IRL item, ask client preference: "Upload documents" OR "Provide read-only bank access" — for the latter, fetch big-USA-bank instructions library and surface them 6. Read-only access path → create staff task to add login + add to Vault; "View in Vault" link auto-appears on Pre-Close item 7. Upload path → create RECURRING task with email reminder every 3 days 8. For Amortization Schedule items: client uploads ONCE, stays as recurring attachment, task auto-marked complete every month 9. Stage 3 — AI Review: run AI Anomaly Detection (M-023) on cleanup period or initial GL → 10-section AI Accounting Review output with risk rating, ratio analysis, coding error detection, audit risk flags 10. Stage 4 — Manual Review: bookkeeper + manager review AI findings; correct miscoded transactions; approve/reject vendor merges; send unresolved questions to client via Final Review tab (portal + Excel email dual delivery) 11. Stage 5 — Go Live: confirm bank rec balanced, all FS Group mapping complete, no unmapped accounts; first monthly invoice generated; recurring billing set up 12. After Go Live, on the LAST DAY of each month system auto-creates next month's close in "Submitted" stage; ongoing operation follows SOP-004

DECISION POINTS

- If client has cleanup work: charge advance per EL Annexure (separate fee from monthly), complete cleanup BEFORE Go Live; cleanup is "Implementation" folder which is OUT-OF-YEAR (M-030) - If client has multiple entities: each entity = separate Client record (NOT one client with many entities); design intent: inter-entity balance reconciliation flagged in accounting flow - If client refuses bank access AND won't upload: cannot proceed; escalate to Partner; pause engagement until resolved - If accounting frequency is Quarterly / Yearly / Custom: same 5-step onboarding but recurring close cadence adjusts

EDGE CASES

- QBO Desktop not supported (no OAuth API): convert to QBO, OR import IIF/CSV manually, OR migrate to Xero - 2FA on client's accounting software: store TOTP secret in Vault (M-027); auto-rotates 6-digit codes - One QBO company linked to multiple engagements (e.g. multi-year audit on same entity): allowed, but each engagement holds its own qboRealmId for safety - Client logs out / revokes access mid-month: Integration status flips to "expired"; alert bookkeeper; re-OAuth needed - Big-bank read-only access: instructions library pre-loaded for major US banks; for small/credit union banks, may need to provide instructions manually

KPIS / QUALITY CHECKS

- Time from EL signed → Go Live: target 14-30 days (depends on cleanup scope) - IRL items at 100% before Go Live (no items in "Outstanding" status) - Unprocessed folder empty every day (operational SLA per Module 30) - First month bank rec balanced on first attempt (no AJEs needed) — quality signal for IRL completeness

RELATED MODULES & SOPS

- Modules: M-040 Onboarding · M-020 Monthly Close · M-021 QBO/Xero · M-027 Password Vault · M-009 Tasks · M-023 AI Anomaly · M-007 Client Portal · M-030 Storage · M-010 Billing - SOPs: SOP-004 (monthly close pass) · SOP-009 (handle PBC/document escalation) · SOP-010 (integration setup) · SOP-008 (portal lock if invoice unpaid)

NOTES

- Discovery + EL phases were REMOVED from accounting onboarding (handled at signup level); this SOP picks up post-EL - Closed-year folders are LOCKED from edit/delete + marked "Closed" — applies after year-end (M-030) - Reports module functions are FOLDED into Monthly Close per-client; standalone Reports module covers cross-client lens (M-029)
Still need help?
Email our support team — we reply within 24 hours.
Email Live chat
ProDeskCPA — Practice Management for CPA Firms