Integration is assessed during scoping. Availability depends on the product, version, subscription, API access and permissions. We confirm the supported read and write actions before quoting; a platform name alone does not establish that every workflow is available.
Using AI does not replace a registered practitioner's professional judgement. TPB guidance addresses competence, accuracy and client confidentiality when using AI. Your review process must suit the work and the risks; using an AI tool does not by itself establish compliance.
The project should document which information is processed, the selected providers, processing locations, retention, access and model-training settings. These depend on the services and configuration. Do not assume Australian hosting, a particular security certification or an absence of third-party processing without checking the agreed architecture and terms.
TPB guidance explains that, depending on how an AI tool operates, supplying client information can disclose it to a third party. Client permission is required for disclosure of client affairs unless there is a legal duty to disclose. Review the proposed information flows and explain relevant disclosures before using client data.
Some extraction, matching and checking steps may be suitable. Complex reconciliations, award interpretation, tax treatment and unusual transactions need a defined human review process. Test representative exceptions before enabling an automated action.
A scoped workflow can collect updates from selected official sources for review. A qualified person must assess relevance and approve process or rule changes. We do not promise automatic legal interpretation or continuous compliance.
Pricing is quoted after scoping the workflow, integrations, client volume, data requirements and support. Include ongoing software and usage fees when assessing the business case. The calculator on this page is an illustrative capacity model, not a price quote or a forecast of earnings.
Client information should remain separated under the agreed permissions and provider terms. Cross-client learning is not a default feature or an assumed benefit. Any proposed use of client information for model training needs a separate assessment of permissions, confidentiality and the selected service settings.
Timing depends on the workflow, access to systems, review requirements and pilot results. Agree training and acceptance criteria during scoping. Start with approved test material and confirm the process before introducing live client information.