Move from Stripe Invoicing.

Stripe is a payment processor first. Stripe Invoicing was bolted on so developers issuing one-off charges had a document to send — and it's fine for that. It is not a country-compliant invoicing system, it doesn't produce Peppol BIS Billing 3.0, XRechnung, ZUGFeRD, Singapore Tax Invoice, NF-e, CFDI, or Japan QIS documents natively, and the moment you need a structured tax invoice or a B2B mandate-compliant document, you've outgrown it. The important framing: you keep Stripe for payments. This is augment, not replace.

What we import

Stripe's API exposes the historic invoice and customer data we need.

Source	What comes across
Stripe API (OAuth / restricted key)	Customers, historical invoices, invoice items, payments, products, prices, subscription metadata
Stripe CSV export	Customers, invoices, charges — list-level CSVs from the Stripe Dashboard

Invoice numbers preserve. Multi-currency stays multi-currency. Tax rates per line map to Guliel's tax configuration. Customer records arrive with their Stripe customer ID retained as a reference field, which matters for the ongoing integration described below.

What we still do with Stripe — after the move

This is the part that's different from a normal migration.

• Payments stay on Stripe. Guliel integrates with Stripe as a payment rail going forward. When you issue a Guliel invoice, the payment link routes through your Stripe account. Funds land in Stripe. Reconciliation is automatic.
• Refunds and disputes stay on Stripe. Issued from inside Stripe; the resulting status reflects back into Guliel.
• Webhook reflection. Stripe payment events update Guliel invoice state — paid, partially_paid, failed — without manual intervention.

In short: Stripe handles the money, Guliel handles the document, the customer relationship, the expense / supplier / report side, and the country-specific compliance Stripe doesn't do.

What we don't import

Be clear before you click.

• Stripe Connect platform structure. If you run a marketplace on Connect (connected accounts, transfers, application fees), that platform structure stays on Stripe. We import the platform-level customers / invoices, not the connected-account tree.
• Subscription billing logic. Stripe Billing's subscription engine (proration, trials, dunning) stays on Stripe. Guliel isn't subscription billing — for that, Chargebee or Recurly remain better tools. We import subscription invoices as historical records.
• Stripe Radar fraud rules and Sigma queries. Risk and analytics live in Stripe.
• Stripe Tax automated jurisdiction logic. We handle invoice-level tax, not full nexus determination. If you use Stripe Tax for automatic nexus calculation across US states or EU countries, keep it — it complements Guliel rather than competes.
• Files attached to Stripe customer records — limited via CSV; available via API.
• Disputes evidence packets. Stay in Stripe.

If something on your Stripe account isn't on either list — ask. Stripe-heavy SaaS businesses have a wide range of setups.

Estimated time to migrate

Most Stripe Invoicing migrations finish in under 30 minutes — the API is fast, the data model is clean, and the integration handshake for ongoing payments takes another five minutes after the import. Larger merchants with 50,000+ historical invoices: 1–2 hours plus a reconciliation report. Multi-account Stripe setups (separate Stripe accounts per legal entity) map one Stripe account per Guliel organization, billed per org.

Start the move

Connect Stripe, scope the historic import, run a preview, commit. Migration is free on every plan. Pricing for what comes after lives at /pricing. The country-by-country compliance side — the actual reason most teams move off Stripe Invoicing — is at /invoicing. The full integration list including the live Stripe payments connection sits under /product/integrations.

FAQ

Will my Stripe customers see anything change?

Only the document. Payment flow continues through Stripe; what's different is that the invoice now comes from Guliel in a country-compliant format (Peppol BIS Billing 3.0, XRechnung, etc., where applicable).

Do I lose anything by keeping Stripe for payments?

No. Stripe stays in the loop on the money side — this is augment, not replace. Built-in payments inside Guliel are on our roadmap; Stripe handles it well until then.

What about my Stripe subscriptions?

Subscription billing stays on Stripe. Guliel isn't a subscription billing engine. We import the historical invoices but the recurring schedule continues to fire from Stripe.

Will my invoice numbers carry over?

Yes. Existing Stripe invoice numbers preserve; Guliel continues from your latest number for newly issued documents.

Is migration free?

Yes. Migration costs nothing on any plan, including the Free tier (200 invoices / month).

What's the difference between Stripe Invoicing and Guliel Invoicing?

Stripe Invoicing is a document generator for charges. Guliel is country-compliant invoicing infrastructure — Singapore Tax Invoice, US Commercial Invoice, Peppol BIS Billing 3.0, XRechnung, ZUGFeRD, NF-e, CFDI, Japan QIS, and more across 38+ countries — plus expenses, suppliers, logistics, automations, reports, and an AI companion.

Will Stripe Tax still work?

Yes. Stripe Tax for jurisdiction determination is complementary, not competitive. We handle invoice-level tax on the document; Stripe Tax handles nexus calculation across jurisdictions.