# Overview

Connect your Stripe account with BeeL. to issue an invoice automatically for every payment.

## At a glance

| | |
|---|---|
| **What it does** | Issues an invoice in BeeL. every time you receive a payment in Stripe |
| **How it connects** | Via [Stripe Connect](https://stripe.com/connect) (OAuth) |
| **What you need** | A Stripe account and an active BeeL. subscription |
| **What you should know** | Stripe's own invoices are not issued through BeeL.: turn them into proformas so your customers receive one invoice |

---

## How does it work?

BeeL. connects to your Stripe account using **Stripe Connect**. This means you authorize BeeL. to receive notifications about your payments, without sharing your API keys or sensitive data.

### The flow is simple

1. **Your customer pays** in Stripe (subscription, one-time payment, anything)
2. **Stripe notifies BeeL** automatically via a webhook
3. **BeeL. issues the invoice**, mirroring the Stripe charge exactly — see [Data conversion](/stripe/data-conversion)
4. **BeeL. submits its billing record to AEAT** (VeriFactu) if it is enabled for the NIF
5. **Your customer receives the invoice** by email (if enabled)

You don't have to do anything per payment. Just connect and configure once.

<Callout type="info">
  **Refunds and credit notes** generate corrective invoices automatically. BeeL. maps Stripe's reason to one of R1–R5 — see [Generated invoices](/stripe/generated-invoices).
</Callout>

---

## What does this mean for my customers?

This is important and we want to be transparent:

<Callout type="warn">
**Stripe invoices and BeeL. invoices are different things.** Stripe generates its own payment documents; they are not issued through BeeL., so they carry no number from your BeeL. series, no billing record and no VeriFactu QR.
</Callout>

To avoid confusion, we recommend **configuring Stripe invoices as proforma** and disabling their invoicing emails. That way your customers only receive the invoice issued through BeeL.

The downside is that **your customers won't be able to see invoices in the Stripe portal**. This is a current limitation — the invoices issued through BeeL. are in BeeL., not in Stripe. We're working to improve this experience.

---

## Initial setup

1. Go to [**Settings > Integrations**](https://app.beel.es/ajustes/integraciones) in BeeL
2. Click **Connect** on the Stripe card
3. Authorize the connection with your Stripe account (Stripe Connect opens)
4. [Open the Stripe configuration](https://app.beel.es/ajustes/integraciones?provider=stripe&settings=true) and choose your invoice series, whether to send emails, etc.
5. **In Live mode, switch on auto-invoicing** for the connection. A Live connection starts with it off, so charges are not invoiced until you do — see [Connection settings](/stripe/connection-settings#auto-invoicing). In Test mode it starts on.

Once auto-invoicing is on, every payment generates an invoice automatically. A payment whose data is not enough to invoice it waits in **Needs attention** with the reason — see [Edge cases and limits](/stripe/edge-cases-and-limits).

<Callout type="info">
  **Managing several NIFs (agencies & fleets)?** Connect Stripe **per NIF over the
  API** — white-label, from your own portal — instead of the dashboard flow above.
  Each company (owned or [managed](/multi-nif/managed-accounts)) gets its own
  connection so charges are auto-invoiced under the right NIF. See
  [**Connect Stripe**](/multi-nif/payment-connections) for the connect · list ·
  disconnect endpoints.
</Callout>

---

## Setup guides

<Cards>
  <Card title="Configure Proforma Invoices in Stripe" href="/stripe/configuracion-proforma">
    How to disable Stripe invoices so your customers receive one invoice per payment.
  </Card>
  <Card title="How Taxes Are Applied" href="/stripe/configuracion-impuestos">
    Fiscal Mirror rule — BeeL. reflects Stripe's tax breakdown exactly, with a clean fallback when Stripe Tax isn't enabled.
  </Card>
  <Card title="Connection settings" href="/stripe/connection-settings">
    Every per-connection setting — auto-invoicing, customer creation, email delivery.
  </Card>
</Cards>

## How it works

<Cards>
  <Card title="Supported Stripe events" href="/stripe/supported-events">
    Which events BeeL. listens to, which create invoices, and which are explicitly ignored.
  </Card>
  <Card title="What invoice gets generated" href="/stripe/generated-invoices">
    The F1 vs F2 decision tree, the refund → R1–R5 mapping, and series resolution.
  </Card>
  <Card title="Data conversion" href="/stripe/data-conversion">
    Field-by-field mapping from Stripe payload to BeeL. invoice, with the Fiscal Mirror rule explained.
  </Card>
  <Card title="Customer mappings" href="/stripe/customer-mappings">
    How BeeL. matches Stripe customers to BeeL. customers and creates ad-hoc records when needed.
  </Card>
  <Card title="VeriFactu submission" href="/stripe/verifactu-submission">
    Why AEAT submission is decided by the issuing NIF, not by the connection.
  </Card>
</Cards>

## Operations

<Cards>
  <Card title="Edge cases and limits" href="/stripe/edge-cases-and-limits">
    Every skip reason, how to retry a failed event, and the known limits of the integration.
  </Card>
</Cards>

---

Full OpenAPI spec: https://docs.beel.es/api/openapi