Sage 300 + Payment Hub, multi-company, multi-currency payment automation built into your ERP.

Why Sage 300 customers add Payment Hub, and what changes when they do

Sage 300, formerly Sage ERP Accpac, is Sage's globally-positioned mid-market ERP. Where Sage 100 anchors on the North American SMB tier and Sage Intacct anchors on cloud-native financial management, Sage 300's distinctive promise is multi-company, multi-currency, multi-language operations for businesses that have outgrown single-country accounting. Three editions cover the spectrum: Standard (5 companies / 5 users / 3 account segments / 7 years of financial history), Advanced (unlimited companies / 10 users / 4 segments), and Premium (unlimited / unlimited / 10 segments / 99 years of history). Sage 300cloud delivers the same functional reach in a cloud-deployed model. Database options include Microsoft SQL Server, Oracle, and Pervasive.SQL.

Sage 300's distinctive architecture is the layered ring model documented in Sage's own architecture diagrams. At the core sit the foundational platform capabilities, Mobile access, Multicurrency, Multilanguage, Multi-company management, Workflow tools, Custom fields, KPI dashboards, Reliable reporting. Around that core, the inner-ring functional pillars, Finance and accounting, Inventory and operations, Project and job costing, Business intelligence, Purchasing and vendor management. Wrapping those, the outer-ring extension modules, Manufacturing, Inventory advisor, CRM, Order entry, Fixed asset management, Alerts and Workflows, POS and eCommerce, Human resources and payroll, Service management. This layered architecture is what gives Sage 300 its global mid-market reach.

The gap, common across long-running Sage 300 installations, is the certified-gateway lock-in on the payment-acceptance side. Sage 300 ships with a Credit Card Processing module, typically configured to integrate with one of Sage's certified gateways (historically Sage Payment Solutions / Paya, now Sage Pay or selected third-party processors). Most Sage 300 customers configured this years ago, often back in their Accpac days, and never changed it. The result for global businesses is particularly painful: single-gateway, single-MID across all Companies / Currencies / Countries, no Level III interchange enrichment, no surcharging where legal, limited dunning, and a customer portal payment surface limited to what Sage 300 + Sage CRM natively provides, typically English-only despite the underlying ERP's multi-language reach. Payment Hub fills this gap through Sage 300's published integration paths, gateway- and processor-agnostic, 19+ gateway choices behind one consistent integration, with per-Company / per-Currency / per-Language routing that matches Sage 300's global architecture.

The three Sage 300 editions, all served by Payment Hub

Sage 300 ships in three editions with distinct capacity tiers, plus Sage 300cloud for cloud deployment. Payment Hub integrates the same way across all four, same routing matrix, same gateway connections, same customer portal. What changes is the scale of multi-Company / multi-Currency activity each edition handles.

The integration code is the same across all four (Standard / Advanced / Premium / Sage 300cloud). The deployment process and the scale of activity differ. Standard is on-premise with the smaller capacity ceilings. Advanced removes the Company limit and expands users to 10. Premium removes all caps and expands to 10 account segments and 99 years of financial history. Sage 300cloud delivers the same functional reach in a cloud-deployed model. For customers on a Standard → Advanced → Premium upgrade path (often as global operations expand) or on a Premium → Sage 300cloud move (part of a cloud transformation), Payment Hub's configuration ports forward, same gateway connections, routing rules, customer portal customizations, L3 mappings, language overlays carry across the upgrade or migration.

Sage 300cloud's three-ring architecture, where Payment Hub plugs in

Sage 300cloud is documented in Sage's own architecture diagrams as a three-ring layered model. At the core: foundational platform capabilities (mobile, multi-currency, multi-language, multi-company, workflow, dashboards, reporting). Inner ring: functional pillars (Finance, Inventory, Project, BI, Purchasing). Outer ring: extension modules (Manufacturing, CRM, Order Entry, Service Management, etc.). Payment Hub plugs in at the platform layer and surfaces across all three rings.

The three rings inform where Payment Hub touches the system. At the platform core: multi-currency routing pulls from Sage 300's standard Currency table, multi-language portal flows pull from the Language Translation Overlay, multi-company routing pulls from the Company table. At the inner ring: AR Customer / AR Invoice / AR Receipt records get created and read in Finance and Accounting. Order Entry records drive L3 enrichment. Project and Job Costing records drive milestone billing. At the outer ring: Manufacturing module events trigger production-milestone captures. CRM portal embeds the modernized payment surface. Order Entry events fire shipment captures. Service Management drives recurring billing for service contracts.

Global multi-currency / multi-language reach, Sage 300's signature differentiator

The capability that distinguishes Sage 300 from Sage 100 and Sage Intacct is its native global reach, multi-currency, multi-language, multi-jurisdiction tax compliance, built into the core ERP. Payment Hub respects and extends this across the payment surface.

