Formatwerk
einvoice archive pack
Validates the invoice with the KoSIT validator and builds a ZIP containing the unchanged invoice XML, the full validator report XML, a manifest.json with SHA-256 hashes of both files, the validator version, the validation time and the key invoice data (number, dates, seller, buyer, totals), and a README explaining the contents. The original bytes are never modified, as required for unchanged archiving under GoBD.
POST https://format.halowerk.com/v1/einvoice-archive-packInputs
| Field | Type | Required | Description |
|---|---|---|---|
| xml | string | Yes | XRechnung/EN 16931 invoice in UBL or CII syntax. |
Show full input schema
{
"type": "object",
"additionalProperties": false,
"required": [
"xml"
],
"properties": {
"xml": {
"type": "string",
"minLength": 50,
"maxLength": 5000000,
"description": "XRechnung/EN 16931 invoice in UBL or CII syntax."
}
}
}Published input example
{
"xml": "<?xml version=\"1.0\" encoding=\"UTF-8\"?><Invoice xmlns=\"urn:oasis:names:specification:ubl:schema:xsd:Invoice-2\">…</Invoice>"
}Result & documentation
Machine-readable documentation of this hub
Source of this page: the published HALOWERK catalog. Updated: 2026-11-17 UTC.
More endpoints in this hub
- Formatwerk0.004 USDC
accounting csv unify
POSThttps://format.halowerk.com/v1/accounting-csv-unifyDATEV booking batch files (EXTF/DTVF, category 21) are read by their documented field positions: amount and S/H become a signed amount relative to the account, Belegdatum TTMM is resolved within the fiscal year from the header. Other export
- Formatwerk0.005 USDC
avv checklist
POSThttps://format.halowerk.com/v1/avv-checklistChecklist after Art. 28 GDPR (Regulation (EU) 2016/679 Art. 28 (GDPR), https://eur-lex.europa.eu/eli/reg/2016/679/oj, German and English text retrieved from the EU Publications Office 2026-11-01): Art. 28(3) sentence 1 (subject-matter, dura
- Formatwerk0.004 USDC
bagit package
POSThttps://format.halowerk.com/v1/bagit-packageCreate: files go to data/, manifest-<alg>.txt and tagmanifest-<alg>.txt are written for SHA-256 (default), SHA-512 or legacy SHA-1/MD5, bag-info.txt gets your metadata plus Bagging-Date, Bag-Size and Payload-Oxum; paths are checked (no abso