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

[CLARIFY] Why is the invoicing address taken from the commercial partner? #104

Closed
aisopuro opened this issue Apr 5, 2019 · 3 comments
Closed
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.

Comments

@aisopuro
Copy link

aisopuro commented Apr 5, 2019

Regarding the module base_ubl:

In the code used to generate the customer section (the AccountingCustomerParty, the partner used for the address details is the partner's commercial partner, not the partner themselves.

We have noticed that this means that if the invoicing address is truly different from the company it is related to (perhaps the company has several different invoicing addresses), then the address selected onto the invoice is not respected: the invoice of the parent is used instead.

The decision is explicitly made here, but no comment or docstring has been supplied explaining why it is done like this.

The module was originally authored by @alexis-via : might he be able to shed some light on why things are done this way?

I am trying to figure out whether I need to hack some kind of patch into our own system or try to make a fix PR here. If this is the expected behaviour in the rest of the world, and I'd end up breaking everybody else's installations, I probably shouldn't go for it.

@alexis-via
Copy link
Contributor

This decision to use the commercial partner may be discussed and I'm open to modification.
In e-invoicing, the postal address is not supposed to be so important because you're not supposed to send your XML file by post... but I can understand that it can be important for some people :)

@aisopuro
Copy link
Author

Well in Finland at least, if you're dealing with big companies or governmental entities, it may be that the company has multiple different invoicing addresses, and sometimes these invoicing addresses aren't just physical addresses, but actually different E-invoicing addresses.

I feel like there might be a need for a setting that allows you to change the logic for what partner's data is used. But I'm honestly unsure where such a setting should live. Should it be a global setting, or a per-partner setting (like a boolean or selection that allows the user to say "I want you to take the details from the parent" or "I want you to take the details from this parrtner, even if it has a parent"). I'm unsure what the best way would be to implement this.

And I will freely admit that I... can't really exactly remember what this is about 😓 sorry. So if no-one is interested in putting thought into this, I think it might be fair to close this.

alexis-via added a commit to akretion/edi that referenced this issue May 8, 2020
Add legal entity block when commercial_partner.is_company = True
alexis-via added a commit that referenced this issue May 13, 2020
Add legal entity block when commercial_partner.is_company = True
thomaspaulb pushed a commit to sunflowerit/edi that referenced this issue Dec 8, 2020
Add legal entity block when commercial_partner.is_company = True
thomaspaulb pushed a commit to sunflowerit/edi that referenced this issue Dec 8, 2020
Add legal entity block when commercial_partner.is_company = True
astirpe added a commit to onesteinbv/edi that referenced this issue Dec 9, 2020
FIX OCA#104 UBL: use address of partner, not of commercial_parter
thomaspaulb pushed a commit to sunflowerit/edi that referenced this issue Feb 14, 2021
Add legal entity block when commercial_partner.is_company = True
KKamaa pushed a commit to sunflowerit/edi that referenced this issue Aug 12, 2021
Add legal entity block when commercial_partner.is_company = True
@github-actions
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 Dec 12, 2021
KKamaa pushed a commit to sunflowerit/edi that referenced this issue Mar 16, 2022
Add legal entity block when commercial_partner.is_company = True
thomaspaulb pushed a commit to sunflowerit/edi that referenced this issue Dec 29, 2022
Add legal entity block when commercial_partner.is_company = True
bosd pushed a commit to bosd/edi that referenced this issue Jun 27, 2023
Add legal entity block when commercial_partner.is_company = True
bosd pushed a commit to bosd/edi that referenced this issue Jun 27, 2023
Add legal entity block when commercial_partner.is_company = True
bosd pushed a commit to bosd/edi that referenced this issue Jun 27, 2023
Add legal entity block when commercial_partner.is_company = True
bosd pushed a commit to bosd/edi that referenced this issue Jun 27, 2023
Add legal entity block when commercial_partner.is_company = True
OCA-git-bot pushed a commit to bosd/edi that referenced this issue Sep 30, 2023
Add legal entity block when commercial_partner.is_company = True
OCA-git-bot pushed a commit to bosd/edi that referenced this issue Oct 2, 2023
Add legal entity block when commercial_partner.is_company = True
aronabencherif pushed a commit to xcgd/edi that referenced this issue Nov 7, 2023
Add legal entity block when commercial_partner.is_company = True
TDu pushed a commit to camptocamp/edi that referenced this issue Nov 22, 2023
Add legal entity block when commercial_partner.is_company = True
petrus-v pushed a commit to petrus-v/edi that referenced this issue Dec 18, 2023
Add legal entity block when commercial_partner.is_company = True
Wodran14 pushed a commit to DynAppsNV/edi that referenced this issue Jun 3, 2024
Add legal entity block when commercial_partner.is_company = True
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

No branches or pull requests

2 participants