Sage 300 customers operating internationally typically run a Company entity per country (US, Canada, UK, Germany, Singapore, Hong Kong, Mexico, common deployment pattern). Each Company has its own functional currency, language, GL chart, tax setup, and compliance overlay. Payment Hub respects this entity-level partitioning end-to-end. Currency routing: each Sage 300 Company entity routes to its currency-matched gateway / merchant account / settlement bank, with cross-currency captures using Sage 300's standard exchange-rate revaluation tables for GL impact. Language localization: customer portal flows render in the recipient's language matched to the Sage 300 Company's locale. Receipt emails, surcharge disclosures, dunning communications all localize. Tax handling: Avalara for North American sales tax, native EU VAT for European entities, Singapore GST and Malaysia SST modules for those markets, all flowing into L3 enrichment cleanly. Compliance overlays: GDPR for EU customer data (residency, right-to-be-forgotten, consent capture), IFRS-aware multi-currency revaluation for global consolidation, full PCI DSS Level 1 service-provider posture across all jurisdictions.

Sage 300 modules, all touched by Payment Hub

Sage 300's module set, assembled across the three architectural rings, covers the full ERP functional reach. Payment Hub integrates across the major categories. Primary touch points are Financials, Order Entry / Inventory, and the global-business modules. Supporting touch points across the rest.

The integration touches every category. Finance &, Accounting is the primary surface, AR Customer, AR Invoice, AR Receipt, Order Entry orders, multi-currency revaluation, intercompany journals all flow through Payment Hub via Web API and SDK. Inventory &, Operations drives the manufacturing, distribution, and service-specific patterns: order-entry deposits, multi-warehouse routing, shipment-triggered captures, RMA refunds. Payroll &, HR coexists, payment events on the AR side don't conflict with Payroll on the AP side. PJC drives project milestone billing. Insights &, Reporting consumes Payment Hub events as first-class data points, Sage Intelligence Reporting picks them up in Excel. Crystal Reports renders payment-aware reports. The KPI Homepage Dashboard surfaces payment metrics, Alerts &. Workflows can trigger on payment events. Customization &, Integration tools are the path Payment Hub uses (Web API, SDK, ODBC, Web Screens). CRM &, eCommerce: Sage CRM gets the embedded portal payment surface, POS &. ECommerce gets gateway-agnostic checkout for Sage 300-running storefronts.

Payment Hub vs Sage 300's native Credit Card Processing, honest side-by-side

Sage 300'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, but for global businesses operating across multiple currencies, languages, and compliance regimes, the gap is wider than on Sage 100. Payment Hub is the gateway-agnostic alternative for Sage 300 customers who need multi-currency, multi-language, multi-jurisdiction flexibility.

How the integration works, Web API + SDK + ODBC + Web Screens

Payment Hub plugs into Sage 300 through the platform's published integration paths. Web API for modern REST-based real-time scenarios. SDK for .NET-based programmatic access. ODBC for direct database queries (across SQL Server / Oracle / Pervasive.SQL). Web Screens for embedded payment surfaces. No core Sage 300 modifications. Eight features that come online when Sage 300 gets Payment Hub:

The integration workflow, a global manufacturer on Sage 300 Premium across 8 countries, end to end

Walk through one realistic Sage 300 scenario. Halversen Industrial Group, a $185M Canadian-headquartered industrial-equipment manufacturer running Sage 300 Premium across 12 Company entities in 8 countries: Canada (HQ Toronto), United States (Chicago), United Kingdom (Manchester), Germany (Frankfurt), Mexico (Monterrey), Singapore (regional Asia HQ), China (Shanghai manufacturing), India (Bangalore engineering). 850 employees. Long-time Sage customer, originally on Accpac since 2002, upgraded to Sage 300 Premium in 2015. Heavy use of Order Entry, Inventory Control, Manufacturing, Project Job Cost, Multicurrency, Intercompany Transactions, Sage CRM. Currency footprint includes CAD, USD, GBP, EUR, MXN, SGD, CNY, INR. Language footprint: English (primary), French (Quebec subsidiary), simplified Chinese (Shanghai), Spanish (Monterrey). Currently on a single Sage-certified gateway through one MID across all 12 entities, no L3 enrichment, no cross-currency routing, English-only portal. Eight steps showing how Payment Hub modernizes the global payment layer.

Use cases that light up on Sage 300

All eleven Payment Hub use cases run on Sage 300. These are the patterns where the Sage 300 integration shines, and where mid-market and global Sage 300 customers across all editions get the highest use.

Technical details, for the Sage 300 admins and developers

For Sage Business Partners, Sage 300 Certified Consultants, and Sage 300-running businesses' IT teams: the connection model, record surface, multi-currency posture, security posture, and customization compatibility.

Integration paths in detail

