ERP Heritage · Odoo Accounting Suite
AU BAS Reporting
Australian Business Activity Statement: full 33-label worksheet, accrual and cash GST recognition, Simpler BAS output, locked lodgement evidence, and GST control reconciliation.
Overview
What this module does, in one read.
A BAS reporting framework for Australian deployments. Original returns and ordered amendments are company/quarter scoped; G1, 1A and 1B compute from AU tax grids and untaxed sales, W5 sums reviewed withholding inputs, and lodged runs become immutable evidence.
Out of scope: SBR (Standard Business Reporting) wire transport. Lodgement to the ATO uses a registered third-party agent or the SBR API.
Capabilities
Eight things this module gives you, with no padding.
Originals and amendments
One original plus a strictly ordered chain of amendments is enforced per company and fiscal quarter.
AU-grid calculation
G1, 1A and 1B preserve authoritative signed AU tax-grid tags for invoices and refunds; G1 also includes posted genuinely untaxed customer revenue without inventing GST.
Immutable lodgement snapshot
Label definition, amount, company currency, actor, time, and tax-lock evidence freeze when lodged.
Durable failure audit
Successful computes and failures use the shared report-execution pipeline; DB errors roll back worksheet rebuilds atomically and request independent durable failure evidence.
Restricted manual inputs
Computed rows are read-only. A dedicated action exposes only manual rows; W5 is server-computed from W2, W3 and W4.
Accrual and cash basis
Accrual uses posted invoice dates; cash uses bounded reconciliation SQL and settlement-date proportions, including untaxed sales.
Dynamic report output
The report catalog renders the latest exact-period BAS snapshot; Simpler BAS emits only G1, 1A, 1B and PAYG-W rows.
Built from public spec
The label set follows the published ATO BAS form.
Workflow
Configure once. Operate. Audit. Report.
Four steps, the same across every ERP Heritage module so a finance team learns the suite once.
Configure
Settings > Accounting > ERP Heritage. Multi-company, multi-currency, journals, accounts. One-time setup, persisted on the company record.
Operate
The user works inside the standard Odoo accounting flow. The module surfaces only the controls relevant to its scope.
Audit
Every action that changes accounting state writes an audit row. The audit log is append-only at the framework level.
Report
Reports flow through the same reproducible audit pipeline, with cache invalidation by per-company move version.
Why Heritage
Where this module leads, where it matches, what we are honest about.
- Atomic rebuild plus durable failure evidence
- Cash-basis settlement apportionment
- Immutable currency and label snapshots
- Full 33-label worksheet
- Simpler BAS lodgeable subset
- Company/quarter scope and amendments
- No SBR wire transport (lodgement still through agent or SBR API)
- W1-W4 remain reviewed manual inputs; no payroll/withholding engine is invented
- No PAYG monthly or FBT activity-statement variants
The full ERP Heritage Accounting Suite (24 modules)
Engineering
Ten engineering rules we hold ourselves to.
No silent fallbacks.Missing config, missing accounts, malformed input each surface explicit messages naming the bad field.
Tests cover the bug, not just the feature.Every defect found in review has a regression test attached to the fix, kept in the repository.
Plain Python where possible.Algorithms that do not need the ORM live under tools/ with unit tests that run without Odoo.
Atomic counters via SQL.Concurrent counters use UPDATE col = col + 1, never read-modify-write loops.
Per-record savepoints in cron loops.A single bad record never freezes the batch; failing rows are recorded, the rest of the batch keeps moving.
Schema-first XML output.PAIN.001 and PAIN.008 generators target the published namespace; tests parse output back and assert structure.
ValidationError versus UserError.Constraint failures raise ValidationError; action failures raise UserError with a remedy.
Privilege groups, not direct upstream references.ACL CSVs reference suite-specific groups; the post-migration script promotes upstream-only users.
Append-only audit logs.Approval log, override log, reconciliation audit, mandate amendment log all override write and unlink at the model level.
Originality from public spec.Every standard implementation is built from the published technical specification, not from another vendor codebase.
The standard we hold: every shipped capability is original code from a public technical specification, with regression tests, with a documented engineering rule for the invariant the code preserves, and with no vendor names in code or user-facing docs. From the suite contributing process
Frequently asked questions
Honest answers to the questions a buyer asks.
Does this run on Odoo 16 Community?
Yes. Every module is built and tested against Odoo 16 Community. No Enterprise dependency anywhere in the stack.
What is the licence?
LGPL-3, the same licence as Odoo Community. You can read the source, modify it, and ship it inside your own Odoo deployment without restriction.
Will this conflict with another accounting addon I already use?
Probably not. The modules add new models in their own namespace (eh.*) and inherit standard models without overriding behaviour silently. If your existing addon also extends the same standard model, ordinary Odoo inheritance rules apply.
Are the engineering principles documented?
Yes. The contributing process and ten engineering rules are kept in the repository so a reviewer can verify the code holds itself to them.
Is there a test suite?
Yes. Every module ships its own integration tests; the engine module ships a full unit test suite for the SQL builder, cache, and report orchestrator.
How do I get support?
Reach the team via info@erpheritage.com.au. Training, deployment, and custom extension work is handled by ERP Heritage directly.
Built by ERP Heritage
ERP Heritage builds enterprise-grade accounting software for the Odoo community. Our suite covers the operational accounting cycle end to end: invoice intake, posting, reconciliation, reporting, period close, payment runs, customer portal, multi-step approvals, and year-end. Every module ships with explicit licensing posture, documented engineering principles, comprehensive tests, and a clear differentiation story.
Ready to deploy?
Install this module, run the test suite, and inspect the structured audit log. For training, deployment, or a custom extension, reach our team.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 24939 |
| Technical Name |
eh_account_l10n_au_bas |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
Please log in to comment on this module