Industries
Integration
Supported
Use Cases
Timeline
Why SAP Business One customers add Payment Hub, and what changes when they do
Business One is a complete ERP for a company of 10 to 500 people, and its financial core is stronger than most SMB systems. What it does not include is a way to take a card or bank payment and land it as an incoming payment without someone keying it.
The typical SAP B1 shop we meet has a good process on paper and a manual step in the middle. Invoices go out from B1 with the standard layout. Customers pay by check, by ACH they set up on their own, or by calling with a card number that someone types into a virtual terminal. The processor's report arrives and the bookkeeper creates incoming payments in B1 by hand, matching amounts to invoices. When a deposit is required, the down payment invoice and the payment get handled as two separate events that may or may not line up.
Payment Hub closes that gap. The customer pays from a link on the invoice or in a portal that reads open items from B1, and the result posts back through the Service Layer as an incoming payment applied to the invoice, or to the down payment invoice, in the right company database. The bookkeeper reviews instead of keys.
What makes this worth doing at SMB scale is less the transaction count and more the people count. A Business One customer usually has one or two people in finance. Every hour of re-keying is an hour of a person who also closes the books, runs payroll and answers customer questions. Taking the manual step out is how a small finance team keeps up with a growing business.
What stays in SAP Business One
B1 remains the system of record. Business Partners, sales documents, A/R invoices, down payment invoices, incoming payments and the general ledger all stay in your company database, on HANA or SQL. Payment Hub reads what it needs through the Service Layer and writes incoming payments in the same shape your finance team would create by hand.
Your existing SAP B1 setup does not change. Payment terms, document numbering, layouts, the chart of accounts and any add-ons you run stay exactly as configured. Payment Hub adds a payment link to the invoice layout and a portal beside B1, not inside it.
The SAP B1 customer base, all served by Payment Hub
SAP positions Business One across a handful of small and mid-sized industries with different selling motions. Payment Hub covers all of them, and which features matter most shifts with the business.
Distribution
Products
Manufacturing
Services
Ecommerce
& Medical
Wholesale distributors and consumer products companies get the most from consolidated invoice payment and the portal, because their customers carry many open invoices. Light manufacturers use down payment invoices on made-to-order work and want the deposit and the balance to reconcile automatically. Professional services firms lean on recurring payments and statement autopay. Retail and ecommerce companies on B1 usually already have a storefront gateway and use Payment Hub to bring invoice and phone payments onto the same reconciliation.
A single B1 installation often crosses two of these, which is why the full feature set is installed and you enable what fits.
Payment Hub vs SAP B1 payment options, honest side-by-side
SAP Business One does not ship with card processing. Partners fill the gap with add-ons that register inside the company database and connect to one processor. Payment Hub takes a different route, and the differences are practical rather than subtle.
| Capability | Typical SAP B1 add-on | Payment Hub on SAP B1 |
|---|---|---|
| Gateway / processor choice | ✗ Usually one processor per add-on, chosen by the add-on vendor | ✓ 19+ gateways on your merchant account: Worldpay, Adyen, Cybersource, Fortis, PayTrace, Stripe, Braintree, Authorize.Net and more |
| Customer self-service portal | ✗ Rarely included, or sold as a separate product | ✓ Branded portal reading live A/R invoices and down payment invoices from B1 |
| Click-to-pay links on invoices | ✗ Depends on the add-on | ✓ Payment link on the Crystal Reports or PLD invoice layout you already use |
| Down payment invoice handling | ✗ Often manual: pay, then create the incoming payment against the down payment invoice | ✓ Deposit posts as an incoming payment against the down payment invoice automatically |
| Multi-company | ✗ One add-on install and license per company database | ✓ One configuration mapping each company to its merchant account, bank and GL |
| Upgrade impact | ✗ Add-on must be re-registered and re-tested on each B1 patch level | ✓ Nothing installed in the company database, so B1 upgrades do not affect the integration |
| Level III line-item data | ✗ Uncommon | ✓ Line detail from the sales document attached to eligible commercial card transactions |
| ACH / eCheck | ✓ Some add-ons support it | ✓ ACH, eCheck and card on one portal, all posting as incoming payments |
An add-on is a reasonable choice for a single-company B1 customer with low card volume and a partner who already supports it. The case for Payment Hub gets stronger with each additional company database, with any real deposit or down payment workflow, and the moment a customer asks for a portal. Those are the three points where the add-on approach starts to cost more than it saves.
The Missing LinkBetween Paymentsand Your ERP
Clarity Payment Hub closes that gap, connecting your orders, invoices, and payment channels into one flow.
Speak to a Platform ArchitectHow Clarity Connect integrates Payment Hub with SAP Business One
The integration runs on the SAP B1 Service Layer, the REST and OData interface SAP ships with Business One for HANA and Business One for SQL. Eight capabilities make up the integration, and none of them install anything in your company database.
Service Layer integration
Payment Hub reads and writes through Service Layer entities: BusinessPartners, Orders, Deliveries, Invoices, DownPayments and IncomingPayments. Sessions authenticate with a dedicated B1 user against a named company database. Every call is logged.
Real-time incoming payments
A payment taken in the portal, on an invoice link or by phone posts to B1 as an incoming payment applied to the A/R invoice or down payment invoice it settles, with the payment means, bank account and GL account set the way your finance team would set them.
Document-flow-aware order-to-cash
Deposits post against down payment invoices. Balances post against the final A/R invoice net of the down payment. Partial deliveries invoice and collect separately. The integration follows the B1 document chain instead of fighting it.
Level III auto-enrichment
Line detail from the sales document, including item code, quantity, unit price, tax and ship-to, is attached to eligible commercial card transactions so they settle at Level III interchange. Useful for distributors and manufacturers selling to businesses.
Multi-company and multi-currency routing
Each company database is mapped to its own merchant account, bank and GL. Settlement currency follows the document currency, so a Canadian subsidiary invoicing in CAD settles in CAD without a separate setup.
Tokenized method vault
Cards and bank accounts are tokenized at the gateway and stored against the Business Partner, so repeat payments and portal use never expose card data to B1, your network or your staff.
Recurring and scheduled payments
Services firms and subscription-style customers run on the scheduler: fixed monthly draws, statement autopay, or installment plans, with dunning on failed attempts and every run posting as a normal incoming payment.
Compatible with add-ons, B1if and partner customizations
The integration sits beside whatever you already run in B1. It does not conflict with registered add-ons, B1if scenarios or user-defined objects, because it does not live inside the company database.
The integration workflow, down payment invoice to closed Business Partner balance
A concrete walk-through. A specialty food and beverage wholesaler on SAP Business One for HANA, with a US company and a Canadian company, takes a $28,600 order from a regional grocery chain that requires a 25 percent deposit on first orders. Payment Hub handles the deposit, the balance and the cash application through the Service Layer.
Sales enters the order in SAP B1
The account manager creates sales order 21044 in the US company database for Harbor Grocers: $28,600 across 14 lines with a two-week lead time. Customer terms require a 25 percent deposit on a first order. B1 creates the A/R down payment invoice for $7,150 from the order.
B1 Sales OrderDown Payment InvoiceDeposit paid from the invoice link
The down payment invoice goes out on the standard layout with a Payment Hub link. Harbor's AP clerk pays it on a corporate card. Payment Hub tokenizes the card, attaches Level III line detail from the order, and authorizes and captures on the US company merchant account.
Click-to-PayLevel IIITokenizedB1 records the deposit against the down payment invoice
Payment Hub writes an incoming payment through the Service Layer, applied to down payment invoice 90201, with the bank and GL account set for the US company. Finance sees it in B1 immediately. The processor report is never touched.
Service LayerIncoming PaymentDelivery and A/R invoice
Two weeks later the warehouse creates the delivery from the order and B1 issues A/R invoice 90218 for the full $28,600 with the $7,150 down payment applied, leaving $21,450 open. The invoice layout carries the payment link again, showing the net balance due.
DeliveryA/R Invoice 90218Customer pays the balance in the portal
Harbor's AP clerk logs into the branded portal, which reads open invoices from B1 through the Service Layer. She sees invoice 90218 with the deposit already applied and pays $21,450 on the saved card. The portal marks it paid immediately.
Customer PortalSaved MethodIncoming payment applies and the BP balance closes
Payment Hub posts the incoming payment against invoice 90218. The Business Partner balance for Harbor Grocers goes to zero. No one in finance created or matched anything.
Auto-AppliedBP Balance 0Same customer, Canadian company
A month later Harbor's Canadian buying group orders through the Canadian company database in CAD. The same portal login shows both companies' invoices. Payment routes to the Canadian merchant account and settles in CAD, with the incoming payment posting in the Canadian database.
Multi-CompanyCAD SettlementMonth-end in both companies
Every payment exists in B1 as an incoming payment against the right document in the right company. Bank reconciliation in both databases matches the processor statements. The finance lead reviews exceptions instead of building the reconciliation.
Month-EndReconciledThe detail worth noticing is the down payment. In most SMB setups the deposit and the balance are two disconnected payments that finance has to stitch together. Here they are two incoming payments against two related documents, which is exactly how SAP designed Business One to work.
Payment Hub use cases on SAP Business One
All 11 Payment Hub use cases run on SAP B1. The ones Business One customers deploy first are highlighted here, and each links to the full use-case page.
A payment link on the A/R invoice layout, with the incoming payment applied on payment.
Document-flow-awareOrder-to-CashDeposits against down payment invoices, balances against the final invoice, partial deliveries handled.
Customer-facingSelf-Service Payment PortalA branded portal reading live invoices from B1, with saved methods and pay-many.
Open ARConsolidated Invoice PaymentCustomers pay many invoices at once or pay on account, applied by age in B1.
FinanceERP Payment ReconciliationEvery payment lands as an incoming payment with bank and GL set, so bank rec matches the processor.
ServicesSubscription BillingScheduled draws and statement autopay for services firms, posting as normal incoming payments.
Technical details, for SAP B1 admins and partners
The engineering reality of the integration, for IT teams, SAP B1 administrators, developers and SAP partners evaluating Payment Hub for a Business One customer.
- API layer. SAP Business One Service Layer (REST / OData), available on Business One for SAP HANA and on Business One for SQL from version 9.3 onward. Entities used: BusinessPartners, Orders, Deliveries, Invoices, DownPayments, IncomingPayments and Items. Customers on older SQL releases without the Service Layer are handled through the DI API on a case basis.
- Authentication. A dedicated B1 user with a license type and authorizations limited to the objects above, logging into a named company database. Credentials are stored encrypted on Payment Hub's side and rotated on your schedule.
- Data direction. Reads: Business Partners, contacts, open sales documents, open A/R invoices and down payment invoices, company and currency settings. Writes: incoming payments and payment-method tokens stored as Business Partner properties. Payment Hub never writes items, prices, sales document lines or journal entries directly.
- Card data. No cardholder data reaches SAP B1, your network or Payment Hub's application tier. Entry happens on a PCI DSS Level 1 hosted surface at the gateway, and B1 receives a token and a reference. PCI scope goes down.
- Multi-company routing. A configuration map from company database to merchant account, bank account, GL account and settlement currency. Adding a company is a configuration change.
- Add-ons and customizations. Nothing is registered in your company database: no add-on, no user-defined tables, no stored procedures, no B1if scenarios. Existing add-ons and customizations run unchanged, and B1 patch upgrades do not affect the integration.
- Deployment. Works with on-premise B1, partner-hosted B1 and SAP Business One Cloud. The Payment Hub service reaches the Service Layer over TLS through your firewall or the hosting partner's endpoint.
- Timeline. Standard go-live is 48 hours from Service Layer access: connect, map companies, add the payment link to your invoice layout, test against your B1 test company, cut over. Portal branding, gateway migration and scheduled payments are added when you want them.
- Support. Clarity supports the integration and the payment side end to end. Your SAP partner keeps supporting Business One exactly as they do today.
SAP Business One + Payment Hub FAQ
The questions SAP B1 administrators, finance leads, IT teams and SAP partners ask before adding Payment Hub to a Business One deployment.
Does Clarity Payment Hub integrate with SAP Business One?
Yes. Payment Hub integrates with SAP Business One through the Service Layer, the REST and OData interface SAP ships with B1 for HANA and B1 for SQL. Invoice payments, deposits against down payment invoices, portal payments and refunds all post to B1 in real time as incoming payments.
Business Partners, sales documents, invoices and the general ledger stay in your company database as the single source of truth.
Does SAP Business One have built-in credit card processing?
No. Business One does not ship with card processing. Partners cover the gap with add-ons tied to a single processor. Payment Hub provides processing, a customer portal, invoice links and Level III enrichment on 19+ gateways, without installing anything in the company database.
Which SAP B1 versions and platforms are supported?
Business One for SAP HANA and Business One for SQL from 9.3 onward, which is where the Service Layer is available on both platforms. Older SQL releases are assessed for a DI API path before quoting. On-premise, partner-hosted and SAP Business One Cloud deployments all work.
How does Payment Hub handle down payment invoices?
A deposit paid through Payment Hub posts as an incoming payment applied to the A/R down payment invoice. When the final A/R invoice is created with the down payment drawn, the customer sees the net balance on the invoice link and in the portal, and that payment applies to the final invoice. The two documents stay related the way SAP designed them to.
We run several company databases. Is that a problem?
No, it is one of the main reasons B1 customers choose Payment Hub over an add-on. Each company is mapped once to its merchant account, bank, GL account and settlement currency. Customers who buy from more than one of your companies see all their invoices in one portal login.
Do we have to install anything inside SAP B1?
No. There is no add-on to register, no user-defined fields or tables, no stored procedures and no B1if scenario. The integration talks to B1 only through the Service Layer. That is also why B1 patch upgrades do not require re-testing the integration.
Can we keep our current gateway and merchant account?
Almost always. Payment Hub connects to Worldpay, Adyen, Cybersource, Fortis, PayTrace, Stripe, Braintree, Authorize.Net and more. If your processor is on the list you keep your rates. If you change processors later, the integration stays the same.
Does the customer portal show what our finance team sees in B1?
Yes. The portal reads open A/R invoices, down payment invoices, credits and applied payments directly from B1 through the Service Layer. When a customer pays, the incoming payment posts back and the portal reflects it at once.
Does Level III interchange optimization apply to a B1 customer?
It applies when a meaningful share of your card volume comes from commercial or purchasing cards, which is common for distributors and manufacturers on B1 that sell to other businesses. Payment Hub attaches line detail from the sales document to eligible transactions so they qualify. Savings are typically 0.5 to 1.0 percent on that volume.
What about ACH and bank payments?
ACH and eCheck run on the same portal and the same invoice links as cards, and post to B1 as incoming payments with the bank payment means. Many B1 customers use ACH for large invoices and cards for smaller ones, and the customer chooses at payment time.
What is the implementation timeline for SAP Business One?
Forty-eight hours from Service Layer access is the standard go-live for the core integration: connection, company mapping, invoice link on your layout, testing in your B1 test company and cutover. Portal branding, gateway migration and recurring setup are added on top without delaying the core.
Who supports the integration, Clarity or our SAP partner?
Clarity supports the integration and the payment side. Your SAP partner keeps supporting Business One as they do today. We work with partners during rollout so questions land in the right place.