[FIX] account_voucher : Wrong payment date when invoice is paid from bank statement (Ref : Case 592393)
[FIX] account_voucher: when importing invoices the payment date should be set to the statement date instead of being set to the original invoice date
[FIX] account_voucher : Wrong payment date when invoice is paid from bank statement, code forward-port from 6.1 revision 6966 (Ref : Case 592393)
[FIX] account_voucher: implemented on_change to set voucher date based on statement line
[MERGE] Merged in the fix from 6.0 which overwrites the voucher date and period in case the on_change was not executed
Launchpad automatic translations update.
Launchpad automatic translations update.
Launchpad automatic translations update.
[FIX] purchase: on po confirm, avoid to write location_id on the chained stock move if the move is done

On purchase order confirmation, if the order_line comes from a procurement order created by a sale order,
it tried to write on the location_id, whatever the move state was, even done.

Or, sometimes, the stock move associated to the procurement order (from the so) was already done, for example because we forced the availability of the stock move.
It makes sense to not write the location_id if the move is already done, because the location_id is already good.
[FIX] purchase: on po confirm, avoid to write location_id on the chained stock move if the move is done

On purchase order confirmation, if the order_line comes from a procurement order created by a sale order,
it tried to write on the location_id, whatever the move state was, even done.

Or, sometimes, the stock move associated to the procurement order (from the so) was already done, for example because we forced the availability of the stock move.
It makes sense to not write the location_id if the move is already done, because the location_id is already good.
[FIX] purchase: on po confirm, avoid to write location_id on the chained stock move if the move is done

On purchase order confirmation, if the order_line comes from a procurement order created by a sale order,
it tried to write on the location_id, whatever the move state was, even done.

Or, sometimes, the stock move associated to the procurement order (from the so) was already done, for example because we forced the availability of the stock move.
It makes sense to not write the location_id if the move is already done, because the location_id is already good.
[MERGE] [FIX] account_voucher: forward port of fixes from 6.1 (rev 6966)
When importing invoices to a bank statement the bank statement lines are created with statement date instead of today
Set the date on the created voucher in the same wizard to the statement date instead of invoice date (problematic if different period)
When creating the account moves (at bank statement confirmation), make sur the date and period of the vouncher are synchronised
[MERGE] [FIX] account_voucher: forward port of fixes from 6.1 (rev 6966)
When importing invoices to a bank statement the bank statement lines are created with statement date instead of today
Set the date on the created voucher in the same wizard to the statement date instead of invoice date (problematic if different period)
When creating the account moves (at bank statement confirmation), make sur the date and period of the vouncher are synchronised
[MERGE] [FIX] account_voucher: forward port of fixes from 6.1 (rev 6966)
When importing invoices to a bank statement the bank statement lines are created with statement date instead of today
Set the date on the created voucher in the same wizard to the statement date instead of invoice date (problematic if different period)
When creating the account moves (at bank statement confirmation), make sur the date and period of the vouncher are synchronised