For accounting practices
The evidence your funds will need, in BGL before year end
SMSF Core makes sure the evidence your team will need actually gets into BGL before year end. We read what a fund already holds in Simple Fund 360, work out which evidence should exist for the year but is not there, collect it from the trustee and put it back into the fund's BGL Documents. Your practice keeps working in BGL. We do not prepare accounts, we do not replace BGL, and we do not ask your team to work in another system.
What changes for your team
Someone opens each fund in May and works out what is still missing from the Documents screen
We read the fund's holdings and Documents list in Simple Fund 360 and work out what should exist for the year but is not there
The trustee gets a list of everything the fund might need and sends half of it
The trustee gets one plain email with one ask, and forwards or uploads that item
What comes back is filed by hand, renamed, and matched to the right fund and year
The document is matched to the fund, year and type, the trustee approves it, and it lands in the fund's BGL Documents with tags
Missing evidence surfaces at first review, and the chase starts again
Your team opens the fund in BGL and the evidence is already there
What stays where it is
Simple Fund 360 stays the ledger, the workpapers and the annual return. Preparation, review, audit and lodgement stay with whoever does them today. If your practice outsources preparation, nothing changes for the preparer either: the evidence lands in the fund's BGL Documents, which is where they already work. What goes away is the step in between, where someone on your side asks the trustee for documents, waits, asks again, and files what comes back.
The trustee keeps their own side of SMSF Core, where the fund's records sit through the year and where a check runs before they act on something that would show up on your desk later. That side is described on the trustee page.
The pilot: connect ten funds, measure what comes back
Connect ten of your funds on Simple Fund 360 through BGL's consent flow. We work out which evidence each fund should have for this financial year and does not, ask the trustees for it, and put what comes back into the fund's BGL Documents. You measure three things: whether each request was correctly identified, whether the evidence was usable as filed without a second ask, and the minutes your team did not spend relaying documents. The first practices pay nothing for the first financial year, and the founder does the setup himself. The BGL connection runs today in BGL's sandbox under an API scope granted in August 2026; production connections open with the pilot, practice by practice.
- Requests correctly identified: you mark each one correct, not needed or wrong type, in one click.
- Evidence usable as filed: any re-request counts as a fail for that item, on our side.
- Minutes not spent relaying documents: your own estimate per request, captured when you confirm it.
Not included: account preparation, audit and lodgement. We are finishing the last step of the loop, the write-back into BGL Documents, and the first practices connect as it is ready. No contract and no migration; if the evidence does not arrive usable, you stop and nothing in BGL has moved.
The first call starts with one question, because the answer decides what we ask trustees for: which SMSF problems do you currently discover after the trustee has already done something, that you wish you could have caught beforehand?
Common questions from practices
- Does SMSF Core replace BGL Simple Fund 360?
- No. Simple Fund 360 stays the ledger, the workpapers and the annual return. SMSF Core reads what a fund already holds there, works out which evidence should exist for the year but is not in the fund's Documents, collects it from the trustee and puts it back into BGL. Your team keeps working in BGL and does not log in to another system.
- How does SMSF Core get access to a client fund?
- Through BGL's own consent flow, which your practice controls because you hold the BGL login. SMSF Core reads the fund list, holdings and the Documents list, and writes tagged documents back to the fund's Documents. The connection runs today in BGL's sandbox under an API scope BGL granted in August 2026; production connections open with the pilot, practice by practice. It does not post transactions, prepare accounts or touch the annual return. You can withdraw the consent at any time.
- We outsource preparation. Does that change anything?
- No. The evidence lands in the fund's BGL Documents, which is where your preparer already works. Whoever on your side relays trustee documents to the preparer today stops doing that step for the connected funds, and the review stays with your team.
- What does the pilot cost, and what is not included?
- The first practices pay nothing for the first financial year. The founder does the setup: connecting the funds, confirming the expected-evidence list with you and briefing the trustees. Not included: account preparation, audit and lodgement. Those stay exactly where they are today.
Not a licensed financial service. Information only. Named platforms are referenced for compatibility and are the property of their owners.