Australian accounting: inspect the evidence behind the result

Synthetic examples. Review aid, not professional advice; accounting decisions stay with the reviewer.

Input: $120 super contribution for payday 6 August 2026, remitted 14 August, with no fund receipt evidence as at 20 August.

From a clone, with uv installed:

bash

cd packages/payday-super-checker
uv run --locked --extra dev --python 3.12 payday-super-check evaluation/payday_super_evidence/fixtures/timely_remittance_no_receipt.csv --as-at 2026-08-20 --confirm-remittance-only

The confirmation acknowledges the missing receipt; it does not establish payment.

Output: AT_RISK, due 17 August 2026; exit 0 acknowledges the remittance-only evidence, without proving timely receipt.

Evidence	Result	Human decision
Remitted before the deadline; receipt missing	`AT_RISK`	Obtain fund receipt evidence before concluding it was on time.
Fund receipt recorded on 17 August	`ON_TIME` on supplied facts	Confirm the evidence and any applicable timing exception.

Read the five-minute Payday Super case · Division 7A repayment case · MCP setup

Installation, component identities, integration and reference

Development home for the Aus Accounting MCP application and seven independently released Australian accounting engines. Each component keeps its own distribution name, version, lockfile, tests, release notes, commands and licence. There is no root distribution, shared runtime library or combined version.

Use Aus Accounting MCP

For the MCP server, install Python 3.10+ and uv, then configure your MCP client to run:

bash

uvx aus-accounting-mcp

This starts a local stdio server; it waits for an MCP client rather than opening a web page. It requires no API key. Package installation downloads dependencies; the tools then use bundled data without network requests or record writes.

Client setup and examples · Tool reference · PyPI · Glama listing

The tools list ATO benchmark industries, compare supplied expense buckets, review Payday Super timing, look up reviewed Division 7A rates, review an operator-supplied Division 7A loan, refuse unsupported Division 7A matters, and generate synthetic CTR/BAS fixtures. They also assess related Payday contributions, calculate six bounded tax worksheets and retrieve cited local Markdown excerpts. Division 7A review is limited to the delegated engine's s 109N/s 109E scope; it does not form amalgamated loans or classify repayments under s 109R. Outputs are review aids, not advice or lodgments.

For an editable source installation, run pip install -e . from apps/aus-accounting-mcp/. The repository root is not an installable Python package.

Components

Path	Distribution	Import package	Commands
`packages/australian-tax-calculators/`	`australian-tax-calculators`	`austaxcalc`	Python worksheet functions
`apps/aus-accounting-mcp/`	`aus-accounting-mcp`	`aus_accounting_mcp`	`aus-accounting-mcp`, `aus-accounting-mcp-demo`
`packages/ato-benchmark-compare/`	`ato-benchmark-compare`	`atobenchmark`	`ato-benchmark-compare`
`packages/payday-super-checker/`	`payday-super-checker`	`paydaysuper`	`payday-super-check`
`packages/div7a-loan-review/`	`div7a-loan-review`	`div7aloan`	`div7a-loan-review`
`packages/the-exchequer-tally/`	`the-exchequer-tally`	`edwinnixon`	`the-exchequer-tally`
`packages/solomons-sword/`	`solomons-sword`	`louisgoldberg`	`solomons-sword`
`packages/the-wip-tally/`	`the-wip-tally`	`wiptally`	`wip-tally`

IMPORTS.md records the source repository, commit and tree of every imported engine. The MCP application is the io.github.ryanduguid/aus-accounting MCP Registry server; it depends on the published ato-benchmark-compare, payday-super-checker, div7a-loan-review and australian-tax-calculators distributions. In the development workspace, uv resolves those four dependencies to their checked-out sources.

Working in a component

Change into the component directory and use the commands its own README.md, AGENTS.md or CONTRIBUTING.md documents. The root CONTRIBUTING.md routes the common commands and names the root workflow that runs them.

Boundaries

The MCP application depends on engines only through their published distributions.
Engines never import aus_accounting_mcp or another engine, and no production module uses a relative import that leaves its package; tests/test_boundaries.py proves both.
Only the workflows under the root .github/workflows/ are active; component directories carry none.
No client data, credentials or generated client reports enter this repository.

Releases

Each component is released on its own namespaced tag <component>/vX.Y.Z by its own root workflow .github/workflows/release-<component>.yml, which calls the pinned Release Policy reusable workflow for that component directory only. CONTRIBUTING.md has the table.

Each component's LICENSE applies to that component, and packages/ato-benchmark-compare/NOTICE covers its bundled ATO data. Outputs are review aids, not advice.