XIntelliSync Learn Centre
Eight compliance regimes. Forty-three cornerstone pages. One honest connection map.
Most SaaS publishes a blog. We documented the regulatory landscape every Australian SMB has to navigate — then tagged every cluster with what XIntelliSync actually does in that domain. No closest-match invention. No fabricated capabilities. The page tells you upfront whether XIntelliSync IS the product, PREPARES the artefact, is SUBJECT-TO the regime, or USES it as a downstream consumer.
The four honest connection classes
Every cluster tells you upfront what XIntelliSync does and does not do.
Most platforms describe every regime as if they handled it end-to-end. We refuse. Each cluster below carries one of four class tags — and the tag is enforced against the real agent catalogue at build time.
XIntelliSync IS this. The page describes the platform itself.
XIntelliSync prepares the artefact. You lodge / authorise externally. We refuse to fake either.
XIntelliSync prepares the adjacent inputs (e.g. wage data driving workers-comp premium). The duty-holder responsibility stays yours.
XIntelliSync prepares the financial statements. The director-level lodgement and statutory filings stay yours.
XIntelliSync is itself bound by the regime — and so are you. Platform-side enforcement is on us. Customer-side stays yours.
XIntelliSync uses the regime infrastructure as an accredited-partner consumer. Read-only, one direction, no shortcuts.
The eight cornerstone clusters
Each pillar is the cornerstone. Each spoke is a deep-dive.
Eight pillar pages. 34 spoke deep-dives. One standalone positioning page. Every cluster card below shows the connection class, four to six spokes, and a one-sentence anchor stating what XIntelliSync actually does in that domain.
AI Verification
IS THE PRODUCTThe four-system Trust Stack: IntelliX Omega + Horizon + XAVS + XGVS.
What XIntelliSync does — This page describes the XIntelliSync verification engine itself — documented publicly because the alternative is asking you to trust an AI black box with your TFNs and BAS lodgement.
Spoke deep-dives (6)
Payroll Compliance Australia
PREPARES121+ Modern Awards · STP Phase 2 · 12% Super · Payday Super · ABA payment file.
What XIntelliSync does — 11+ payroll-cluster agents prepare STP, super, and the ABA file. The ATO does the lodgement; your bank does the payment. We refuse to fake either.
Spoke deep-dives (4)
BAS / GST / TPAR Compliance
PREPARESBAS quarterly cycle · GST classifications · TPAR contractor reporting · ATO Business Portal.
What XIntelliSync does — 5+ tax-cluster agents prepare BAS, GST summary, and TPAR for ATO Business Portal lodgement. We are not a registered ATO Digital Service Provider — the lodgement step stays yours.
Spoke deep-dives (4)
Privacy Act / APP / NDB
SUBJECT-TO13 APPs · $3M turnover threshold · Notifiable Data Breach · Privacy by Design.
What XIntelliSync does — XIntelliSync IS an APP entity. XGVS gates Privacy Act + APP + NDB on every action. We hold the data; APP 11 reasonable security is enforced gate-by-gate. Section 26WK NDB lodgement stays your obligation.
Spoke deep-dives (4)
Workplace Health & Safety Australia
PREPARES (BOUNDARY)WHS Act 2011 · workers compensation · notifiable incidents · industry Codes of Practice.
What XIntelliSync does — XIntelliSync's payroll cluster generates the wage data your workers-comp insurer rates against. WHS Register, regulator notification, and claim lodgement stay your duty-holder responsibility under WHS Act 2011 s 19.
Spoke deep-dives (4)
Director ID / ASIC / Corporate
PREPARES (STATEMENTS ONLY)Director ID via ABRS · ASIC annual statement · insolvent trading · structure choice.
What XIntelliSync does — The accounting cluster prepares the financial statements your accountant uses for the ASIC annual review. Director ID via ABRS, ASIC Connect lodgement, and solvency resolution stay your direct task.
Spoke deep-dives (4)
Essential 8 + Cyber Compliance
SUBJECT-TOACSC Essential 8 · cyber insurance · MFA · application control + patching · incident response.
What XIntelliSync does — XIntelliSync is itself subject to ML 2-3 Essential 8 (XGVS code-audit gates enforce platform-side cyber posture). Your own Essential 8 implementation runs on YOUR endpoints, identity provider, patching tool, and backup stack — not on your accounting platform.
Spoke deep-dives (4)
Consumer Data Right (CDR)
USES (READ-ONLY)CDR accreditation · banking + energy + non-bank lending · consent management · UK / EU comparison.
What XIntelliSync does — XIntelliSync uses CDR via accredited partner (Basiq) for bank reconciliation + cash-flow forecasting. Read-only, one direction, no outbound payment initiation. Customer consent visible end-to-end in the CDR Dashboard at both bank and partner.
Spoke deep-dives (4)
Where to start
Eight starting points by where you are right now.
About this Learn Centre
Five questions answered.
How is the Learn Centre organised?
Eight cluster pillars covering the eight compliance regimes every Australian SMB must navigate. Each pillar has 4-6 spoke deep-dives. Total: 8 pillars + 34 spokes + 1 standalone positioning page = 43 cornerstone pages. Every cluster is tagged with its connection class — IS, PREPARES, PREPARES-BOUNDARY, PREPARES-STATEMENTS, SUBJECT-TO, or USES — so you know upfront what XIntelliSync actually does in that domain.
What does each connection class mean?
IS = XIntelliSync is the product (the page describes the platform itself). PREPARES = XIntelliSync prepares the artefact, you lodge externally. PREPARES-BOUNDARY = XIntelliSync prepares adjacent inputs (e.g. wage data driving workers-comp premium); the duty-holder responsibility stays yours. PREPARES-STATEMENTS = XIntelliSync prepares financial statements; director-level lodgement stays yours. SUBJECT-TO = the platform is itself bound by the regime, and so are you. USES = XIntelliSync consumes the regime infrastructure read-only via accredited partner.
Why does XIntelliSync publish 43 pages on compliance?
Because we built the platform that handles your TFNs, payroll, BAS, and bank reconciliations on a financial OS — and a financial OS is only worth trusting if the operator can read every regulatory regime governing it. We wrote down what we know, then committed to keeping the pages in sync with the production code. The alternative is asking you to trust an AI black box with your business. We refuse to ask you to do that.
Is the content kept current?
Every cornerstone page lists external authoritative regulator portals (.gov.au + AustLII for the legislation) so you can cross-check. The Public Content Operating Contract (LOCKED 25 Apr 2026) requires every regulatory claim to cite an authoritative source, and the canonical numbers carry a "+" suffix to handle additive growth. Drift detection runs as part of XGVS Stage 1 cross-file consistency.
How do these pages relate to the XIntelliSync product?
Every cluster card on this hub has a "What XIntelliSync actually does" anchor sentence. If the cluster is IS or PREPARES, the platform agents map directly to the regime. If the cluster is SUBJECT-TO or USES, XIntelliSync is itself bound by or consuming the regime. PREPARES-BOUNDARY clusters (e.g. WHS) explicitly draw the line between platform-prepared inputs and customer-side duty-holder responsibility. Zero closest-match invention per ACL §18 / §29.
The Learn Centre is the documentation. The product is what runs the work.
Every cluster on this page maps to real agents in the catalogue or real XGVS gates in production. If a regulator audited your operations tomorrow, the answer to "how does your platform handle this?" would have a citation in code, not in marketing.