How it works
Seven steps from expected evidence to a tagged document in BGL.
AI-assisted, rules-led. Rules work out what a fund needs and what it already holds, AI reads what the trustee sends, the trustee confirms, and Simple Fund 360 stays the system of record.
- Rules decide
- AI reads documents
- Trustees confirm
- Simple Fund 360 stays the system of record
The loop
One fund, one loop, seven steps.
Each step is labelled with what does it. Rules and the ledger are code. The AI step reads. The trustee step is the only approval, and it comes before the only write.
- 1
Expected evidence
RulesThe fund's holdings in Simple Fund 360 set the list for the year: a market valuation and an insurance certificate for each property, lease or rent evidence when it is leased, a loan statement for each borrowing, and an annual tax statement for each ETF or managed fund.
- 2
Already held
RulesWhat the fund's Documents, tags and workpapers in Simple Fund 360 already hold comes off the list. Only the gap is carried forward.
- 3
Collect what is missing
RulesOne open request per fund, nearest deadline first, in one plain email to the trustee between 09:00 and 09:15 Sydney. The request stays open until a usable document arrives.
- 4
AI reads the document
AIThe document the trustee forwards or uploads is read and classified on four facts: document type, what it relates to, financial year and period covered. An uncertain read is not matched; it goes to the practice's Needs review count.
- 5
Trustee confirms
TrusteeA match shows the trustee a Confirm button next to the request it answers. Nothing is filed before the trustee presses it. A wrong document gets a reply naming what is still needed.
- 6
Written back to Simple Fund 360
RulesOn Confirm the document is written to the fund's Documents in Simple Fund 360, tagged with the financial year, the document type and SMSF Core. That is the only write. Nothing in the fund is changed or deleted.
- 7
Logged
LedgerEvery step, from the request opening to the write-back, is recorded in an audit ledger with what happened, who did it and when. The practice's morning digest is read from the same record.
Governance
How our AI is governed
AI never calculates tax, determines a compliance outcome or posts an unconfirmed record.
What the AI does
It reads and classifies incoming documents: the document type, what it relates to, the financial year and the period covered. That is the whole of its job.
What it never does
AI never calculates tax, determines a compliance outcome or posts an unconfirmed record. It does not choose what a fund needs, and it does not mark a request done.
Rules are deterministic code
Which evidence a fund needs, what is already held and what is written back are decided by rules written as code, tested for the same answer in two separate engines. The same fund gives the same list every time.
Trustee confirmation comes first
No document is written to Simple Fund 360 until the trustee has confirmed the match. The practice has no approve step and the AI has no file step.
Every step is recorded
Requests, reads, confirmations and write-backs are recorded in an audit ledger that the practice digest and the fund's history are read from.
Where documents are processed
Document text is sent to Anthropic in the United States to be read, before anything is filed. Fund records, and what is read from BGL, are stored with Supabase in Sydney, Australia.
Where each step runs and how data is held is set out on the security page and in the privacy policy.
Where the loop runs
For an accounting practice on Simple Fund 360, the loop runs across every linked fund and the preparer finds the evidence in Documents. That page is for practices.
For a trustee who runs their own fund, the same reading and confirming applies to the statements forwarded through the year. That page is for trustees.
Not a licensed financial service. Information only. Simple Fund 360 is a BGL product name; SMSF Core is not a BGL product. Named platforms are referenced for compatibility and are the property of their owners.