Multi-location payments — one Payment Hub, many locations, every transaction posting to the right entity

Introduction

A multi-location payment solution on Clarity runs every branch, store, clinic, campus, plant, or field office from one deployment, with per-branch identity baked into every charge. Each charge routes to the right merchant ID, posts to the right ERP entity, warehouse, and tax jurisdiction, reconciles to the right cash drawer, and rolls up to one head-office dashboard. The result is consolidated AR across a distributed business, so the business runs payment operations as one business: centralized oversight at the head office and per-branch control at the branch, without a separate payment stack at every branch. Running many branches comes down to managing money across a business, and the right payment solutions give finance teams central control, real-time visibility, and per-branch reporting. Managing spend, managing AR, and managing reporting all run from one system, so the business sees one set of numbers. Payment solutions built for distributed businesses make the difference between guesswork and oversight.

What multi-branch actually means in operations

The phrase multi-branch hides a lot of variation. A three-branch plumbing distributor, a twelve-clinic dental group, a thirty-branch municipal utility, an eighty-store retail chain, a 300-franchise restaurant group, a 1,200-campus university system, and a 2,500-branch insurance carrier all run multi-branch payment operations, but the operational realities differ. What they share is this: every one of these businesses struggles when the payment system treats each branch as an island.

The common failure mode in multi-branch payment operations is that each branch ends up with its own terminal, its own cash-drawer ledger, its own ad-hoc Excel reconciliation, and its own way of cramming the results into the head-office ERP at end of month. Tax gets booked to the wrong jurisdiction. Cash confirmation records post to the wrong entity. The head office has no real-time view of what any branch is doing. New-branch onboarding takes weeks because it requires deploying and configuring an entirely separate payment stack. Franchisee, branch-manager, and controller frustration compounds quarter over quarter.

Clarity is built for exactly this: one of the few multi-branch payment solutions that serves every branch from one platform, with per-branch identity baked into every charge, so the routing, posting, reporting, tax, and reconciliation all happen automatically at the right level.

The branch routing matrix: how each charge knows where to post

At the center of a multi-branch Payment Hub deployment is a routing table, a small configuration that maps each branch to its ERP identity, tax identity, merchant identity, and GL identity. When a charge happens at any branch, it consults this table and posts it to every downstream system with the correct identifiers. A production routing table also includes staff role scopes, surcharge rules, Level 3 eligibility flags, confirmation templates, branch-specific custom fields, and per-branch currency where applicable, all configured centrally and applied per charge automatically.

When an Oakland branch client walks in and pays a $2,400 invoice, the routing logic fires automatically: the charge goes to MID-4081-CA, the California merchant ID, posts to NetSuite subsidiary OAK-02 as a cash confirmation against the client's open invoice, applies Alameda County California tax (10.75 percent), credits GL 1010-OAK, and decrements inventory from OAK-WH-A if the charge includes a sales-order component. The staff member does not select any of this, and the client does not select any of this. The routing happens because Payment Hub knows the charge originated at Oakland.

Three deployment models: pick the one that fits your operations

Businesses approach multi-branch payment operations differently depending on legal setup, franchise model, and head-office governance. Clarity supports three common architectures and hybrids between them. The choice affects merchant-ID strategy, the flavor of reporting each branch gets, and the degree of head-office versus local autonomy.

Hub and spoke

Shared merchant IDs across all branches, with policy, branding, and rules set centrally. Branches post to a central, multi-branch or multi-warehouse ERP, the head office owns reconciliation and reporting, and new-branch onboarding is configuration-only.

Federated entities

Per-branch merchant IDs with separate settlement, mapped to per-entity ERP subsidiaries or company codes. Central governance combines with per-entity reporting, a multi-entity ERP is required (NetSuite OneWorld, Dynamics 365 F&O multi-company, Sage Intacct, SAP), and intercompany accounting is supported.

Hybrid (central and branch)

A shared MID for most branches, with a separate MID where required, on a central ERP with branch-specific tax and GL overrides. Branch-level counter staff get autonomy, central controls govern policy, pricing, and Level 3, branch managers see their own branch, and the head office sees all. This is the most common pattern in mid-market multi-branch operations.

Payment Hub does not enforce a model; it supports whichever matches your business's legal and operational setup. Many deployments start in hub and spoke and migrate toward hybrid as they scale, adding per-branch MIDs and per-branch tax overrides selectively where state-level regulation or acquisition-driven entity separation demands it.

How it powers multi-branch at any scale

Eight capabilities make multi-branch work without turning every branch into its own payment-tech project. Each is central configuration applied per charge, not a per-branch install or integration.

Per-charge branch identity

Every charge carries an originating-branch identifier, by staff login, terminal ID, portal subdomain, or customer ship-to record. That identity drives routing downstream into your ERP, gateway, tax engine, and dashboards automatically.

ERP multi-entity and multi-subsidiary posting

Clarity Connect writes each charge to the correct ERP entity, subsidiary, or company code: NetSuite OneWorld subsidiaries, Dynamics 365 F&O companies, Acumatica branches, Sage Intacct entities, SAP company codes. Intercompany accounting stays clean.

