This module will make posible to send e-invoice / e-transport to Romanian goverment anaf.ro.
To use this module you must have a digital signature usb token from Romania connected with a ANAF account.
Table of contents
Installation
To install this module, you need to:
clone the branch 14.0 of the repository https://github.com/OCA/l10n-romania
add the path to this repository in your configuration (addons-path)
update the module list
search for “Romania - Account ANAF Sync” in your addons
install the module
Configuration
Go to https://pfinternet.anaf.ro/my.policy put put your username and password and code that came on email (or create a new user if you do not have)
Go to “Editare profil Oauth”
At profile Oauth
put some text at “Denumire Aplicatie”
at callback URL 1 put your Odoo instance url: /l10n_ro_account_anaf_sync/anaf_oauth
(if you odoo site is https://odoo.zzz.ro you must put https://odoo.zzz.ro/l10n_ro_account_anaf_sync/anaf_oauth url shown also in odoo company e-invoice tab)
at Serviciu check e-factura and/or e-transport
press Generare Client ID
Copy the Client ID and Client Secret.
Go to Odoo instance and from Settings -> Romania -> Configure ANAF sync create a new record for each company that you have access on ANAF website.
From a computer that can connect to anaf.ro and login with digital signature.
With the usb Token inserted press in Odoo the button Get Token from Anaf. It will ask you for usb token pin. You will get a error or a token and a new valability date If the ANAF website is not asking for a pin you must open and close your browser to ask you again the signature token pin
If you do not have errors press the test button and all should be ok.
The access token can be used also to test in other ways like
> curl "https://api.anaf.ro/TestOauth/jaxrs/hello?name=bbb" -H "Authorization: Bearer a010f5e7dd3e44d114d73729419bd1b9968b92fe2015f0512dcZZZZZZZZ" -i Future
Info:
https://mfinante.gov.ro/web/efactura/informatii-tehnice
https://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
-
Fekete Mihai <feketemihai@nexterp.ro>
-
Anastasescu Răzvan-Ioan <razvan@qdev.ro>
Do not contact contributors directly about support or help with technical issues.
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainer:
This module is part of the OCA/l10n-romania project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Metadata
Release files for odoo-addon-l10n-ro-account-anaf-sync 17.0.1.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_addon_l10n_ro_account_anaf_sync-17.0.1.6.0-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_l10n_ro_account_anaf_sync-17.0.1.6.0-py3-none-any.whl |
Release files / odoo_addon_l10n_ro_account_anaf_sync-17.0.1.6.0-py3-none-any.whl
| Download URL | odoo_addon_l10n_ro_account_anaf_sync-17.0.1.6.0-py3-none-any.whl |
|---|---|
| Size | 2.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
69f11acbb2172430991a2a33219b659bb6ef50f2201defc245d9810f0ff528ad
|
|
BLAKE2b-256 checksum How to use checksums |
91ce6cc14b4fb94c224cb77e16dab548460a0a032f8816463d482916d4e64cf5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Security for odoo-addon-l10n-ro-account-anaf-sync 17.0.1.6.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.