Before you switch: demo questions and live tests to expose a QuickBooks‑sync stack
A practical checklist for contractors: demo questions, live trial tests, and migration mechanics to tell if a field app is the ledger or just syncing to QuickBooks.
Why this matters
There are two common architectures for field-service software: the app is the accounting system, or the app records jobs and syncs invoices, payments, and customers to QuickBooks where the ledger lives. The practical differences matter for migration, daily workflows, and how many manual steps your office will keep doing after the switch.
How the QuickBooks‑sync trap shows up in day‑to‑day work
- Timing and reconciliation pain: a sync means transactions you see in the field may not match the ledger until the next sync, and fixes often need duplicate edits in two places.
- Deletes and edits are risky: voiding or deleting an invoice in the field app can create orphaned transactions in QuickBooks or require a reversing entry in the ledger system.
- Payments and deposits: payments entered on the truck may post to a clearing account in QuickBooks and then need to be moved to the bank deposit. That step sometimes gets missed.
- Inventory and parts: parts used on a job in the field app may not flow into job costing or COGS in the ledger unless there’s careful mapping and reconciliation.
Use the online booking anchor to test whether the product is truly unified
If a vendor claims to be "all‑in‑one," test features that must read the single schedule the dispatcher uses. Trade Books' model gives a concrete example you can use as a probe: "The online booking page only offers time slots the dispatch calendar can actually take; it reads the same schedule the dispatcher sees."
Ask the vendor to do this live on the demo:
- Have them create a blocker on the dispatch board for a given day and tech, then show the online booking page to confirm that the blocked time slot disappears.
- Ask them to change a job address into a different service zone or move it outside a zone and show whether that address can still book online. If the system supports per‑zone booking caps, ask them to set a cap and show that the booking page respects that capacity without affecting phone bookings.
- While you watch, have someone submit a booking and confirm that "A slot is locked the moment a customer takes it, so two customers cannot book the same window." This proves the booking page reads the same dispatch calendar and enforces locks in real time.
If the vendor can’t run those live checks during the demo, or if online bookings appear to accept a slot and the dispatch board doesn’t show it immediately, that’s a red flag of a decoupled system or delayed sync.
Direct demo questions that reveal a sync‑to‑QuickBooks architecture
- "Where is the ledger?" — If the answer is "QuickBooks" rather than the field app, you have a two‑system stack.
- "If I change an invoice in the field app after it synced, what happens in QuickBooks?" — Ask for the exact sequence: is there an automatic update, a reversal, or a manual reconciliation step?
- "How do payments post and get deposited?" — Follow the flow: payment entry in the field app → held in a clearing account or directly applied in QuickBooks → bank deposit steps. Ask what you must do each day to match the bank.
- "If I delete a job or invoice in the field app, what does QuickBooks show?" — Have them demonstrate deleting and show both sides.
- "Who owns the canonical customer record?" — If both systems can edit customer data, ask how conflicts are resolved.
- "Where do parts leave inventory and how does COGS post?" — Get a live example: add a part to a job, invoice it, and watch the accounting side.
Trial tests to run yourself (do these the week of your trial)
Ask for a trial account with your data or use the demo data to run these checks. These tests don’t require accountant knowledge — just follow the steps and watch what changes where.
- Create a job, assign a tech and a time slot, and then view the dispatch board. Then open the app’s online booking page and confirm the same available time slot is shown.
- Book that slot as a fake customer. Confirm the slot locks immediately on the dispatch board and that a second browser can’t book the same window.
- Change the job address into a different service zone and test whether the online booking availability and per‑zone daily capacity are impacted as expected.
- Create an invoice from the job, record a payment on the truck, and then check QuickBooks (or the ledger view) to confirm the payment posted and where it landed. If it went to a clearing account, trace the deposit process.
- Edit the invoice in the field app after sync: change a line item or price, then watch the ledger. Does it update cleanly, or do you get a new credit and a new invoice?
- Delete or void a job/invoice in the field app and verify the accounting system’s record. Any orphaned items mean manual cleanups ahead.
Migration mechanics checklist (what your office should plan)
- Export open AR, unpaid invoices, customer records, and job history from your current system before cutover.
- Plan a final day of operations: freeze changes in the old system, run the last bank deposit reconciliation, and capture the closing balances you’ll import.
- Confirm how recurring jobs and maintenance contracts export and reattach in the new system. Ask about a plan for outstanding credits and retainers.
- Decide who will own fixes for data mismatches in the first month and schedule a daily short reconciliation routine until you see steady results.
- Test your payments flow end to end in the trial period: card and ACH capture, refunds, and how deposits are matched to bank statements.
What to do this week even if you aren’t buying
- Run the online booking checks on your current system: does your booking page really read the dispatcher’s calendar? Try booking simultaneously from different browsers to check locking behavior.
- Export a list of unsettled invoices and open customer balances so you know what the migration will need to bring forward.
- Write down your top three pain points that would be fixed if the field app were also the ledger (faster closes, fewer reconciliations, fewer duplicated edits).
Trade Books trial and pricing if you want to test a built‑in accounting route
If you want to try a platform that includes built‑in accounting, Trade Books has a 30-day free trial, no credit card required, and no contracts. Trade Books Starter plan costs $49/month (For solo contractors getting organized). Monthly only — Trade Books has NO annual plans. Trade Books Professional plan costs $149/month (For growing teams ready to scale). Monthly only — Trade Books has NO annual plans. Trade Books Enterprise plan costs $299/month (Full platform for established operations). Monthly only — Trade Books has NO annual plans.
Final decision rule
If your demo and trial answers show that day‑to‑day fixes require touching QuickBooks, or if payments and deposits need separate reconciliation steps outside the field app, treat that as a two‑system stack. That’s not inherently bad, but it means budgeting time for daily reconciliations and a more deliberate migration process. If the vendor proves bookings, dispatch, and payments update the ledger in real time and edits don’t leave orphaned transactions, you’re looking at a tighter single‑system workflow — and you can plan your migration accordingly.
Run the live tests above during demos and trials. The simple booking and lock checks that use the dispatch calendar and service zone rules reveal a lot about whether the product is built as one system or as a sync‑to‑QuickBooks stack.
If you want a checklist PDF you can take into demos, start with the trial tests section and the demo questions — they’re the ones that expose the most costly surprises during migration.