Skip to Content
Odoo model

account.accrued.orders.wizard

Accrued Orders Wizard. Defined in module account; exists in Odoo 16, 17, 18, 19, 20. Across the upgrade steps we tracked: 3 fields added, 0 removed, 0 renamed.

  1. Odoo 16 account
  2. Odoo 17 account
  3. Odoo 18 account
  4. Odoo 19 account
  5. Odoo 20 account

Odoo 16 to 17

Community only All changes in this step

No change to this model's own fields in this step.

Odoo 17 to 18

Community only All changes in this step

No change to this model's own fields in this step.

Odoo 18 to 19

Community + Enterprise All changes in this step

No change to this model's own fields in this step.

Odoo 19 to 20

Community + Enterprise All changes in this step

Fields added (3)

FieldTypeModule
accrual_typeselectionaccount
duplicate_entry_idmany2oneaccount
duplicate_price_totalmonetaryaccount
2 actions on this model removed
  • purchase.action_accrued_expense_entry
  • sale.action_accrued_revenue_entry

All fields declared on account.accrued.orders.wizard (12)

Fields this model declares itself in any version, with the versions they exist in. Inherited fields (mail.thread and other mixins) are on the parent model's page.

present not present not covered (Enterprise, Odoo 16 and 17)

Show all 12 fields
FieldTypeLabelModule1617181920
account_idmany2one account.accountAccrual Accountaccount
accrual_typeselectionAccrual Typeaccount
amountmonetaryAmountaccount
company_idmany2one res.companyaccount
currency_idmany2oneCompany Currencyaccount
datedateaccount
display_amountbooleanaccount
duplicate_entry_idmany2one account.moveaccount
duplicate_price_totalmonetaryaccount
journal_idmany2one account.journalJournalaccount
preview_datatextaccount
reversal_datedateaccount

Related models

Linked by its relational fields: account.accountaccount.journalaccount.moveres.company

Coverage. Odoo 16 to 17 and 17 to 18 compare Community modules only (the Enterprise 16 and 17 sources are not available to us). Odoo 18 to 19 and 19 to 20 include Community and Enterprise modules. Everything here comes from a static read of the Odoo source code: a field counts as removed only when no parent model, mixin or delegated model still provides it. Fields created dynamically at run time can be missed, and entries we could not confirm are marked as low confidence.