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.

These settings live in the dashboard, not the public API. Configure them at Settings → Integrations → Stripe → pick connection. There is no public endpoint to read or modify them programmatically today.

At a Glance


Where to configure	Settings → Integrations → Stripe → pick connection
Independent per connection	Yes — multiple Stripe accounts can have different settings
Changes affect	Only new invoices; already-issued invoices are immutable
Most-tuned settings	Simplified threshold, VeriFactu submission, auto-create customer

Fiscal limits

Simplified threshold

Controls when BeeL issues a simplified invoice (F2) vs a standard invoice (F1) for a Stripe payment.


Default	400 €
Maximum	3 000 € (legal cap for F2)
Minimum	0 € (disables simplified — every payment must be F1)
Comparison	Payment total IVA-included

Three useful values:

3 000 € — the most permissive setting. BeeL issues F2 whenever possible (saves you from collecting NIFs for small purchases).
400 € (default) — a conservative threshold for typical B2C SaaS pricing.
0 € — disables simplified entirely. Every Stripe payment must produce an F1; if the customer lacks NIF + address, the event is parked in the Necesita atención inbox. Useful for B2B-only connections.

See Generated invoices for the full F1/F2 decision tree.

Prices include tax

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


Default	On (charges are inclusive)
On	BeeL treats the charge total as inclusive: `base = total / (1 + rate/100)`
Off	BeeL treats the charge total as the base and adds IVA on top — the resulting invoice total is larger than what Stripe charged

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

Turn this off only if your Stripe prices are net. Most B2C prices in Stripe are tax-inclusive; turning it off on inclusive prices produces invoices whose total exceeds what the customer paid.

VeriFactu submission

Auto-submit to AEAT


Default	On
Effect when on	Issued invoices are auto-submitted to AEAT
Effect when off	Invoices are issued locally and NOT sent to AEAT
Other gates	Global VeriFactu onboarding must also be complete — see Auto-submit policy

Common reasons to turn this off temporarily:

Migrating historical Stripe data and you don't want backfills to reach AEAT
A staging Stripe connection that should not produce real fiscal records
A one-off testing window before going live

See VeriFactu submission for the full policy.

Customer management

Auto-create customer


Default	On
Effect when on	BeeL stores a mapping for each new Stripe customer and auto-links to a managed customer when NIFs match
Effect when off	Invoices are issued with the buyer's data inline; nothing is stored for re-use

See Customer mappings.

Invoice delivery

Auto-invoicing


Default	On
Effect when on	Payment-success events generate invoices
Effect when off	Events are received but no invoice is created (useful for staging, migration, or pause windows)

When off, events land in the Necesita atención inbox — see Edge cases and limits for the operator workflow.

Auto-send via email


Default	On
Effect when on	Generated invoices are automatically emailed to the customer (using the email from the Stripe payload)
Effect when off	Invoices are generated but NOT auto-emailed

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 automatically. The mapping is fixed, not a per-connection setting:

Original invoice was simplified (F2) → always R5
Stripe reason is duplicate or fraudulent → R4
Any other Stripe reason → R1

See Generated invoices > Mapping Stripe's reason for the full table and rationale.

What changes when you flip a setting

Setting changed	Affects next Stripe event?	Affects existing invoices?
Simplified threshold	Yes	No
Auto-submit to AEAT	Yes (for new submissions)	No (already-submitted invoices stay submitted)
Auto-create customer	Yes	No (existing mappings stay as they are)
Auto-invoicing	Yes	No
Auto-send via email	Yes	No (already-sent emails are not re-sent)
Prices include tax	Yes (fallback path only)	No

Generated invoices — how settings affect the F1/F2 + R1–R5 decisions
Customer mappings — auto-create / linked vs ad-hoc
VeriFactu submission — the auto-submit gate
How Taxes Are Applied — the Fiscal Mirror rule

Connection settings

On this page