Find step-by-step product guidance by the job you are doing, then contact Balansix Support with the accounting context when you need direct help.
Search by the outcome you are trying to achieve, then follow the workflow from start to finish. The support centre is designed to speak the language of an accountancy practice rather than forcing accountants to translate their problem into software terminology first.
Set up the practice, users, roles, clients and first working cohort.
PMClients, engagement, recurring work, team, time and communications.
OCRClient uploads, record capture, review and document workflow.
BKBanking, ledgers, VAT, allocations, year-end schedules and reporting.
FASetup, mapping, disclosures, diagnostics and controlled finalisation.
CLPortal access, uploads, requests and practice-controlled visibility.
SCUsers, roles, MFA, client restrictions, read-only states and locks.
?Common browser, access, upload and workflow checks before raising a case.
If a transaction will not reconcile, an opening balance does not agree or an accounts-production output is not behaving as expected, tell us what you were trying to achieve and the accounting context. Support should not require you to pretend the problem is only a button problem.
Use the job-based guides for the standard workflow and the most common checks.
Browse guides →Include the relevant module, client context, period, what you expected and what happened.
Contact support →Where the issue depends on accounting treatment or workflow design, describe the underlying accounting position so the support response can address the real problem.
Raise a case →For a product or accounting-workflow issue, include enough information for the support team to reproduce the problem without asking you to start again.
Balansix Support should not need your password, one-time authentication code or another user's credentials to investigate a support issue.
Start with Getting Started, then follow the product guide that matches the first workflow you are implementing. For a phased migration, complete one representative client cohort before scaling further.
Include the client, period, transaction or balance, relevant workflow, expected accounting result and what Balansix produced. A screenshot is useful where the problem is visual or a message is shown.
No. Never send passwords or one-time authentication codes in a support request.
The Client Experience guide covers portal access, uploads, information requests and the separation between the client view and staff-only accounting controls.
Bring a real client workflow to the demonstration and compare how many handoffs, re-keying points and separate systems Balansix can remove.