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

FIX #30397: for direct debit payments, BIC is optional #30398

Merged
merged 9 commits into from
Jul 17, 2024

Conversation

priojk
Copy link
Contributor

@priojk priojk commented Jul 16, 2024

According to SWIFT regulations for direct debit payments, IBAN is sufficient information and the BIC code is optional. But Dolibarr is rejecting the creation of direct debit payments without BIC code (see Issue #30397).

The code adjusts the behaviour of Dolibarr and allows the creation of direct debit payment xml-files based only on the customer IBAN (for the time being, only if the variable WITHDRAWALS_WITHOUT_BIC is set, in order not to interfere with existing installations).

@eldy eldy changed the base branch from 19.0 to develop July 16, 2024 19:50
@eldy eldy added the PR to fix or conflict to solve PR needs to be fixed to be integrated (except for conflicts, a comment describes the fix to do) label Jul 16, 2024
@eldy eldy merged commit b1b6c91 into Dolibarr:develop Jul 17, 2024
7 checks passed
priojk added a commit to priojk/dolibarr that referenced this pull request Jul 19, 2024
If no BIC is provided, only the BIC line must be omitted, not the surrounding block, even if it is empty.
eldy pushed a commit that referenced this pull request Jul 20, 2024
* Fix regression of #30398

If no BIC is provided, only the BIC line must be omitted, not the surrounding block, even if it is empty.

* fix whitespace
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR to fix or conflict to solve PR needs to be fixed to be integrated (except for conflicts, a comment describes the fix to do)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants