Daily updates from Odoo
Wednesday, September 18, 2024
3 changes
Enhancements to existing features
Australian payroll now automates more Single Touch Payroll steps by adding payslips to STP records, creating STP records for pay runs, and warning users about unsubmitted records. The update also improves compliance handling for SuperStream, backpayments, child support, Medicare, STP finalisation, and file replacement, reducing manual work and reporting risk.
Original PR description
- Adds new payslips to STP automatically when they are created.
- Creates a new STP record for each Payrun. Adds warnings to the
dashboard for any STP records that have not been submitted.
3494990Odoo financial reports now apply the appropriate currency conversion method when consolidating companies with different currencies, using average, historical, or period-end rates depending on the account type. This improves the accuracy of consolidated statements and period comparisons, while related sales and manufacturing reports keep their existing behavior.
Original PR description
The CTA conversion method is used when consolidating multiple companies with different main currencies. The general idea is to use different rates depending on the account we're consolidating: -…
The CTA conversion method is used when consolidating multiple companies with different main currencies. The general idea is to use different rates depending on the account we're consolidating:
- Income/Expense accounts should use the average rate on the considered period
- Equity accounts should use the historical rate at the date they were made
- Other accounts should use the current rate, the one that applies at the end of the considered period
Before this commit, Odoo handled such conversions by always applying the current rate everywhere. For this, a structure called the currency table was used.
The community counterpart commit modifies the currency table in order to handle CTA conversion. This commit converts the reports to this new structure, and adds a field on account.report to control whether the report should use 'current' rates or CTA in case of multi-currency consolidation.
We also change the way the comparison feature of the reports works with multi-currency consolidation. In the past, the 'current' rate at the date_to chosen in the reports filter was used for every compared period. Now, each compared period computes a different rate depending on its date bounds. So, the 'current' rate will correspond in each period to the rate applying at the end of the period. The 'average' rate is also computed on each period individually.
Non-accounting reports defined in some sale and mrp modules are also impacted by this commit, to update the way they call the currency table. Their behavior is unaffected, they still make use of the current rates at the time they're opened.
task-4129647Subscriptions can now be billed at the end of a period based on what customers actually received or used, making recurring contracts better suited for usage-based services and delivered goods. The update also clarifies delivery timing for subscription products and prevents invoices from being created for already finished contracts.
Original PR description
Currently we always create invoice for the [period next_invoice_date --> next_invoice_date + period] but for products with an invoicing policy based on delivered quantity it is on non-sense.
There are also a lot of use cases requiring periodic invoicing but at the end of the period with an invoicing based on what the customers "received". Some examples:
Subscription for a service where the usage made affects the price:
Electricity
mobile subscriptions
...
Subscription of a physical product that can fail during the period preventing the customer to use it.
Leasing / renting of cars
Tracking device in truck (existing client)
Subscriptions of fresh produce
taskid: 3071118