Since the bank is optional on bank accounts and the BIC can be set
on the bank account if there is no bank, we allow the system to
get the BIC from the bank account in case it is not on the bank.
We give priority to the BIC indicated on the bank, keeping
the same behaviour with existing data where the bank BIC is
available.
* Start code factoring between SCT and SDD.
* More code factoring between SCT and SDD As a consequence, we now have support for structured remittance info in SDD.
* The requested collection date now uses the fields date_prefered and date_scheduled of payment.order, instead of the field in the SDD wizard.
* Mutualize more code between SCT and SDD.
* Replace unallowed ascii caracters by '-' Update some error messages Update translation files and FR translation Include sepa_export in gen_args Factorize more code between SDD and SCT Fix view of payment lines The modules account_banking_pain_base and account_banking_sepa_* are now fully PEP8 compliant
* For SCT, if BIC is not provided, we should not put the 'Creditor Agent' block at all, according to EPC guidelines (on this point, it is different from the Direct Debit !)
* Add demo data
* Add missing utf-8 header Update state field on SEPA file objects and display it in tree+form views. Migrate form views to version 7.0 and simplify them.
2024-03-25 09:16:59 +07:00
Launchpad Translations on behalf of banking-addons-team
* Better prototype for the _prepare_field function. Update help message, POT file and FR translation.
* Revert the dependancy to account_banking_payment_export (the field payment_order_type on payment.mode.type has a default value of "payment" anyway).
* Akretion-Noviat code sprint dated 2013-11-21: - 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'
* FIX label : Customer (which is wrong, it is most of the time a Supplier !)-> Creditor More PEP8 stuff.
2024-03-25 09:16:59 +07:00
Launchpad Translations on behalf of banking-addons-team
* Add support for pain.001.001.05 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()
* Update strings. Update FR translation.
* fields.date.context_today doesn't work with datetime => we now use the native field create_date Coding style improvements.
* Add logo
- introduce account_banking_payment_export module with all features from account_banking_payment that do not involve changing the payment order workflow or depend on bank statement changes
- account_banking_payment_export does not depend on account_banking
- account_banking_payment is consequently stripped of above features
- account_banking_sepa_credit_transfer depend on account_banking_payment_export and is compatible with the default payment order workflow
- clarified comment about workflow in account_banking_sepa_credit_transfer
- avoid generating invalid sepa credit transfer files when bank accounts have no BIC
The field 'sepa' on account.payment.order is only display for SEPA
payment methods.
If the option "show warning if not SEPA" is enabled on the payment
method, a warning banner is now displayed on payment orders with a SEPA
payment method which are not SEPA.
Steps to reproduce the problem:
- Have a partner with no zip code and no city.
- Include it in a payment order.
- Generate the SEPA XML file.
Current behavior: The file couldn't be generated because there's an
empty <AdrLine> element.
We put properly parenthesis in the conditions for this to no happen.
TT43260
