australian-accounting

<p align="center"> <picture> <source media="(max-width: 600px) and (prefers-color-scheme: light)" srcset=".github/assets/banner-phone-light.svg"> <source media="(max-width: 600px)" srcset=".github/assets/banner-phone.svg"> <source media="(prefers-color-scheme: light)" srcset=".github/assets/banner-light.svg"> <img src=".github/assets/banner.svg" width="100%" alt="AU Accounting. ATO benchmarks, Payday Super and Div 7A, run locally. Pixel art of an abacus beside the AU Accounting wordmark in slab-serif block letters."> </picture> </p> <div align="center">

<br> <br>

</div>

Seven independently released Python engines that apply Australian tax and payroll rules to figures you supply, plus Aus Accounting MCP, a local Model Context Protocol server that hands those engines to an AI assistant. It serves Australian accountants and bookkeepers, and the developers who build tooling for them.

Each tool returns a calculation, the facts it used and the matters it refuses to decide. The engines and the MCP server run locally: they read files you point them at, contact no service, write to no ledger and lodge nothing. Two boundaries sit outside that: an MCP host sends every tool argument and result to its model provider, and the optional LodgeiT adapter below makes bounded HTTP calls only when you enable it. Missing facts stay unknown: a Payday Super row with a fund-receipt date but no matched_amount or remitted_amount evidences when the fund received something, not how much, so the checker leaves it UNKNOWN rather than ON_TIME and names the amount it needs (from payday-super-checker 0.1.7; 0.1.6 and earlier read that receipt as covering the whole SG amount and say so in a caveat). Supply the amount the fund received with every receipt date. A person reviews every output before it is relied on.

Start here: what each component is · MCP client setup · tool reference · scope, limits and examples

Ryan Duguid is not a registered tax agent or BAS agent. Project support is limited to software issues reproduced with fabricated data. Do not send taxpayer information or request advice, return preparation, tax-treatment confirmation, or lodgement.

Synthetic examples. 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.

Try one contribution

With uv installed, download the synthetic CSV as timely_remittance_no_receipt.csv. Open a terminal in that folder and run:

uvx --from payday-super-checker==0.1.7 payday-super-check timely_remittance_no_receipt.csv --as-at 2026-08-20 --confirm-remittance-only -o payday-report.csv

This downloads the pinned PyPI package without cloning the repository. It writes payday-report.csv in the current folder, replacing that file if it exists. Open the report to see the due date and verdict.

The confirmation acknowledges the missing receipt; it does not establish payment. Omit --confirm-remittance-only to see the same AT_RISK result with exit 2, which asks you to resolve or acknowledge that evidence gap.

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 for the full $120 contribution | ON_TIME on supplied facts | Confirm the evidence and any applicable timing exception. |

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

The recorded public evaluation uses release 0.1.3. Follow its fixed revision and commands to reproduce that historical run; the quick trial above uses release 0.1.7, which requires an evidenced amount alongside a fund-receipt date.

Choose the next example

| Your task | Start here | | --- | --- | | BAS pack review | Two synthetic packs with expected findings | | Xero Activity Statement transaction GST review | BAS workflow and transaction procedure | | Month-end close | Balanced trial balance with unresolved exceptions | | GST planning | Browser planning calculators | | Division 7A | Repayment assertions and the review boundary | | Other engines and agent workflows | Examples and reproduction routes |

For transaction GST coding, load the linked bas-preparation skill and its bundled transaction reference. They require row coverage and separate evidence for supply treatment, buyer credits and BAS attribution. Aus Accounting MCP does not provide a transaction GST classifier; its calculations or a control-account tie-out cannot establish correct tax coding. Missing facts remain unresolved for the authorised reviewer. The walkthrough explains instruction-file delivery to Codex, ChatGPT and Copilot without claiming equivalent tested behaviour.

<details> <summary>Installation, component identities, integration and reference</summary>

Development home for the Aus Accounting MCP application and 7 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.14+ and uv, then configure your MCP client to run:

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. The MCP host you connect it to is a separate boundary: it sends every tool argument and result to its model provider, so use fabricated data with a hosted model.

uvx keeps using the version it first downloaded, so a new release does not reach you on its own. To move to a release, name it in your client configuration, for example aus-accounting-mcp==<version> from PyPI; uvx downloads it, and later launches reuse the cached copy without a download until the uv cache is cleaned.

Once it is connected, ask your assistant in plain English. Each of these fabricated requests resolves to one tool call:

| Ask | Tool | |---|---| | "Compare a hairdresser with $180,000 sales, no other income, $60,000 wages, $30,000 rent and $40,000 other expenses to the ATO benchmarks." | get_ato_benchmarks | | "Super for a 6 August 2026 payday was $120 and was sent on 14 August. As at 20 August, is it on time?" | calc_payday_super_deadline | | "What is the Division 7A benchmark interest rate for 2026-27?" | get_div7a_benchmark_rate | | "An employee who gave a TFN and claims the tax-free threshold (scale 2) is paid a regular $1,000 weekly wage in 2026-27, with no offsets, loans, bonuses or other adjustments. How much PAYG should be withheld?" | calculate_tax_worksheet |

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 14 bounded tax and super 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. Outpu