Solution · By integration

Connecting Stripe to Holded is the easy part. Making the books add up isn't.

The charge goes through. The invoice, the credit note, the fee and the net payout are another story: someone ends up squaring them in a spreadsheet at month end. We build the AI layer between Stripe's API and Holded's that does that work on its own.

Ship it in my business See how it works

The problem

The money lands in Stripe. The accounting lives in Holded. In between, a spreadsheet.

Stripe doesn't pay you charge by charge: it pays a batched payout, net of fees, and someone has to open it up to find out which charges are inside and which invoice belongs to each.
The Stripe fee isn't a discount on the sale: it's an expense that has to be booked separately for your margin and your taxable base to add up.
Refunds and chargebacks land days or weeks after the charge, and each one forces a credit note in Holded that nobody has scheduled.
The customer paid through a checkout that never asked for a tax ID or a legal name, and the invoice sits waiting for someone to chase the billing details over email.
If you charge in several currencies, the amount Stripe sees and the amount that hits the bank aren't the same number, and the FX difference ends up as a manual adjustment.

Cost of staying the same

You have the most automatable payment gateway on the market wired to your accounting by one person with a spreadsheet. The cost never shows on an invoice: it shows as month-ends that slip, VAT filed in a rush, margins that don't match what you actually charged, and refunds credited weeks late because nobody saw them go by.

The solution

An AI layer between Stripe's API and Holded's that turns money into accounting

1We start from what you already have. If you use Holded's native Stripe integration, we don't rip it out: we leave it doing what it does well —pulling in the charge— and build on top what it doesn't cover, which is exactly the part that takes judgment.
2We listen to Stripe events over webhook —payment succeeded, subscription invoice paid, refund, dispute, payout settled— and translate each one into the right document in Holded through its API: invoice, credit note, expense or journal entry.
3We break the payout open. The AI splits the batched deposit, matches every charge to its invoice and books the Stripe fee as its own expense, so the bank statement squares against Holded without anyone ticking line by line.
4We close the odd cases, which are the ones that eat the hours: a refund with its credit note, a chargeback with its provision and its resolution, a customer with no billing details who gets chased and completed in the Holded contact, and the FX difference posted where it belongs.
5We leave it measured and with a net: what share of charges reaches Holded untouched, which cases escalate to your accountant with the context already summarized, and how much the close time drops.

What changes

What you stop losing

The payout stops being an opaque number: it lands broken down into charges, fee and net, with every charge pointing at its Holded invoice.
Mechanism
Refunds and chargebacks stop being discovered at the close: they fire their credit note or their provision the day they happen, not when someone reviews the statement.
Mechanism
The invoice stops waiting on billing details: the AI chases them from the customer and completes the contact in Holded, instead of leaving the charge with no document.
Mechanism
What we measure: % of charges that reach Holded untouched, invoice and ledger account accuracy, days of delay on the close, and number of manual adjustments per month.
What we measure

Spec sheet

Work it removes: squaring by hand what Stripe charges against what Holded invoices: opening payouts, posting fees, issuing credit notes and chasing billing details
Typical setup: 2–4 weeks
Input: a Stripe event: a charge, a subscription invoice, a refund, a dispute or a settled payout
Output: the right document created in Holded —invoice, credit note, expense or journal entry— with its contact, its ledger account and its tax
Works with: Stripe (API + webhooks)Holded (API v2)Stripe Billing (suscripciones)Stripe Connect
Can connect to: Your native Stripe–Holded integration, if you already have it runningYour bank connected in Holded, so the payout squares against the statementYour invoicing series, ledger accounts and VAT rates
What we measure: % of charges that reach Holded untouchedinvoice and ledger account accuracydays of delay on the monthly closenumber of manual adjustments per month
Good fit for: companies that charge through Stripe —SaaS, ecommerce, recurring services— and keep their books in Holded
Not a fit for: anyone who only charges by bank transfer or a card terminal, or who needs a tax advisor to decide the accounting treatment: an integration doesn't replace that

Frequently asked questions

For the happy path, yes: the official integration pulls charges into Holded and helps you reconcile, which is why we leave it alone. Where it runs out of road is everything that takes judgment: opening a batched payout net of fees to work out which invoice belongs to each charge, issuing the credit note for a refund with the right series and date, provisioning a chargeback and resolving it when Stripe rules one way or the other, completing a contact the checkout never asked a tax ID for, or posting the FX difference on a charge in dollars. Those cases are what eat your accountant's hours, and they're exactly what we build on top.

You can, and for the simple flow —charge in, invoice out— it works. What chokes is the exception, and in accounting the exception isn't a rare case: it's the job. A flow that opens a payout, matches every charge to its invoice, decides whether this is a credit note or a provision and chases missing details runs to ten or fifteen steps, and in tools that bill per step you pay for that hardening every month. Our take is honest: if your case fits in a three-step flow, build it yourself with Make and don't call us. If your month goes on squaring exceptions, that's where we come in.

That's why it starts with a net. Documents that touch the books —invoices, credit notes, expense posting— start in proposal mode: the AI leaves them ready in Holded and your accountant approves them, until accuracy is high and you release autonomy by transaction type. Anything doubtful —a payment with no clear invoice, a customer with no details, an open dispute— always escalates to a person, with the case already summarized and a link to the Stripe transaction. We don't replace anyone's accounting judgment: we take the keyboard work off their plate.

Want it running in your business?

You’ve pinned the problem. We ship the fix and leave it measured.

See the service