Belgian localization for in- and outgoing invoices (prereq to account_coda):
Rename ‘reference’ field labels to ‘Communication’
Add support for Belgian Structured Communication
A Structured Communication can be generated automatically on outgoing invoices according to the following algorithms:
- Random+++RRR/RRRR/RRRDD+++
R..R = Random Digits, DD = Check Digits
- Date+++DOY/YEAR/SSSDD+++
DOY = Day of the Year, SSS = Sequence Number, DD = Check Digits
- Customer Reference +++RRR/RRRR/SSSDDD+++
R..R = Customer Reference without non-numeric characters, SSS = Sequence Number, DD = Check Digits
The preferred type of Structured Communication and associated Algorithm can be specified on the Partner records. A ‘random’ Structured Communication will generated if no algorithm is specified on the Partner record.
Metadata
Release files for openerp-l10n-be-invoice-bba 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-be-invoice-bba-7.0.406.tar.gz | 12.2 kB | Without provenance | Details for openerp-l10n-be-invoice-bba-7.0.406.tar.gz |
Release files / openerp-l10n-be-invoice-bba-7.0.406.tar.gz
| Download URL | openerp-l10n-be-invoice-bba-7.0.406.tar.gz |
|---|---|
| Size | 12.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5ca12e036b0712d6ba02b3ff736814d2cc38daaf3b1749c9bb1526fe1f3723d2
|
|
BLAKE2b-256 checksum How to use checksums |
adeb321047143b50d90c437d25f24a0b48d7da1db7ba27f71c83de0ea0b421ed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for openerp-l10n-be-invoice-bba 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.