Vendor Demo Questions for Bookkeeping Software

The best vendor demo questions for bookkeeping software make the tool run on your files, not the vendor's. Bring three or four real client statements, ask what happens when one fails, ask what counts against your plan, and ask how data leaves the system. Score every answer the same way so two demos can be compared afterwards.

Preparing your own statements before a vendor demo

Preparing for a vendor demo means choosing a small set of your own client statements that show the problems your practice actually has. Send them ahead and ask the vendor to run them live. A demo on the vendor's sample files proves only that the sample files work.

Pick files that cover the range of your client list rather than your easiest client:

• A clean digital PDF from a large bank, as a baseline.
• A scanned or photographed statement, because some clients still send paper.
• A credit card statement, which often prints no running balance.
• A long statement with many pages or a statement period that crosses a month end.
• One awkward file, such as two accounts in one PDF or a statement with a page missing.

Remove or mask anything the vendor does not need. Account numbers can be cut to the last four digits, and you can ask the client's permission or use your own firm's statements if you prefer not to share client data with a company you have not signed with yet. Ask the vendor how demo files are stored and when they are deleted, and note the answer.

Write down what you expect from each file before the demo: the number of transactions, the opening and closing balances, and two or three lines you know are hard to code. You can then check the output on the spot instead of trusting the screen.

Who should attend

Bring the person who will run the tool every month, not just the person who signs. A team member who closes ten clients a month will notice slow screens and awkward review steps that an owner watching for ten minutes will miss.

Which demo questions expose statement failures?

Demo questions that expose statement failures ask the vendor to show a file that does not convert cleanly, and what the tool does about it. Every tool fails on some statements. The question is whether it tells you clearly, holds the file back, and lets you fix it, or exports wrong numbers without a warning.

Ask these during the live run:

1. "Show me a statement that failed. What does the screen say, and what do I do next?"
2. "How does the tool know a statement converted correctly? Does it check the opening balance plus transactions against the closing balance?"
3. "What happens to a statement with a missing page?"
4. "If a description wraps onto two lines, does it come back as one line or two?"
5. "Where do transactions go when the tool is not sure of the category?"

A good answer to the second question describes a balance check that stops a bad statement from being exported. A vague answer about accuracy rates is not the same thing, because a rate tells you nothing about which statement is the wrong one. For your own baseline, AutoBankConvert checks that the opening balance plus the transactions equals the closing balance before a statement is marked done, and flags it otherwise.

If you are replacing a current converter, ask the vendor to run a file your existing tool handles badly. The guide to switching bank statement converters covers how to plan the move once you have chosen.

Demo questions about client limits and plan edges

Demo questions about plan limits find out what you pay for and what happens when you outgrow it. Ask what a plan counts, whether it is statements, pages, clients or users, and what happens on the day you cross the line. Busy months matter most, so ask about a January catch-up rather than an average month.

Questions that surface plan edges:

• "What exactly does the plan count, and how is a 40-page statement counted?"
• "What happens when I go over in one month? Does conversion stop, slow down or bill extra?"
• "Can I add a client for one month of catch-up work and then remove them?"
• "How many people in my firm can log in, and can each have different rights?"
• "Does each client keep its own rules and history, separate from every other client?"

The last question is about safety as much as price. A practice runs many sets of books, and a rule written for one client should never change another client's coding. Ask the vendor to show two clients side by side and change a rule in one.

Write the answers down word for word where you can. A price page can change, but notes from the call give you something to point to later.

Export and exit questions for the software demo

Export and exit questions check that data gets into each client's ledger in a form it accepts, and that you can take your data with you if you leave. Ask to see an export opened in the actual ledger, not a file name on a screen. Then ask what you can download on the day you cancel.

Getting data into the ledger

• "Which accounting systems can you export to, and in which file formats?"
• "Can I export one client, or every client in a batch, in one step?"
• "Show me the export imported into the ledger my clients use."
• "If my client uses a desktop ledger, what file do I get?"

Integration claims vary a lot between vendors, and "works with" can mean anything from a live connection to a spreadsheet you reformat by hand. The post on bookkeeping software integrations covers how to read those claims.

Getting data out when you leave

• "Can I download every converted statement and every rule I wrote?"
• "How long do you keep my files after I cancel, and can I ask you to delete them sooner?"
• "Are my categorization rules exportable, or do they stay in your system?"

A vendor that is relaxed about these questions is usually confident in its product. One that changes the subject is telling you something about the cost of leaving.

How should you score a vendor's demo answers?

Score a vendor's demo answers with one sheet used for every vendor, giving each question 0, 1 or 2. Zero means no answer or a deflection, one means a verbal answer with nothing shown, and two means the vendor showed it working on your file. Fill the sheet in during the call, not from memory afterwards.

An example scoring sheet

The scores below are made up for two unnamed vendors, to show how the tally works.

Vendor B gave a pleasant demo, and it handled the scan better. But it showed nothing on exports and dodged the exit questions, so the score drops well below Vendor A. The sheet makes that visible in a way a general impression does not.

Follow the demo with a trial

A demo score is a filter, not a decision. Take the top one or two vendors into a trial on a full month of a real client, and compare the export against the books you already closed. If you are deciding for a firm with several staff, the guide to bookkeeping software for accountants lays out how statement tools fit with the rest of a firm's stack.

Demo red flags that a sales script hides

Demo red flags are habits that suggest the product is weaker than it looks. The most common is a vendor who will not run your files, followed by answers that turn every limit into "we can work something out". Others show up in how setup and onboarding are described.

Watch for these:

• Your files "will be processed later". If a tool cannot run a normal statement during a call, find out why before you trust it with a month end.
• Only percentages. "99 percent accurate" without saying how errors are caught means you will be the one catching them.
• No answer on failures. Every product has statements it cannot read. Not knowing what happens to them is a gap in the product or in the salesperson.
• Setup that sounds free of effort. Moving a client in takes work: their accounts, their chart of accounts, their past coding. A vendor who says otherwise has not done it at scale.
• Pressure to sign before a trial. A discount that expires in a day is a reason to slow down.

The onboarding point deserves its own follow-up. Ask the vendor to walk you through adding one new client from scratch, then compare those steps with your own bookkeeping client onboarding checklist to see what the tool handles and what stays with you.

If you want to try these questions on a statement tool, request an AutoBankConvert setup; it onboards firms in small groups and replies with a setup time.