> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.invoice-api.xhub.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.invoice-api.xhub.io/_mcp/server.

# Parse SK — Peppol BIS 3.0 UBL (cross-border)

POST https://service.invoice-api.xhub.io/api/v1/invoice/sk/peppol-ubl/parse
Content-Type: application/json

Parse a **SK — Peppol BIS 3.0 UBL (cross-border)** document. No pre-generated sample is shipped for this country/format yet — replace the `data` field with your own base64-encoded document before sending. Requires `e-invoice:sk:peppol-ubl:parse` entitlement.

Reference: https://docs.invoice-api.xhub.io/api-reference/parse/sk/peppol-ubl

## Authentication

- `Authorization` header (bearer token, required) — API Key authentication. Use `sk_live_*` for production or `sk_test_*` for testing.

## Servers

- `https://service.invoice-api.xhub.io` (Invoice API v1 (production), default)
- `/` (Diese Instanz (lokale Entwicklung))

## Request

### Body (application/json)

This endpoint expects an object.

- `data` (string, required) — Base64 encoded document (XML or PDF with embedded XML)
- `filename` (string, optional) — Original filename (helps detect format)

## Response

### 200

Invoice parsed successfully

- `success` (boolean, required) — Whether parsing was successful
- `invoice` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoice, optional) — Extracted invoice data
- `format` (string, optional) — Detected format (e.g., ZUGFERD_EN16931)
- `hash` (string, optional) — SHA-256 hash of the input document
- `errors` (list of ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaErrorsItems, optional) — Parsing errors (if any)
- `warnings` (list of ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaWarningsItems, optional) — Parsing warnings (if any). A party address without a country (seller, buyer, tax representative, payee) gets the country of the format, and the warning `PARTY_COUNTRY_ASSUMED` names the field and the place in the document.
- `infos` (list of ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInfosItems, optional) — Informational messages (e.g., XML extracted from PDF)

## Errors

### 400 Bad Request Error

Bad Request - Invalid document or unsupported format

- `PostApiV1InvoiceSkPeppolUblParseRequestBadRequestError`
  - ErrorResponse: ErrorResponse
  - RequestValidationError: RequestValidationError

### 401 Unauthorized Error

Unauthorized - Invalid or missing API key

- `error` (string, required) — Error code
- `message` (string, required) — Human-readable error message
- `code` (string, optional) — Machine-readable reason, where one exists — e.g. `UNSUPPORTED_FORMAT_VERSION`, `UNSUPPORTED_FORMAT_PROFILE`, `CONFLICTING_FORMAT_OPTIONS`
- `field` (string, optional) — The request field the error refers to, where one exists

### 403 Forbidden Error

Forbidden - Missing required entitlement

- `error` (string, required) — Error code
- `message` (string, required) — Human-readable error message
- `code` (string, optional) — Machine-readable reason, where one exists — e.g. `UNSUPPORTED_FORMAT_VERSION`, `UNSUPPORTED_FORMAT_PROFILE`, `CONFLICTING_FORMAT_OPTIONS`
- `field` (string, optional) — The request field the error refers to, where one exists

### 429 Too Many Requests Error

Quota Exceeded - Usage limit reached

- `error` ("QUOTA_EXCEEDED", required) — Error code
- `message` (string, required) — Error message
- `quota` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaQuota, required)

### 500 Internal Server Error

Internal Server Error

- `error` (string, required) — Error code
- `message` (string, required) — Human-readable error message
- `code` (string, optional) — Machine-readable reason, where one exists — e.g. `UNSUPPORTED_FORMAT_VERSION`, `UNSUPPORTED_FORMAT_PROFILE`, `CONFLICTING_FORMAT_OPTIONS`
- `field` (string, optional) — The request field the error refers to, where one exists

## Types

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoice

Extracted invoice data

- `invoiceNumber` (string, required) — Unique invoice number
- `type` (enum, required) — Invoice type. Maps to BT-3 (UNTDID 1001) where the target format supports it: invoice=380, credit_note=381, correction=384, proforma=325, partial=326, partial_construction=875, partial_final_construction=876, final_construction=877, self_billed=389. Where a format has no code for the type (e.g. Peppol BIS outside DE-to-DE, where PEPPOL-EN16931-P0112 restricts both 326 (partial) and 384 (correction) to a DE seller together with a DE buyer), the document is issued as 380 and the response carries a DOCUMENT_TYPE_FALLBACK warning — never silently, and never a silent 381: `correction` on a non-DE-to-DE Peppol route always falls back to 380, not to the credit-note code. Where the type is not permitted at all (proforma in XRechnung/Peppol BIS), the request is rejected with HTTP 422. Note: `partial` (326) is a partial invoice for a delivered instalment. A prepayment REQUEST is not 386 — 386 is not permitted in XRechnung; use type=invoice, and report prepayments already received via `prepayments` (BT-113).
  - Allowed values: `invoice`, `credit_note`, `proforma`, `correction`, `partial`, `partial_construction`, `partial_final_construction`, `final_construction`, `self_billed`
- `issueDate` (string, required) — Issue date (ISO 8601: YYYY-MM-DD)
- `seller` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceSeller, required) — Seller party information
- `buyer` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceBuyer, required) — Buyer party information
- `items` (list of InvoiceLineItem, required) — Invoice line items. Hard ceiling: 5000, or 25000 where large-invoice validation is enabled (`maxItems` shows the value of the server you call). Routes that render a PDF layout stay at 5000 — `/generate` for `pdf` or a hybrid format such as ZUGFeRD or Factur-X, and `/convert` into a hybrid format; above that they answer 400 with the same `too_big` body (`maximum: 5000`). To embed the XML of a larger invoice into your own PDF, use `/embed`. Your plan may allow fewer — a request above the plan limit is rejected with 400 `TOO_MANY_LINE_ITEMS`. Sub-items (`subItems`) count as lines: above 25000 lines in total the request is rejected with 400 `TOO_MANY_INVOICE_LINES`; above 5000 lines in total on a server without large-invoice validation the response carries the warning `INVOICE_LINES_ABOVE_MODE_LIMIT`.
- `currency` (string, required) — Currency code (ISO 4217, three upper-case letters). A code outside ISO 4217 is rejected under `/api/v2` with 400 `INVALID_CURRENCY` (`field: currency`); under `/api/v1` the request is processed as before and `warnings` carries `CURRENCY_CODE_UNKNOWN`.
- `subtotal` (double, required) — Total net amount
- `total` (double, required) — Total gross amount
- `taxSummary` (list of ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceTaxSummaryItems, required) — Tax summary per tax rate
- `dueDate` (string, optional) — Due date (ISO 8601: YYYY-MM-DD). Optional when payment terms (BT-20) are given.
- `deliveryDate` (string, optional) — Delivery/service date (ISO 8601)
- `servicePeriod` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceServicePeriod, optional) — Service period (Leistungszeitraum, BG-14). Required in DE if different from issueDate. Send `start`, `end` or both (BR-CO-19); an empty object returns a 400. Formats whose schema requires both dates (ebInterface, Facturae) return a 400 `INVOICE_SERVICE_PERIOD_BOTH_DATES_REQUIRED` when one is missing; ISDOC has no invoicing period and reports `INVOICE_SERVICE_PERIOD_NOT_REPRESENTABLE` as a warning.
- `payee` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoicePayee, optional) — Payee (BG-10), if different from the seller. On the CH/LI QR bill (`qr-bill`) the payee is the creditor: postal code, city, country and its own bank account are required.
- `paymentTerms` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoicePaymentTerms, optional) — Payment terms
- `cashDiscountPercent` (double, optional) — Cash discount (Skonto) percentage agreed on the document. > 0, \<= 100, at most two decimals. On German e-invoices this becomes the #SKONTO#TAGE=n#PROZENT=n.nn# line inside the payment terms note (BR-DE-18). Ignored when paymentTerms.earlyPaymentDiscount is present.
- `cashDiscountDays` (integer, optional) — Days within which the cash discount applies (integer, 0..365).
- `cashDiscountBaseAmount` (double, optional) — Optional base amount for the cash discount when it is not the payable amount (BASISBETRAG segment, BR-DE-18).
- `paymentMethods` (list of ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoicePaymentMethodsItems, optional) — Payment methods accepted for this invoice. Used in ZUGFeRD/XRechnung to generate SpecifiedTradeSettlementPaymentMeans. For bank_transfer, seller.bankAccount must also be set.
- `orderNumber` (string, optional) — Purchase order number (Bestellnummer)
- `customerNumber` (string, optional) — Customer number at the seller
- `contractNumber` (string, optional) — Contract number (BT-12)
- `projectNumber` (string, optional) — Project reference (BT-11). More than 100 characters: warning `FIELD_TOO_LONG` (field `projectNumber`), the value is written unchanged; a later release rejects it with 400.
- `tenderReference` (string, optional) — Tender or lot reference (BT-17). Several public contracting authorities reject an invoice without it. Rendered as `cac:OriginatorDocumentReference`.
- `objectId` (string, optional) — Object identifier of the invoice (BT-18) — the thing the invoice is about, e.g. a contract object or a plant. Rendered as `cac:AdditionalDocumentReference` with `cbc:DocumentTypeCode` 130.
- `objectIdScheme` (string, optional) — Scheme of the object identifier (BT-18-1, UNTDID 1153).
- `businessProcess` (string, optional) — Business process type (BT-23). Rendered as `cbc:ProfileID`. When omitted the generator emits the profile the target format prescribes.
- `roundingAmount` (double, optional) — Rounding amount (BT-114)
- `prepaidAmount` (double, optional) — Amount already paid in advance (BT-113) — a deposit or down payment the buyer has already transferred. Lowers the payable amount only (BR-CO-16: BT-115 = BT-112 − BT-113 + BT-114); the taxable base (BT-109) and the tax amounts stay unchanged, because the buyer paid earlier, not less. Emitted as `cbc:PrepaidAmount` (UBL) resp. `ram:TotalPrepaidAmount` (CII), and as the national equivalent in ISDOC (`PaidDepositsAmount`), ebInterface (`PrepaidAmount`) and Facturae (`TotalPaymentsOnAccount`). Formats without an already-paid element ignore it: FatturaPA, myDATA, NAV, Swiss/Liechtenstein QR-Bill, SAF-T PT, ATCUD/AT-QR and TicketBAI/LROE/VeriFactu. KSeF FA(3) also omits it — it models payment *events* (amount plus payment date), and inventing a date for a clearance system would be worse than the missing amount.
- `allowancesCharges` (list of ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceAllowancesChargesItems, optional) — Invoice-level allowances (discounts) and charges (surcharges) (BG-20 / BG-21). For line-level discounts, use items[].discount instead.
- `delivery` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceDelivery, optional) — Delivery information (BG-13). Includes delivery date (BT-72), deliver-to name (BT-70), location identifier (BT-71), and delivery address (BG-15).
- `directDebitMandate` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceDirectDebitMandate, optional) — Direct debit mandate (BG-19). Send it with direct_debit: most formats (XRechnung, Peppol PEPPOL-EN16931-R061) require the mandate reference for payment means code 49 and 59.
- `cardAccount` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceCardAccount, optional) — Card payment details (BG-18). Set it together with a card payment means code (BT-81 = 48, 54 or 55). Formats that cannot represent the group report a GROUP_NOT_REPRESENTABLE warning instead of dropping it silently.
- `supportingDocuments` (list of ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceSupportingDocumentsItems, optional) — References to supporting documents WITHOUT the file (BT-122/BT-123) — for the file itself use `attachments`. Oman needs the registryId here for the prepayment document and for exports with VATZR-OM-12.
- `retention` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceRetention, optional) — Security retention. Reduces only the payment, never the totals or the VAT. Written as a sentence into the payment terms (BT-20 or the national equivalent) of every e-invoice format that has payment terms, in the language of the seller (machine-translated for FR, NL, IT, ES, PL; English for other languages). A reason you send is used as given and is not translated. Do not use allowancesCharges for it. Formats or profiles without payment terms (ZUGFeRD and Factur-X MINIMUM, and myDATA without a payment method) reject the request with 422 (RETENTION_NOT_CARRIED); a plain PDF is not affected.
- `prepayments` (list of ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoicePrepaymentsItems, optional) — The individual prepayments behind `prepaidAmount` (BT-113). Needed where a country requires the prepayment invoice to be referenced — Oman writes each one as `cac:AdditionalDocumentReference` with document type code PDR. Elsewhere `prepaidAmount` alone is enough.
- `notes` (string, optional) — Additional notes displayed on the invoice
- `profile` (enum, optional) — XRechnung CIUS profile. `xrechnung` produces the standard CustomizationID `urn:cen.eu:en16931:2017#compliant#urn:xoev-de:kosit:standard:xrechnung_3.0`. `xrechnung-extension` produces the EXTENSION CustomizationID `urn:cen.eu:en16931:2017#compliant#urn:xoev-de:kosit:standard:xrechnung_3.0#conformant#urn:xoev-de:kosit:extension:xrechnung_3.0` which unlocks the additional XRechnung-EXTENSION business terms (subItems, third-party payments, ...). Defaults to `xrechnung` when omitted.
  - Allowed values: `xrechnung`, `xrechnung-extension`
- `referencedInvoiceNumber` (string, optional) — Number of the previously issued invoice this document references (BT-25, BG-3). Used for credit notes, corrections, and partial-invoice chains. Renders as `<cac:BillingReference>` in UBL / `IncludedNote` reference in CII.
- `referencedInvoiceDate` (string, optional) — Issue date of the referenced invoice (BT-26, ISO 8601 YYYY-MM-DD). Pairs with `referencedInvoiceNumber`.
- `deliveryNote` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceDeliveryNote, optional) — Despatch advice / delivery note reference (BT-16 / BT-17). Renders as `<cac:DespatchDocumentReference>` in UBL.
- `thirdPartyPayments` (list of ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceThirdPartyPaymentsItems, optional) — Third-party prepaid payments (BG-DEX-09, ZUGFeRD EXTENDED). Each entry is rendered as `<cac:PrepaidPayment>` in UBL.
- `attachments` (list of ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceAttachmentsItems, optional) — Embedded supporting documents (BG-24 / BT-122..125). Rendered as `<cbc:EmbeddedDocumentBinaryObject>` in UBL. More than 20 attachments: warning `FIELD_TOO_LONG` (field `attachments`); a later release rejects it with 400.
- `serviceCategory` (enum, optional) — Service category hint for the reverse-charge note. When a line or the VAT breakdown uses `taxCategoryCode: "AE"`, the generator writes the mandatory note: with seller and buyer in the same country and `construction`, the national note (in Germany §13b UStG); otherwise the EU-wide note (Art. 226 No. 11a VAT Directive), where one exists for the seller country. Without the buyer's country the response carries `REVERSE_CHARGE_BUYER_COUNTRY_MISSING`.
  - Allowed values: `construction`, `general`
- `constructionTax` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceConstructionTax, optional) — German construction-tax block (§13b UStG / §48 EStG). Setting `exemptionCertificateNumber` triggers the `#FREISTELLUNG#` note in the generated invoice. `withholdingPercent` documents the Bauabzugsteuer rate.
- `countrySpecific` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceCountrySpecific, optional) — Country-specific invoice data. Must include countryCode matching the invoice country. For DE: buyerReference (BT-10, required), paymentMeansCode (BT-81), leitwegId (B2G), isKleinunternehmer (§19 UStG). Other countries have their own fields — see country-specific documentation.

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaErrorsItems

- `code` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaErrorsItemsCode, required) — Stable house code identifying the check (e.g. `DE_SELLER_CITY_001`, `NL_PAYMENT_MEANS_REQUIRED`, or `SPEC_RULE_FAILED` when a conformance gate objected). Never a standard rule identifier — look those up in `rule`. Safe to match on: it does not change when a rule is re-identified.
- `message` (string, required) — Error message
- `rule` (string, optional) — Identifier of the standard rule this finding violates (e.g. `BR-06`, `BR-DE-5`, `PEPPOL-EN16931-R008`), as published in EN 16931, Peppol BIS or the national CIUS. Present only when a pinned rulebook actually carries that rule and it governs this very check — so you can look it up and read the same statement. Absent means no standard rule covers this finding; the check is then ours alone and `code` names it.
- `field` (string, optional) — Field path (if applicable)
- `maximum` (double, optional) — Only on a `FIELD_TOO_LONG` warning: the limit of `field` — characters for a text field, base64 characters for `attachments[i].content` and `attachments[*].content`, the number of entries for `attachments`.
- `enforceFrom` (string, optional) — Only on a `SPEC_RULE_PENDING` warning: the date (`YYYY-MM-DD`, UTC) from which this finding is rejected with 422. Until then the document is still returned with 200.
- `specId` (string, optional) — Only on a `SPEC_RULE_PENDING` warning: the rulebook the newly enforced rule belongs to (e.g. `en16931-3.0.2-ubl`, `factur-x-1.08-extended`).
- `pendingKey` (string, optional) — Only on a `SPEC_RULE_PENDING` warning whose finding carries no standard rule identifier: a technical key of the finding (not a rule identifier — do not look it up in a rulebook). Stable, so you can recognise the same finding again. Absent when `rule` is present.

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaWarningsItems

- `code` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaWarningsItemsCode, required) — Stable house code identifying the check (e.g. `DE_SELLER_CITY_001`, `NL_PAYMENT_MEANS_REQUIRED`, or `SPEC_RULE_FAILED` when a conformance gate objected). Never a standard rule identifier — look those up in `rule`. Safe to match on: it does not change when a rule is re-identified.
- `message` (string, required) — Error message
- `rule` (string, optional) — Identifier of the standard rule this finding violates (e.g. `BR-06`, `BR-DE-5`, `PEPPOL-EN16931-R008`), as published in EN 16931, Peppol BIS or the national CIUS. Present only when a pinned rulebook actually carries that rule and it governs this very check — so you can look it up and read the same statement. Absent means no standard rule covers this finding; the check is then ours alone and `code` names it.
- `field` (string, optional) — Field path (if applicable)
- `maximum` (double, optional) — Only on a `FIELD_TOO_LONG` warning: the limit of `field` — characters for a text field, base64 characters for `attachments[i].content` and `attachments[*].content`, the number of entries for `attachments`.
- `enforceFrom` (string, optional) — Only on a `SPEC_RULE_PENDING` warning: the date (`YYYY-MM-DD`, UTC) from which this finding is rejected with 422. Until then the document is still returned with 200.
- `specId` (string, optional) — Only on a `SPEC_RULE_PENDING` warning: the rulebook the newly enforced rule belongs to (e.g. `en16931-3.0.2-ubl`, `factur-x-1.08-extended`).
- `pendingKey` (string, optional) — Only on a `SPEC_RULE_PENDING` warning whose finding carries no standard rule identifier: a technical key of the finding (not a rule identifier — do not look it up in a rulebook). Stable, so you can recognise the same finding again. Absent when `rule` is present.

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInfosItems

- `code` (string, required) — Info code (e.g., EXTRACTED_FROM_PDF)
- `message` (string, required) — Informational message

### ErrorResponse

- `error` (string, required) — Error code
- `message` (string, required) — Human-readable error message
- `code` (string, optional) — Machine-readable reason, where one exists — e.g. `UNSUPPORTED_FORMAT_VERSION`, `UNSUPPORTED_FORMAT_PROFILE`, `CONFLICTING_FORMAT_OPTIONS`
- `field` (string, optional) — The request field the error refers to, where one exists

### RequestValidationError

The request body failed the input check. `error` lists every finding; each names the field (`path`) and the rule (`code`). Depending on the code, a finding also carries the limit (`maximum`, `minimum`), the expected type (`expected`), the allowed values (`values`) or the unknown keys (`keys`).

- `success` (false, required)
- `error` (list of RequestValidationErrorErrorItems, required)

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaQuota

- `current` (double, required) — Current usage count
- `limit` (double, required) — Usage limit
- `period` (string, optional) — Quota period type of the plan quota that was hit, when the rejection carries one ('monthly', 'yearly', ...). Absent whenever the rejection has no period at all — for example a lapsed subscription, where the limit is 0 and no plan quota was involved. This is a period TYPE, never a calendar label such as "2026-03".

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceSeller

Seller party information

- `name` (string, required) — Legal name of the party
- `countryCode` (string, required) — Country code (ISO 3166-1 alpha-2)
- `tradingName` (string, optional) — Trading name (if different from legal name)
- `street` (string, optional) — Street address. More than 200 characters: warning `FIELD_TOO_LONG` (field e.g. `seller.street`), the value is written unchanged; a later release rejects it with 400.
- `additionalStreet` (string, optional) — Additional address line (BT-36 seller / BT-51 buyer / BT-65 tax representative). More than 200 characters: warning `FIELD_TOO_LONG` (field e.g. `seller.additionalStreet`), the value is written unchanged; a later release rejects it with 400.
- `addressLine3` (string, optional) — Third address line (BT-162 seller / BT-163 buyer / BT-164 tax representative).
- `city` (string, optional) — City. More than 100 characters: warning `FIELD_TOO_LONG` (field e.g. `seller.city`), the value is written unchanged; a later release rejects it with 400.
- `postalCode` (string, optional) — Postal code. More than 20 characters: warning `FIELD_TOO_LONG` (field e.g. `seller.postalCode`), the value is written unchanged; a later release rejects it with 400.
- `state` (string, optional) — State/region (ISO 3166-2). More than 100 characters: warning `FIELD_TOO_LONG` (field e.g. `seller.state`), the value is written unchanged; a later release rejects it with 400.
- `taxId` (string, optional) — National tax identification number. For the buyer, not transmitted in ZUGFeRD/Factur-X (only the VAT ID is); a warning is returned.
- `vatId` (string, optional) — VAT identification number with its country prefix (BT-31 seller / BT-48 buyer / BT-63 tax representative). EN 16931 (BR-CO-09) requires the prefix (ISO 3166-1 alpha-2, Greece `EL`). If the rulebook of the format reports BR-CO-09 and the value starts with a digit, the prefix of the party `countryCode` is added and the response carries the warning `VAT_ID_COUNTRY_PREFIX_ADDED` (field e.g. `buyer.vatId`). Formats without BR-CO-09 keep the value as sent.
- `registrationNumber` (string, optional) — Public register identifier of the party (BT-30 seller / BT-47 buyer) — Handelsregister, Firmenbuch, Companies House, … Rendered as `cac:PartyLegalEntity/cbc:CompanyID`. GENERIC field: until now every country read this from its own country-specific field (AT `tradeRegisterNumber`, FI `yTunnus`, …), so a business without a matching country block could not send its register number at all. Those fields keep working as a fallback.
- `registrationScheme` (string, optional) — ISO 6523 ICD code of the register (BT-30-1 / BT-47-1). 🔴 Only set this when the pinned ICD list actually carries a code for the register. The Austrian Firmenbuch has none — an invented code is FATAL per BR-CL-11.
- `identifiers` (list of ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceSellerIdentifiersItems, optional) — Further party identifiers (BT-29 seller / BT-46 buyer / BT-60 payee), repeatable. Written by every EN 16931 format. UBL: `cac:PartyIdentification/cbc:ID` (with `schemeID` if set). CII (ZUGFeRD, Factur-X, XRechnung CII, …): entries with `schemeId` become `ram:GlobalID`, entries without become `ram:ID`. Seller: every entry is BT-29. Buyer: BT-46 occurs at most once. The first entry of `buyer.identifiers` is BT-46 and replaces the invoice `customerNumber`; `customerNumber` is then not written and the response carries the warning `FIELD_NOT_WRITTEN` (field `customerNumber`). Without buyer identifiers `customerNumber` stays BT-46. Further buyer entries are not written either (`FIELD_NOT_WRITTEN`, field `buyer.identifiers.<n>`). `vatId` is only BT-31 (`SpecifiedTaxRegistration`, scheme `VA`). One exception, XRechnung (DE), seller: if the seller has no `identifiers`, no legal registration (BT-30) and no written BT-31, BR-CO-26 still needs one of them. Then `vatId` (or else `taxId`) is written as BT-29, and the response carries the warning `SELLER_IDENTIFIER_DERIVED`. Payee: only the first non-empty entry of `payee.identifiers` becomes BT-60 (with its `schemeId`); further entries are not written (`FIELD_NOT_WRITTEN`, field `payee.identifiers.<n>`). Only without one does the payee `vatId` or `taxId` fill BT-60.
- `email` (string, optional) — Email address
- `phone` (string, optional) — Phone number
- `website` (string, optional) — Website URL
- `contact` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceSellerContact, optional) — Structured contact person (BG-6 for seller, BG-9 for buyer)
- `bankAccount` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceSellerBankAccount, optional) — Bank account (required on seller for SEPA bank transfers in ZUGFeRD/XRechnung). For direct debit (SEPA Lastschrift), buyer bankAccount is also required.

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceBuyer

Buyer party information

- `name` (string, required) — Legal name of the party
- `countryCode` (string, required) — Country code (ISO 3166-1 alpha-2)
- `tradingName` (string, optional) — Trading name (if different from legal name)
- `street` (string, optional) — Street address. More than 200 characters: warning `FIELD_TOO_LONG` (field e.g. `seller.street`), the value is written unchanged; a later release rejects it with 400.
- `additionalStreet` (string, optional) — Additional address line (BT-36 seller / BT-51 buyer / BT-65 tax representative). More than 200 characters: warning `FIELD_TOO_LONG` (field e.g. `seller.additionalStreet`), the value is written unchanged; a later release rejects it with 400.
- `addressLine3` (string, optional) — Third address line (BT-162 seller / BT-163 buyer / BT-164 tax representative).
- `city` (string, optional) — City. More than 100 characters: warning `FIELD_TOO_LONG` (field e.g. `seller.city`), the value is written unchanged; a later release rejects it with 400.
- `postalCode` (string, optional) — Postal code. More than 20 characters: warning `FIELD_TOO_LONG` (field e.g. `seller.postalCode`), the value is written unchanged; a later release rejects it with 400.
- `state` (string, optional) — State/region (ISO 3166-2). More than 100 characters: warning `FIELD_TOO_LONG` (field e.g. `seller.state`), the value is written unchanged; a later release rejects it with 400.
- `taxId` (string, optional) — National tax identification number. For the buyer, not transmitted in ZUGFeRD/Factur-X (only the VAT ID is); a warning is returned.
- `vatId` (string, optional) — VAT identification number with its country prefix (BT-31 seller / BT-48 buyer / BT-63 tax representative). EN 16931 (BR-CO-09) requires the prefix (ISO 3166-1 alpha-2, Greece `EL`). If the rulebook of the format reports BR-CO-09 and the value starts with a digit, the prefix of the party `countryCode` is added and the response carries the warning `VAT_ID_COUNTRY_PREFIX_ADDED` (field e.g. `buyer.vatId`). Formats without BR-CO-09 keep the value as sent.
- `registrationNumber` (string, optional) — Public register identifier of the party (BT-30 seller / BT-47 buyer) — Handelsregister, Firmenbuch, Companies House, … Rendered as `cac:PartyLegalEntity/cbc:CompanyID`. GENERIC field: until now every country read this from its own country-specific field (AT `tradeRegisterNumber`, FI `yTunnus`, …), so a business without a matching country block could not send its register number at all. Those fields keep working as a fallback.
- `registrationScheme` (string, optional) — ISO 6523 ICD code of the register (BT-30-1 / BT-47-1). 🔴 Only set this when the pinned ICD list actually carries a code for the register. The Austrian Firmenbuch has none — an invented code is FATAL per BR-CL-11.
- `identifiers` (list of ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceBuyerIdentifiersItems, optional) — Further party identifiers (BT-29 seller / BT-46 buyer / BT-60 payee), repeatable. Written by every EN 16931 format. UBL: `cac:PartyIdentification/cbc:ID` (with `schemeID` if set). CII (ZUGFeRD, Factur-X, XRechnung CII, …): entries with `schemeId` become `ram:GlobalID`, entries without become `ram:ID`. Seller: every entry is BT-29. Buyer: BT-46 occurs at most once. The first entry of `buyer.identifiers` is BT-46 and replaces the invoice `customerNumber`; `customerNumber` is then not written and the response carries the warning `FIELD_NOT_WRITTEN` (field `customerNumber`). Without buyer identifiers `customerNumber` stays BT-46. Further buyer entries are not written either (`FIELD_NOT_WRITTEN`, field `buyer.identifiers.<n>`). `vatId` is only BT-31 (`SpecifiedTaxRegistration`, scheme `VA`). One exception, XRechnung (DE), seller: if the seller has no `identifiers`, no legal registration (BT-30) and no written BT-31, BR-CO-26 still needs one of them. Then `vatId` (or else `taxId`) is written as BT-29, and the response carries the warning `SELLER_IDENTIFIER_DERIVED`. Payee: only the first non-empty entry of `payee.identifiers` becomes BT-60 (with its `schemeId`); further entries are not written (`FIELD_NOT_WRITTEN`, field `payee.identifiers.<n>`). Only without one does the payee `vatId` or `taxId` fill BT-60.
- `email` (string, optional) — Email address
- `phone` (string, optional) — Phone number
- `website` (string, optional) — Website URL
- `contact` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceBuyerContact, optional) — Structured contact person (BG-6 for seller, BG-9 for buyer)
- `bankAccount` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceBuyerBankAccount, optional) — Bank account (required on seller for SEPA bank transfers in ZUGFeRD/XRechnung). For direct debit (SEPA Lastschrift), buyer bankAccount is also required.

### InvoiceLineItem

- `description` (string, required) — Item description
- `quantity` (double, required) — Quantity (BT-129). Written to the XML with the decimals you send — at least two, at most what the target format allows (FatturaPA and TicketBAI 8, NAV 10, CIUS-PT 3). Negative values allowed for return/credit lines, EN 16931 BG-25. More decimals than the format allows are rounded to its limit, and `warnings` carries `QUANTITY_DECIMALS_ROUNDED` (`lossy: true`) with the field and the written value.
- `unit` (string, required) — Unit code (UN/ECE Rec 20)
- `unitPrice` (double, required) — Unit price, net (BT-146). Written to the XML with the decimals you send — at least two, at most what the target format allows. EN 16931 puts no limit on this field (unlike the document totals, which are capped at two decimals), so a price of 1.639 per litre stays 1.639. Formats with a documented limit are capped: FatturaPA 8 decimals, ebInterface 4. A capped price is rounded, and `warnings` carries `PRICE_DECIMALS_ROUNDED` (`lossy: true`) with the field and the written value. Use `priceBaseQuantity` (BT-149) when the price refers to a number of units other than one.
- `netAmount` (double, required) — Net amount (quantity * unitPrice)
- `taxAmount` (double, required) — Tax amount
- `position` (integer, optional) — Line item position number (BT-126 — zero-indexed line IDs are valid)
- `articleNumber` (string, optional) — Article/SKU number — the SELLER's item identifier (BT-155).
- `gtin` (string, optional) — Global Trade Item Number (BT-157). Rendered as `cac:StandardItemIdentification/cbc:ID` with `schemeID="0160"`.
- `itemDescription` (string, optional) — Longer item description (BT-154), IN ADDITION to `description` (BT-153, the item name). Not a duplicate: the name identifies the article, this describes it. When omitted, the generators repeat the name.
- `buyerItemId` (string, optional) — Item identifier assigned by the BUYER (BT-156). Lets the recipient book the line against his own item master without parsing the description text.
- `classification` (list of InvoiceLineItemClassificationItems, optional) — Item classifications (BT-158), repeatable — e.g. UNSPSC, eCl@ss, eTIM.
- `originCountry` (string, optional) — Country of origin of the item (BT-159, ISO 3166-1 alpha-2).
- `attributes` (list of InvoiceLineItemAttributesItems, optional) — Item attributes (BG-32), repeatable — name and value, both required.
- `note` (string, optional) — Free-text note for THIS line (BT-127).
- `objectId` (string, optional) — Object identifier of the line (BT-128) — e.g. a meter number or a ticket id. Rendered as `cac:DocumentReference` with `cbc:DocumentTypeCode` 130.
- `objectIdScheme` (string, optional) — Scheme of the object identifier (BT-128-1, UNTDID 1153).
- `orderLineReference` (string, optional) — Referenced purchase order line number (BT-132).
- `buyerAccountingReference` (string, optional) — Buyer's accounting reference / cost centre for this line (BT-133).
- `servicePeriod` (InvoiceLineItemServicePeriod, optional) — Service period of THIS line (BG-26, BT-134/135). A collective invoice spanning several months needs the period per line — on document level it would be wrong.
- `discount` (InvoiceLineItemDiscount, optional) — Line item discount (BT-136 to BT-138)
- `allowances` (list of InvoiceLineItemAllowancesItems, optional) — Line-level allowances / discounts (BG-27), repeatable. Rendered as `cac:InvoiceLine/cac:AllowanceCharge` with `cbc:ChargeIndicator=false` (UBL) resp. `ram:SpecifiedTradeAllowanceCharge` (CII). Use this instead of `discount` when the line carries more than one reduction or needs a coded reason (BT-140).
- `charges` (list of InvoiceLineItemChargesItems, optional) — Line-level charges / surcharges (BG-28), repeatable — e.g. packaging or an express surcharge. Rendered with `cbc:ChargeIndicator=true`. There is no `discount`-style short form for charges; this is the only way to express them.
- `grossPrice` (double, optional) — Item gross price (BT-148) — the list price BEFORE the price discount, as printed in the catalogue. Together with `priceDiscount` (BT-147) it documents how `unitPrice` (BT-146) came about: BT-147 = BT-148 − BT-146. Rendered as `cac:Price/cac:AllowanceCharge/cbc:BaseAmount`.
- `priceDiscount` (double, optional) — Item price discount (BT-147) — the reduction from `grossPrice` (BT-148) to `unitPrice` (BT-146). Affects the PRICE only; it does not change the line net amount, which is already computed from `unitPrice`. For a reduction that lowers the line total, use `allowances` (BG-27).
- `priceBaseQuantity` (double, optional) — Item price base quantity (BT-149) — the number of units `unitPrice` refers to. `unitPrice: 12, priceBaseQuantity: 100` means "12 per 100 pieces". Omitted means 1.
- `priceBaseUnit` (string, optional) — Unit of the price base quantity (BT-150, UN/ECE Rec 20). Defaults to the unit of the line (`unit`) when omitted.
- `taxRate` (double, optional) — Tax rate in percent (BT-152, 0..1). Required for every VAT category except "O" (Not subject to VAT), where EN 16931 BR-O-05 forbids it. Omit the field for category O; for every other category it stays mandatory.
- `taxCategoryCode` (string, optional) — Tax category code (EN 16931: S, Z, E, AE, K, G, O, ...)
- `taxExemptionReason` (string, optional) — Tax exemption reason free text (BT-120)
- `taxExemptionReasonCode` (string, optional) — Tax exemption reason code (BT-121, VATEX code)
- `grossAmount` (double, optional) — Gross amount (net + tax)
- `lineSubtype` (enum, optional) — Sub-line-item type (BT-X-8, ZUGFeRD 2.4 EXTENDED). DETAIL = included in totals, INFORMATION = info only, GROUP = sum of sub-items.
  - Allowed values: `DETAIL`, `INFORMATION`, `GROUP`
- `parentLineId` (string, optional) — Parent line item position reference (BT-X-304, for hierarchical line items)
- `perPackageQuantity` (double, optional) — Quantity per package unit (BT-X-561)
- `subItems` (list of InvoiceLineItem, optional) — Nested sub-line-items (BG-DEX-01, ZUGFeRD 2.4 EXTENDED hierarchy). Each entry has the same shape as a top-level item and may itself have subItems. Use `lineSubtype` (DETAIL/INFORMATION/GROUP) on each sub-item to control how it contributes to totals. At most 100 levels deep (400 `SUB_ITEMS_TOO_DEEP`). Sub-items count as lines: all lines together, top-level and nested, may not exceed 25000 (400 `TOO_MANY_INVOICE_LINES`).

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceTaxSummaryItems

- `netAmount` (double, required) — Net amount for this tax rate
- `taxAmount` (double, required) — Tax amount
- `taxRate` (double, optional) — Tax rate in percent (BT-119, 0..1). Required for every VAT category except "O" (Not subject to VAT), which carries no rate.
- `taxCategoryCode` (string, optional) — Tax category code
- `exemptionReason` (string, optional) — Tax exemption reason free text (BT-120)
- `exemptionReasonCode` (string, optional) — Tax exemption reason code (BT-121, VATEX code)
- `taxCurrencyTaxAmount` (double, optional) — Tax amount of this rate in the tax currency (invoice-level `taxCurrencyCode`, BT-6). Austria (ebInterface 6.1): if the invoice currency is not EUR, set `taxCurrencyCode` to "EUR" and give this amount for every rate, otherwise the call is rejected with 422 `AT_EBI_TAX_EUR_AMOUNT_REQUIRED` (rule AT-EBI61-011). No exchange rate is applied.

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceServicePeriod

Service period (Leistungszeitraum, BG-14). Required in DE if different from issueDate. Send `start`, `end` or both (BR-CO-19); an empty object returns a 400. Formats whose schema requires both dates (ebInterface, Facturae) return a 400 `INVOICE_SERVICE_PERIOD_BOTH_DATES_REQUIRED` when one is missing; ISDOC has no invoicing period and reports `INVOICE_SERVICE_PERIOD_NOT_REPRESENTABLE` as a warning.

- `start` (string, optional) — Period start (BT-73, ISO 8601: YYYY-MM-DD)
- `end` (string, optional) — Period end (BT-74, ISO 8601: YYYY-MM-DD)

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoicePayee

Payee (BG-10), if different from the seller. On the CH/LI QR bill (`qr-bill`) the payee is the creditor: postal code, city, country and its own bank account are required.

- `name` (string, optional) — Payee name (BT-59). Required by BR-17 when a payee is given.
- `tradingName` (string, optional) — Trading name (if different from legal name)
- `street` (string, optional) — Street address of the payee
- `additionalStreet` (string, optional) — Additional address line of the payee
- `addressLine3` (string, optional) — Third address line (BT-162 seller / BT-163 buyer / BT-164 tax representative).
- `city` (string, optional) — City of the payee. Required on the CH/LI QR bill (`qr-bill`): without it 422 `CH_ADDR_005`, field `payee.city`.
- `postalCode` (string, optional) — Postal code of the payee. Required on the CH/LI QR bill (`qr-bill`): without it 422 `CH_ADDR_004`, field `payee.postalCode`.
- `countryCode` (string, optional) — Country code of the payee (ISO 3166-1 alpha-2). Required on the CH/LI QR bill (`qr-bill`): without it 422 `CH_ADDR_006`, field `payee.countryCode`.
- `state` (string, optional) — State/region (ISO 3166-2). More than 100 characters: warning `FIELD_TOO_LONG` (field e.g. `seller.state`), the value is written unchanged; a later release rejects it with 400.
- `taxId` (string, optional) — National tax identification number. For the buyer, not transmitted in ZUGFeRD/Factur-X (only the VAT ID is); a warning is returned.
- `vatId` (string, optional) — VAT identification number with its country prefix (BT-31 seller / BT-48 buyer / BT-63 tax representative). EN 16931 (BR-CO-09) requires the prefix (ISO 3166-1 alpha-2, Greece `EL`). If the rulebook of the format reports BR-CO-09 and the value starts with a digit, the prefix of the party `countryCode` is added and the response carries the warning `VAT_ID_COUNTRY_PREFIX_ADDED` (field e.g. `buyer.vatId`). Formats without BR-CO-09 keep the value as sent.
- `registrationNumber` (string, optional) — Public register identifier of the payee (BT-61), for example a Handelsregister or Companies House number. Rendered as `cac:PartyLegalEntity/cbc:CompanyID` (UBL) and `ram:SpecifiedLegalOrganization/ram:ID` (CII).
- `registrationScheme` (string, optional) — ISO 6523 ICD code of the register (BT-30-1 / BT-47-1). 🔴 Only set this when the pinned ICD list actually carries a code for the register. The Austrian Firmenbuch has none — an invented code is FATAL per BR-CL-11.
- `identifiers` (list of ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoicePayeeIdentifiersItems, optional) — Payee identifiers (BT-60). Only the first non-empty entry is written; further entries give `FIELD_NOT_WRITTEN` (field `payee.identifiers.<n>`).
- `email` (string, optional) — Email address
- `phone` (string, optional) — Phone number
- `website` (string, optional) — Website URL
- `contact` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoicePayeeContact, optional) — Structured contact person (BG-6 for seller, BG-9 for buyer)
- `bankAccount` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoicePayeeBankAccount, optional) — The payee's own account. When set, it is the payment account (BT-84) in every format and the account of the QR bill, instead of `seller.bankAccount`. On the CH/LI QR bill (`qr-bill`) the payee is always the creditor, and creditor and account must match (SIX IG 4.3.1): a payee without its own account gets 422 `CH_IBAN_003`, field `payee.bankAccount.iban`.

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoicePaymentTerms

Payment terms

- `dueDays` (double, optional) — Payment due in days
- `description` (string, optional) — Payment terms description
- `earlyPaymentDiscount` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoicePaymentTermsEarlyPaymentDiscount, optional) — Early payment discount (Skonto). E.g., 2% discount if paid within 10 days. Takes precedence over the top-level cashDiscount* fields when both are present.

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoicePaymentMethodsItems

Payment method

- `type` (enum, required) — Payment method type. When `countrySpecific.paymentMeansCode` is not set, the first entry sets the payment means code (BT-81, UNTDID 4461) in XRechnung, ZUGFeRD and UBL/Peppol: direct_debit=49 (Direct debit), credit_card=54 (Credit card, only together with `cardAccount`), cash=10, paypal=68 (Online payment service), danish_fik=93 (DK Indbetalingskort FIK), giro=50 (DK postal giro), other=1. bank_transfer / credit_transfer keep the format default: 58 (SEPA credit transfer) in German formats, 30 (Credit transfer) elsewhere. If the target format rejects the derived code (for example 49 without `directDebitMandate`), the document keeps the default and carries the warning PAYMENT_MEANS_CODE_NOT_DERIVED. The same happens when the format would drop your payee account (BG-17) for the derived code (XRechnung and ZUGFeRD write it only for credit transfer). With a card or direct debit the code stays and the warning PAYEE_ACCOUNT_NOT_WRITTEN says the account was left out. credit_card without `cardAccount` carries CARD_ACCOUNT_REQUIRED. An explicit `countrySpecific.paymentMeansCode` always wins. Factur-X, Facturae and FatturaPA map the type with their own tables.
  - Allowed values: `bank_transfer`, `credit_transfer`, `direct_debit`, `credit_card`, `paypal`, `cash`, `danish_fik`, `giro`, `other`
- `details` (string, optional) — Additional details (e.g., "PayPal: invoice@example.com")

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceAllowancesChargesItems

Invoice-level allowance (discount) or charge (surcharge)

- `isCharge` (boolean, required) — true = surcharge (BG-21), false = discount/allowance (BG-20)
- `amount` (double, required) — Allowance/charge amount (BT-92 / BT-99)
- `percentage` (double, optional) — Percentage (BT-94 / BT-101) — alternative to fixed amount
- `baseAmount` (double, optional) — Base amount for percentage calculation (BT-93 / BT-100)
- `reason` (string, optional) — Reason text (BT-97 / BT-104)
- `reasonCode` (string, optional) — Reason code per UNTDID 5189 (allowance) / 7161 (charge) (BT-98 / BT-105)
- `taxCategoryCode` (string, optional) — Tax category code (BT-95 / BT-102)
- `taxRate` (double, optional) — Tax rate in percent (BT-96 / BT-103)

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceDelivery

Delivery information (BG-13). Includes delivery date (BT-72), deliver-to name (BT-70), location identifier (BT-71), and delivery address (BG-15).

- `date` (string, optional) — Delivery date (BT-72, ISO 8601)
- `name` (string, optional) — Deliver-to party name (BT-70)
- `locationId` (string, optional) — Delivery location identifier (BT-71)
- `address` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceDeliveryAddress, optional) — Delivery address (BG-15)

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceDirectDebitMandate

Direct debit mandate (BG-19). Send it with direct_debit: most formats (XRechnung, Peppol PEPPOL-EN16931-R061) require the mandate reference for payment means code 49 and 59.

- `mandateId` (string, required) — SEPA mandate reference (BT-89)
- `creditorId` (string, optional) — SEPA creditor identifier (BT-90, 0..1). Optional in EN 16931 — required only by national rules (BR-DE-30 for XRechnung, DE-R-030 for German suppliers in Peppol BIS), which are reported against the generated document.
- `debitAccountId` (string, optional) — Debited account IBAN (BT-91)

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceCardAccount

Card payment details (BG-18). Set it together with a card payment means code (BT-81 = 48, 54 or 55). Formats that cannot represent the group report a GROUP_NOT_REPRESENTABLE warning instead of dropping it silently.

- `pan` (string, required) — BT-87 — masked card primary account number. BR-51 forbids the full PAN: PCI allows the first 6 and last 4 digits to be shown, so at most 10 digits — mask characters do not count towards that limit.
- `holderName` (string, optional) — BT-88 — name of the card holder
- `networkId` (string, optional) — Card network identifier (cbc:NetworkID; no EN 16931 business term)

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceSupportingDocumentsItems

Reference to a supporting document without the file itself (BT-122/BT-123)

- `id` (string, required) — BT-122 — identifier of the supporting document
- `description` (string, optional) — BT-123 — description of the supporting document
- `registryId` (string, optional) — Registry/access-point identifier (cbc:UUID). Required in Oman for the prepayment document and for an export invoice with VATZR-OM-12 (IBR-013-OM).

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceRetention

Security retention. Reduces only the payment, never the totals or the VAT. Written as a sentence into the payment terms (BT-20 or the national equivalent) of every e-invoice format that has payment terms, in the language of the seller (machine-translated for FR, NL, IT, ES, PL; English for other languages). A reason you send is used as given and is not translated. Do not use allowancesCharges for it. Formats or profiles without payment terms (ZUGFeRD and Factur-X MINIMUM, and myDATA without a payment method) reject the request with 422 (RETENTION_NOT_CARRIED); a plain PDF is not affected.

- `amount` (double, required) — Retained amount. Reduces only the amount to pay, never the totals or the VAT.
- `percent` (double, optional) — Retention rate in percent, if you want it named in the sentence
- `baseAmount` (double, optional) — Amount the retention rate refers to, if it is not the invoice total
- `reason` (string, optional) — Reason for the retention. Written as sent, never translated.
- `dueDate` (date, optional) — Date the retained amount becomes due (ISO 8601: YYYY-MM-DD)

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoicePrepaymentsItems

A single prepayment (BT-113 in detail)

- `amount` (double, required) — Amount already paid
- `paidAt` (string, optional) — Date the prepayment was received (ISO 8601: YYYY-MM-DD)
- `reference` (ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoicePrepaymentsItemsReference, optional) — Reference to the prepayment invoice

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceDeliveryNote

Despatch advice / delivery note reference (BT-16 / BT-17). Renders as `<cac:DespatchDocumentReference>` in UBL.

- `number` (string, required) — Despatch advice / delivery note number (BT-16).
- `date` (string, optional) — Despatch advice / delivery note date (BT-17, ISO 8601).

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceThirdPartyPaymentsItems

Third-party prepaid payment (BG-DEX-09 / BT-DEX-001..003, ZUGFeRD EXTENDED)

- `type` (string, required) — Third-party payment type identifier (BT-DEX-001). Free-form code chosen by the issuer (e.g., "voucher", "loyalty", "partial").
- `paidAmount` (double, required) — Amount already paid by the third party (BT-DEX-002).
- `description` (string, required) — Human-readable description of the third-party payment (BT-DEX-003).

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceAttachmentsItems

Supporting document (BG-24 / BT-122..125): embedded file, external reference, or both

- `filename` (string, optional) — Attachment filename (BT-125-2). Together with `mimeType` and `content`, or none of the three.
- `mimeType` (string, optional) — IANA media type of the attachment (BT-125-1). Together with `filename` and `content`, or none of the three.
- `content` (string, optional) — Base64-encoded binary content of the attachment (BT-125, 0..1). Send `content`, `mimeType` and `filename` together, or none of them for a reference without an embedded file (BT-122/BT-124). The whole request body is limited to 128 MiB (413 `PAYLOAD_TOO_LARGE` with `limit`); base64 adds a third, so all attachments together stay below about 95 MiB decoded. More than 20,971,520 base64 characters (15 MiB decoded) in one attachment, or more than 41,943,040 (30 MiB decoded) in all attachments together: warning `FIELD_TOO_LONG` (field `attachments[i].content` or `attachments[*].content`, `maximum` in characters); the invoice is processed unchanged, a later release rejects it with 400.
- `description` (string, optional) — Optional human-readable description of the attachment (BT-123).
- `reference` (string, optional) — Identifier of the supporting document (BT-122).
- `uri` (string, optional) — External location of the supporting document (BT-124). Rendered as `cac:Attachment/cac:ExternalReference/cbc:URI` (UBL) or `ram:URIID` (CII). A reference without an embedded file sends `uri` and/or `reference` and leaves out `content`, `mimeType` and `filename`.

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceConstructionTax

German construction-tax block (§13b UStG / §48 EStG). Setting `exemptionCertificateNumber` triggers the `#FREISTELLUNG#` note in the generated invoice. `withholdingPercent` documents the Bauabzugsteuer rate.

- `exemptionCertificateNumber` (string, optional) — Freistellungsbescheinigung number per §48b EStG. When set, the generator emits a "#FREISTELLUNG#" note documenting the construction-withholding exemption.
- `withholdingPercent` (double, optional) — Construction withholding tax rate in percent (Bauabzugsteuer). Typically 15 in Germany when no Freistellungsbescheinigung is presented.
- `recipientTaxOffice` (string, optional) — Tax office responsible for the recipient of the construction service.

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceCountrySpecific

Country-specific invoice data. Must include countryCode matching the invoice country. For DE: buyerReference (BT-10, required), paymentMeansCode (BT-81), leitwegId (B2G), isKleinunternehmer (§19 UStG). Other countries have their own fields — see country-specific documentation.

- `countryCode` (string, optional) — ISO 3166-1 alpha-2 country code identifying this country-specific block. Optional — when omitted it is taken from the country in the request path.
- `invoiceTypeCode` (string, optional) — BT-3 document type code, set explicitly. Takes precedence over `type` and is validated against the code list of the target format (and its conditions — e.g. Peppol permits 326/384 only when both parties are German). A code that contradicts `type` is rejected (HTTP 422) rather than silently resolved. Use this when your ERP already maps to UNTDID 1001 itself.
- `transactionType` (string, optional) — BTOM-001 Oman invoice transaction type — a 20-character binary mask carried as the `@name` attribute on the document type code. Positions (1-based): 1 full tax, 2 simplified, 3 self-billed, 4 third party, 5 summary, 6 continuous, 7 export, 8 deemed, 9 import RCM, 10 profit margin, 11 profit margin self-billed, 12 e-commerce, 13 import of goods, 14 special zone, 15 prepayment. When omitted the generator writes the standard tax invoice mask.
- `peppolEndpointId` (any, optional, deprecated) — Deprecated (AE, AU, BE, NZ), a string. countrySpecific.peppolEndpointId is deprecated and is not written. Use buyer.electronicAddress (the seller uses seller.electronicAddress). A request that still sends it is accepted and the response carries a `FIELD_NOT_WRITTEN` warning. The field will be removed in a later release.

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaErrorsItemsCode

Stable house code identifying the check (e.g. `DE_SELLER_CITY_001`, `NL_PAYMENT_MEANS_REQUIRED`, or `SPEC_RULE_FAILED` when a conformance gate objected). Never a standard rule identifier — look those up in `rule`. Safe to match on: it does not change when a rule is re-identified.

- enum
  - Allowed values: `DE_AC_001`, `DE_AC_002`, `DE_BIC_INVALID`, `DE_BR_AE_02`, `DE_BR_AE_03`, `DE_BR_DE_16`, `DE_BR_DEX_04`, `DE_BR_DEX_05`, `DE_BR_DEX_06`, `DE_BR_DEX_07`, `DE_BR_DEX_08`, `DE_BR_K_02`, `DE_BR_K_04`, `DE_BR_K_05`, `DE_BR_O_01`, `DE_BR_O_02`, `DE_BR_O_05`, `DE_BUYER_IBAN_001`, `DE_BUYER_IBAN_REQUIRED`, `DE_CREDITOR_ID_INVALID`, `DE_CREDITOR_ID_REQUIRED`, `DE_DLV_001`, `DE_INV_NUM_NOT_SEQUENTIAL`, `DE_INV_NUM_REQUIRED`, `DE_INV_NUM_SPECIAL_CHARS`, `DE_INV_NUM_TOO_LONG`, `DE_KU_001`, `DE_KU_002`, `DE_LW_002`, `DE_MANDATE_ID_REQUIRED`, `DE_MANDATE_ID_TOO_LONG`, `DE_REF_001`, `DE_REF_002`, `DE_SELLER_CONTACT_001`, `DE_SELLER_IBAN_FORMAT`, `DE_SELLER_IBAN_INVALID`, `DE_SEPA_003`, `DE_VAT_001`, `GR_AFM_001`, `GR_AFM_002`, `GR_CREDIT_NOTE_MISSING_MARK`, `GR_GEN_001`, `GR_INV_001`, `GR_INV_002`, `GR_INV_NUM_REQUIRED`, `GR_PDF_001`, `GR_PDF_002`
- string

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaWarningsItemsCode

Stable house code identifying the check (e.g. `DE_SELLER_CITY_001`, `NL_PAYMENT_MEANS_REQUIRED`, or `SPEC_RULE_FAILED` when a conformance gate objected). Never a standard rule identifier — look those up in `rule`. Safe to match on: it does not change when a rule is re-identified.

- enum
  - Allowed values: `DE_AC_001`, `DE_AC_002`, `DE_BIC_INVALID`, `DE_BR_AE_02`, `DE_BR_AE_03`, `DE_BR_DE_16`, `DE_BR_DEX_04`, `DE_BR_DEX_05`, `DE_BR_DEX_06`, `DE_BR_DEX_07`, `DE_BR_DEX_08`, `DE_BR_K_02`, `DE_BR_K_04`, `DE_BR_K_05`, `DE_BR_O_01`, `DE_BR_O_02`, `DE_BR_O_05`, `DE_BUYER_IBAN_001`, `DE_BUYER_IBAN_REQUIRED`, `DE_CREDITOR_ID_INVALID`, `DE_CREDITOR_ID_REQUIRED`, `DE_DLV_001`, `DE_INV_NUM_NOT_SEQUENTIAL`, `DE_INV_NUM_REQUIRED`, `DE_INV_NUM_SPECIAL_CHARS`, `DE_INV_NUM_TOO_LONG`, `DE_KU_001`, `DE_KU_002`, `DE_LW_002`, `DE_MANDATE_ID_REQUIRED`, `DE_MANDATE_ID_TOO_LONG`, `DE_REF_001`, `DE_REF_002`, `DE_SELLER_CONTACT_001`, `DE_SELLER_IBAN_FORMAT`, `DE_SELLER_IBAN_INVALID`, `DE_SEPA_003`, `DE_VAT_001`, `GR_AFM_001`, `GR_AFM_002`, `GR_CREDIT_NOTE_MISSING_MARK`, `GR_GEN_001`, `GR_INV_001`, `GR_INV_002`, `GR_INV_NUM_REQUIRED`, `GR_PDF_001`, `GR_PDF_002`
- string

### RequestValidationErrorErrorItems

