s in countries that don't required it.
Add tracking on important fields of the mandate.
Better form view on company.
Update constraint on mandate following my devs on "Original Mandate Identification".
- add module account_banking_pain_base
- add support for initiating party identification, priority and structured remittance info in XML file
- the requested execution date now uses the fields date_prefered and date_scheduled (the field of the wizard has been removed)
- the 'convert to ascii' feature is now an option of the payment mode (enabled by default)
- set 'communication' field of payment.line to 140 chars and hide field 'communicatio
n2'
- constraints
- display related payment lines
- set mandates to expired after 36 months of inactivity (via a cron)
- add tracking/chatter
- add default draft state + validate button
[FIX] In Debit mode, don't use the partner_bank_id of the customer invoice !
In the wizard 'Select invoices to pay', add maturity date in the view of the account move lines
Fix dependencies (I need the field "payment_order_type" which is in account_banking_payment)
Only use ASCII characters in the XML file (that's how banks use XML !)
Use the payment order reference as the Message Identification of the XML file.
Use the payment line sequence as the "End to End Identification"
Remove the Instruction Identification ('InstrId') because it is not a required field (only the End to End identification is required)
Rename variables in the function create_sepa() to include the number of each field as
used in the EPC guidelines
Reduce the number of flake8 warnings
Make code more modular :
- self.pool.get('banking.export.sepa').create() has a _prepare fonction
- most of the content of the XML file can be inherited via _prepare_field()
- convert accented chars to ascii chars (via the unidecode lib)
- use "PrvtId" instead of "OrgId" in the XML
Use the sequence of payment.order as the "Message identification" of the XML file (advantages : it is unique, users can easily customize the sequence and users can easily find the payment corresponding to the "Message Identification" in OpenERP). It is also used as the Payment Identification, combined with the sequence type.
Use the sequence of payment.line in the "EndtoEnd Identification" field.
Reduce flake8 warnings.
