Payments to finance

What happens after the payment.

Your payment provider settles in batches, net of fees, with refunds and chargebacks mixed in. Your ERP expects invoices and bookings. We connect the two: every line matched to the order and invoice it belongs to, delivered to finance, and anything that does not match in a queue someone can work through.

Talk to usSee the queueRead-only on your payment provider · EU-hosted
The stage we own

From payout to finance close.

Authorization, capture and payout stay with your payment provider. We take what it reports afterwards and turn it into bookings your ERP and your controller accept.

Where Beetl sits between provider and ERP.
What your finance team sees

One payout, three things to look at.

Each payout is checked line by line against orders and invoices. What matches is booked. What does not is listed with the reason and a suggested next step, so month-end is a queue rather than a hunt.

1Totals per payout, split into captures, fees, refunds and chargebacks.
2Only the exceptions surface, each with the reason it did not match.
3Every booking traces back to the report line it came from.
One payout, matched line by line.

Where this comes up.

Your ERP has no connector for your provider

The provider's own reconciliation covers the big ERPs. Business Central, Odoo, Xentral, weclapp or a legacy system are left to a spreadsheet.

More than one provider or entity

Several payment providers, several merchant accounts or several companies, and the controller needs one consistent picture.

A migration or a new provider

Moving to a new payment provider or a new ERP, and the finance side has to keep working from the first payout.

Platforms paying out to sellers

Marketplaces and platforms that split payments and pay out to many accounts, and need per-seller statements their own customers trust.

How the work runs

One payout first, then every payout.

Map one payout

We take one real payout report and your ERP's booking structure, and agree with your finance team how each type of line is booked.

Match and deliver

Every line matched to its order and invoice, the bookings delivered to your ERP or as an import file, and the exceptions listed in a review queue.

Run it every payout

The same rules on every settlement, with totals checked per payout. Either we run it on Beetl or hand it over to your team.

FAQ

Which payment providers?
Adyen settlement detail and payment accounting reports, Stripe balance transactions and payouts, and Mollie settlements. Other providers with a report export or an API work the same way.
Which ERPs and accounting systems?
Business Central, Odoo, Xentral, weclapp and SAP through their supported APIs, and DATEV through its import format. If your system takes a file, we deliver the file.
Does this replace our payment provider's own connector?
No. Where a provider ships a connector for your ERP, use it. We cover the ERPs, entities and edge cases it does not: several providers, several companies, custom invoicing, or a legacy system.
Who decides how fees and chargebacks are booked?
Your finance team. We implement the accounting treatment you approve, and every rule is SQL your team can read.
Do you touch the payment flow?
No. We read reports and events after the payment has happened. Payment processing stays with your provider.

Bring one payout report.

We show you what it takes to match it against your ERP, as the first step of a short fixed-price pilot.

Talk to us