- `code` (string, required) — Rule that failed, e.g. `too_big`, `invalid_type`, `invalid_value`.
- `path` (list of RequestValidationErrorErrorItemsPathItems, required) — Path of the field in the request body, e.g. `["invoice", "seller", "name"]`.
- `message` (string, required)
- `maximum` (double, optional)
- `minimum` (double, optional)
- `inclusive` (boolean, optional)
- `origin` (string, optional)
- `expected` (string, optional)
- `values` (list of any, optional)
- `keys` (list of string, optional)
- `format` (string, optional)

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceSellerIdentifiersItems

Party identifier with optional scheme (BT-29 / BT-46)

- `id` (string, required) — Identifier of the party (BT-29 seller / BT-46 buyer).
- `schemeId` (string, optional) — Identification scheme of the identifier (BT-29-1 / BT-46-1, ISO 6523 ICD).

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceSellerContact

Structured contact person (BG-6 for seller, BG-9 for buyer)

- `name` (string, optional) — Contact person name
- `phone` (string, optional) — Contact phone number
- `email` (string, optional) — Contact email address
- `department` (string, optional) — Department of the contact person (BT-41-0 seller / BT-56-0 buyer). In ZUGFeRD/Factur-X only one of name or department is transmitted; if both are set, the name is used and a warning is returned.

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceSellerBankAccount

Bank account (required on seller for SEPA bank transfers in ZUGFeRD/XRechnung). For direct debit (SEPA Lastschrift), buyer bankAccount is also required.

- `iban` (string, required) — IBAN (International Bank Account Number)
- `bic` (string, optional) — BIC/SWIFT code (8 or 11 characters)
- `bankName` (string, optional) — Name of the bank
- `accountHolder` (string, optional) — Account holder name (if different from party name)

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceBuyerIdentifiersItems

Party identifier with optional scheme (BT-29 / BT-46)

- `id` (string, required) — Identifier of the party (BT-29 seller / BT-46 buyer).
- `schemeId` (string, optional) — Identification scheme of the identifier (BT-29-1 / BT-46-1, ISO 6523 ICD).

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceBuyerContact

Structured contact person (BG-6 for seller, BG-9 for buyer)

- `name` (string, optional) — Contact person name
- `phone` (string, optional) — Contact phone number
- `email` (string, optional) — Contact email address
- `department` (string, optional) — Department of the contact person (BT-41-0 seller / BT-56-0 buyer). In ZUGFeRD/Factur-X only one of name or department is transmitted; if both are set, the name is used and a warning is returned.

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceBuyerBankAccount

Bank account (required on seller for SEPA bank transfers in ZUGFeRD/XRechnung). For direct debit (SEPA Lastschrift), buyer bankAccount is also required.

- `iban` (string, required) — IBAN (International Bank Account Number)
- `bic` (string, optional) — BIC/SWIFT code (8 or 11 characters)
- `bankName` (string, optional) — Name of the bank
- `accountHolder` (string, optional) — Account holder name (if different from party name)

### InvoiceLineItemClassificationItems

Item classification (BT-158)

- `id` (string, required) — Classification code of the item (BT-158).
- `schemeId` (string, required) — Identification scheme of the classification code (BT-158-1, UNTDID 7143).
- `schemeVersion` (string, optional) — Version of the identification scheme (BT-158-2).

### InvoiceLineItemAttributesItems

Item attribute (BG-32)

- `name` (string, required) — Name of the item attribute (BT-160).
- `value` (string, required) — Value of the item attribute (BT-161).

### InvoiceLineItemServicePeriod

Service period of THIS line (BG-26, BT-134/135). A collective invoice spanning several months needs the period per line — on document level it would be wrong.

- `start` (string, optional) — Line service period start (BT-134, ISO 8601 YYYY-MM-DD).
- `end` (string, optional) — Line service period end (BT-135, ISO 8601 YYYY-MM-DD).

### InvoiceLineItemDiscount

Line item discount (BT-136 to BT-138)

- `type` (enum, optional) — Discount type: percentage or absolute amount
  - Allowed values: `percentage`, `absolute`
- `value` (double, optional) — Discount value
- `reason` (string, optional) — Discount reason (BT-139)

### InvoiceLineItemAllowancesItems

Line-level allowance (BG-27) or charge (BG-28)

- `amount` (double, required) — Amount of the allowance/charge (BT-136 / BT-141), in the invoice currency.
- `baseAmount` (double, optional) — Base amount the percentage applies to (BT-137 / BT-142).
- `percentage` (double, optional) — Percentage of the allowance/charge (BT-138 / BT-143).
- `reason` (string, optional) — Reason for the allowance/charge in clear text (BT-139 / BT-144).
- `reasonCode` (string, optional) — Coded reason for the allowance (BT-140, UNCL 5189) resp. the charge (BT-145, UNCL 7161). Several CIUS require the code when the reason is codeable.

### InvoiceLineItemChargesItems

Line-level allowance (BG-27) or charge (BG-28)

- `amount` (double, required) — Amount of the allowance/charge (BT-136 / BT-141), in the invoice currency.
- `baseAmount` (double, optional) — Base amount the percentage applies to (BT-137 / BT-142).
- `percentage` (double, optional) — Percentage of the allowance/charge (BT-138 / BT-143).
- `reason` (string, optional) — Reason for the allowance/charge in clear text (BT-139 / BT-144).
- `reasonCode` (string, optional) — Coded reason for the allowance (BT-140, UNCL 5189) resp. the charge (BT-145, UNCL 7161). Several CIUS require the code when the reason is codeable.

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoicePayeeIdentifiersItems

- `id` (string, optional) — Identifier of the payee (BT-60). Empty entries are skipped.
- `schemeId` (string, optional) — Identification scheme of the identifier (BT-29-1 / BT-46-1, ISO 6523 ICD).

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoicePayeeContact

Structured contact person (BG-6 for seller, BG-9 for buyer)

- `name` (string, optional) — Contact person name
- `phone` (string, optional) — Contact phone number
- `email` (string, optional) — Contact email address
- `department` (string, optional) — Department of the contact person (BT-41-0 seller / BT-56-0 buyer). In ZUGFeRD/Factur-X only one of name or department is transmitted; if both are set, the name is used and a warning is returned.

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoicePayeeBankAccount

The payee's own account. When set, it is the payment account (BT-84) in every format and the account of the QR bill, instead of `seller.bankAccount`. On the CH/LI QR bill (`qr-bill`) the payee is always the creditor, and creditor and account must match (SIX IG 4.3.1): a payee without its own account gets 422 `CH_IBAN_003`, field `payee.bankAccount.iban`.

- `iban` (string, required) — IBAN (International Bank Account Number)
- `bic` (string, optional) — BIC/SWIFT code (8 or 11 characters)
- `bankName` (string, optional) — Name of the bank
- `accountHolder` (string, optional) — Account holder name (if different from party name)

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoicePaymentTermsEarlyPaymentDiscount

Early payment discount (Skonto). E.g., 2% discount if paid within 10 days. Takes precedence over the top-level cashDiscount* fields when both are present.

- `days` (integer, required) — Discount valid within this many days (integer, 0..365)
- `discountPercent` (double, required) — Discount percentage (Skonto) — > 0, \<= 100, at most two decimals
- `baseAmount` (double, optional) — Optional base amount the discount is computed from, when it is not the payable amount (BT-115) — e.g. a partial amount on German construction invoices with retention. Emitted as the BASISBETRAG segment of the XRechnung #SKONTO# line (BR-DE-18). Omit it when the discount applies to the full payable amount.

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoiceDeliveryAddress

Delivery address (BG-15)

- `street` (string, optional) — Delivery street (BT-75)
- `additionalStreet` (string, optional) — Additional delivery address line (BT-76)
- `city` (string, optional) — Delivery city (BT-77)
- `postalCode` (string, optional) — Delivery postal code (BT-78)
- `state` (string, optional) — Delivery state/region (BT-79). More than 100 characters: warning `FIELD_TOO_LONG` (field `delivery.address.state`), the value is written unchanged; a later release rejects it with 400.
- `addressLine3` (string, optional) — Third delivery address line (BT-165)
- `countryCode` (string, optional) — Delivery country code (BT-80)

### ApiV1InvoiceSkPeppolUblParsePostResponsesContentApplicationJsonSchemaInvoicePrepaymentsItemsReference

Reference to the prepayment invoice

- `documentNumber` (string, required) — Invoice number of the prepayment document
- `registryId` (string, optional) — Registry/access-point identifier of the prepayment document. Required in Oman (IBR-011-OM); the country gate says when.

### RequestValidationErrorErrorItemsPathItems

- string
- double

## Examples

### parse_sk_peppolUbl_example

**Response**

```json
{
  "success": true,
  "invoice": {
    "invoiceNumber": "INV-2026-0042",
    "type": "invoice",
    "issueDate": "2026-03-20",
    "seller": {
      "name": "TechCorp GmbH",
      "countryCode": "DE",
      "street": "Kantstraße 12",
      "city": "Berlin",
      "postalCode": "10623"
    },
    "buyer": {
      "name": "Muster GmbH",
      "countryCode": "DE",
      "street": "Hauptstraße 42",
      "city": "München",
      "postalCode": "80331"
    },
    "items": [
      {
        "description": "Consulting",
        "quantity": 10,
        "unit": "HUR",
        "unitPrice": 150,
        "netAmount": 1500,
        "taxAmount": 285,
        "position": 1,
        "taxRate": 19,
        "grossAmount": 1785
      }
    ],
    "currency": "EUR",
    "subtotal": 1500,
    "total": 1785,
    "taxSummary": [
      {
        "netAmount": 1500,
        "taxAmount": 285,
        "taxRate": 19
      }
    ],
    "dueDate": "2026-04-19",
    "paymentTerms": {
      "dueDays": 30
    }
  },
  "format": "ZUGFERD_EN16931",
  "hash": "a1b2c3d4e5f6..."
}
```

