-
-
Notifications
You must be signed in to change notification settings - Fork 515
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
l10n_es_payment_order_confirming_aef: Bankinter no toma una fecha de emisión correcta #3425
Comments
No termino de entender el problema, pero lo que puedo decir es que la fecha de pago depende de lo que se elija en la orden de pago. Puede ser una fecha fija o puede ser la fecha de hoy. Obviamente, si se escoge fecha de vencimiento, y la primera línea tiene una fecha en el futuro posterior al de otras líneas, esa fecha no será representativa. De todas, ¿para qué utilizan los bancos ese dato de fecha proceso? Cada línea luego lleva información de su propia fecha:
con lo que es un dato bastante testimonial. |
Los demás bancos, para nada. Bankinter para procesar el fichero, si no, ni crea los confirming hasta esa fecha, y es como si nunca se hubiera subido el fichero. Según me han explicado los usuarios, es para dar planificar una disponibilidad del confirming desde fecha previa a la subida real del fichero (los otros bancos no tendrían esta posibilidad). Solución: |
Vale, como no tiene ninguna función especial, se puede utilizar la fecha que comentas. ¿Puedes hacer un PR con el cambio? |
… as today Bankinter is actually using the processing date indicated in the file for their planning and using the first line payment date causes that the files generated don't work with that bank. As harmless for the rest of the banks, let's use the date where the file is generated for this data. Closes OCA#3425
… as today Bankinter is actually using the processing date indicated in the file for their planning and using the first line payment date causes that the files generated don't work with that bank. As harmless for the rest of the banks, let's use the date where the file is generated for this data. Closes OCA#3425
… as today Bankinter is actually using the processing date indicated in the file for their planning and using the first line payment date causes that the files generated don't work with that bank. As harmless for the rest of the banks, let's use the date where the file is generated for this data. Closes OCA#3425
Bankinter is actually using the processing date indicated in the file for their planning and using the first line payment date causes that the files generated don't work with that bank. As harmless for the rest of the banks, let's use the date where the file is generated for this data. Closes OCA#3425
Bankinter is actually using the processing date indicated in the file for their planning and using the first line payment date causes that the files generated don't work with that bank. As harmless for the rest of the banks, let's use the date where the file is generated for this data. Closes OCA#3425
Bankinter is actually using the processing date indicated in the file for their planning and using the first line payment date causes that the files generated don't work with that bank. As harmless for the rest of the banks, let's use the date where the file is generated for this data. Closes OCA#3425
Bankinter is actually using the processing date indicated in the file for their planning and using the first line payment date causes that the files generated don't work with that bank. As harmless for the rest of the banks, let's use the date where the file is generated for this data. Closes OCA#3425
Bankinter is actually using the processing date indicated in the file for their planning and using the first line payment date causes that the files generated don't work with that bank. As harmless for the rest of the banks, let's use the date where the file is generated for this data. Closes OCA#3425
Bankinter is actually using the processing date indicated in the file for their planning and using the first line payment date causes that the files generated don't work with that bank. As harmless for the rest of the banks, let's use the date where the file is generated for this data. Closes OCA#3425
Bankinter is actually using the processing date indicated in the file for their planning and using the first line payment date causes that the files generated don't work with that bank. As harmless for the rest of the banks, let's use the date where the file is generated for this data. Closes OCA#3425
Module
l10n_es_payment_order_confirming_aef
Describe the bug
Bankinter usa la fecha de proceso del fichero AEF que actualmente es incorrecta (tomamos el primer pago y su fecha). Los demás bancos usan la fecha de subida del fichero a sus plataformas. Por ende, es probable que la mejor solución sea poner el campo de fecha de generación del fichero como "fecha proceso".
Si se pone una fecha de vencimiento del primer pago (criterio para hacer esto? Ninguno), nunca se habilita la remesa en el sistema para que los proveedores lo decidan usar o no.
l10n-spain/l10n_es_payment_order_confirming_aef/models/confirming_aef.py
Lines 114 to 116 in 0feaf74
To Reproduce
Affected versions: 14.0,15.0,16.0
Steps to reproduce the behavior:
Expected behavior
La fecha de generación del fichero se establece aquí:
l10n-spain/l10n_es_payment_order_confirming_aef/models/confirming_aef.py
Lines 114 to 116 in 0feaf74
The text was updated successfully, but these errors were encountered: