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

Gap analysis to reach german market requirements #19328

Open
1 of 14 tasks
wojosc opened this issue Oct 16, 2019 · 12 comments
Open
1 of 14 tasks

Gap analysis to reach german market requirements #19328

wojosc opened this issue Oct 16, 2019 · 12 comments

Comments

@wojosc
Copy link
Contributor

wojosc commented Oct 16, 2019

@wojosc
Copy link
Contributor Author

wojosc commented Nov 29, 2019

Numbers/Digits: In Germany we seperate the thousends with a dot and the decimal place as comma (instead of dot/point) eg 4.599,99 € https://discuss.erpnext.com/t/v12-1-6-decimals-in-currencies-not-working/53486/21

Seems to work now...

@barredterra
Copy link
Collaborator

Adresses are Street No, "second Adress line", Postalcode (5 digits or less), City. County is not commonly used.

https://github.com/frappe/erpnext/blob/develop/erpnext/regional/germany/address_template.html

@mariotruss
Copy link

@barredterra Is this in the core already?

@barredterra
Copy link
Collaborator

barredterra commented Dec 5, 2019

Yes!

I just added a fix: #19828 , please let me know what you think.

@barredterra
Copy link
Collaborator

Minor issue: #19855

@barredterra
Copy link
Collaborator

barredterra commented Dec 7, 2019

I created two pull requests to add the German CoA "SKR03":

Please upvote the one you like more and leave a comment why.

@barredterra
Copy link
Collaborator

Compliance to the GoBD, including this report, is a hard requirement in case any German company is supposed to do their accounting with ERPNext:

@crescent28
Copy link
Contributor

@wojosc Create a discuss post for community to contribute for this kind of requirements.

@christf
Copy link

christf commented Oct 7, 2020

GoBD is fairly easy when used in combination with a git repository that was configured for the purpose (no history rewriting on the master branch, each change creates a commit that is pushed on submet). Conversions to pdf actually do not help.

@wojosc
Copy link
Contributor Author

wojosc commented Oct 8, 2020

In v13 there will be an immutable ledger. I think this will cover most of the requirements. I suggest to wait for that befor we proceed any further.

@barredterra
Copy link
Collaborator

@christf you are legally required to keep the PDF you sent to a business partner, unless you are able to reproduce it exactly in the future. We cannot reproduce it exactly, so we have to keep it.

@ankush ankush added the to-validate Old issues pending validation label Dec 10, 2021
@ankush ankush removed the to-validate Old issues pending validation label Jan 19, 2022
@stale
Copy link

stale bot commented Mar 20, 2022

This issue has been automatically marked as inactive because it has not had recent activity and it wasn't validated by maintainer team. It will be closed within a week if no further activity occurs.

@stale stale bot added the inactive label Mar 20, 2022
@ankush ankush added the valid label Mar 20, 2022
@stale stale bot removed the inactive label Mar 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants