Datev Lohnbescheinigung Splitter
Datev Lohnabrechnungen beinhalten immer alle Lohnbescheinigungen und Meldebescheinigungen für alle Mitarbeitenden. Um diese automatisiert nach Personalnummer in einzelne pdf splitten zu können, gibt es dieses script.
Erwarteter Input
Datev Datei (pdf) mit Entgeltabrechnungen, Lohnbescheinigungen und/oder Meldebescheinigungen zur Sozialversicherung.
Ergebnis
Einzelne pdf Dateien, die jeweils die Informationen für zu einer einzelnen Personalnummer enthalten. Im Original zusammenhängende Seiten zu einer Personalnummer werden auch zusammen exportiert.
Benutzung
usage: datev_splitr [-h] [-q] [-d] [-t] [-p PREFIX] [-o OUTPUT] [-e EXPORT_PNS] infile
positional arguments:
infile Datev file to process
options:
-h, --help show this help message and exit
-q, --quiet Show only warnings and errors
-d, --debug Show more context
-t, --trace Show even more context / trace
-p PREFIX, --prefix PREFIX
Prefix for all result files
-o OUTPUT, --output OUTPUT
Where to write the output files (path must exist)
-e EXPORT_PNS, --export-pns EXPORT_PNS
Export csv file with processed Personalnummern.
Beispiel
datev_splitr -p PREFIX- -o tmp -d auswertungen.pdf
oder in der Entwicklungsumgebung
pdm run python pdf_extract.py -p PREFIX- -o tmp -d auswertungen.pdf
Erstellt im Unterordner tmp alle Dateien mit dem prefix PREFIX-.
D.h. Die Dateien heißen dann bspw.: PREFIX-00203-2022-Dezember.pdf für eine Lohnabrechnung Dezember 2022,
Personalnummer 00203
-e pns.csv Exportiert die Personalnummern mit und ohne Prefix und den gefundenen Namen.
Mit dem Prefix RD- sieht das Ergebnis bspw so aus:
RD-00004,00004,vorname name
RD-00006,00006,vorname2 name2
RD-00014,00014,vorname3 name3
Welche Seiten werden exportiert?
- Praktisch alle auf denen eine Personalnummer zu finden ist
Metadata
Release files for Datev-Splitter 0.5.0
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 | |
|---|---|---|---|---|
| Datev-Splitter-0.5.0.tar.gz | 7.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| Datev_Splitter-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.5 kB
Release files / Datev-Splitter-0.5.0.tar.gz
| Download URL | Datev-Splitter-0.5.0.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b140e6cf856766f6a9fdd637a14a195cd2494c8519c54210baabbdb21d0f6203
|
|
BLAKE2b-256 checksum How to use checksums |
c9a569d6c1b9a9d94c9385e87cdf7f67354040a5e936b92668edb0e1f288664a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.9.2 readme-renderer/37.3 requests/2.28.1 requests-toolbelt/0.10.1 urllib3/1.26.13 tqdm/4.64.1 importlib-metadata/6.0.0 keyring/23.13.1 rfc3986/2.0.0 colorama/0.4.6 CPython/3.10.6
|
Release files / Datev_Splitter-0.5.0-py3-none-any.whl
| Download URL | Datev_Splitter-0.5.0-py3-none-any.whl |
|---|---|
| Size | 6.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
66a55d259aff441e657295f9ee9e0ed3eb8603f88009ebe6a1274ee0e05ba4de
|
|
BLAKE2b-256 checksum How to use checksums |
40b75ee278b0422c58cb89a77a00c88270e817f96ca1011aee005f988e19ce04
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.9.2 readme-renderer/37.3 requests/2.28.1 requests-toolbelt/0.10.1 urllib3/1.26.13 tqdm/4.64.1 importlib-metadata/6.0.0 keyring/23.13.1 rfc3986/2.0.0 colorama/0.4.6 CPython/3.10.6
|
Security for Datev-Splitter 0.5.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.