lp://staging/~roberto-v/account-payment/adding_account_vat_on_payment_7

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp://staging/~domsense/account-payment/adding_account_vat_on_payment_7 at revision 111

Lorenzo Battistini: Approve on 2014-02-27

Diff: 141 lines (+102/-0)

5 files modified

account_vat_on_payment/__init__.py (+1/-0)
account_vat_on_payment/__openerp__.py (+1/-0)
account_vat_on_payment/account.py (+16/-0)
account_vat_on_payment/partner.py (+36/-0)
account_vat_on_payment/partner_view.xml (+48/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

118. By Roberto Gianassi on 2014-02-24

[FIX] Fixing remarks.

117. By Roberto Gianassi on 2014-02-14

[FIX] When partner field is empty value is False.

The value passed to the onchange_partner_id for the partner is False
when the field is empty. In this case, it is not possible to use such a
value with the browse function or an error arises. Fixed that.

116. By Roberto Gianassi on 2014-02-14

[ADD] Moved default_has_vat_on_payment on account.fiscal.position.

After some research, the VAT on Payment seems dependent on the account
fiscal position of the customer/supplier.
Moved the default_has_vat_on_payment flag to that model to take that
into account.
The field is now a boolean because is not needed anymore to force the
user to make a choice.

115. By Roberto Gianassi on 2014-02-12

[FIX] Typo.

114. By Roberto Gianassi on 2014-02-12

[FIX] Fixed a bug on XML record creation.

If a module (like fetchmail_invoice) containing a partner record to be
preinstalled through a data.xml file was installed after this one, a
bug occurred.
The bug shows because the record is created with the
default_has_vat_on_payment flag to empty and then validation fails.
To solve this, the create function for partners is changed to check for
the presence of that flag in the vals dictionary. If the flag is found,
we assume the creation happens through the UI and so normal checking goes
on. If the flag is not found, we assume the creation happens for an XML
record and so we add an arbitrary, but valid value for the flag.

113. By Roberto Gianassi on 2014-02-11

[IMP] PEP8 fixings.

112. By Roberto Gianassi on 2014-02-11

[IMP] Copyright fix.

111. By Roberto Gianassi on 2014-02-10

Added a selection field to define a default value for VAT on Payment flag.

Usually, invoices emitted for a particular customer/supplier have the
same value for the VAT on Payment flag.
This patch adds the possibility to specify the default value of such a
flag.
This definition must be done inside the partner form and is made through
a selection. This is done to force the user to flag the right value.
Using a boolean is too easy to forget to check the field.
Once the default value is set, all subsequent invoices created for that
partner have the VAT on Payment flag automatically set to the right value.

110. By Lorenzo Battistini on 2013-11-28

[FIX] typo

109. By Lorenzo Battistini on 2013-11-27

[fix] URL