Appearance
Connect QuickBooks for Migration or Parallel Work
App path: Integrations or the client's QuickBooks integration detail.
Use this scenario when a client is moving from QuickBooks Online to Kraal, or when the firm wants a temporary parallel period while confidence builds.
Goal
QuickBooks is connected, synced, repaired where needed, and used as a trusted source only after Kraal verifies the baseline data.
Setup checklist
- Open the client.
- Open Integrations.
- Choose QuickBooks Online.
- Authorize the QuickBooks company.
- Confirm Kraal shows the connected company you expected.
- Run the first sync.
- Review imported:
- chart of accounts;
- customers and vendors;
- items and services;
- invoices and bills;
- payments and journal entries.
- Open the repair queue on the QuickBooks integration detail and resolve mappings, write-back issues, or missing accounts.
Migration proof checklist
- Run a Trial Balance in QuickBooks for the cutover date.
- Run the matching Trial Balance in Kraal.
- Compare cash, AR, AP, equity, income, and expense totals.
- Resolve material differences before treating Kraal as the operating record.
- Keep the proof in the client workpapers or close binder.
Parallel-run checklist
- Pick one month for the parallel run.
- Process the month in Kraal.
- Run P&L, Balance Sheet, Trial Balance, AR Aging, and AP Aging in both systems.
- Resolve connector exceptions before issuing reports.
- Decide whether to continue parallel work or cut over fully.
What good looks like
- The QuickBooks card shows a specific connection state.
- Exceptions link to the repair flow, not a generic error.
- Kraal reports tie out to the expected QuickBooks baseline.
- Daily Board surfaces QBO repair work when it blocks close or migration.
- Users understand whether they are in migration mode or parallel-run mode.