Skip to Content
Meniu
Trebuie să fiți înregistrat pentru a interacționa cu comunitatea.
Această întrebare a fost marcată
5 Răspunsuri
918 Vizualizări

Hello community


Affecting version: 14.0 up to 18.0

If working with Swiss Payments and QR-bill and generate a PAIN file or QR-Invoice, the containing Data in PAIN and QR code must be generated with structured address data.

- Address Type "S" (for QR-Code)

- address splited, not one line for eg. ZIP and city


Details about the change:

https://www.six-group.com/en/products-services/banking-services/payment-standardization/swiss-payments.html#scrollTo=structured-hybrid-address


Fact sheets:

https://www.six-group.com/en/products-services/banking-services/payment-standardization/standards/qr-bill.html#scrollTo=structured-address-extended-character-set


Does anybody know, that this will be implemented into base or must be made in a inherited method?


Regards

thomi


Imagine profil
Abandonează

Didn't investigate deeply by any means, but are you referring to this? https://github.com/odoo/odoo/pull/208411

Autor

I hate this forum type and it's functions...
Yes and i have solutions for Flectra.
If you find out how to contact me, do it...

have a nice day
thomi

Cel mai bun răspuns

We've just been informed by our bank that generating QR invoices with unstructred address information ("K" model) is no longer allowed after November 21st 2025 - so in about 45 days from now. So this seems to affect pretty much all odoo customers in Switzerland.

I'm dumbfounded how this hasn't blown up more and hasn't been fixed yet.

Fortunately, it seems like a relativey small change in addons/l10n_ch/models/res_bank.py​, line 116 and onwards.

I have never made a PR to odoo source code and I don't know how this could be pushed to older versions etc (we're currently on 17 in the middle of upgrading to 18), so if odoo base doesn't fix this, I'll have to write a smal module that overrides the _l10n_ch_get_qr_vals​ function

Imagine profil
Abandonează
Cel mai bun răspuns

Hi,

The Switzerland localization docs (for version 18.0) cover things like ISR, QR codes etc., but while they mention QR codes, they do not explicitly say that “address type S (structured)” is fully enforced.

Refer: https://www.odoo.com/documentation/18.0/applications/finance/fiscal_localizations/switzerland.html


Hope it helps

Imagine profil
Abandonează
Cel mai bun răspuns

Hello Thomas and all

Is there any update on this? 

Did you find a solution or know that this will be implemented on time?

Kind regards

Roger

Imagine profil
Abandonează
Cel mai bun răspuns

Hi Thomas!

Thanks for your comment. I have got actually the same question and I wanted to know if you received an response to your message?

Thanks a lot!

Diane


---------------------------------------------


Thanks Thomas for your reply!

I'll also try to find an answer and let you know if I get more info ;-)

Best Regards,

Diane

Imagine profil
Abandonează
Autor Cel mai bun răspuns

Hey Christoph

Thanks for info, but no :( it has nothing to do with my query. In that commit you mentioned, it's about to get the correct address for the qr-code.

The main change about my query is, that:
1. Address Type must change from "K" to "S"

2. the address must be splited, eg. zip and city can't be on one line

Regards

Thomas

 

Imagine profil
Abandonează
Autor

Hey Diane

Cause any reason, i can't answer direct to your question.
I'm got into this part and found that i'ts also about supplier payment order, generating the address blocks for supplier and the company itself.

But not found time to implement and test it.

As nobody from community is interested to share their thoughts, i try to share it as soon i have something.

Regards, Thomas