Editions
Industries
+ Sage 100 SDK
Supported
Timeline
Why Sage 100 customers add Payment Hub, and what changes when they do
Sage 100 has one of the longest heritages of any ERP on this site. It started as Sage ERP MAS 90 in the late 1980s, became MAS 200 with networked deployment, then MAS 200 SQL with the Microsoft SQL Server option, and rebranded as Sage 100 ERP in 2012. Today's Sage 100, positioned in Sage's recent brochure as "not your typical ERP, a total business management solution", preserves the deep functional reach Sage built up over three decades while modernizing the user experience and adding cloud-deployment options. Four editions: Standard (the on-premise ProvideX file system), Advanced (multi-site WAN with thin-client architecture), Premium (Microsoft SQL Server backbone for scalability), and Online via Sage Partner Cloud (Microsoft Azure, AWS, or Sage-accredited cloud platforms ADSS Global, Cloud at Work, CompuData, RKL Solutions, SWK Technologies). Sage's brochure names six target verticals: Manufacturing, Wholesale and Distribution, Retail, Business Services, Financial Services, and beyond.
Sage 100's distinctive technical DNA is its open-architecture integration philosophy. The brochure puts it directly: "'Open architecture' has been the catch phrase for business application software and databases for years. Businesses have moved beyond the obligation to perform software gymnastics to obtain integrated reporting." Sage 100 ships with multiple integration paths built in: the Business Object Interface (BOI) for COM-based programmatic access, Visual Integrator for ETL-style imports / exports, ODBC connectivity for direct database access (especially powerful on Premium with the SQL Server backbone), and the Sage 100 SDK for tighter scenarios. This open-architecture commitment is what makes Payment Hub integration so clean.
The gap, common across long-running Sage 100 installations, is the certified-gateway lock-in on the payment-acceptance side. Sage 100 ships with the Credit Card Processing module, typically configured to integrate with one of Sage's certified gateways (historically Sage Payment Solutions / Paya, now Sage Pay or third-party gateways). Most Sage 100 customers configured this years ago, often back in their MAS 90 / 200 days, and never changed it. The result: single-gateway, single-MID across all Companies / Warehouses, no Level III interchange enrichment, no surcharging, limited dunning, and a customer portal payment surface limited to what Sage 100 + Sage CRM natively provide. Payment Hub fills this gap through Sage 100's published integration paths, gateway- and processor-agnostic, 19+ gateway choices behind one consistent integration. The integration is non-invasive (no Custom Office / VBScript / panel modifications required). It respects your decades of customizations from the MAS 90 / 200 era. It works across all 4 editions and all 6 target verticals.
The four Sage 100 editions, all served by Payment Hub
Sage 100 ships in four editions covering the full deployment spectrum from on-premise legacy to cloud-hosted modern. Payment Hub integrates the same way across all four, same routing matrix, same gateway connections, same customer portal. What changes is the deployment process and the database backbone.
Sage 100 Standard
The on-premise edition with Sage's proprietary ProvideX file system. The MAS 90 lineage. Payment Hub integrates via BOI for real-time and Visual Integrator for batch. Standard outbound HTTPS connectivity to gateways.
Sage 100 Advanced
Multi-site / WAN deployment optimized for TCP/IP with thin-client architecture. The MAS 200 lineage. Same BOI / Visual Integrator / ODBC integration as Standard. Works across LAN / WAN environments without additional remote-access software.
Sage 100 Premium
Microsoft SQL Server backbone for scalability, reporting, and integration. The MAS 200 SQL lineage. Same BOI / Visual Integrator integration plus optional direct SQL Server-side queries for higher-volume scenarios. Best fit for $25M+ Sage 100 customers.
Sage 100 Online · Sage Partner Cloud
Cloud-deployed via Microsoft Azure, AWS, or Sage-accredited cloud platforms (ADSS Global, Cloud at Work, CompuData, RKL Solutions, SWK Technologies). Same BOI / Visual Integrator integration. Cloud-side outbound HTTPS connectivity. Single-day data migration with no retraining (per Sage Partner Cloud Beta Program partners).
The integration code is the same across all four editions. The deployment process differs: Standard / Advanced are on-premise installs at the customer. Premium adds the SQL Server licensing and DBA setup. Sage Partner Cloud is hosted by the certified MSP and Payment Hub connects via standard outbound HTTPS. For customers on a Standard / Advanced → Premium upgrade path (often part of a SQL Server modernization), or on a Premium → Sage Partner Cloud move (part of a cloud transformation), Payment Hub's configuration ports forward, same gateway connections, routing rules, customer portal customizations, L3 mappings carry across the upgrade or migration.
Six target industries, all served by Payment Hub
Sage 100's brochure names six target verticals where the platform has deep functional reach. Each has different payment characteristics. Payment Hub adapts to each.
Each industry has a different typical Payment Hub fit. Manufacturing customers running Sage 100's manufacturing modules (Bill of Materials, Production Management, Operations Management, Work Order, MRP, Kitting, Lot and Serial Tracking, Capable to Promise) get deposits at sale-order entry, milestone billing on production-status events, partial-shipment captures, BOM-driven deposit logic for kit-assembled products, multi-Warehouse routing. Wholesale and Distribution customers running Inventory Management, Sales Order, Purchase Order, Returns get multi-Warehouse MID routing, customer portal multi-invoice batch pay, ACH automation for net-30 buyers, and Avalara-driven sales tax handling. Retail gets card-present P2PE-validated terminals integrated through Sage 100 Sales Receipts, multi-Location (store) MID routing. Business Services gets project billing and T&E pass-through. Financial Services gets recurring billing and compliance overlay (KYC / AML / OFAC where applicable). And many more: Sage 100 has long served a broader set of vertical-adjacent industries (construction, professional services, nonprofits, hospitality) where Payment Hub adapts to the specific payment cadence.
Sage 100 modules, all touched by Payment Hub
Sage 100 organizes its functional reach across five major module categories. Payment Hub integrates across all five, primary touch points are Financials and Distribution &, Manufacturing. Supporting touch points across the rest.
Financials
Distribution and Manufacturing
Payroll and Time Track
Insights and Reporting
Customization &, Integration
CRM &, eCommerce
The integration touches every category. Financials is the primary surface, Customer, AR Invoice, AR Receipt, Sales Order all flow through Payment Hub via BOI. Distribution and Manufacturing drives the manufacturing-specific patterns: BOM-driven deposits, MRP-aware milestone billing, partial-shipment captures from Sales Order Shipment events, multi-Warehouse routing. Payroll and Time Track coexists, payment events on the AR side don't conflict with payroll on the AP side. Insights and Reporting consumes Payment Hub events as first-class data points, Crystal Reports renders payment-aware reports. Sage Intelligence Reporting picks them up in Excel. Business Insights Explorer drills into them. Sage Alerts and Workflow can trigger on payment events. Customization &, Integration tools are the path Payment Hub uses (BOI, Visual Integrator, ODBC, SDK). CRM &, eCommerce: Sage CRM gets the embedded portal payment surface. EBusiness Manager applets get gateway-agnostic checkout for Sage 100-running B2C / B2B websites.
Payment Hub vs Sage 100's native Credit Card Processing, honest side-by-side
Sage 100's Credit Card Processing module ships with the platform and integrates with one of Sage's certified gateways. It works for simple invoice-payment scenarios. Payment Hub is the gateway-agnostic alternative for Sage 100 customers who need more, multi-gateway flexibility, Level III enrichment, customer portal modernization, multi-Company / multi-Warehouse routing, and the manufacturing / distribution patterns the native module doesn't ship.
| Capability | Native Sage 100 Credit Card Processing | Payment Hub on Sage 100 |
|---|---|---|
| Gateway / processor choice | ● Limited to Sage-certified gateways. Switching = re-do CC Processing config | ● 19+ gateways (Worldpay, Adyen, Fortis, PayTrace, Stripe, Authorize.Net, NMI, USAePay, plus Sage-certified gateways if you keep them) |
| Level III interchange enrichment | ● Not auto-enriched, requires custom config or third-party | ● Auto-enriched from Sage 100 Sales Order Detail / AR Invoice Detail / Production Order line records, 20+ fields per transaction |
| Customer portal payment surface | ● Limited via Sage CRM / eBusiness Manager. Basic payment via certified gateway | ● Modernized payment surface, multi-invoice batch pay, stored credentials, ACH, multi-currency, L3 |
| Multi-Company / multi-Warehouse routing | ● Single-MID typical, multi-Company support varies | ● Per-Company / per-Warehouse routing, different MIDs, gateways, currencies, surcharging policies |
| Multi-invoice consolidation | ● Per-invoice flow | ● Batch pay across multiple invoices, single auth, single capture, line-level cash app |
| Surcharging / convenience fees | ● Not native | ● Compliant surcharging engine (per-state, per-card-brand, per-merchant rules) |
| Real-time line-level cash application | ● Auto-apply on captures, line-level varies | ● Real-time line-level cash app via AR Receipt + line-level distribution via BOI |
| Manufacturing-edition patterns (BOM / MRP-driven) | ● Not native to CC Processing | ● Triggered by Sage 100 Production Management events, BOM-aware deposits, MRP-driven milestone billing |
| Sage CRM portal embedding | ● Sage CRM portal renders. Payment via certified gateway | ● Embedded payment surface inside Sage CRM portal, gateway-agnostic flexibility |
| Dunning automation | ● Sage Alerts &, Workflow can drive reminders, not gateway-aware retry | ● Full dunning ladder with auto-retry, gateway-aware, configurable per Company / Warehouse |
| Custom Office / VBScript / panel respect | ● Native, CC Processing fires Sage 100 events | ● Same, Payment Hub-driven postings via BOI fire your existing VBScript / Custom Office events |
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 the integration works, BOI + Visual Integrator + ODBC + SDK
Payment Hub plugs into Sage 100 through the platform's published integration paths. BOI for real-time programmatic access. Visual Integrator for ETL-style scheduled batch flows. ODBC for direct database queries (especially powerful on Premium with SQL Server). Sage 100 SDK for tighter scenarios. No core Sage 100 modifications. Eight features that come online when Sage 100 gets Payment Hub:
Business Object Interface (BOI)
COM-based programmatic access for real-time scenarios, token, charge, refund, void, AR Receipt creation, AR Invoice creation. Same path Sage 100's own components use. Authentication via Sage 100 user credentials or dedicated integration users.
Visual Integrator for batch flows
For batch scenarios, daily settlement reconciliation, daily ACH return processing, monthly L3 savings reports, customer portal usage exports, Payment Hub uses Visual Integrator's scheduled jobs. Coexists with existing Visual Integrator integrations.
ODBC for direct database queries
Sage 100's ODBC connectivity provides direct database access, particularly powerful on Sage 100 Premium with SQL Server. Payment Hub uses ODBC for high-volume read scenarios (daily settlement reconciliation, customer-portal data warehousing).
Level III auto-enrichment
Pulls 20+ required L3 fields from Sage 100 Sales Order Detail (SO_SalesOrderDetail), AR Invoice Detail (AR_InvoiceHistoryDetail), and Production Order line records. Avalara-driven tax data flows in cleanly. Mid-market Sage 100 customers commonly recover $15K–$200K+/yr.
Sage CRM customer portal embedding
Embedded payment surface inside Sage CRM's customer portal. Multi-invoice batch pay, stored credentials, ACH / direct debit, multi-currency, surcharging disclosure, L3 enrichment. Sage CRM continues to authenticate and render normally.
Multi-Company / multi-Warehouse routing
Each Sage 100 Company or Warehouse gets its own gateway, MID, bank account, currency, tax setup, surcharging policy. Routing decisions happen on Company / Warehouse field. Scales to 25+ Companies across multi-entity Sage 100 deployments.
Manufacturing-module integration
Subscribes to Sage 100 Production Management / Work Order / MRP events. BOM-driven deposit calculations for kit-assembled products. Milestone billing on production-status events. Partial-shipment captures from Sales Order Shipment.
Crystal Reports / Business Insights publishing
Payment events publish into Sage 100 as first-class data points. Crystal Reports renders payment-aware reports. Sage Intelligence Reporting picks them up in Excel. Business Insights Explorer drills into them, Sage Alerts &. Workflow can trigger on payment events.
The integration workflow, a multi-warehouse industrial supply distributor on Sage 100, end to end
Walk through one realistic Sage 100 scenario. Westbridge Industrial Supply, a $48M industrial supply distributor running Sage 100 Premium (SQL Server backbone) across 6 warehouses in the Midwest (Chicago HQ, Indianapolis, Detroit, Cleveland, Milwaukee, St. Louis). 145 employees. Long-time Sage customer, originally on MAS 200 since 2008, upgraded to Sage 100 Premium in 2014. Heavy use of Inventory Management, Sales Order, Bill of Materials (for kit-assembled industrial products), Purchase Order, Returns, Avalara sales tax. Visual Integrator runs nightly EDI imports from major B2B customers. Sage CRM for the sales team. Currently on a single Sage-certified gateway through one MID across all 6 warehouses, no L3 enrichment, no multi-Warehouse routing, no surcharging. Eight steps showing how Payment Hub modernizes the payment layer.
B2B order, $58K from a long-time contractor customer at the Chicago warehouse
Westbridge's Chicago CSR takes a phone-and-portal order from Riverside Mechanical Contractors (12-year Westbridge customer): 142 line items totaling $58,400. Mix of stocked items (110 lines) and 32 lines that are kit-assembled per Sage 100 BOM. Sage 100 Premium creates Sales Order in Company=01-WIS (Westbridge Industrial Supply main entity), Warehouse=CHI-01. Custom field "Project Name" populated for the contractor's audit trail. Avalara calculates IL sales tax automatically.
SO-2026-08412 · $58,400Company=01-WIS · Warehouse=CHI-01142 line items · 32 BOM kitsBOM-driven deposit, Sage 100 Production Management triggers $14,600 deposit (25% on kit-assembled portion)
The 32 BOM line items require kit-assembly (the contractor's project specs include some custom-configured packages). Westbridge's policy: 25% deposit on the kit-assembled portion of any order >$10K. Sage 100 BOM module calculates the kit portion at $58,400 × portion × 25% = $14,600 deposit due. Payment Hub catches the BOM-driven deposit-required signal via BOI event subscription. Sends a portal payment link to Riverside's AP team. AP pays via Visa Purchasing card (Riverside's standard procurement card for Westbridge orders) on the embedded Sage CRM customer portal.
BOM-driven deposit$14,600 · 25% on kitsVisa PurchasingL3 enrichment + routing, 142 line items packaged. Worldpay merchant account for Company=01-WIS, Warehouse=CHI-01
L3 enrichment auto-fires from the 142 line items in Sage 100 Sales Order Detail. Avalara tax data flows in automatically. All 22 L3 fields packaged. Routing matrix: Company=01-WIS, Warehouse=CHI-01 → Worldpay merchant account (Westbridge replaced the legacy Sage-certified gateway with Worldpay across all 6 warehouses), USD, GL=10110-Cash-USD-CHI, surcharge=disabled (B2B contractor relationship). Capture posts at large-ticket interchange. Estimated L3 savings on this single deposit transaction: ~$120.
Worldpay · USD · GL-CHIL3 from 142 line itemsL3 saved $120AR Receipt creation via BOI, line-level cash application against the deposit invoice
Capture confirms at Worldpay. Payment Hub creates AR Receipt in Sage 100 via BOI: $14,600 against deposit invoice DEP-2026-08412, Worldpay reference attached, Company=01-WIS / Warehouse=CHI-01 set. Custom Office field "Project Name" carries forward to the cash receipt. Westbridge's existing VBScript event handler on AR_ReceiptHeader (custom audit-trail logic the company has used since MAS 200 days) fires as designed. Sage 100 AR aging refreshes. Riverside's outstanding balance updates.
AR Receipt via BOIVBScript firesCustom Office preservedProduction / kit assembly, 32 BOM kits assembled at Chicago warehouse over 5 business days
Westbridge's warehouse team assembles the 32 kit-assembled products. Sage 100 Production Management tracks each kit through its assembly steps. As each kit completes, Production Management emits a status event. After all 32 kits complete (Day 5), Sage 100 Sales Order Shipment triggers. Mobility for Barcode scanners pick the goods. Truck departs.
Production Management5 business daysMobility for BarcodeFinal invoice, Sage 100 generates $43,800 final invoice. Riverside batch-pays multiple open invoices
Sale ships. Sage 100 generates final invoice INV-2026-08412 for the remaining $43,800 ($58,400 − $14,600 deposit). Plus, Riverside has two other smaller open invoices ($8,400 + $3,200 = $11,600 from prior orders). Riverside's AP team logs into the Sage CRM customer portal, sees all 3 invoices, batch-pays $55,400 in a single transaction via stored Visa Purchasing card. L3 enrichment fires on the consolidated 200+ line items across all 3 invoices. Capture posts, Payment Hub creates 3 AR Receipts via BOI. Line-level cash application across all 3 invoices.
3 invoices · $55,400 batch200+ line itemsL3 saved $450Multi-warehouse expansion, Indianapolis + Detroit + Cleveland warehouses live, Milwaukee + St. Louis last
Over 6 months, Westbridge rolls Payment Hub out to all 6 warehouses. Each warehouse routes to its own Worldpay sub-MID (per-Warehouse settlement to local Westbridge bank accounts, vs. previously consolidated through one Intuit-style centralized MID). Cumulative L3 savings across all 6 warehouses in Year 1: $87K against Westbridge's $28M annual B2B card volume. Customer portal usage doubles as the AP teams of Westbridge's 1,200+ active B2B customers prefer the modernized batch-pay experience.
6 warehouses liveL3 saved $87K (Year 1)Per-warehouse settlementCrystal Reports + Sage Intelligence, quarterly L3 savings + multi-warehouse settlement reports
Westbridge's controller pulls a custom Crystal Report for the quarterly Board review: "L3 Savings by Warehouse, Q1 2026", Chicago $19K, Indianapolis $14K, Detroit $11K, Cleveland $9K, Milwaukee $7K, St. Louis $5K. Total Q1: $65K. Sage Intelligence Reporting (Excel) consolidates the data with operational KPIs (sales volume per warehouse, customer concentration). Sage Alerts &, Workflow now fires automated payment-failure alerts to the warehouse manager when retry sequences exhaust. The plant-floor-to-top-floor visibility extends to payment metrics with the same Sage 100 reporting tools Westbridge has used for decades.
Crystal ReportsSage Intelligence ReportingSage Alerts triggeredUse cases that light up on Sage 100
All eleven Payment Hub use cases run on Sage 100. These are the patterns where the Sage 100 integration shines, and where mid-market Sage 100 customers across the 6 target verticals get the highest use.
Real-time line-level cash application via AR Receipt + line-level distribution through BOI. AR aging refreshes immediately. Manual reconciliation drops to near zero across all warehouses.
Interchange Level III cost reductionAuto-enrichment from Sage 100 Sales Order Detail / AR Invoice Detail / Production Order line records. Avalara-driven tax data. Sage 100 customers recover $15K–$200K+/yr.
Multi-Warehouse Multi-Company / multi-Warehouse paymentsPer-Company / per-Warehouse routing, different gateways, MIDs, currencies, surcharging policies. Maps directly to Sage 100's native multi-Company and multi-Warehouse structures.
Manufacturing O2C BOM-driven O2C automationEnd-to-end O2C through Sage 100 Sales Order → BOM → Production Management → Sales Order Shipment → AR Receipt. BOM-driven deposits, MRP-aware milestone billing, partial-shipment captures.
Customer Portal Sage CRM customer portal modernizationEmbedded payment surface inside Sage CRM's customer portal. Multi-invoice batch pay, stored credentials, ACH, multi-currency, L3 enrichment, surcharging.
ACH ACH / eCheck automationSame-day ACH, NACHA validation, returns handling. Best fit for B2B distribution net-30 buyers and recurring service contracts. Sage 100 customers in Wholesale and Distribution see the highest ACH use.
Recurring Service contracts &, recurring billingFor Sage 100 Business Services, Financial Services, and software subscription businesses. Stored credentials, auto-retry, dunning, mid-cycle changes, all coexisting with Sage 100's memorized recurring transactions.
Collections Dunning &, collections automationAugments Sage Alerts &. Workflow with gateway-aware retry logic. Configurable dunning ladder per Company / Warehouse. Email templates branded per region/language.
Cost Recovery Compliant surchargingPer-state, per-card-brand, per-merchant-class rules. Auto-disclosure on Sage CRM portal and hosted pages. Surcharge revenue offsets card cost. Not native to Sage 100 Credit Card Processing.
B2C / B2B eCommerce checkout via eBusiness ManagerFor Sage 100 customers running eBusiness Manager applets (.order, .inquiry, .store): hosted checkout, tokenization, 3DS2 / SCA in EU, Apple Pay / Google Pay. Replaces gateway-locked legacy checkout.
POS / Card Present Counter sales / parts counterFor Sage 100 Retail / Wholesale customers running parts-counter operations: P2PE-validated terminals integrated through Sage 100 Sales Receipts. Per-Warehouse MID routing.
If you're running Sage 100 (any edition, any of the 6 target verticals), Clarity will run a guided demo on your environment, your gateways, your Company / Warehouse routing, and your industry-specific patterns. Pilot one Company / Warehouse live in 48 hours.
Technical details, for the Sage 100 admins and developers
For Sage Business Partners, Sage 100 ProAdvisors, and Sage 100-running businesses' IT teams: the connection model, record surface, security posture, and customization compatibility.
Integration paths in detail
Business Object Interface (BOI): Sage 100's COM-based programmatic API. Primary path for real-time scenarios. Same path Sage 100's own components use. Visual Integrator: Sage 100's native ETL tool for scheduled batch flows. Best for daily settlement reconciliation, monthly L3 reports, customer portal usage exports. ODBC connectivity: direct database access, especially powerful on Sage 100 Premium with Microsoft SQL Server. Best for high-volume read scenarios. Sage 100 SDK: for tighter integration scenarios where BOI doesn't expose the right entry points. Authentication via Sage 100 user credentials or dedicated integration users.
Sage 100 records consumed and posted
- AR_Customer: read/write via BOI. Stored credentials linked back via Custom Office field.
- SO_SalesOrderHeader / SO_SalesOrderDetail: read for L3 enrichment and order-state events.
- AR_InvoiceHistoryHeader / AR_InvoiceHistoryDetail: read for invoice payment + L3 enrichment.
- AR_CashReceiptsHeader / AR_CashReceiptsDetail: written via BOI on every capture, line-level cash application.
- AR_OpenInvoice: read for AR aging and customer-portal display.
- BM_BillHeader / BM_BillDetail: read for BOM-driven deposit logic.
- WO_OperationDetail / WO_TransactionEntry: subscribed for production-status milestone events.
- SO_ShippingHistoryHeader: subscribed for partial-shipment captures.
- CI_Item: read for item-level pricing and L3 categorization.
- CI_Warehouse / SY_Company: read for routing rule lookup.
- CI_TaxDetail: read for tax breakdown (Avalara-driven).
Customization respect
- Custom Office (form / panel customization) preserved, custom panels render normally.
- Customizer (UI personalization) preserved.
- VBScript event handlers fire on Payment Hub-driven postings (when Payment Hub creates an AR Receipt or applies cash, your VBScript fires as designed).
- Custom panels and custom data dictionary fields visible to Payment Hub via BOI introspection.
- Existing Visual Integrator jobs coexist with Payment Hub's Visual Integrator scheduled flows.
- Sage CRM integrations preserved.
- Existing Sage Alerts &. Workflow rules fire normally. New rules can trigger on Payment Hub events.
Security and compliance
- Sage 100 user-credential authentication (Standard / Advanced / Premium). Cloud-side connectivity (Sage Partner Cloud).
- PCI DSS Level 1 service provider, with PCI scope minimized via tokenization at gateway.
- Card data never lands in Sage 100. Tokens stored in AR_Customer Custom Office field.
- P2PE-validated terminals available for card-present (Retail / parts-counter scenarios).
- SOC 2 Type II (Clarity).
- 3DS2 / SCA support natively across all gateways for European compliance (PSD2).
- For Sage Partner Cloud customers, the certified MSP's compliance posture (Microsoft Azure / AWS / SOC 2 / SOC 3 etc.) extends naturally.
Deployment scenarios
- Sage 100 Standard (on-premise ProvideX): BOI / Visual Integrator integration, outbound HTTPS only.
- Sage 100 Advanced (multi-site WAN): same integration, works across LAN / WAN.
- Sage 100 Premium (SQL Server): same integration plus optional direct SQL queries for high-volume scenarios.
- Sage 100 Online / Sage Partner Cloud: cloud-deployed, outbound HTTPS to gateways and Payment Hub services.
- Multi-Company / multi-Warehouse: common across all editions. Payment Hub's routing matrix scales.
- MAS 90 / 200 → Sage 100 upgrade in progress: Payment Hub deploys on current version. Configuration ports forward through the upgrade.
Sage 100 vs Sage 300 vs Sage Intacct vs Sage X3
Sage 100 sits in Sage's North American SMB ERP tier, the natural step up from QuickBooks, the natural step down from Sage Intacct (cloud-native financial management) or the move-up to Sage 300 (multi-currency / multi-company small enterprise) or Sage X3 (mid-market global). For Sage 100 customers eventually moving up the Sage stack, Payment Hub's configuration ports forward, same gateway connections, routing rules, surcharging, dunning, customer portal, L3 mappings carry across the Sage product transition. The integration surface changes (BOI / Visual Integrator on Sage 100 → Sage 300 web services / Sage Intacct REST API / Sage X3 SOAP API on the destination), but the application configuration carries forward without re-implementation.
Frequently asked questions about Sage 100 + Payment Hub
Answers to the most common questions from Sage 100 customers, Sage Business Partners, and IT teams planning payment modernization for their Sage 100 deployments.
Does Clarity Payment Hub integrate with Sage 100?
Yes. Clarity Payment Hub integrates with Sage 100 (formerly Sage ERP MAS 90 / 200 / 200 SQL) through Sage 100's published integration paths: the Business Object Interface (BOI) for COM-based programmatic access, Visual Integrator for ETL-style scheduled imports / exports, ODBC connectivity for direct database access (especially powerful on Sage 100 Premium with Microsoft SQL Server backbone), and the Sage 100 SDK for tighter integration scenarios.
Authentication via Sage 100's standard user authentication or dedicated integration users. Every transaction posts to Sage 100 in real time. Customer records, Sales Orders, Invoices, AR Receipts (Cash Receipts), and multi-Company / multi-Warehouse data stay as the single source of truth in Sage 100.
Which Sage 100 editions does Payment Hub support?
All four. Sage 100 Standard (the on-premise edition with ProvideX file system), Payment Hub integrates via BOI, Visual Integrator, and ODBC. Sage 100 Advanced (multi-site / WAN deployment with thin-client architecture), same integration. Works across the LAN / WAN setup. Sage 100 Premium (Microsoft SQL Server backbone for scalability), same integration plus the option of direct SQL Server-side queries for higher-volume scenarios.
Sage 100 Online / Sage Partner Cloud (deployed via Microsoft Azure, AWS, or Sage-accredited cloud platforms ADSS Global, Cloud at Work, CompuData, RKL Solutions, SWK Technologies), same integration model, with cloud-side outbound HTTPS connectivity. The integration code is the same across all four editions, deployment process differs.
Does Payment Hub work across Sage 100's industry editions and verticals?
Yes. Sage 100's brochure names six target verticals: Manufacturing, Wholesale and Distribution, Retail, Business Services, Financial Services, and "And many more." Payment Hub adapts to each.
Manufacturing customers running Bill of Materials, Production Management, Work Order, MRP, Operations Management, Kitting, Lot and Serial Tracking get deposits at sale-order entry, milestone billing on production-status events, partial-shipment captures, multi-Warehouse routing. Wholesale and Distribution customers running Inventory Management, Sales Order, Purchase Order, Returns, Capable to Promise get multi-Warehouse MID routing, customer portal batch pay, ACH automation. Retail and Business / Financial Services get the appropriate industry-specific Payment Hub patterns.
Does Payment Hub use Sage 100's Visual Integrator for ETL-style payment workflows?
Yes. Visual Integrator is Sage 100's native ETL tool, it lets you import data from external sources (CSV, ODBC, SQL, web services) into Sage 100 via scheduled jobs. Payment Hub uses Visual Integrator for batch scenarios where appropriate: daily settlement reconciliation imports, daily bank-side ACH return processing, quarterly Level III savings reports, monthly customer portal usage exports.
Where real-time integration is required (capture confirmation, cash receipt creation, refund processing), Payment Hub uses BOI directly. The combination of Visual Integrator (batch) + BOI (real-time) covers the full integration surface. Where existing Visual Integrator jobs run for other purposes, Payment Hub coexists.
How is this different from Sage 100's native Credit Card Processing module?
Sage 100 ships with the Credit Card Processing module, typically configured to integrate with one of Sage's certified gateways (historically Sage Payment Solutions / Paya, now Sage Pay or third-party gateways). It works for simple invoice-payment scenarios but locks customers into the certified gateway. Most Sage 100 customers are effectively single-gateway, single-MID across all Companies / Warehouses, with no Level III interchange enrichment, no surcharging, limited dunning.
Payment Hub is the gateway- and processor-agnostic alternative: pick any of 19+ gateways (Worldpay, Adyen, Fortis, PayTrace, Stripe, Authorize.Net, NMI, USAePay, plus Sage-certified gateways if you want to keep them). Your existing merchant account, processor, and negotiated rates stay. Payment Hub also adds capabilities the native Credit Card Processing module doesn't ship.
Does Payment Hub support Sage 100's multi-Company and multi-Warehouse architecture?
Yes. Sage 100's multi-Company architecture (separate Company codes for each legal entity) and multi-Warehouse architecture (separate Warehouse codes for inventory locations) both map directly into Payment Hub's location routing table. Each Company can have its own merchant ID, gateway, bank account, currency, tax setup, and country. Each Warehouse can route per-location-specific MIDs for shipment-triggered captures and warehouse-aware customer portal flows.
Routing decisions happen on the originating transaction's Company and Warehouse. For Sage 100 Premium customers running multi-Company on SQL Server with consolidated reporting, Payment Hub's routing matrix scales, every Company / Warehouse can have its own gateway / merchant-account mix, with consolidated reporting back to the parent.
Does Level III interchange optimization work for Sage 100 customers?
Yes. Sage 100 customers, especially the Manufacturing, Wholesale and Distribution edition customers, typically have substantial B2B commercial-card volume that Sage 100's native Credit Card Processing handles at non-qualified or partially-qualified interchange. Payment Hub automatically pulls line-item data from Sage 100's Sales Order Detail (SO_SalesOrderDetail), Invoice Detail (AR_InvoiceHistoryDetail), and Production Order line records, then packages the 20+ required L3 fields per gateway / card-brand spec.
Tax data flows in cleanly from Avalara (which Sage 100 integrates natively for sales tax). Typical Sage 100 customer with $5M in annual B2B card volume recovers $15K–$50K annually. Larger multi-Company / multi-Warehouse Sage 100 customers with $25M+ commercial-card volume can recover $100K–$200K+.
Does Payment Hub work with Sage 100's Business Insights and reporting?
Yes. Sage 100's reporting layer, Crystal Reports, Sage Intelligence Reporting (Excel-based), Business Insights Explorer / Reporter / Dashboard, Sage Alerts and Workflow, Sage Data and Analytics, Sage Enterprise Intelligence, Sage Inventory Advisor, all consume Payment Hub data.
Payment Hub publishes payment events as first-class records in Sage 100. Business Insights Explorer drills into them. Crystal Reports renders payment-aware reports. Sage Intelligence Reporting picks them up in Excel. Sage Alerts and Workflow can trigger on Payment Hub events (capture confirmation, dispute, retry-success). The plant-floor-to-top-floor visibility Sage aims for extends to payment metrics: surcharge yield, L3 yield, retry success, dispute rate, MRR, days-from-invoice-to-cash flow into the existing reporting surface.
Does Payment Hub work with Sage CRM for the customer portal layer?
Yes. Sage 100 customers commonly add Sage CRM for sales-team productivity and customer relationship management. Sage CRM exposes customer data and provides limited customer-portal capabilities. Payment Hub embeds an enhanced customer-portal payment surface on top of Sage CRM's portal: multi-invoice batch pay, stored credentials, ACH / direct debit, multi-currency, surcharging disclosure, L3 enrichment on commercial cards.
The Sage CRM portal continues to render and authenticate normally. Only the payment slice is Payment Hub. For Sage 100 + Sage CRM customers running B2B portals with major customer accounts (common in Wholesale and Distribution), this unifies the payment experience and reduces manual ACH / check processing.
Does Payment Hub respect Sage 100 customizations, Custom Office, Customizer, scripts, custom panels?
Yes. Sage 100 customers customize through Custom Office (form / panel customization), Customizer (UI personalization), VBScript scripting on customer / item / transaction events, and custom panels added through Sage 100's panel framework.
Payment Hub uses Sage 100's published BOI / Visual Integrator / ODBC paths exclusively, it doesn't bypass your customizations. Custom panels continue to render. VBScript event handlers fire on Payment Hub-driven postings (when Payment Hub creates an AR Receipt or applies cash, your event scripts fire as designed). Custom Office field additions are visible to Payment Hub via BOI introspection. The integration is non-invasive on the customization layer. Your decades of MAS 90 / 200 / 100 customizations stay intact.
Does Payment Hub support Sage 100's manufacturing modules (BOM, Production Management, Work Order, MRP)?
Yes. Sage 100's manufacturing modules (Bill of Materials, Production Management, Operations Management, Work Order, Material Requirements Planning, Kitting, Lot and Serial Tracking, Forecasting and Replenishment, Capable to Promise, Mobility for Barcode) drive the production lifecycle.
Payment Hub adds the manufacturing-specific payment patterns the native Credit Card Processing module doesn't ship: deposits at Sales Order entry (held against the order in AR as an unapplied payment), milestone billing on production-status events from Production Management, partial-shipment captures triggered by Sales Order Shipment events, BOM-driven deposit logic for kit-assembled products. The triggers come from Sage 100's existing manufacturing modules. Payment Hub interprets the events and runs the captures.
What's the implementation timeline for Sage 100?
A typical Payment Hub + Sage 100 integration goes live in 48 hours once Clarity receives Sage 100 test environment access (BOI integration credentials, ODBC connection details for read access, Visual Integrator scheduling permissions if needed for batch flows), gateway credentials, and your baseline routing configuration.
For multi-Company / multi-Warehouse Sage 100 customers, pilot with one Company / Warehouse in the first 48 hours, then add additional entities in subsequent batches. For customers running Sage 100 Premium on SQL Server, the optional direct SQL Server queries deploy alongside BOI for higher-volume reporting scenarios. For customers planning a Sage Partner Cloud migration, Payment Hub deploys on Sage 100 first. The cloud migration adds the cloud-side connectivity when ready, and the configuration ports forward. Your existing Sage 100 license, Custom Office customizations, VBScript, custom panels, Visual Integrator jobs, and Sage CRM integration all stay intact.