Skip to content
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

Payment order for inter-bank transfer #1313

Open
alexis-via opened this issue Jul 9, 2024 · 2 comments
Open

Payment order for inter-bank transfer #1313

alexis-via opened this issue Jul 9, 2024 · 2 comments
Labels
bug stale PR/Issue without recent activity, it'll be soon closed automatically.

Comments

@alexis-via
Copy link
Contributor

Scenario: company with 2 bank accounts. I would like to generate a SEPA XML payment file to transfer money from bank account n°1 to bank account n°2.

I tested this scenario on odoo 16.0: I create a payment order with 1 payment line: in the payment line, I select the partner linked to my company and I enter the amount and a communication label. I confirm the payment order. The SEPA XML payment file is OK. It creates a payment order with is_internal_transfer=False ; the account move generated is between the supplier account and the outstanding payment account (I would expect an account move between the outstanding payment account and the Inter-Banks Transfer Account (company_id.transfer_account_id).

It seems to me that this scenario is not supported for the moment. Am I missing something ? @pedrobaeza as you are the author of the support of account.payment, can you confirm that this scenario is not supported ?

If it is confirmed that this scenario is not supported, I'm ready to implement it.

@alexis-via alexis-via added the bug label Jul 9, 2024
@pedrobaeza
Copy link
Member

It's not supported indeed. I have never heard before of using payment order for making internal transfers, but it can be. You have to adjust the payment creation to put the flag if the line partner is the company's partner.

Copy link

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jan 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

No branches or pull requests

2 participants