镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

[ADD] l10n_kr: add documentation for South Korean localization - #20846

Open
kidoodoo wants to merge 1 commit into
20.0from
20.0-l10n-kr-new-page-KIDO
Open

kidoodoo wants to merge 1 commit into
20.0from
20.0-l10n-kr-new-page-KIDO

Conversation

@kidoodoo

@kidoodoo kidoodoo commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

This commit adds the South Korea fiscal localization page, covering:

  • Modules
  • Localization overview: chart of accounts, reporting, taxes (sales, purchases, deemed input tax at another rate, simplified taxpayers), and fiscal positions
  • Contacts
  • Accounting: proof of issuance, tax report, and payment providers
  • Sales

This commit adds the South Korea fiscal localization page, covering:
- Modules
- Localization overview: chart of accounts, reporting, taxes (sales,
  purchases, deemed input tax at another rate, simplified taxpayers),
  and fiscal positions
- Contacts
- Accounting: proof of issuance, tax report, and payment providers
- Sales
@robodoo

robodoo commented Nov 3, 2026

Copy link
Copy Markdown
Collaborator

Pull request status dashboard

🤖 Open bundle on Runbot

@C3POdoo
C3POdoo requested a review from a team November 3, 2026 04:17
@kidoodoo

kidoodoo commented Nov 3, 2026

Copy link
Copy Markdown
Contributor Author

Leaving message here for the reviewer.

I would like to check if I should communicate with the translation team for the details that needs to be careful about. For instance, this documentation contains English version of the tax names. Such as 10%, 10% FA and etc. In Odoo db installed in Korean language, it is 부가세 10%, 부가세 10% (불공제).

Wanted to check how I can better handle these cases. We do not have a Korean translator yet, but we will have one soon I heard.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants