Buying guide / Trial
Accounting software: a practical trial checklist
Follow one transaction from its source document to the export.
By SaaS Ranking · Reviewed
Download the checklist (CSV)- 1. PrepareUse an invented month
- 2. ReconcileFollow a payment
- 3. ReviewTest separate roles
- 4. ExportRead the records back
Your working checklist
Ask these questions in your trial. Open a question to see the evidence to keep; use the CSV to record your answers.
ScopeWhich entity, currency, period and workflow are we testing?
Ask for: Agreed trial scope.
ImportWhat happens when we import the same item twice?
Ask for: Duplicate-import result.
MatchingCan we trace a partial payment and explain the remaining balance?
Ask for: Matched transaction and reviewer notes.
CorrectionsHow does a correction preserve the original record?
Ask for: Before-and-after record history.
PermissionsCan the operator and reviewer complete only their assigned tasks?
Ask for: Two-role permission test.
ReportsCan the reviewer reconcile the sample across the required reports?
Ask for: Dated sample report pack.
IntegrationsHow are a delayed feed and an unsuccessful sync shown?
Ask for: Connector failure and recovery test.
ExitCan a second person read transactions and attachments outside the product?
Ask for: Export files and read-back result.
The download includes blank answer, evidence URL, review date, owner, due date and decision fields. Complete them in your own spreadsheet.
Work through the review
Choose software with the person who will maintain the books. Build an invented month containing an invoice, a partial payment, a credit, a receipt and a period-end report. Agree what the reviewer expects to see before the demonstration. This is a software workflow test; local reporting, tax and retention requirements need a separate review for your organisation.
Make the sample contain an exception
A clean invoice and payment demonstrate only the simplest path. Add a duplicate import, an unmatched payment and a correction after approval. Ask the operator to show where each exception appears and how it is resolved. Keep the original source documents so the reviewer can distinguish the initial record from its correction. Record manual steps and any required add-on alongside the product plan.
Reconcile the same amount in several views
Follow the sample payment through the bank view, the customer account and the relevant report. Check the period and currency used in each view before comparing totals. Request an explanation for every difference. If the trial uses a live feed, establish how a disconnection or delayed import is surfaced. A working integration should make incomplete coverage visible rather than presenting a partial list as the complete month.
Test the operator and reviewer separately
Give one account the everyday bookkeeping task and another the review task. Attempt to change a payment reference, approve a correction and export the report using each role. Record who can do what and which event remains in the history. Ask your reviewer whether that separation fits the team. Do not infer a permission model from an administrator demonstration, since that account may bypass the limits ordinary users see.
Inspect the output before ending the trial
Export the sample transactions, contacts, reports and attachments that your team needs. Have a second person open the files outside the software and locate the invoice, payment and correction. Check identifiers, dates and source-document links separately. Keep a list of anything that requires a second export or an API. Estimate migration effort from a representative rehearsal, then retain the artefacts with the quote.
Source and scope
Xero documents inspecting how a statement line relates to a transaction. That is one concrete example of traceability. Our checklist asks buyers to test their own sample in each shortlisted product and makes no claim about another vendor’s capabilities.
Xero: view bank reconciliation details. Reviewed 2026-10-03.
Put the next step in your file
Compare public evidence for accounting vendors, then keep the source, date and your decision together.
Continue your review
SaaS proof of concept: a practical trial checklist
Run the same real task in each trial and keep a result your team can reproduce.
Read guide →8 questions · CSV includedSwitchSaaS exit plan: test your data export
Test whether an export can become a working replacement.
Read guide →