Multi-state and multi-jurisdiction tax

Each branch's originating address drives the tax-engine lookup, by state, county, city, and district, per charge. It integrates with Avalara, Vertex, TaxJar, or the tax engine in your ERP. Destination-based tax for interstate sales follows the ship-to ZIP automatically.

Per-branch merchant-ID routing

Share one gateway MID across all branches, run separate MIDs per branch, or do both, sharing where possible and separating where state or entity rules require. Payment Hub routes each charge to the correct MID with no staff awareness and no special configuration.

Per-branch cash-drawer reconciliation

Each branch's staff opens and closes drawers per shift, with per-drawer totals, per-shift reconciliation, and per-branch GL posting. Multi-drawer branches with several counter stations get separate contexts, and the branch manager can consolidate all drawers at end of day.

Branch-scoped staff roles

Counter staff see their home branch only. A branch manager sees one or more assigned branches. A district supervisor sees a region. The head office sees all. The audit log records which staff member authorized each charge at which branch, never ambiguous and never cross-contaminated.

Head-office consolidated dashboard

A real-time view of revenue, charge volume, card mix, open aging, and exception rate, rolled up across every branch and drillable down to the originating charge. It feeds your BI or data-warehouse layer for analytics beyond payment operations alone. Finance teams and operations teams get one view, so the teams managing many branches stop managing many systems. Central control and per-branch control coexist, the head office can track revenue and exceptions across the business, and visibility is real across the whole business.

Fast new-branch onboarding

Adding a new branch, store, clinic, or branch is a configuration change: set up the ERP entity, confirm the tax jurisdiction, set up the MID strategy, set staff roles, and provision terminals or the portal URL. Typical time from decision to first charge is 24 to 48 hours, not a new deployment and not a new integration project.

The multi-branch workflow: from a branch charge to head-office dashboard

Here is a $3,200 counter charge at the Oakland branch, posted to the right NetSuite subsidiary, with the right California tax, reconciled to the right cash drawer, and rolled up to the head-office dashboard by the time the branch manager clocks in the next morning, all automatically.

Staff clocks in at the Oakland counter. Oakland counter staff (role counter_CA_oakland) log into Clarity at 8:00 AM Pacific. Branch identity is asserted from the staff login (Oakland) and the terminal ID (OAK-TERM-02). The drawer opens for this shift. Staff see only Oakland-branch clients, Oakland-branch open invoices, and Oakland-branch saved methods.

A customer walks in at 10:45 AM with a $3,200 purchase. Acme Manufacturing (record OAK-4021) walks up with a $3,200 order. Staff ring up the line items, three industrial widgets at $980 each plus $260 in installation services. Tax applies at the Alameda County CA rate of 10.75 percent, pulled from the branch routing table, for a total of $3,544.20.

The customer pays with a Visa Corporate card. The customer taps their Visa Corporate card. Payment Hub identifies the BIN as commercial and flags the charge for Level 3 enrichment. Line items, customer code (ACME-4021), destination ZIP, unit of measure, product codes, freight, and tax breakdown are pulled from the Oakland branch's NetSuite subsidiary (OAK-02) and packaged into the Level 3 envelope.

The gateway routes to the California MID. Because Oakland runs on a separate California MID (MID-4081-CA), it submits the authorization to that specific merchant record. The charge authorizes in under two seconds, and the receipt prints at OAK-TERM-02 with Oakland branding, the Oakland receipt template, and Oakland return-policy text.

ERP posting fires through Clarity Connect. Clarity Connect writes to NetSuite OneWorld: the sales order lands in subsidiary OAK-02, inventory decrements from warehouse OAK-WH-A, the cash receipt posts to GL 1010-OAK for Oakland, sales tax allocates to GL 2240-CA-SALES-TAX, and the customer's record total updates. None of it touches the Dallas, Atlanta, or Denver subsidiary records.

The drawer and dashboard update. The $3,544.20 posts to Oakland's active cash drawer for the open shift. Oakland branch's end-of-day expected totals now include this charge. The head-office dashboard picks up the charge in real time: Oakland's daily revenue updates, the consolidated revenue-across-all-branches view ticks up, and the California tax accrual increments.

Oakland branch closes out at 6:00 PM. Oakland's staff close their shift, and the drawer reconciles, with expected totals matching recorded totals within tolerance. The end-of-shift summary goes to the Oakland branch manager. If the variance exceeds tolerance, the branch manager receives a flagged notification, and Payment Hub surfaces which charge or charge group caused the variance.

The head office sees the consolidated view the next morning. At 7:00 AM CT the next day, the head-office controller opens the dashboard. Oakland's previous-day total is visible, segmented into card, ACH, and cash, commercial versus consumer, and Level 3-qualified versus downgraded. Cross-branch revenue sits alongside Dallas, Atlanta, and Denver. The controller can drill down from yesterday's $208,000 consolidated total to Oakland's $58,000 to the specific $3,544 Acme Manufacturing charge, and its ERP posting record, in under 30 seconds.

Industries running Payment Hub across multiple locations

multi-branch payment consolidation is relevant wherever the same business operates at more than one physical branch with its own counter, clinic, office, or campus. These are the industries where it matters most, and what the typical deployment looks like for each.

Wholesale and Industrial Distribution

Regional branch networks, multi-state distributors, and contractor-facing supply chains. Branch counter, branch will-call, and customer-portal payment all post to the right NetSuite subsidiary or Dynamics company, across HVAC and plumbing regional branches, electrical and building-product supply, and industrial MRO and fleet-parts distributors. Deployment is typically 4 to 50 branches.

Healthcare Multi-Clinic Groups

Dental groups, urgent-care networks, physical-therapy chains, and specialty-medicine multi-sites. Each clinic handles patient AR, co-pays, and supplier payment with the right provider NPI, tax ID, and GL, while head-office practice management sees everything, across DSOs, urgent-care networks, and specialty-clinic networks.

Government and Municipal Multi-Office

City departments (utility, permits, parks, clerk), multi-campus state agencies, and regional public-works offices. Each office accepts payment with its own permit-fee schedule, tax, and GL coding, consolidated for city-hall-level reporting, across municipal utility multi-service districts, county clerk, DMV, and permit offices, and state agency regional offices.

Manufacturing Multi-Plant and Multi-Warehouse

Manufacturers with multiple plants, distribution warehouses, or will-call branches. Each branch handles its own shipping pickups and local B2B charges while the central manufacturing ERP sees all of it. A multi-entity setup is common for private-equity manufacturing rollups, alongside industrial manufacturers with regional warehouses and multi-plant food and consumer-goods producers.

Retail and Franchise Chains

Multi-store retail networks and franchise operators. Each store or franchisee gets its own MID, common for franchise entity separation, its own receipt branding, and its own cash drawer, while the franchisor sees consolidated chain-wide reporting, across retail chains, franchise restaurants and service businesses, and multi-unit hospitality.

Higher Education Multi-Campus

University systems with multiple campuses, regional satellite branches, or separate undergraduate, graduate, and continuing-ed invoicing entities. It is a strong fit for vendor, bookstore, and facilities charges, and more complex for student tuition, which runs through separate Student Information System workflows, across community-college multi-campus systems, university regional and online extension, and K-12 district-level payment operations.

Professional Services Multi-Office

Legal, engineering, consulting, and CPA firms with multiple office branches. It is a strong fit when each office handles its own client-engagement invoicing and AR, and less impactful when billing is fully centralized regardless of office, so it is worth evaluating based on billing architecture, across multi-office consulting firms, regional CPA and tax practices, and engineering and architecture multi-branch firms.

Single-Branch or Pure eCommerce

Businesses operating from a single physical branch or pure-play online merchants do not need multi-location routing. Clarity still delivers ERP integration value and Level 3 optimization, but the multi-location-specific capabilities on this page are overkill, and a single deployment with no routing table suffices for single-warehouse B2B, pure DTC eCommerce, and single-office professional services.

ERP and multi-entity integration: how Clarity Connect handles the complexity

Multi-location payment operations land on multi-entity or multi-branch ERP setup. Clarity Connect is the integration layer that translates Payment Hub's originating-branch identity into the right ERP construct, whether that is a subsidiary, company code, branch, warehouse, expense center, or custom dimension.

NetSuite OneWorld gets per-subsidiary routing with intercompany auto-balance, native multi-book where enabled, and per-subsidiary tax and currency, selecting the correct subsidiary on each charge based on originating branch. Microsoft Dynamics 365 F&O multi-company deployments get per-legal-entity posting, with Payment Hub writing to the correct company code and the intercompany ledger handling central-bank reconciliation where applicable. Dynamics 365 Business Central multi-company deployments post each branch to its company, chart of accounts, and VAT or sales-tax setup. Acumatica multi-branch and multi-company deployments post to the correct branch and company combination with per-branch tax, numbering, and GL record mapping. Sage Intacct multi-entity deployments write to the correct entity and populate user-defined dimensions (branch, department, project) based on routing rules. SAP S/4HANA and ECC post per company code with proper profit-center, cost-center, and plant derivation. Epicor Kinetic and P21 post per warehouse and branch with per-branch AR, cash, and tax accounts. Infor SX.e and CloudSuite Distribution post to the correct warehouse and entity per originating branch. SYSPRO, Workday, Oracle EBS, Sage 100, 300, and X3, and Tyler Technologies are all supported with per-entity and per-branch routing through Clarity Connect, with specific integration points varying by ERP.

Where your multi-location setup exceeds what the ERP represents natively, for example a smaller outpost inside a bigger region that does not have its own ERP entity, Clarity supports virtual-branch routing. The charge posts to the parent ERP record with a custom dimension, tag, or segment that preserves the originating-branch identity for reporting, even when the accounting setup does not require entity separation.

Frequently Asked Questions