Sending and receiving Peppol documents in Germany for your own company

This guide walks through everything needed to exchange Peppol documents for a company registered in Germany, assuming you are setting up your own German company, and that the company sends and receives documents over Peppol. Change any of the three answers at the top of the page to get the guide for a different situation.

What you are setting up

You are putting one company, your own or one you represent, on the Peppol network, so it can exchange invoices electronically with its customers and suppliers.

The setup is a one-time affair: registering the company and getting it verified takes a few minutes in the Recommand dashboard, and there is nothing to gain from automating something you do once. What you do integrate is the part that repeats: sending and receiving documents. Our existing integrations can also connect Recommand to accounting or invoicing software you already use, with no code at all.

A single team can hold several companies at no extra cost, useful if you run more than one legal entity, and the document volume of all of them counts towards one plan.

Peppol in Germany

Germany has no central platform: e-invoices travel directly between the parties, over Peppol, email or EDI. What the law prescribes is the content, a structured invoice following EN 16931, not the channel.

What is specific to Germany:

• A B2B mandate in phases. Every German business has had to be able to receive structured e-invoices since 1 January 2025. Issuing them becomes mandatory from 1 January 2027 for businesses with a prior-year turnover above EUR 800,000, and from 1 January 2028 for the rest, with statutory exemptions.
• XRechnung alongside Peppol BIS 3. XRechnung is the German specialisation (CIUS) of EN 16931, in UBL and in CII. German companies registered through Recommand receive both Peppol BIS 3 and XRechnung, and Recommand can write and read both.
• The VAT number is the Peppol address. German businesses are published under scheme 9930 with their VAT number (USt-IdNr.), so a German Peppol address looks like 9930:DE123456788.
• Public authorities are addressed by their Leitweg-ID. Invoices to German public authorities go to scheme 0204, and the same Leitweg-ID has to appear in the invoice as buyer reference (BT-10).
• German sellers have extra mandatory fields. Peppol BIS 3 and XRechnung both require a German seller to state payment instructions and a contact phone number and email address.

Create your account and API credentials

1. Sign up at app.recommand.eu/signup.
2. Your account starts with a team. The team holds your company, your subscription and your document history, and you can invite colleagues to it.
3. Create an API key on the API keys page. Note the key, the secret and your team ID.
4. Check the credentials with a request that needs no data of its own:

curl -X GET https://app.recommand.eu/api/core/auth/verify \
  -u key_xxx:secret_xxx

It answers {"success": true} when the key and secret are accepted, and 401 when they are not, so it tells you about your credentials and nothing else.

All endpoints in this guide live under https://app.recommand.eu/api/v1 and accept HTTP Basic authentication with the key as username and the secret as password. If you would rather not store a long-lived secret, JWT API keys and OAuth2 with a JWT assertion are available too, see the authentication guide.

Try it safely first

You do not have to get anything right the first time. Everything below, adding the company, registering it, sending and receiving, can be done in a playground team first, where nothing is delivered over the real Peppol network, nothing is registered on it, and nothing is billed.

Open the team switcher at the top of the dashboard and pick Add playground. Give it a name, leave the Peppol Test Network box unticked, and you are switched into the new team straight away. There is nothing to set up beyond that.

Add a company to that team and use it as both sender and recipient to watch a document travel end to end. When the flow does what you want, repeat it once in your real team.

Two things worth knowing before you start:

• POST /:companyId/generate takes the same body as the send endpoint minus the email delivery options, which have no meaning when nothing is delivered, and returns the exact XML that sending would produce, fully validated, without transmitting, storing or billing it. Raw XML is not accepted here: there is nothing to generate from a document you already have. It also returns the resolved documentType, doctypeId and processId.
• Failure addresses. In a playground that is not connected to the Peppol Test Network, sending to 404:404 or 0208:1234567894 always fails, so you can exercise your error handling. Any other unregistered recipient is skipped without an error.

A playground stays useful after you are live, too: it is the safest place to try a new invoice layout or a new integration. See how can I test without sending real invoices.

Register the company

You are registering one company, once, so the dashboard is the shortest path.

1. Open Companies and start the company wizard.
2. Fill in the legal name, address and country, plus the identifiers described in the next section.
3. Choose whether the company should also receive documents over Peppol, or only send them.
4. Save. The company is registered on the Peppol network as part of this step: its identifiers and the document types for its country are set up for you.

Right after saving, the dashboard offers the verification step, which the section below covers. Note the company's ID from its detail page. Every API call for sending and receiving takes it in the path.

Three identifiers that are easy to mix up

A German invoice involves three different identifiers. Only the first one is a Peppol address:

German identifiers and Peppol address

{
  "name": "Beispiel GmbH",
  "address": "Musterstraße 1",
  "postalCode": "10115",
  "city": "Berlin",
  "country": "DE",
  "enterpriseNumber": "HRB 12345 B",
  "vatNumber": "DE123456788"
}

The VAT number is checked against the German format and its check digit, and registered as the company's Peppol identifier: 9930: followed by the VAT number. The register number is never registered as a Peppol identifier.

Without a VAT number

A company without a VAT number gets no identifier by default. Following the German identifier guideline, add one of these yourself with the create identifier endpoint or in the dashboard:

• 0088: the company's GS1 Global Location Number (GLN), 13 digits
• 9918: the company's IBAN

Both are checked for their check digits.

Public authorities: the Leitweg-ID

A German public authority receives invoices under scheme 0204 with its Leitweg-ID, for example 0204:991-33333TEST-33. Only add a 0204 identifier for a public authority that receives through Recommand, using the exact Leitweg-ID it was assigned; its check digits are verified. The older Leitweg-ID scheme 9958 is deprecated on Peppol and is refused.

Which identifier you send from

A company sends from the identifier with the lowest scheme, but never from a Leitweg-ID: that one only names an authority's invoice reception. An invoice to a Leitweg-ID always goes out under the company's VAT number (9930) or, without one, its GLN (0088), the sender identifiers the federal invoice portals list.

Registering for both directions

Sending needs no registration of its own; receiving does. So register the company as a recipient, which is the default:

{
  "isSmpRecipient": true
}

What that means:

• The company becomes findable on the Peppol network and can be delivered to through Recommand's access point, while sending its own documents out through the same access point.
• Recipient registration is exclusive. If the company already receives through another Peppol provider, registration fails until it is deregistered there. What that takes depends on the country, which the next section covers.
• The document types the company accepts are registered along with it, based on its country. Which ones those are is covered further down.
• The company is only published once it is verified.

Moving an existing German registration

Recipient registration is exclusive: a German company that already receives through another Peppol provider has to be deregistered there before it can be registered with Recommand, unless that provider issues a migration key, which moves the registration over without a gap.

If you do not know who the current provider is, look the VAT number up as a recipient (9930:DE123456788): the verify endpoint returns the SMP it is published on, which names the provider to ask.

Verify the company

A company cannot exchange documents on Peppol until an authorised representative has confirmed their identity. The company object exposes this as isVerified, and it stays false until the check is done.

For German companies the flow is short:

1. Open the verification URL (from the create-company response, the dashboard, or a fresh one from the verify company endpoint).
2. The representative fills in their name and completes the identity check.
3. isVerified flips to true and the company is published on the Peppol network.

In some cases manual verification by our team will be required. If that's the case, isVerified will remain false until this manual verification is completed. The user is informed of this in the verification process.

Verifying once, in the dashboard

You have one company, and it is verified once. There is nothing here worth automating: open Companies in the dashboard, pick the company and start verification. If you are authorised to act for the company, complete the check yourself; otherwise use the button to forward the link to whoever is.

The page is self-contained and works in any browser. The person completing it does not need a Recommand account.

That is the whole step. From here on the API takes over: sending and receiving documents is what you actually integrate.

Pick the document format

Send Peppol BIS 3 UBL unless the recipient asks for XRechnung. When a recipient is only registered for XRechnung, Recommand picks it automatically; to ask for it explicitly, name its document type on the send request:

The document you post is the same for every format. XRechnung does require a few fields that are optional elsewhere, and a send that misses one is refused with the full list before anything is transmitted:

• buyerReference (BT-10), unless it is filled in from a Leitweg-ID (see below)
• paymentMeans, at least one payment instruction
• the seller's phone and email, and the seller's and buyer's city and postal code
• for a CII credit note, paymentTerms

Peppol BIS 3 applies the same payment instruction and seller contact rules to every German seller, so fill them in whichever format you send.

Raw XRechnung XML can be sent as it is with documentType: "xml": the document type and process are read from the document, for UBL and CII alike. XRechnung 3.0 extension documents and earlier XRechnung versions are sent under the identifier the document declares, but are not read.

Invoicing a public authority

Address the authority by its Leitweg-ID, as 0204: followed by the Leitweg-ID. German public authorities require XRechnung, so a document to a Leitweg-ID is written as XRechnung by default, also when the authority is registered for Peppol BIS 3 as well. The XRechnung fields listed above are therefore required. The same Leitweg-ID has to be the invoice's buyer reference (BT-10), so leave buyerReference out and Recommand fills it in. A different buyerReference is refused, because the authority would reject the invoice; put order numbers in purchaseOrderReference instead.

{
  "recipient": "0204:991-33333TEST-33",
  "documentType": "invoice",
  "document": {
    "invoiceNumber": "RE-2026-001",
    "purchaseOrderReference": "4500012345",
    "buyer": { "name": "Bundesamt für Beispiele", "street": "Amtsweg 2", "city": "Bonn", "postalZone": "53113", "country": "DE" },
    "paymentMeans": [{ "paymentMethod": "credit_transfer", "iban": "DE89370400440532013000", "reference": "RE-2026-001" }],
    "lines": [{ "name": "Beratung", "quantity": "1", "netPriceAmount": "100.00", "vat": { "category": "S", "percentage": "19.00" } }]
  }
}

Send a document

One endpoint sends everything: POST /:companyId/send. The companyId is the sender, recipient is the Peppol address of the receiver, and document is the invoice or credit note as JSON. Recommand will validate the document and generate the XML.

curl -X POST https://app.recommand.eu/api/v1/{companyId}/send \
  -u key_xxx:secret_xxx \
  -H "Content-Type: application/json" \
  -d @send-invoice.json

{
  "recipient": "0208:0123456789",
  "documentType": "invoice",
  "document": {
    "invoiceNumber": "INV-2026-001",
    "issueDate": "2026-08-17",
    "dueDate": "2026-09-16",
    "currency": "EUR",
    "buyer": {
      "name": "Customer Company",
      "street": "Customer Street 1",
      "city": "Antwerp",
      "postalZone": "2000",
      "country": "BE",
      "vatNumber": "BE0987654321"
    },
    "paymentMeans": [{ "iban": "BE68539007547034" }],
    "lines": [
      {
        "name": "Consulting Services",
        "quantity": "10.00",
        "unitCode": "HUR",
        "netPriceAmount": "100.00",
        "vat": { "category": "S", "percentage": "21.00" }
      }
    ]
  }
}

The seller block is filled in from your company when you leave it out, which is usually what you want: it keeps your registered identifiers and the document in agreement. The full field reference lives in sending invoices and sending credit notes.

Worth wiring up while you are here:

• Validation errors. Outgoing documents are always validated. A success: false response with errors keyed by field path is a document the recipient would have rejected. Surface it wherever the data was typed.
• Delivery outcomes. success: true confirms the send request succeeded. Check deliveryStatus and deliveries, and subscribe to delivery status webhooks for outcomes reported later.
• Email fallback. Pass email.to with when: "on_peppol_failure" to fall back to email on Peppol failure, including one reported after the send returns, or send with recipient: null for email-only delivery. See email delivery and notifications.
• PDFs. pdfGeneration.enabled attaches a generated PDF of the document. You can also attach an existing PDF (or other files) via attachments; see adding attachments.

For a full field reference, see sending invoices and sending credit notes.

Sending without writing code

The same send is available two other ways, and they mix freely with the API:

• From the dashboard. Send document takes the recipient and the invoice lines, previews what the recipient will get, and remembers your usual settings. You can also drop an existing UBL or CII XML file into the upload zone if your software already produces one.
• From your accounting or invoicing software. If you use one of the supported tools, let it do the work: your invoices flow to Recommand and out over Peppol without retyping. See integrations for the current list, including Microsoft Business Central, Exact Online, Yuki, ClearFacts, ERPNext and Harvest.

Document types registered for you

When you register a German company as a recipient, it is published for Peppol BIS 3 and for XRechnung 3.0 in both syntaxes, so senders can reach it with the European or the German flavour of EN 16931:

Whichever of these a sender picks, you get the same parsed invoice or credit note out of the API, with the original XML stored next to it.

Need more document types, such as self-billing, message level responses, invoice responses? Register the combinations you want with the create company document type endpoint.

Pick up incoming documents

Once the company is published as a recipient, everything sent to it arrives in Recommand automatically. There are two ways to get the documents into your own systems.

Webhooks (recommended)

Register an endpoint once with the create webhook endpoint and events are pushed to you as they happen, document.received among them:

curl -X POST https://app.recommand.eu/api/v1/webhooks \
  -u key_xxx:secret_xxx \
  -H "Content-Type: application/json" \
  -d @create-webhook.json

{
  "url": "https://your-app.example/webhooks/recommand",
  "companyId": null,
  "secret": "your_webhook_signing_secret"
}

Pass a secret and verify the HMAC SHA-256 signature on every delivery before you trust the payload, then acknowledge with a 200 before doing the heavy processing. Both are covered in working with webhooks.

Polling the inbox

If you would rather pull, the inbox endpoint lists unread documents, and mark as read drops one off the list once your system has it. Fetch details, the original XML or a rendered PDF from the documents endpoints.

Receiving without writing code

• In the dashboard. Incoming invoices appear under Sent and received, with the original XML, a readable rendering, attachments and the delivery history.
• By email. Add notification email addresses per company so incoming documents land in the mailbox your bookkeeping already watches, attachments included. See email delivery and notifications.
• In your accounting software. Forward incoming documents straight to Exact Online, Yuki, ClearFacts or another supported tool, see integrations.

Two things worth setting up early, whichever route you take:

• Labels and suppliers to keep documents organised as volume grows, see suppliers and labels.
• Rules to act on incoming documents automatically: forwarding, labelling, notifying, see rules.

The full picture, including retries and idempotency, is in receiving documents.

Going live

A short list before you start sending or receiving real invoices:

• A valid subscription, so sending is not blocked. Playgrounds skip that check; production does not.
• The company verified, with isVerified true. Until then it cannot exchange documents.
• Errors surfaced, not swallowed. Validation errors name the field that is wrong; put that in front of whoever can fix it rather than logging it.
• Webhook endpoint hardened, if you took that route: signature verification, a fast 200, retries and idempotency on your side.
• One real document sent and received, ideally between two companies you control, so you have seen both ends.
• Notification addresses set, so incoming documents also reach a mailbox somebody reads.

Where to get help

• Troubleshooting. Common rejections, delivery failures and validation errors are collected in the troubleshooting guide.
• Questions. The FAQ covers Peppol, addressing, VAT and billing.
• Email. support@recommand.eu:include the company ID and, for a delivery problem, the document ID.
• Discord. Join the server for release announcements and quick questions.
• Keep track of changes. New endpoints and behaviour are recorded in the changelog.

Other guides for Germany

• Sending Peppol documents in Germany for the companies you onboard
• Receiving Peppol documents in Germany for the companies you onboard
• Sending and receiving Peppol documents in Germany for the companies you onboard
• Sending Peppol documents in Germany for your own company
• Receiving Peppol documents in Germany for your own company