---
title: "Send a customer e-invoice to PA"
method: POST
path: "/api/external/v2/customer_invoices/{id}/send_to_pa"
tags: ["Customer Invoices"]
---

# Send a customer e-invoice to PA

`POST /api/external/v2/customer_invoices/{id}/send_to_pa`

## Request

- Base URL: `https://app.pennylane.com`
- URL: `https://app.pennylane.com/api/external/v2/customer_invoices/{id}/send_to_pa`
- Auth: OAuth 2
  - Authorization code: `https://app.pennylane.com/oauth/authorize`
  - Token URL: `https://app.pennylane.com/oauth/oauth/token` scopes: `customer_invoices:all`

Send a customer e-invoice to the Partner Dematerialization Platform (PA).

After an e-invoice import, the file may still be processing. If you call this
endpoint before processing is finished, the API returns 409. Retry after a few
seconds. A 204 response means the invoice is being sent to the PA.


> ℹ️
> This endpoint requires the following scope: `customer_invoices:all`

## Path parameters

- `id` integer, required

## Headers

- `X-Company-Id` string

## Response `204`

Customer e-invoice is being sent to the Partner Dematerialization Platform (PA)

## Other responses

- `400`: Bad request
- `401`: Access token is missing or invalid
- `403`: Access to this resource forbidden
- `404`: The resource was not found
- `409`: Conflict with the current state of the target resource, such as when trying to create a resource that already exists.
- `422`: Unprocessable content

## Changes

- **2026-11-03** `871f863307e5`: 2 info
  - added the new optional `header` request parameter `X-Company-Id`
  - added the non-success response with the status `409`

[Operation history](https://skmtc.dev/pennylane/apis/company-v2/changes/api/external/v2/customer_invoices/:id/send_to_pa/post.md)

---

[API](https://skmtc.dev/pennylane/apis/company-v2.md) - [All operations](https://skmtc.dev/pennylane/apis/company-v2/llms.txt) - [OpenAPI document](https://skmtc.dev/pennylane/apis/company-v2/revisions/871f863307e5?raw)