Payment Hub for Sage X3, payment automation built into your industry-deep mid-market global ERP.

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

Sage X3, formerly Sage Enterprise Management, sits at the top of Sage's mid-market global ERP stack. Where Sage 100 anchors on the North American SMB tier, Sage 300 anchors on globally-diversified mid-market, and Sage Intacct anchors on cloud-native financial management, Sage X3's distinctive promise is industry depth combined with global enterprise scale: 7,000+ customers across 80 countries, multi-mode manufacturing across process, discrete, and agricultural verticals, regional or international operations with multi-legislation handling, complex business processes, and high-growth trajectories. Available in four deployment configurations: cloud (Sage-managed AWS-hosted), as a Sage service, partner-hosted (via Sage-accredited managed service providers), and on-premise.

Sage X3's signature architectural commitment is what Sage calls "by design" multi-everything. Multi-language for global teams. Multi-company sharing a database for shared-services structures. Multi-site for geographic diversification. Multi-currency with unlimited currencies and rate types. Multi-ledger with up to 10 ledgers per company supporting parallel statutory and IAS/IFRS books. Multi-legislation with country-specific tax engines, VAT returns, EU Intrastats, EU services tax declarations, Para-fiscal taxes, withholding taxes, and IFRS-aware fixed asset and revenue recognition. Plus 9 analytical dimensions per ledger (20 per model), 99-level pyramid structures for dimensional reporting, GDPR tooling built into the platform, and SEPA SCT / SDD compliance native to the AR cycle.

