Why Finance & Operations customers add Payment Hub
Use Clarity Payment Hub for Dynamics 365 Finance payment processing and post card, ACH and portal payments as customer payment journals, settled against open transactions in every legal entity.
It works through standard data entities, with no X++.
The F&O customers we work with have usually already automated the bank side. Lockbox files import. Bank statements reconcile through advanced bank reconciliation. What still runs on people is card and portal payment. A customer wants to pay an invoice on a corporate card, so someone in the shared service center takes the number over the phone, runs it in a virtual terminal, and keys a customer payment journal line the next morning from the processor's report, then settles it. Multiply that across four legal entities and a few hundred payments a month and it is a full-time role.
Payment journals posted and settled, not keyed
AR automationReminders and dunning on open customer transactions for each legal entity, so the shared service center works exceptions instead of keying payments.
Cash application and payment reconciliationEach payment becomes a customer payment journal in the legal entity that issued the invoice, posted and settled against the invoice or prepayment it pays.
One payment, settled in F&O
- CUSTOMER PORTALPaid across open transactions
- PAYMENT JOURNALPosted through data entities
- SETTLEMENTMatched to CustTrans
- LEGAL ENTITYPosted to USMF
Prepayments and invoices in every legal entity
B2B payments for the enterpriseInvoice, prepayment, order and portal payments from one configuration across legal entities, through standard data entities and with no X++.
Credit card processing fees and surchargingA disclosed surcharge on credit card payments where state and card-network rules allow it. Debit cards are never surcharged.
A prepayment, end to end
- SO-004412Prepayment invoice issued
- ACHPaid from a link
- FINAL INVOICESettled against the prepayment
- SURCHARGEDisclosed where rules allow
A portal across every legal entity a customer buys from
Customer payment portalA portal reading open customer transactions across every legal entity a customer buys from.
ACH paymentsACH and eCheck beside cards, each posted as a payment journal with the right method of payment.
Lower card costs on commercial cards
Level 2 and Level 3 interchangeSales order line detail goes with each eligible commercial card payment, which the Commerce connector doesn't send for AR.
Visa CEDPVisa's Commercial Enhanced Data Program grades commercial card payments on that detail. On Visa's April 18, 2026 schedule, failed data earns nothing over no data, and the checks aren't published, so the detail comes from F&O's own sales order lines.
Card cost controls
- COMMERCIAL CARDLevel III from sales order lines
- VISA CEDPLine-item data validated
- DEBIT CARDNever surcharged
Payment Hub vs native Dynamics 365 payment options, honest side-by-side
Microsoft's own card processing for Dynamics 365 lives in Commerce, through the Dynamics 365 Payment Connector for Adyen and partner connectors, and it is built for point of sale and ecommerce. F&O accounts receivable has no equivalent for invoice payment. It is worth being precise about what each covers.
| Capability | Native D365 (Commerce payment connector) | Payment Hub on D365 F&O |
|---|---|---|
| Scope | ✗ Point of sale and Commerce storefront transactions | ✓ AR invoice, prepayment, order and portal payments posted as customer payment journals |
| Gateway / processor choice | ✗ Adyen through Microsoft's connector, or a partner-built connector | ✓ 19+ gateways on your merchant account: Worldpay, Adyen, Cybersource, Fortis, PayTrace, Stripe, Braintree, Authorize.Net and more |
| Customer self-service portal for AR | ✗ Not included | ✓ Branded portal reading open customer transactions across legal entities |
| Click-to-pay links on invoices | ✗ Not included | ✓ Payment link on the Electronic reporting or SSRS invoice format you already use |
| Settlement against open transactions | ✗ Not applicable to AR invoices | ✓ Payment journal settled against the invoice or prepayment at posting |
| Multi-legal-entity routing | ✓ Per-entity configuration in Commerce | ✓ Routing by legal entity, merchant account, bank and offset account from one configuration |
| Level III line-item data | ✗ Not sent for AR | ✓ Sales order line detail attached to eligible commercial card transactions |
| ACH / eCheck | ✗ Card-focused | ✓ ACH, eCheck and card on one portal, all posted as payment journals with the right method of payment |
If your business is Commerce-first and card payments happen at a register or a storefront, Microsoft's connector is the right tool for that traffic. Payment Hub is for the AR side: invoices, prepayments, statements and portals. Most enterprises on F&O end up running both, one for Commerce and one for AR, and the two do not compete.
See it running in your own F&O sandbox
A 30-minute walkthrough: a prepayment invoice paid by ACH, a customer payment journal posted and settled in real time, and a portal reading open transactions across two legal entities.
What changes when they do
So how does Payment Hub help? Payment Hub closes the loop on a few fronts. The customer pays from a link on the invoice, or from a portal that reads open transactions across the entities they buy from, or the shared service center takes the card in a compliant surface. Payment Hub creates the customer payment journal in the right legal entity, posts it, and settles it against the invoice or prepayment it pays. The AR analyst reviews a posted journal instead of building one.
What stays in Finance & Operations
F&O remains the system of record. Customers, sales orders, free text and sales invoices, prepayment invoices, customer payment journals, settlements and the general ledger all stay in F&O. Payment Hub reads what it needs through data entities and writes payment journals in exactly the shape your AR team would create by hand, so every report, worklist and aging looks the same.
On the AR side Commerce doesn't cover
Finance & Operations runs enterprises with several legal entities and, often, a shared service center for AR. Microsoft's own card processing lives in Commerce, through the Payment Connector for Adyen, for the register and the storefront. Integrating Payment Hub with F&O keeps that for Commerce traffic and adds the invoice side:
Questions
Does Clarity Payment Hub integrate with Dynamics 365 Finance & Operations?
Yes. Payment Hub integrates with Finance & Operations through the standard OData data entities, authenticated with an Entra ID app registration. Invoice payments, prepayments, portal payments and refunds are created as customer payment journals in the right legal entity, posted, and settled against the transaction they pay.
How is this different from the Dynamics 365 Payment Connector for Adyen?
Microsoft's connector, and partner-built connectors like it, serve Dynamics 365 Commerce: point of sale and the Commerce storefront. They do not take payment on an AR invoice or post a customer payment journal. Payment Hub is built for the AR side, and most enterprises that run Commerce keep the connector for that traffic and add Payment Hub for invoices, prepayments and the portal.
Does the integration require X++ or a custom model?
No. It uses only the standard data entities Microsoft ships and maintains. Nothing is deployed to your environment, so One Version updates do not require the integration to be regression-tested, and your ISV solutions and dual-write maps are not affected.
How does Payment Hub settle payments in F&O?
Each payment becomes a customer payment journal line in the legal entity that issued the invoice, with the method of payment, bank account and offset your AR team configures. Payment Hub posts the journal and settles it against the invoice or prepayment invoice it pays. Unapplied payments post with the customer set so they can be settled from the open transactions form.
What is the implementation timeline for F&O?
Forty-eight hours from app registration is the standard go-live for the core integration: connection, legal entity mapping, payment link on your invoice format, testing in a sandbox and production cutover. Portal branding, gateway migration and shared-service enrollment are added on top without delaying the core.
Related resources
Enterprise payment automation on Dynamics 365 Finance & Operations.
Live in 48 hours. Your F&O environment, ISV solutions, dual-write maps and Electronic reporting formats stay intact.
Book a Live Demo