Data ownership and reconciliation when switching field service software
Practical checklist for contractors: migration mechanics, demo questions that reveal a two‑system QuickBooks stack, and a hands‑on trial script to verify accounting, payments, and job costing before you switch.
Why architecture matters: built‑in accounting versus a QuickBooks sync
When you shop for field‑service software you’re really choosing where your books live. There are two common architectures: the app owns jobs and also owns the general ledger, or the app runs jobs and then syncs transactions into QuickBooks. Both can work, but they have different migration mechanics, daily workflows, and reconciliation burdens. Choose with your eyes open.
Practical differences you’ll feel in day‑to‑day work
- Timing of transactions — With a sync you often get a delay or a handoff where invoices and payments must move into QuickBooks before they affect reports. With built‑in accounting the job, invoice, payment and GL update happen in one place.
- Reconciliation headaches — Syncs can create mismatches: payments posted to a holding account, invoices duplicated, or unapplied credits. Reconciling bank deposits and job revenue becomes an extra step.
- Job costing integrity — If parts, labor, purchase orders and payroll don’t post to the same ledger from the same system, your job cost reports will need manual reconciliation to be reliable.
- Support and fixes — With two systems you may be bounced between the field‑app vendor and your bookkeeper or QuickBooks support when things go wrong. That costs time and sometimes money.
Migration mechanics: what actually moves and what often gets left behind
Before you switch, insist on a clear answer about which of the following will migrate automatically, which will need manual work, and which are not supported:
- Customer records, service addresses, open jobs and closed jobs with line‑item history.
- Invoices, payments, unapplied credits and customer statements.
- Chart of accounts mapping and historical GL entries.
- Vendor bills, purchase orders and inventory quantities or stock locations.
- Payroll history and labor allocations to jobs.
- Open credits, refunds, and deposit batches waiting to be banked.
Ask for a sample export from the vendor and run a quick import to make sure fields line up. Exports nested in PDFs or screenshots are useless; insist on CSV or native data formats.
Direct demo questions that expose a two‑system QuickBooks stack
Use these exact, specific questions on your next demo. If the answers are vague, expect extra work after launch.
- "Do jobs and the general ledger live in the same database, or do you send journal entries to QuickBooks?" If they say 'we sync to QuickBooks' or 'we post to QuickBooks', probe for details.
- "Is the sync one‑way or two‑way, and how often does it run?" Be wary of batch or manual syncs that require user action to push data.
- "Show me a live example: create an invoice, take a payment, and show me the resulting GL entries." Watch whether the app itself shows the GL entries or if the entries only appear in QuickBooks.
- "What happens to payment deposits? Do they land in an undeposited/clearing account that must be banked separately in QuickBooks?" This is a common source of reconciliation work.
- "Who resolves a sync error, and what is the SLA for fixing it?" Errors are inevitable — the vendor should own or clearly hand off responsibility.
- "Can you undo or roll back a batch if there is a mapping mistake?" Rolling back is rare; ask how they correct mistakes without duplicating entries.
- "Can I get a full export of my GL and job history as CSV, including account codes and memo fields?" If the vendor says no, you will lose portability.
Hands‑on trial script to run before you flip the switch
Run these tasks during a trial so you can see the real behavior — not just screenshots. Use test customers and a test bank account. This handheld script has a dozen checks that catch the common breakpoints.
- Create a new customer with service address and contact. Verify the same record and address appear in the accounting view or GL export.
- Create a job, add line items for parts and labor, and assign a price book item. Save and check the job history export.
- Generate an invoice from that job. Inspect whether an accounting journal or invoice rows are visible inside the app immediately.
- Take a payment on the invoice. Verify where the payment is recorded and whether it posts to a clearing account or directly to the bank account in the ledger.
- Deposit that payment to bank in the app, then compare to bank deposit records in the accounting export or QuickBooks sync.
- Record a refund or credit and ensure it reduces AR in the same ledger where the invoice lives.
- Create a vendor bill and pay it. Confirm the vendor bill and payment post to the same ledger as job costs.
- Run a job cost report and a profit by job report in the app. Cross‑check those numbers against the exported GL entries for the same period.
- Create a payroll entry or a labor allocation to a job and check that labor cost posts to job cost in the same system.
- Export the chart of accounts and journal entries. Open them in a spreadsheet and check for missing memos or unmapped account codes.
- Introduce a deliberate mapping change (like reassigning an income account) and watch how the system handles historical entries.
- Ask for a sample rollback or correction flow for a duplicate invoice pushed to QuickBooks. Time how long it would take to resolve.
Red flags that mean you’ll be running two systems
- Demo answers that centre on "we sync to QuickBooks" without showing accounting entries inside the field app.
- Support language that shifts blame: "that looks like a QuickBooks issue" when you ask about revenue or deposits.
- Payments land in an undeposited or clearing account that needs manual deposit work in QuickBooks.
- Reports in the field app and reports in QuickBooks don’t match without a reconciliation step.
- Vendor or payroll costs are recorded in a different system than invoices and payments.
What to demand from any vendor before you commit
- Sample data exports in CSV for customers, jobs, invoices, payments, vendor bills and a full GL.
- A documented migration plan with responsibilities and estimated timelines.
- Clear support ownership for sync errors and a rollback/correction procedure.
- Access to a live trial that lets you perform the hands‑on script above with no restrictions.
A note on Trade Books' plans and trial
Trade Books Starter plan costs $49/month (For solo contractors getting organized). Monthly only — Trade Books has NO annual plans.
Starter plan includes up to 1 user.
Trade Books Professional plan costs $149/month (For growing teams ready to scale). Monthly only — Trade Books has NO annual plans.
Professional plan includes up to 10 users.
Trade Books Enterprise plan costs $299/month (Full platform for established operations). Monthly only — Trade Books has NO annual plans.
Enterprise plan includes up to 50 users.
Trade Books has a 30-day free trial, no credit card required, and no contracts.
Trade Books is flat monthly pricing with no per-truck or per-user overage fees within plan limits.
Final note: pick the workflow you want, then verify it
Some contractors prefer a best‑in‑class field app plus QuickBooks because of familiarity or an existing bookkeeper. That’s a valid path, but it comes with predictable migration and reconciliation work. If you want fewer handoffs and cleaner job costing from day one, demand to see accounting entries inside the same system during your demo and run the trial script above.
When you run a session with both the vendor and your bookkeeper, have them walk through the script together. If the vendor can export clean CSVs, map your chart of accounts, and demonstrate a safe correction flow, you’re in a good position to decide. If they can’t, ask for a written plan for the extra work you’ll need to budget for after go‑live.
Ready to try a single system with built‑in accounting? Start a trial or see pricing on our site.