The gap, common across long-running Sage X3 installations, is the certified-gateway lock-in on the payment-acceptance side. Sage X3 ships with Sage Pay integration (currently UK-only per Sage's documentation) for online, face-to-face, and phone payments, plus generic certified-gateway integration in some regions. Most Sage X3 customers configured this years ago, often in their Sage Enterprise Management days, and never changed it. The result for global operations is particularly painful: single-gateway, single-MID across all Companies / Ledgers / Legislations, no Level III interchange enrichment, no surcharging where legal, dunning limited to Sage X3's standard 9-level reminder ladders, and no modern customer portal payment surface. Payment Hub fills this gap through Sage X3's published Web API / SOAP / EDI / Builder paths, gateway- and processor-agnostic, 19+ gateway choices behind one consistent integration, with per-Company / per-Ledger / per-Legislation routing that matches Sage X3's signature multi-everything architecture.

The five Sage X3 industry verticals, all served by Payment Hub

Sage X3's product brochure names five industry super-verticals where the platform has deep functional reach. Each has different payment characteristics. Payment Hub adapts to each with vertical-specific patterns.

Each vertical has a distinct typical Payment Hub fit. Agriculture customers running seed-to-sale traceability, wineries, dairy operations, co-ops, livestock producers, get lot/serial-traceable cash application back to specific harvests / batches / herds, plus seasonal-cash-flow-aware dunning. Process Manufacturing customers running formula-% bills of materials, weighing scales, lot/serial tracking, Quality Control, and Non-Conformance Management get formula-driven deposits, weighing-station-completion-triggered milestone captures, batch-genealogy-aware refund processing on Non-Conformance findings, critical for FDA / EMA / GMP-regulated chemicals and pharmaceuticals customers. Discrete Manufacturing customers running Production Management with Multi-product / Multi-level Work Order launches, Shop Floor Tracking, and Configure-to-Order get BOM-driven deposits, Work Order milestone billing, partial-shipment captures. Distribution customers get multi-Warehouse MID routing, batch SEPA SDD pay, ACH automation, EDI-driven document flows. Product Services customers running Project Management get project-milestone billing with revenue recognition (Free or Cost-based percentage of completion), time-billing automation from weekly timesheet completion.

Sage X3's four functional pillars and cross-cutting layers, where Payment Hub plugs in

Sage X3 organizes its functional reach across four primary modules, Financial Management, Supply Chain Management, Production Management, and Project Management, wrapped by cross-cutting platform layers that touch every transaction. Payment Hub plugs in at the platform layer and surfaces across all four pillars.

Payment Hub touches every pillar. Financial Management is the primary surface, AR Customer, AR Invoice, AR Receipt, multi-ledger postings (statutory + IFRS), multi-legislation tax handling all flow through Payment Hub via Web API and SOAP. Supply Chain Management drives the distribution / inventory-driven payment patterns: order-entry deposits, multi-warehouse MID routing, EDI document flows for B2B trading partners, inter-company / inter-site transactions. Production Management drives the manufacturing-specific patterns: BOM-driven deposits (formula-% for process, kit-driven for discrete), Production Management milestone events, weighing-station-completion triggers, Non-Conformance refund flows, lot/serial-traceable cash application. Project Management drives services-vertical billing: project-billing-center captures, milestone billing, time billing, revenue recognition with chosen percentage-of-completion method. The cross-cutting layers, workflow, auditing, role-based workspaces, fire on Payment Hub events as they would on any other Sage X3 transaction.

Multi-everything by design, Sage X3's signature architectural commitment

The capability that distinguishes Sage X3 from Sage 100, Sage 300, and most other mid-market ERPs is its "by design" multi-everything architecture. Six dimensions of multi-, plus the dimensional-reporting capacity that supports them. Payment Hub respects and extends this across the payment surface.

Sage X3 customers operating internationally typically run a Company entity per country and a Site entity per physical operation, often combined into shared-services structures via the multi-Company architecture. Payment Hub respects this entity-level partitioning end-to-end. Multi-language: customer portal flows render in the recipient's language matched to the Sage X3 Company's locale. Receipt emails, surcharge disclosures, dunning communications all localize. Multi-company: each Company can have its own gateway / merchant account / settlement bank / language / tax legislation / compliance overlay. Multi-site: each physical Site can route per-location MIDs for shipment-triggered captures and warehouse-aware customer portal flows. Multi-currency: cross-currency captures handle Sage X3's currency revaluation tables natively, with unlimited currencies and rate types (daily / monthly / average / budget). Multi-ledger: a single Payment Hub capture posts to up to 10 parallel ledgers (e.g., statutory + IFRS + group + management), with appropriate analytical dimensions on each. Multi-legislation: Sage X3 generates country-specific VAT returns, EU Intrastats, EU services tax declarations, Para-fiscal taxes, and withholding taxes per company. Payment Hub L3 enrichment carries the right data for each legislation.

Payment Hub vs Sage X3's native Sage Pay integration, honest side-by-side

Sage X3 ships with Sage Pay integration (currently UK-only per Sage's documentation) for online, face-to-face, and phone payments, plus generic certified-gateway integration in some regions. It works for simple invoice-payment scenarios, but for globally operating Sage X3 customers across the 5 industry verticals, the gap is wider than on any other Sage product. Payment Hub is the gateway-agnostic alternative for Sage X3 customers who need true multi-legislation, multi-ledger, multi-currency, industry-vertical-aware payment flexibility.

How the integration works, Web API + SOAP + EDI + Builder

Payment Hub plugs into Sage X3 through the platform's published integration paths. Open APIs in accordance with web services standards (WSDL/SOAP), REST endpoints. EDI templates with 100+ standard formats. ODBC connectivity for high-volume read on on-premise deployments. Sage X3 Builder for upgradeable customization. No core Sage X3 modifications. Eight features that come online when Sage X3 gets Payment Hub:

The integration workflow, a Process Manufacturing chemicals company on Sage X3 across 18 sites in 12 countries, end to end

Walk through one realistic Sage X3 scenario. Meridian BioChem International, a $480M Netherlands-headquartered specialty chemicals and nutraceuticals manufacturer running Sage X3 on-premise (with planned cloud migration in Year 2) across 18 sites in 12 countries: Netherlands (Rotterdam HQ + Eindhoven plant), Germany (Frankfurt + Hamburg plants), France (Lyon plant), United Kingdom (Manchester plant), Ireland (Cork plant), United States (Chicago plant + Atlanta plant), Brazil (São Paulo plant), Singapore (regional Asia HQ), China (Shanghai plant), India (Hyderabad plant), Japan (Tokyo office). 1,400 employees. Long-time Sage customer, originally on Sage Enterprise Management since 2014. Heavy use of Multi-BOM with formula-% bills of material, Weighing Scale integration, Lot &. Serial Tracking, Production Management, Quality Control, Non-Conformance Management, Project Management. Multi-ledger setup: Dutch GAAP statutory + IAS/IFRS group + management ledger. Currency footprint: EUR primary, plus USD, GBP, BRL, SGD, CNY, INR, JPY. Currently on a single Sage Pay (UK) gateway through one MID across all 18 sites, no L3 enrichment, limited SEPA SDD adoption, no multi-ledger payment posting. Eight steps showing how Payment Hub modernizes the global payment layer.

Use cases that light up on Sage X3

All eleven Payment Hub use cases run on Sage X3. These are the patterns where the Sage X3 integration shines, and where global Sage X3 customers across the 5 industry verticals get the highest use.

Technical details, for the Sage X3 admins and developers

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

Integration paths in detail

Sage X3 Web API + SOAP web services: API definition in accordance with WSDL/SOAP standards. Primary path for real-time scenarios. Modern REST endpoints also supported. Same path Sage X3's own components use. EDI integration: Sage X3's EDI module ships with 100+ standard templates (basic records, movements, accounting data). Payment Hub uses EDI for batch reconciliation flows. Sage X3 Builder: for upgradeable customization, Payment Hub's customization-respect layer plugs in here. ODBC connectivity: direct database access for high-volume read scenarios on on-premise / partner-hosted deployments. Bridges with Crystal Reports library of 400+ standard reports. Authentication via Sage X3 user authentication, LDAP, OAuth2 (Google account, Microsoft live), SAML2, or Sage Id (Single password).

Sage X3 records consumed and posted

• BPCUSTOMER (Customer master), read/write via Web API. Stored credentials linked back via custom analytical dimension.
• SORDER / SORDERQ (Sales Order header / detail), read for L3 enrichment and order-state events.
• SINVOICE / SINVOICED (Sales Invoice header / detail), read for invoice payment + L3 enrichment.
• BPCINVOICE (AR Invoice / Cash Receipt records), written via Web API on every capture, line-level cash application.
• BPCOPENITM (AR Open Items), read for AR aging and customer-portal display. Respects Sage X3's 9-level reminder ladder.
• BOMHEADER / BOMD (Bill of Materials header / detail), read for formula-% BOM deposit logic (process) and BOM-driven deposit (discrete).
• MFGITM / MFGITMTRK (Production Management item / tracking), subscribed for production-status milestone events.
• WEIGHTRACK (Weighing Scale tracking), subscribed for weighing-station-completion events (process manufacturing).
• STOLOT / STOSER (Stock Lot / Serial number), read for lot/serial-traceable cash application.
• NCM (Non-Conformance Management), subscribed for refund triggers.
• PJM (Project Management header), subscribed for milestone-billing events. Read for revenue recognition.
• FACILITY / COMPANY (Site / Company master), read for routing rule lookup.
• TABCUR / TABCHGRATE (Currency / Currency-rate tables), read for cross-currency routing and capture conversion.
• GACCENTRY / GACCENTRYD (GL Journal Entry header / detail), written for multi-ledger parallel postings (up to 10 ledgers).

Multi-everything posture

• Per-Company / per-Site / per-Currency / per-Language / per-Legislation gateway routing through COMPANY / FACILITY / TABCUR / TABCHGRATE lookup.
• Cross-currency capture: authorize in one currency, capture in another, settle through Sage X3 standard revaluation tables.
• Multi-ledger parallel posting: single Payment Hub capture posts to up to 10 parallel Sage X3 ledgers (statutory + IAS/IFRS + group + management) with appropriate analytical dimensions.
• Multi-legislation tax handling: per-country VAT, EU Intrastats, EU services tax declarations, Para-fiscal taxes, withholding taxes, all carry through L3 enrichment correctly.
• Up to 9 analytical dimensions per ledger (20 per model). Custom dimensions on Cost Center / Product Line / Project / Department all preserved.
• 99-level pyramid structures supported for dimensional reporting. Payment events feed pyramid roll-ups correctly.
• Inter-company / inter-site transactions module respected for cross-Company AR / AP flows.

Customization respect

• Custom analytical dimensions on Customer / Order / Invoice / Project records preserved.
• Workflow engine triggers, Payment Hub-driven postings fire your existing workflow rules normally on management events.
• Sage X3 Builder customizations remain upgradeable.
• Vocabulary customizing function preserved through Payment Hub-driven document headers.
• Personalize-mode page layouts unaffected. Embedded payment surfaces respect role-based workspace customization.
• Existing EDI templates coexist with Payment Hub's EDI flows.
• Existing Sage X3 Mobile Automation handhelds (on-premise only) coexist for shop-floor capture scenarios.
• Custom Crystal Reports continue to render Payment Hub-aware data.

Security and compliance

• Sage X3 user authentication, LDAP, OAuth2 (Google, Microsoft live), SAML2, Sage Id (Single password) all supported.
• PCI DSS Level 1 service provider, with PCI scope minimized via tokenization at gateway.
• Card data never lands in Sage X3. Tokens stored as custom analytical dimension on BPCUSTOMER.
• SOC 2 Type II (Clarity).
• Sage X3 GDPR tooling integration: cardholder-data residency aligns with Sage X3 Company region, right-to-be-forgotten cascades. Consent capture matches X3 framework.
• 3DS2 / SCA support natively across all gateways for European compliance (PSD2).
• IAS/IFRS-aware multi-ledger postings for global consolidation.
• EU VAT, EU Intrastats, EU services tax, Para-fiscal taxes, withholding taxes all first-class.
• Database-level traceability triggers preserve audit trail. Second-level signature for critical-field modifications respected.

Deployment scenarios

• Sage X3 cloud (Sage-managed AWS-hosted): Web API + SOAP integration. Outbound HTTPS to gateways and Payment Hub services. SSL/TLS encryption end-to-end.
• Sage X3 as a Sage service: same integration, Sage operates the X3 instance. Payment Hub connects via outbound HTTPS.
• Partner-hosted (Sage-accredited managed service providers): same integration, certified MSP's compliance posture extends.
• On-premise (customer-managed): same Web API / SOAP / EDI integration plus optional ODBC for high-volume read. Full access to Weighing Scale integration, Sage X3 Mobile Automation handhelds, and other on-premise-only capabilities.
• Multi-Company / multi-Ledger / multi-Legislation: common across all four deployments. Payment Hub's routing matrix scales to 100+ entities.
• Sage Enterprise Management → Sage X3 cloud 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 X3 sits at the top of Sage's mid-market global ERP stack, the natural step up from Sage 300 (multi-currency mid-market) for businesses needing deeper industry-vertical functionality (process manufacturing with formulas, agriculture with seed-to-sale traceability, project-billing services with revenue recognition), deeper multi-legislation handling (per-country VAT, EU Intrastats, IAS/IFRS dual-ledger), and broader scale (7,000+ customers in 80 countries vs Sage 300's smaller mid-market). For Sage X3 customers, Payment Hub configuration ports forward across the Sage stack, same gateway connections, routing rules, surcharging, dunning, customer portal, L3 mappings, language overlays carry across product transitions. The integration surface changes (Web API/SOAP on Sage X3 → REST on Sage Intacct → BOI on Sage 100), but the application configuration carries forward without re-implementation.

Related, explore other Payment Hub topics