Evidence-first trust center

Trust signals for Australian tax practices evaluating Lodgeit.

This page maps Lodgeit's experience, expertise, authority, and trust evidence to visible implementation, official source trails, test coverage, and explicit ATO/SBR approval boundaries.

Last reviewed:

Approval boundary

Local implementation evidence is not ATO certification or production whitelisting. ATO-controlled conformance, credentials, and production approvals remain separate operator responsibilities.

Experience

Workflow evidence is tied to real tax-agent journeys: client requests, document collection, review, signing, ATO lodgement preparation, and practice operations.

  • Client portal request center has browser-smoke evidence for magic-link access, upload flow, and staff-link isolation.
  • Practice command centers surface BAS workload, review blockers, ATO job state, due dates, and next actions.
  • The product is built around Australian tax-agent workflows instead of generic document storage.

Expertise

The tax and SBR implementation is backed by local official artefact indexes, validation gates, tax calculators, and explicit EVTE guardrails.

  • Python SBR tier covers MAS-ST, ebMS3, XSD/VR validation, certificate parsing, and service registry resolution.
  • ATO artefact corpus indexes MST, VR, XSD, and guide metadata used by the runtime form and validation layer.
  • Tax engine coverage includes individual, company, trust, partnership, SMSF, BAS, IAS, FBT, FITR, STP, TPAR, depreciation, and schedules.

Authoritativeness

Claims are anchored to public regulator documentation, repository evidence packs, and versioned implementation notes.

  • ATO/SBR source versions and EVTE Product 37492 scope are documented in the repository.
  • OSF evidence maps controls to implementation files and tests rather than marketing statements.
  • Competitor workflow mapping is tracked in the repo so product-readiness claims stay evidence-based.

Trust

The public trust posture distinguishes implemented controls from external approvals and gives clear security, privacy, and support contact paths.

  • RBAC, MFA, encrypted sensitive fields, strict cookies, CSRF checks, audit trails, and PII redaction are implemented and tested.
  • Privacy, breach response, data-classification, cryptography, and vulnerability-management evidence is maintained in repo docs.
  • The Trust Center explicitly states that local evidence is not ATO production certification or whitelisting.

Repository evidence

What is implemented vs externally blocked

View repository
EvidenceStatusSummary
ATO EVTE Product 37492 evidence logEvidenceTracks registered interactions, blocked interactions, and support-confirmed scope.
OSF comprehensive evidence packEvidenceMaps operational-security controls to code, tests, and operating procedures.
Cryptography policyImplementedDocuments encryption, hashing, TLS, and SBR signature controls.
Data classification policyImplementedClassifies tax, identity, audit, document, and operational data by sensitivity.
ATO production whitelistingExternal dependencyRequires ATO-controlled conformance, whitelisting, and production credentials.

Contact paths

Trust improves when review teams and customers can reach the right owner quickly.

Security disclosures
security@cassandra.tax

Disclosures

  • This Trust Center is implementation evidence, not ATO certification, ATO endorsement, production whitelisting, legal advice, or tax advice.
  • Live ATO production access remains blocked until ATO-controlled conformance, whitelisting, credentials, and operator approvals are complete.
  • Security and privacy statements describe implemented software controls; production operators must still complete their own legal, privacy, OSF, and incident-response review.