Connection settings

Each Stripe connection has its own configuration. You can have a strict production connection, a permissive staging connection, and a third one for a different revenue stream — all on the same BeeL. account. This page lists every setting that affects how BeeL. turns a Stripe payment into an invoice.

At a glance

Fiscal limits

Simplified threshold (deprecated)

Before, a charge below the threshold was issued as a simplified invoice (F2) even when the customer had given a NIF and address. That no longer happens: the invoice type now depends only on the customer's data.

• Customer with a NIF (or foreign identifier) and a complete address — standard invoice, at any amount.
• Customer without full fiscal data — simplified invoice up to 3,000 €. Above that amount a simplified invoice is not allowed, so BeeL. saves a draft (and, on Live connections, emails you); it appears in Needs attention (Necesita atención in the dashboard) for you to complete and issue. See Charges that cannot be invoiced automatically.

A simplified invoice generated from a payment never identifies its recipient: it keeps the name, email and address the payment carries, but not the NIF or alternative_id, and it is not linked to the customer. It is the same rule as for invoices you create through the API — see Simplified vs standard. It applies to a customer without full fiscal data, to a customer with a NIF but no address, and when a standard invoice goes to your simplified series because the connection has no default standard series (only up to 3,000 €). The full F1/F2 decision tree is in Generated invoices.

Prices include tax

When Stripe Tax is not enabled on the connection, BeeL. needs to know whether the Stripe charge amount already includes IVA.

When Stripe Tax IS enabled, this setting is ignored (Stripe's breakdown wins). See Data conversion.

VeriFactu submission

There is no per-connection VeriFactu setting. Whether a Stripe-generated invoice reaches AEAT is decided by the issuing NIF, like any other invoice — see VeriFactu submission for Stripe invoices.

Customer management

Auto-create customer

See Customer mappings.

Invoice delivery

Auto-invoicing

A Live connection starts with auto-invoicing off, because every charge it invoices produces a real invoice. Until you switch it on, no charge is invoiced and nothing warns you. Switch it on in the dashboard or with auto_invoice_enabled (Update a payment connection). Charges received before that are not invoiced on their own: retry them once it is on. Disconnecting and reconnecting the account keeps the value you chose.

When off, events are recorded as skipped without asking for attention, and can be retried once you turn auto-invoicing back on — see Edge cases and limits. API field: auto_invoice_enabled.

Event source

A Stripe account sends every event to the same webhook endpoint, but you may only want one family of them invoiced. API field: event_source.

Events outside the chosen family are recorded as skipped on purpose and need no attention. Refunds, disputes and credit notes are acted on under every value, because Stripe does not always report a correction through the family the charge came in; a correction whose charge was never invoiced is recorded as skipped and needs no action either. Changing the value affects events that arrive from then on; events already recorded keep their outcome.

Auto-send via email

You can always send an issued invoice manually later — that path goes through the public Invoicing API.

Refund mapping (not configurable)

The refund.reason and credit_note.reason from Stripe are mapped to AEAT R1–R5 codes by a fixed rule, not a per-connection setting — see Generated invoices > Mapping Stripe's reason.

What changes when you flip a setting

Related