Kashoo
Key Info:
Kashoo is cloud accounting software for small businesses. The vendor documents browser-based accounting and a Kashoo mobile app, positioning the product for recording business finances and working with accounting information from desktop and mobile devices.
Details
Confirming the accounting model
Kashoo should be evaluated against the organisation's actual bookkeeping requirements before any data migration. Build a compact test set containing customer income, a supplier expense, a bank item, a correction and a report period. Confirm how accounts, categories, transaction dates and supporting evidence are represented. If an external accountant participates, test the hand-off and review workflow rather than relying on a general claim of accountant access.
Browser and mobile work
The vendor's mobile-app documentation makes mobile use relevant to the product, but teams should specify which actions can occur away from a controlled workstation. Test sign-in, a new transaction, a correction and the loss of access to a device. Check whether the same records and review controls are visible through browser and app workflows. Document device management, user removal, export and recovery requirements before rolling out mobile accounting to several people.
Data quality and rollout
Small-business accounting systems still need disciplined ownership of categories, opening balances and close procedures. Run an import rehearsal with duplicate contacts, incomplete dates and a balance that does not reconcile, then measure the correction process. Agree on the source of truth for customers, suppliers and bank data. Keep a written implementation record that covers permissions, retention, reporting cadence, support escalation and an exit path if the product no longer fits the business.
Decision record
Approval should depend on a reconciled pilot, not merely successful sign-in. Preserve a copy of the test records, report outputs and assumptions about mobile use, then have the accounting owner confirm that the process can be supported after launch.
Practical acceptance
The product is ready for broader use only when opening balances, transaction categories and report output have been checked by the responsible reviewer. Keep the pilot export and an exception log, then document the recovery steps for a failed import, lost mobile device or change in accounting ownership.
Review scenario
A useful Kashoo pilot contains a complete but small accounting cycle: opening balances, income, supplier cost, a bank movement, a correction and a report review. Test whether a user can identify an incorrect category and whether the reviewer can document the correction. Include a mobile-access change and an export check so the business understands both the convenience and the governance limits of the selected workflow.
Evidence to retain
Retain the opening-balance method, category rules, sample exports and the final reviewed report alongside the mobile-device policy. Note which person resolves bank or import exceptions and how access is removed. This compact evidence set helps a business continue the same accounting practice if staff or devices change after implementation.