When your payment processor runs as a separate system, every payment creates a second job for your finance team: getting that payment, its fee, and its payout back into Microsoft Dynamics 365 Business Central.
How CPM Connects Stripe and Usio Directly to Your Business Central Financials
The Work That Happens Between Two Systems
Most businesses that accept card or electronic payments use a processor such as Stripe or Usio. The processor handles the transaction. Your ERP holds the invoice, the customer record, and the general ledger. If those two systems don’t share data, someone on your team has to connect them by hand.
That work tends to look the same from month to month:
- Matching each payment to the right open invoice
- Recording processing fees as a separate expense
- Recording each payout when it reaches your bank
- Recording refunds and confirming they went back through the processor
None of these steps is difficult on its own. The trouble is volume and timing. When the payout total doesn’t match what your team expects, the search for the difference starts in one system and ends in another.
What Changes When Payments Start From Business Central
and are built within Business Central. CPM connects your payment processor directly to your Business Central financials, so payment activity starts from the records your team already uses.
From Business Central, your team can generate payment requests. With CPM for Stripe, your team can also send secure payment links. When a payment comes through, CPM captures it and creates a payment entry in the related customer’s ledger. You can also set threshold rules that require a minimum payment or authorization before releasing or shipping an order.
As a result, payments, processing fees, and payouts post to the same ledger as your invoices and customer records. Your team stops rebuilding the processor’s activity after the fact.
Fees Post to the Account You Choose
Processing fees are easy to lose track of when they live only in a processor’s reports. With CPM for Stripe, you choose the G/L account where transaction fees are recorded during setup, and CPM posts platform fees to that account.
You also control how dimensions apply to those fees. You can use the fee account’s default dimensions, or have the fee inherit dimensions from the source transaction, such as the sales order. If your reporting depends on dimensions like department or region, this keeps fee expense tied to the activity that created it.
Payouts Post to Your Bank Account
A processor’s payout is rarely a single payment. It’s a batch of payments deposited on the processor’s schedule, and someone has to record it when it arrives.
For both Stripe and Usio, CPM records unpaid activity to a clearing G/L account while your processor balance builds. When your processor sends a payout, CPM detects the payout transaction and posts it to the balancing account you select. This is typically a bank account. The clearing account shows what is still pending, and the bank account reflects what has arrived.
Refunds Follow the Same Path
When you need to issue a refund, your team starts it from the original payment record within Business Central by creating a refund request. CPM captures the refund through your payment processor and creates a refund entry that is applied to the customer ledger entry for the original payment. If the order has already been invoiced, your team creates and posts a credit memo for the refund amount, then applies the refund entry to that credit memo.
Recurring Billing Through Stripe
If you bill on a recurring schedule, subscriptions are set up in Stripe. When Stripe generates a subscription invoice, CPM downloads it and creates a corresponding invoice within Business Central. Your recurring revenue shows up in the same place as the rest of your receivables.
What CPM Does Not Do
Clear limits help you evaluate any tool. CPM does not process payments itself. Stripe or Usio processes the transaction, and CPM connects that activity to Business Central. CPM handles payments that start from within Business Central. It does not process payments taken on outside platforms such as Shopify or Amazon.
CPM is self-installed with step-by-step instructions. Setup is still required, including the G/L accounts, payment methods, and number series described above, so plan for time to configure it to match your chart of accounts.
Questions to Ask Before You Choose a Payment Approach
If you’re comparing payment options for Business Central, these questions will show how much manual work each one leaves for your team:
- Where do processing fees get recorded, and who records them?
- How are payouts recorded when they reach your bank?
- What happens within Business Central when a refund is issued?
- Can your team send payment requests without leaving Business Central?
- Which payment processors does the tool support today?
CPM was named to the ERP Software Blog list of the Best Microsoft Dynamics ERP Tools for Payment Processing 2026.
See CPM Working With Your Business Central Setup
Suite Engine builds applications within Microsoft Dynamics 365 Business Central for businesses that want their operations and financials to stay in one system. Learn more about .
to see how payments, fees, and payouts post to your Business Central financials.
