# Interest in developing account\_tr, edocument\_ubl Turkish extensions, and a generic R&D module

**URL:** https://discuss.tryton.org/t/interest-in-developing-account-tr-edocument-ubl-turkish-extensions-and-a-generic-r-d-module/9196
**Category:** Ideas
**Created:** [April 10, 2026, 10:23am UTC](https://discuss.tryton.org/t/interest-in-developing-account-tr-edocument-ubl-turkish-extensions-and-a-generic-r-d-module/9196 "2026-04-10T10:23:19Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![saimgulay](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/saimgulay/32/3846_2.png) [@saimgulay](https://discuss.tryton.org/u/saimgulay)
#### Post date: [April 10, 2026, 10:23am UTC](https://discuss.tryton.org/t/interest-in-developing-account-tr-edocument-ubl-turkish-extensions-and-a-generic-r-d-module/9196/1 "2026-04-10T10:23:20Z")

</div>

Hello Tryton community,

I am a developer based in the UK, currently building and testing localisation modules for Turkey while also exploring a generic module that could benefit the broader community. I wanted to share my roadmap here to get early feedback and understand whether these contributions would be welcome upstream.

**What I have built so far (locally, under real-world testing):**

**`account_tr`** : A Turkish accounting localisation module following the same pattern as `account_de_skr03`, `account_es`, etc. It defines the Turkish chart of accounts aligned with the Turkish Uniform Accounting System (Tek Düzen Hesap Planı).

**Turkish e-document support** : Rather than creating a separate module, I have extended the existing `edocument_ubl` module using the specification concept pattern already established in the codebase, to support Turkish e-invoice (e-fatura) and e-dispatch note (e-irsaliye) formats as required by the Turkish Revenue Administration (GİB). I believe this is the correct upstream approach.

Both are currently being validated in a real production environment at a manufacturing company in Turkey. Once I am satisfied with the test coverage and stability, I plan to split the work into focused MRs for community review.

**Future interest: generic Research&Development module:**

After the above contributions are settled, I am interested in proposing a generic `project_research` or similar module to support Research & Development activity tracking. This would build on top of `project`, `timesheet`, and `analytic_account`, and would not be Turkey-specific. I have not seen this discussed before and wanted to gauge whether there is broader interest before investing time in a blueprint.

**Further down the road:**

I also intend to work on a `account_gb` module and Making Tax Digital (MTD) compliance for the UK, though these are longer-term goals.

I would greatly appreciate any early feedback — particularly on whether the `edocument_ubl` extension approach is acceptable to the core team, and whether a generic R&D module is something the community sees value in.

Thank you for the work you do on this platform.

---

<div class="post-metadata">

### Author: ![s.vogel](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/s.vogel/32/2328_2.png) [@s.vogel](https://discuss.tryton.org/u/s.vogel)
#### Post date: [April 14, 2026, 1:42pm UTC](https://discuss.tryton.org/t/interest-in-developing-account-tr-edocument-ubl-turkish-extensions-and-a-generic-r-d-module/9196/2 "2026-04-14T13:42:13Z")

</div>

Dear Saïm

We’d appreciate an r&d module very much. Actually, we use the normal project module but more features would be helpful.

Cheers, Stefan

---

<div class="post-metadata">

### Author: ![ced](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/ced/32/1237_2.png) [@ced](https://discuss.tryton.org/u/ced)
#### Post date: [April 16, 2026, 6:15am UTC](https://discuss.tryton.org/t/interest-in-developing-account-tr-edocument-ubl-turkish-extensions-and-a-generic-r-d-module/9196/3 "2026-04-16T06:15:32Z")

</div>

I recently published my position about such topic on [Standard module maintained by externals](https://discuss.tryton.org/t/standard-module-maintained-by-externals/9178)  
So I doubt we will be able to accept and maintain an `account_tr` inside the official Tryton module for now.  
The extension of UBL may depend because UBL is a standard so normally it should not be country related (except maybe for some kind of identifier). But if it is new format that are only described and required by the Turkish administration, I do not think we could accept and support such module.  
About `project_research`, my concern is that it sounds like a verticalisation with a specific workflow in mind. But official modules must be generic and implement common and flexible workflow. So this will depend on what you put in this module.  
And for `account_gb` I fear we will be in the same situation as for `account_de_skr03` and `account_es`.

In short if you want to submit module to be included as official modules in Tryton, it must solve a general issue/workflow in the most generic way possible.

---

<div class="post-metadata">

### Author: ![saimgulay](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/saimgulay/32/3846_2.png) [@saimgulay](https://discuss.tryton.org/u/saimgulay)
#### Post date: [April 16, 2026, 12:38pm UTC](https://discuss.tryton.org/t/interest-in-developing-account-tr-edocument-ubl-turkish-extensions-and-a-generic-r-d-module/9196/4 "2026-04-16T12:38:27Z")

</div>

Thank you Cédric, and Stefan, for the clear and honest feedback.

I understand the reasoning behind the policy on externally maintained locale modules and I think it is a sound one. My motivation for proposing these upstream was that I did not want to use Tryton commercially without contributing back. But given the current policy, I will maintain account\_tr and the Turkish e-document support as external modules under GPL-3, outside the core.

If over the next few years I can demonstrate sustained maintenance to core standards, I may revisit the proposal. And if anything I develop turns out to be genuinely generic and a good fit for upstream, I will rewrite it accordingly and bring it forward at that point.

Thanks again for the work you put into the platform.

---

<div class="post-metadata">

### Author: ![pokoli](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/pokoli/32/22_2.png) [@pokoli](https://discuss.tryton.org/u/pokoli)
#### Post date: [April 16, 2026, 12:44pm UTC](https://discuss.tryton.org/t/interest-in-developing-account-tr-edocument-ubl-turkish-extensions-and-a-generic-r-d-module/9196/5 "2026-04-16T12:44:25Z")

</div>

> [@saimgulay](#):
>
> My motivation for proposing these upstream was that I did not want to use Tryton commercially without contributing back. But given the current policy, I will maintain account\_tr and the Turkish e-document support as external modules under GPL-3, outside the core.

If you are interested in sharing in a common tryton repository we have shared hosting under the [tryton community](https://tryton.community/) umbrella.

We recently moved the localization modules not maintained as core modules there. Turkish modules will be also welcome there. Feel free to contact me to discuss more details, or just join the project project and request your modules repository.

---

<div class="post-metadata">

### Author: ![saimgulay](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/saimgulay/32/3846_2.png) [@saimgulay](https://discuss.tryton.org/u/saimgulay)
#### Post date: [April 17, 2026, 9:52am UTC](https://discuss.tryton.org/t/interest-in-developing-account-tr-edocument-ubl-turkish-extensions-and-a-generic-r-d-module/9196/6 "2026-04-17T09:52:46Z")

</div>

Thank you Sergi. That sounds like exactly the right home for these modules. I will join the project and reach out to discuss the details very soon. Looking forward to it.