**SDK Code**

```python parse_sk_peppolUbl_example
import requests

url = "https://service.invoice-api.xhub.io/api/v1/invoice/sk/peppol-ubl/parse"

headers = {"Authorization": "Bearer <token>"}

response = requests.post(url, headers=headers)

print(response.json())
```

```javascript parse_sk_peppolUbl_example
const url = 'https://service.invoice-api.xhub.io/api/v1/invoice/sk/peppol-ubl/parse';
const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}
```

```go parse_sk_peppolUbl_example
package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://service.invoice-api.xhub.io/api/v1/invoice/sk/peppol-ubl/parse"

	req, _ := http.NewRequest("POST", url, nil)

	req.Header.Add("Authorization", "Bearer <token>")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(res)
	fmt.Println(string(body))

}
```

```ruby parse_sk_peppolUbl_example
require 'uri'
require 'net/http'

url = URI("https://service.invoice-api.xhub.io/api/v1/invoice/sk/peppol-ubl/parse")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Post.new(url)
request["Authorization"] = 'Bearer <token>'

response = http.request(request)
puts response.read_body
```

```java parse_sk_peppolUbl_example
import com.mashape.unirest.http.HttpResponse;
import com.mashape.unirest.http.Unirest;

HttpResponse<String> response = Unirest.post("https://service.invoice-api.xhub.io/api/v1/invoice/sk/peppol-ubl/parse")
  .header("Authorization", "Bearer <token>")
  .asString();
```

```php parse_sk_peppolUbl_example
<?php
require_once('vendor/autoload.php');

$client = new \GuzzleHttp\Client();

$response = $client->request('POST', 'https://service.invoice-api.xhub.io/api/v1/invoice/sk/peppol-ubl/parse', [
  'headers' => [
    'Authorization' => 'Bearer <token>',
  ],
]);

echo $response->getBody();
```

```csharp parse_sk_peppolUbl_example
using RestSharp;

var client = new RestClient("https://service.invoice-api.xhub.io/api/v1/invoice/sk/peppol-ubl/parse");
var request = new RestRequest(Method.POST);
request.AddHeader("Authorization", "Bearer <token>");
IRestResponse response = client.Execute(request);
```

```swift parse_sk_peppolUbl_example
import Foundation

let headers = ["Authorization": "Bearer <token>"]

let request = NSMutableURLRequest(url: NSURL(string: "https://service.invoice-api.xhub.io/api/v1/invoice/sk/peppol-ubl/parse")! as URL,
                                        cachePolicy: .useProtocolCachePolicy,
                                    timeoutInterval: 10.0)
request.httpMethod = "POST"
request.allHTTPHeaderFields = headers

let session = URLSession.shared
let dataTask = session.dataTask(with: request as URLRequest, completionHandler: { (data, response, error) -> Void in
  if (error != nil) {
    print(error as Any)
  } else {
    let httpResponse = response as? HTTPURLResponse
    print(httpResponse)
  }
})

dataTask.resume()
```

### SK — Peppol BIS 3.0 UBL (cross-border)

**Request**

```json
{
  "data": "<DATA REQUIRED Base64>",
  "filename": "invoice-sample.xml"
}
```

**Response**

```json
{
  "success": true,
  "invoice": {
    "invoiceNumber": "INV-2026-0042",
    "type": "invoice",
    "issueDate": "2026-03-20",
    "seller": {
      "name": "TechCorp GmbH",
      "countryCode": "DE",
      "street": "Kantstraße 12",
      "city": "Berlin",
      "postalCode": "10623"
    },
    "buyer": {
      "name": "Muster GmbH",
      "countryCode": "DE",
      "street": "Hauptstraße 42",
      "city": "München",
      "postalCode": "80331"
    },
    "items": [
      {
        "description": "Consulting",
        "quantity": 10,
        "unit": "HUR",
        "unitPrice": 150,
        "netAmount": 1500,
        "taxAmount": 285,
        "position": 1,
        "taxRate": 19,
        "grossAmount": 1785
      }
    ],
    "currency": "EUR",
    "subtotal": 1500,
    "total": 1785,
    "taxSummary": [
      {
        "netAmount": 1500,
        "taxAmount": 285,
        "taxRate": 19
      }
    ],
    "dueDate": "2026-04-19",
    "paymentTerms": {
      "dueDays": 30
    }
  },
  "format": "ZUGFERD_EN16931",
  "hash": "a1b2c3d4e5f6..."
}
```

**SDK Code**

```python SK — Peppol BIS 3.0 UBL (cross-border)
import requests

url = "https://service.invoice-api.xhub.io/api/v1/invoice/sk/peppol-ubl/parse"

payload = {
    "data": "<DATA REQUIRED Base64>",
    "filename": "invoice-sample.xml"
}
headers = {
    "Authorization": "Bearer <token>",
    "Content-Type": "application/json"
}

response = requests.post(url, json=payload, headers=headers)

print(response.json())
```

```javascript SK — Peppol BIS 3.0 UBL (cross-border)
const url = 'https://service.invoice-api.xhub.io/api/v1/invoice/sk/peppol-ubl/parse';
const options = {
  method: 'POST',
  headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
  body: '{"data":"<DATA REQUIRED Base64>","filename":"invoice-sample.xml"}'
};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}
```

```go SK — Peppol BIS 3.0 UBL (cross-border)
package main

import (
	"fmt"
	"strings"
	"net/http"
	"io"
)

func main() {

	url := "https://service.invoice-api.xhub.io/api/v1/invoice/sk/peppol-ubl/parse"

	payload := strings.NewReader("{\n  \"data\": \"<DATA REQUIRED Base64>\",\n  \"filename\": \"invoice-sample.xml\"\n}")

	req, _ := http.NewRequest("POST", url, payload)

	req.Header.Add("Authorization", "Bearer <token>")
	req.Header.Add("Content-Type", "application/json")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(res)
	fmt.Println(string(body))

}
```

```ruby SK — Peppol BIS 3.0 UBL (cross-border)
require 'uri'
require 'net/http'

url = URI("https://service.invoice-api.xhub.io/api/v1/invoice/sk/peppol-ubl/parse")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Post.new(url)
request["Authorization"] = 'Bearer <token>'
request["Content-Type"] = 'application/json'
request.body = "{\n  \"data\": \"<DATA REQUIRED Base64>\",\n  \"filename\": \"invoice-sample.xml\"\n}"

response = http.request(request)
puts response.read_body
```

```java SK — Peppol BIS 3.0 UBL (cross-border)
import com.mashape.unirest.http.HttpResponse;
import com.mashape.unirest.http.Unirest;

HttpResponse<String> response = Unirest.post("https://service.invoice-api.xhub.io/api/v1/invoice/sk/peppol-ubl/parse")
  .header("Authorization", "Bearer <token>")
  .header("Content-Type", "application/json")
  .body("{\n  \"data\": \"<DATA REQUIRED Base64>\",\n  \"filename\": \"invoice-sample.xml\"\n}")
  .asString();
```

```php SK — Peppol BIS 3.0 UBL (cross-border)
<?php
require_once('vendor/autoload.php');

$client = new \GuzzleHttp\Client();

$response = $client->request('POST', 'https://service.invoice-api.xhub.io/api/v1/invoice/sk/peppol-ubl/parse', [
  'body' => '{
  "data": "<DATA REQUIRED Base64>",
  "filename": "invoice-sample.xml"
}',
  'headers' => [
    'Authorization' => 'Bearer <token>',
    'Content-Type' => 'application/json',
  ],
]);

echo $response->getBody();
```

```csharp SK — Peppol BIS 3.0 UBL (cross-border)
using RestSharp;

var client = new RestClient("https://service.invoice-api.xhub.io/api/v1/invoice/sk/peppol-ubl/parse");
var request = new RestRequest(Method.POST);
request.AddHeader("Authorization", "Bearer <token>");
request.AddHeader("Content-Type", "application/json");
request.AddParameter("application/json", "{\n  \"data\": \"<DATA REQUIRED Base64>\",\n  \"filename\": \"invoice-sample.xml\"\n}", ParameterType.RequestBody);
IRestResponse response = client.Execute(request);
```

```swift SK — Peppol BIS 3.0 UBL (cross-border)
import Foundation

let headers = [
  "Authorization": "Bearer <token>",
  "Content-Type": "application/json"
]
let parameters = [
  "data": "<DATA REQUIRED Base64>",
  "filename": "invoice-sample.xml"
] as [String : Any]

let postData = JSONSerialization.data(withJSONObject: parameters, options: [])

let request = NSMutableURLRequest(url: NSURL(string: "https://service.invoice-api.xhub.io/api/v1/invoice/sk/peppol-ubl/parse")! as URL,
                                        cachePolicy: .useProtocolCachePolicy,
                                    timeoutInterval: 10.0)
request.httpMethod = "POST"
request.allHTTPHeaderFields = headers
request.httpBody = postData as Data

let session = URLSession.shared
let dataTask = session.dataTask(with: request as URLRequest, completionHandler: { (data, response, error) -> Void in
  if (error != nil) {
    print(error as Any)
  } else {
    let httpResponse = response as? HTTPURLResponse
    print(httpResponse)
  }
})

dataTask.resume()
```