- Multilang swiss STERCHI account chart and taxes
Author: Camptocamp SA
Financial contributors: Prisme Solutions Informatique SA, Quod SA
Translation contributors: brain-tec AG, Agile Business Group
This release will introduce major changes to l10n_ch.
Due to important refactoring needs and the Switzerland adoption of new international payment standard during 2013-2014. We have reorganised the swiss localization addons this way:
l10n_ch: Multilang swiss STERCHI account chart and taxes (official addon)
l10n_ch_base_bank: Technical module that introduces a new and simplified version of bank type management
l10n_ch_bank: List of swiss banks
l10n_ch_zip: List of swiss postal zip
l10n_ch_dta: Support of dta payment protocol (will be deprecated end 2014)
l10n_ch_payment_slip: Support of ESR/BVR payment slip report and reconciliation. Report refactored with easy element positioning.
l10n_ch_sepa: Alpha implementation of PostFinance SEPA/PAIN support will be completed during 2013/2014
The modules will be soon available on OpenERP swiss localization on launchpad: https://launchpad.net/openerp-swiss-localization
Metadata
Release files for openerp-l10n-ch 7.0.406
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| openerp-l10n-ch-7.0.406.tar.gz | 277.5 kB | Without provenance | Details for openerp-l10n-ch-7.0.406.tar.gz |
Release files / openerp-l10n-ch-7.0.406.tar.gz
| Download URL | openerp-l10n-ch-7.0.406.tar.gz |
|---|---|
| Size | 277.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c035f97a43a1b3739c4e4a563d07b6e65ae80ff0e5c14f7ba640260f4bd8a8c6
|
|
BLAKE2b-256 checksum How to use checksums |
7a2fcde9f1d907d392e5b6daaf4b99b3adc93e29415217f40605e1003fd8371c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for openerp-l10n-ch 7.0.406
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.