| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Employees (hr) • Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 1721 |
| Technical Name |
l10n_au_payroll_stp_finalisation |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Employees (hr) • Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 1721 |
| Technical Name |
l10n_au_payroll_stp_finalisation |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Australia STP End-of-Year Finalisation
Single Touch Payroll finalisation declarations & amendment events for Odoo — set the finalisation indicator, turn income statements Tax ready
At the end of every Australian financial year each employer must finalise their STP data with the Australian Taxation Office. This module assembles the finalisation declaration for the whole year, sets the finalisation indicator on each employee's year-to-date record and produces a canonical declaration document for lodgement through your own Sending Service Provider (BYOK). Built on Australia STP Phase 2. Runs on Odoo 18 & 19, Community and Enterprise.
Finalisation declaration
Populate every employee with a Tax File Number, confirm their year-to-date gross, PAYG withheld and super, set the finalisation indicator and reconcile employer control totals. Lodging turns each employee's online income statement to Tax ready.
Amendment events
When a finalised year needs correcting, clone the lodged declaration into a draft amendment, restate the corrected year-to-date and re-lodge — or remove the finalisation indicator to re-open a record. Every step is tracked in the chatter.
Financial-year engine
1 July – 30 June bounds, the 2025-26 label, the statutory 14 July due date (or 30 September for closely held / micro employers) and an overdue flag, all computed automatically from the year you pick.
Reportable Fringe Benefits
Capture RFBA and exempt RFBE at finalisation. The $2,000 taxable-value reporting threshold is applied to the grossed-up amounts so only reportable fringe benefits are carried into the declaration.
Import year-to-date from pay events
Pre-fill each payee's cumulative figures from the latest STP Phase 2 pay-event line in the financial year, so the finalisation simply confirms the figures already reported during the year.
Real TFN & ABN validation
The ATO modulus-11 Tax File Number checksum (with exemption codes) and the ABR modulus-89 Australian Business Number checksum are enforced before a declaration can be generated.
Bring your own keys (BYOK)
The ATO ingests finalisation declarations through the Standard Business Reporting (SBR2) ebMS3/AS4 channel via a registered Sending Service Provider. This module produces the structured, validated declaration as canonical sorted JSON — your own SSP / SBR credentials lodge it. We never hold ATO credentials and never transmit on your behalf. Production and test SBR endpoints are editable defaults.
Authority: Australian Taxation Office (ATO), Single Touch Payroll
Phase 2 — "Finalising your STP data". The financial-year bounds,
due dates, finalisation indicator and RFBA threshold encode the
published ATO employer reporting rules; confirm against the latest ATO
guidance before live lodgement. No Enterprise hr_payroll
dependency.
Screenshots
Eofy Stp Finalisation Stpfin
Stp Finalisation Declaration
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module