Sage 300 Web API: modern REST-based interface, primary path for real-time scenarios, JSON payloads, OAuth-style authentication. Same path Sage 300 Web Screens use. Sage 300 SDK: .NET-based programmatic access to the full Sage 300 object model. Used for tighter scenarios where Web API doesn't expose the right entry points. ODBC connectivity: direct database access, Microsoft SQL Server / Oracle / Pervasive.SQL drivers depending on backend. Best for high-volume read scenarios. Web Screens: embedded payment surface inside Sage 300's web-based UI. Payment Hub renders the payment slice without disrupting the surrounding screen layout. Authentication via Sage 300 user credentials or dedicated integration users.

Sage 300 records consumed and posted

• ARCUS (AR Customer master), read/write via Web API. Stored credentials linked back via Custom field.
• OEORDH / OEORDD (Order Entry header / detail), read for L3 enrichment and order-state events.
• OEINVH / OEINVD (Order Entry invoice header / detail), read for invoice payment + L3 enrichment.
• ARIBH / ARIBD (AR Invoice batch header / detail), read/write for AR posting + L3 enrichment.
• ARTBH / ARTBD (AR Receipt batch header / detail), written via Web API on every capture, line-level cash application.
• AROBL (AR Open Items), read for AR aging and customer-portal display.
• PJCMASTER / PJCDETAIL (Project Job Cost master / detail), read for project-milestone events. Written for milestone-applied cash.
• BMBOMH / BMBOMD (Bill of Materials header / detail), read for kit-assembled deposit logic.
• ICITEM (Inventory Item master), read for item-level pricing and L3 categorization.
• CSCOMP / CSCOMPSEC (Company / Company-security), read for routing rule lookup.
• CSCURRRATE (Currency rate table), read for cross-currency routing and capture conversion.
• GLAMF (GL Account Master), read for GL distribution mapping. Respects 10-segment Premium structure.

Multi-currency posture

• Per-Company / per-Currency gateway routing through CSCOMP and CSCURRRATE lookup.
• Cross-currency capture: authorize in one currency, capture in another, settle through Sage 300 standard revaluation.
• Functional-currency vs source-currency posting handled via Sage 300's Multicurrency module.
• Daily rate refresh from Sage 300 Currency Manager (or external feed where configured).
• GL impact respects Sage 300 Premium's 10-segment account structure.
• Intercompany Transactions module respected for cross-Company AR / AP flows.

Customization respect

• Custom fields on AR Customer / Order Entry / AR Invoice preserved.
• Workflow tools (Sage 300's native workflow engine), Payment Hub-driven postings fire your existing workflow events normally.
• Alerts &, Workflows by Vineyardsoft rules fire on Payment Hub events.
• Existing Web Screens customizations coexist. Payment Hub's embedded payment surface respects layout.
• Sage CRM integration preserved.
• Document Management / EDI / Language Translation Overlays all respected.
• Existing Visual Integrator / Sage Data &, Analytics jobs coexist.

Security and compliance

• Sage 300 user-credential authentication (Standard / Advanced / Premium). Cloud-side connectivity (Sage 300cloud).
• PCI DSS Level 1 service provider, with PCI scope minimized via tokenization at gateway.
• Card data never lands in Sage 300. Tokens stored in ARCUS Custom field.
• SOC 2 Type II (Clarity).
• GDPR-compliant data handling for EU operations (data residency, right-to-be-forgotten, consent capture).
• 3DS2 / SCA support natively across all gateways for European compliance (PSD2).
• IFRS-aware multi-currency revaluation flows for global consolidation.
• Singapore GST, Malaysia SST, Canadian GST/HST/PST, EU VAT all first-class.

Deployment scenarios

• Sage 300 Standard (5 companies / 5 users): Web API + SDK integration, outbound HTTPS only.
• Sage 300 Advanced (unlimited companies / 10 users): same integration, routing matrix scales.
• Sage 300 Premium (unlimited / unlimited / 99-year history): same integration plus optional optimized direct-DB queries on SQL Server / Oracle for highest-volume scenarios.
• Sage 300cloud: cloud-deployed, outbound HTTPS to gateways and Payment Hub services.
• Multi-Company / multi-Currency / multi-Country: common across Advanced / Premium. Payment Hub's routing matrix scales to 100+ entities.
• Accpac → Sage 300 → Sage 300cloud migration: Payment Hub deploys on current version. Configuration ports forward through the migration.

Sage 100 vs Sage 300 vs Sage Intacct vs Sage X3

Sage 300 sits in Sage's global mid-market ERP tier, the natural step up from Sage 100 (North American SMB), differentiated from Sage Intacct (cloud-native financial management with strong North American focus) by its global multi-currency / multi-language / multi-country architecture, and the natural step down from Sage X3 (full mid-market global ERP with deeper manufacturing). For Sage 300 customers eventually moving up the Sage stack to Sage X3, or laterally to Sage Intacct, Payment Hub's configuration ports forward, same gateway connections, routing rules, surcharging, dunning, customer portal, L3 mappings, language overlays carry across the Sage product transition. The integration surface changes (Web API / SDK on Sage 300 → SOAP API on Sage X3 / REST API on Sage Intacct on the destination), but the application configuration carries forward without re-implementation.

Related, explore other Payment Hub topics