D365ConsultantDivision of Sataware
D365ConsultantDivision of Sataware
Card payments to the ledger

Business Central Stripe integration that explains every payout.

A Business Central Stripe integration exists to answer one question your controller asks every month: why does this deposit not equal the invoices we were paid for? Stripe sends a net payout after it has taken processing fees, returned money for refunds and pulled funds for disputes. We design the link so each payout lands in Business Central as its parts. Each part goes to the right customer and account, and the bank line clears without a spreadsheet.

Net payouts
Stripe deducts fees before it pays out
Clearing account
the usual home for money in transit
Test mode
Stripe's sandbox for safe trial runs
Hand holding out a credit card to pay

Why a Stripe deposit never matches your open invoices

Stripe keeps a balance for your account. Every charge adds to it, and every fee, refund, dispute and adjustment takes something away. On your payout schedule, Stripe sweeps what is available to your bank. So one deposit can hold a long list of balance transactions from several days. Nothing in the bank statement tells you which customers paid.

Before any build, settle which system owns what. Business Central should own customers, invoices, the chart of accounts and the bank reconciliation. Stripe owns card data, the payment itself and the payout. The integration carries facts from Stripe into the ledger. It should never push card details or payment tokens into Business Central. That keeps your ERP out of scope for card data rules.

The second decision is who issues the invoice. If Business Central invoices and Stripe only collects, we apply each payment to an existing open entry. If Stripe Billing runs subscriptions and issues its own invoices, Business Central usually receives summarized revenue by plan and period instead, and the customer ledger lives mostly in Stripe. Mixing the two without a rule produces duplicate receivables.

How Stripe balance transactions map to Business Central

Stripe item
Flows
Business Central posting
System of record
Charge or payment
Stripe to BC
Customer payment applied to the invoice, debit to the Stripe clearing account
Stripe for the payment, BC for the invoice
Processing fee
Stripe to BC
Debit to a merchant fees expense account, credit to clearing
Stripe
Refund
Stripe to BC
Credit memo or refund entry against the customer, credit to clearing
Whichever system approved the refund
Dispute and dispute fee
Stripe to BC
Funds withdrawn to a disputes receivable account, fee to expense
Stripe
Dispute won
Stripe to BC
Reverse the disputes receivable when funds return
Stripe
Currency conversion
Stripe to BC
Difference posted to a realized gain or loss or a conversion fee account
Stripe for the rate used
Payout
Stripe to BC
Transfer from clearing to the operating bank account
Your bank statement
Customer and invoice numbers
BC to Stripe
Written to Stripe metadata so every charge carries the invoice it pays
Business Central

Connector app, iPaaS or your own code

Fastest start

A connector app on AppSource

Several vendors publish apps that pull Stripe payouts into Business Central journals.

  • โœ“Runs inside Business Central with its own setup pages
  • โœ“Check how it treats disputes, multiple currencies and partial refunds
  • โœ“You depend on the vendor keeping pace with Stripe API versions
Several gateways

Integration platform

An iPaaS tool reads Stripe events and writes journal lines through the Business Central API.

  • โœ“Fits when PayPal, a marketplace and Stripe all need the same treatment
  • โœ“Central logs and retry queues
  • โœ“Someone on your side owns the flows
Unusual rules

Custom AL extension or service

Code that reads the payout's balance transactions and builds exactly the entries finance wants.

  • โœ“Handles revenue split by product line or entity
  • โœ“Idempotency keys and webhook signature checks built in
  • โœ“You maintain it when either API changes

Stripe details that trip up finance teams

  • โœ“Payouts draw on the available balance, so a charge taken on Friday may not appear in the deposit you expected
  • โœ“Refunds issued in the Stripe dashboard bypass Business Central unless the integration picks them up as events
  • โœ“A disputed charge leaves your balance weeks after the sale, often in a later period than the revenue
  • โœ“Charges in a foreign currency settle in your payout currency at Stripe's rate, not your Business Central exchange rate
  • โœ“Webhooks can arrive twice or out of order, so every posting needs a unique Stripe ID to reject duplicates
  • โœ“A negative balance is possible when refunds exceed sales, and Stripe may debit your bank account to cover it

Proving it in test mode, then watching it live

  1. 1

    Script the awkward cases

    In Stripe test mode, create a normal sale, a partial refund and a full refund. Add a lost dispute, a won dispute and a charge in a second currency.

  2. 2

    Post into a sandbox environment

    Run each payout into a Business Central sandbox copy of your company and check the clearing account returns to zero after every payout.

  3. 3

    Reconcile a real month in parallel

    Before cutover, let the integration post into the sandbox while your team reconciles the live month by hand, then compare line for line.

  4. 4

    Alert on what does not clear

    After go-live, a daily check flags any clearing balance older than one payout cycle and any Stripe charge with no matching invoice number.

Stripe and Business Central questions from finance

Does Microsoft publish a Stripe connector for Business Central?

Not one we would point you to as the standard answer, so most companies use a vendor app from AppSource or a purpose-built link. Microsoft's own ecommerce connector covers Shopify, whose payouts can include Stripe-processed payments, but a direct Stripe account for invoices or subscriptions needs its own integration. We compare the available apps against your dispute, currency and refund needs before recommending one. If none fits, a small custom extension is often simpler than bending an app.

Should every Stripe charge become a separate entry in Business Central?

Usually yes for B2B invoices and no for high-volume retail. When each charge pays a specific invoice, posting it individually keeps the customer ledger accurate. Sometimes many card sales have no invoice in Business Central. Then a summary per payout by account and dimension keeps the ledger readable, while Stripe keeps the detail. The deciding factor is whether anyone needs to see a customer balance in the ERP.

How do we handle Stripe fees for sales tax and reporting?

Fees are an expense of your business and should post to their own account, never netted against revenue. Netting hides the true cost of card acceptance and understates gross sales, which can confuse sales tax reporting. The integration posts the gross charge to the customer and the fee separately to expense. Your tax advisor can confirm how your state treats the revenue side.

More Business Central Stripe integration questions

What happens when a customer disputes a payment?

Stripe withdraws the disputed amount and a dispute fee from your balance, and the integration should record both at that moment. We post the amount to a disputes receivable account rather than reopening the invoice straight away, because the outcome is unknown. If you win, the returned funds clear that account. If you lose, your normal process writes it off or charges it back to the customer. Either way the payout still reconciles.

Can we still use Business Central bank reconciliation?

Yes, and that is the point of routing payouts through a clearing account. A Business Central Stripe integration moves each payout from clearing to the bank account. So the bank reconciliation or payment reconciliation journal matches one ledger entry to one deposit. Finance keeps its familiar month-end routine. The clearing account itself becomes the control that shows anything Stripe paid but the ledger has not explained.

Talk to us about your project.

Tell us what you run today and what has to change. A senior consultant replies with a written next step.

Get started

Start with a scoping conversation.

Thirty minutes with a senior consultant - not a sales call. We look at how you run today, tell you plainly whether Business Central is the right fit, and give you an honest sense of scope, cost and timeline before you commit to anything.

What happens next
1
We review your enquiry
A consultant reads it before the call - no discovery questionnaire to fill in.
2
30-minute scoping call
Your processes, your current systems, and the gaps that matter most.
3
Written summary & estimate
Indicative phases, licence counts and a cost range, in writing within three days.
Reply within one business day
NDA signed before discovery on request
No obligation, no cost for the scoping call
Microsoft-certified consultants only
Request your scoping call
Four fields. A consultant replies within one business day.
No cost
Your details stay with our consulting team - never shared, never added to a mailing list.