Welcome

Onboarding & import prep

A short, plain-English walkthrough for law-firm staff: how to move a PCLaw general ledger into QuickBooks Online with this app, what to check at each step, and how to roll it back if something looks wrong in QuickBooks.

Before you start — private beta guidance

Do not upload a full client ledger on your first run. Export a small slice of the GL covering one or two transactions and confirm it lands correctly in QuickBooks before sending the full file.
Always review the mapped accounts on the Map accounts screen before posting. A wrong mapping will post real journal entries to the wrong QuickBooks account, which has to be reversed afterwards.
Production mode posts to the real QuickBooks company. You will be asked to type IMPORT to confirm. Read the company name on screen carefully — that's the QBO company that will receive the journal entries.
Reversal is one-click but not invisible. QuickBooks shows reversed journal entries as new REV-… entries. The original lines stay in the Journal report; QuickBooks does not visually mark them as voided.

The full workflow

Export the PCLaw General Ledger as CSV. In PCLaw, run the General Ledger report for the period you want to migrate and save it as CSV. The file must include the columns listed in “Required columns” below.
Upload the CSV. From the dashboard, enter the firm/company name (must match the company in QuickBooks Online) and pick the CSV. The file is encrypted before any processing happens.
Review the import preflight. On the job page you'll see a preflight checklist: number of transactions, debit and credit totals, whether the file balances, and how many unique accounts were detected. Stop here if anything looks wrong — nothing has been sent to QuickBooks yet.
Map your PCLaw accounts to QuickBooks accounts. Click Map accounts on the job. You will see one row per account from the CSV; pick the matching QuickBooks Online account on the right. The import is blocked until every account is mapped.
Connect QuickBooks Online. Click Connect to QuickBooks. Intuit will ask you to sign in and pick the company that should receive the journal entries. The QBO company name is shown back on the job page so you can confirm before importing.
Confirm the production import. In production mode, the job page shows a final confirmation card with the QBO company name, the number of rows, and a text box. You must type IMPORT exactly to enable the post.
Import. Each PCLaw transaction posts as one QuickBooks JournalEntry. Duplicate protection runs first — if the same file or transaction ids were already imported into this QBO company, the import is blocked.
Verify in QuickBooks. Click Re-verify against QuickBooks on the job page to re-fetch every created entry from QBO and compare totals against the CSV. You can also open the QuickBooks Journal report and spot-check the entries by date.
Reverse if needed. If you imported into the wrong period, the wrong company, or with the wrong account mapping, open the job, scroll to Reverse this import, type REVERSE, and click the button. QuickBooks gets offsetting JournalEntries (DocNumber starting REV-) and the originals stay visible for audit.

Required columns

Your CSV must have these columns (case-sensitive). Any extra columns — description, reference, client_id, matter_id, customer_name, vendor_name — are kept but optional.

Column	What it means	Example
`transaction_id`	A unique id for the journal entry. Multiple rows with the same id form one balanced QBO JournalEntry.	`JE-0001`
`date`	Posting date for the entry, ISO format.	`2026-05-01`
`account_number`	The PCLaw account number. Used first for matching to QBO accounts.	`1000`
`account_name`	The PCLaw account name. Used as a fallback when the account number doesn't match.	`Operating Bank`
`debit`	Debit amount for this row, or `0`.	`1000.00`
`credit`	Credit amount for this row, or `0`.	`0.00`
`memo` (optional)	Free-text description copied into the QBO line description.	`Opening operating cash`

Download sample CSV template Download larger sample (multi-transaction)

The sample template contains two balanced demo transactions and is safe to upload — nothing reaches QuickBooks until you explicitly connect and confirm.

What we check before posting

The CSV has every required column.
Each transaction balances (debits == credits).
Every row has a date and at least one of account_number / account_name.
Every PCLaw account is mapped to a QuickBooks Online account.
QuickBooks is connected and the realm/company id is known.
The same file (by SHA-256) has not already been imported into this QBO company.
None of the transaction ids in the file have already been posted to this QBO company.
You have explicitly confirmed the production import by typing IMPORT.

If any check fails, the import is blocked and a beginner-friendly message is shown on the job page. Nothing is posted to QuickBooks until every check passes.

Need help?

Read the support page for common issues, or email support@pclawmigrate.com. Include the job id from the top of the job page and the exact flash message you saw — please don't paste raw ledger content or OAuth tokens.

Back to dashboard Go-live readiness QuickBooks connections