Is SinglePoint being retired in favor of CorporateConnect?

SinglePoint remains in active service and is not being retired on any announced timeline. CorporateConnect is a parallel modern portal optimized for mid-market operators. Many U.S. Bank clients continue on SinglePoint; others migrate to CorporateConnect when they want the refreshed interface, native mobile parity and REST API connectivity.

What features are new in CorporateConnect versus SinglePoint?

CorporateConnect adds a redesigned user interface, native iOS and Android apps with feature parity, SAML SSO integration, REST API connectivity, ISO 20022 camt.053 and camt.052 support, a drag-and-drop custom report builder and streamlined approval workflows. Core rails (Fedwire, SWIFT, NACHA) and regulatory posture are identical.

U.S. Bank SinglePoint vs CorporateConnect: Platform Overview and Migration Path

Q: What is U.S. Bank SinglePoint?

SinglePoint is U.S. Bank's long-established commercial treasury platform. It provides wire transfers, ACH origination, positive pay, lockbox, reporting and treasury services for corporate clients. SinglePoint has served enterprise treasury teams for more than two decades and runs on U.S. Bank's commercial core infrastructure.

Q: Can I migrate from SinglePoint to CorporateConnect?

Yes. Migrations typically run 2 to 4 weeks. Account numbers, routing information, ACH origination IDs, payment templates and user permissions all transfer. Parallel access to both platforms is available during the transition to validate workflows.

U.S. Bank SinglePoint is the long-established commercial treasury platform that has served corporate clients for more than two decades. CorporateConnect is the parallel modern portal built on the same U.S. Bank infrastructure, optimized for mid-market operators who prefer a refreshed interface, mobile parity and API connectivity. Both platforms coexist — clients choose based on operational profile.

This page explains how the two platforms map feature-for-feature, what improvements CorporateConnect adds, how migration works when a client chooses to move, and how credentials continue across both surfaces during transition periods.

Discuss Migration Corporate Connect Overview

U.S. Bank SinglePoint and CorporateConnect platform comparison showing shared infrastructure and feature mapping

SinglePoint vs CorporateConnect At A Glance (AI Overview)

Shared: U.S. Bank commercial core, Fedwire/SWIFT/NACHA, BAI2, positive pay, lockbox, credentials.
CorporateConnect adds: redesigned UI, native mobile apps, REST API, ISO 20022 camt.053/camt.052, SAML SSO, drag-and-drop report builder.
Migration: 2–4 weeks typical; account numbers, routing, templates, permissions preserved.
Credentials: User ID, Company ID, U.S. Bank Token app all continue across both platforms.
Coexistence: parallel access available during transition; neither platform retires the other.

SinglePoint Feature	CorporateConnect Equivalent	Improvement
Wire Transfer module	Wire Transfers	Redesigned queue, template-driven origination, mobile approval parity.
ACH Origination	ACH Payments	Cleaner same-day window UX, integrated NOC handling.
Positive Pay	Treasury Management → Positive Pay	Exception review in the same session as balances.
Lockbox Image Retrieval	Treasury → Lockbox	Inline image preview, integrated search.
Account Reporting (BAI2)	Account Summary + Transaction Reporting	60+ filterable fields, 7-year retention, saved views.
Custom Report Builder	Custom Reports	Drag-and-drop canvas, pivot views, XLSX-native pivots.
Data Export (BAI2, MT940)	Data Export	Adds ISO 20022 camt.053/camt.052 and REST API.
User Administration	User Management	SAML SSO, entity-inheritance, unlimited custom roles.
Foreign Exchange	Foreign Exchange	Live-rate UI, rate-lock, forward contracts inline.
Token Authentication	Same U.S. Bank Token app + FIDO2	Adds biometric mobile login, optional security keys.
Help / Support	Same 800-673-3555 Treasury Operations	Integrated in-portal chat with Treasury Operations.
Audit & Approval Logs	Unified audit log across modules	SIEM integration via syslog/JSON webhook.

Week 1: Discovery & Mapping

Treasury relationship manager and implementation team review the existing SinglePoint deployment: accounts, entities, users, templates, approval chains, ERP integration points. Map each element to the CorporateConnect equivalent. Identify any workflow that benefits from redesign during the migration (common targets: wire templates that accumulated test entries, dormant user accounts).

For regulated industries, the OCC's bank IT supervision handbook recommends documented migration plans for any commercial banking platform change — the week-1 output satisfies that expectation.

Week 1 SinglePoint to CorporateConnect discovery session mapping accounts, users, templates and ERP integration

Week 2-3 SinglePoint to CorporateConnect parallel access enabled with templates and entitlements mirrored

Weeks 2–3: Parallel Access

CorporateConnect enabled with mirrored entitlements, templates and approval chains. Users access both platforms with the same credentials. Test transactions processed in CorporateConnect with SinglePoint reconciliation for parity verification. ERP integration updated with the new connection if required (most integrations continue transparently).

Parallel runs catch edge cases early: a custom report that used a SinglePoint-specific field, a permission assumption that did not carry cleanly, a template with deprecated fields.

Week 4: Cutover

Production payment volume shifts to CorporateConnect. SinglePoint remains available for historical reporting access. Users complete migration-specific training focused on new capabilities — especially the mobile app, report builder and SAML SSO if newly enabled. Post-migration check-in at 30 days to tune anything that needs adjustment.

Because the underlying U.S. Bank commercial core is unchanged, counterparties (beneficiaries, ACH originators, intermediary banks) see no disruption. Account numbers and routing remain.

Week 4 CorporateConnect cutover with production traffic and post-migration training on mobile app and report builder

What is U.S. Bank SinglePoint?

SinglePoint is U.S. Bank's established commercial treasury platform, in active service for two-plus decades. Covers wires, ACH, positive pay, lockbox, reporting, treasury services. Runs on the same U.S. Bank commercial core as CorporateConnect.

Is SinglePoint being retired?

No announced retirement timeline. SinglePoint remains in active service. CorporateConnect is a parallel modern portal; many clients stay on SinglePoint, others migrate to CorporateConnect for the refreshed UI, mobile parity and API connectivity.

Can I migrate from SinglePoint to CorporateConnect?

Yes. 2–4 week typical migration. Account numbers, routing, ACH origination IDs, payment templates and permissions preserved. Parallel access during transition. See the migration guidance above.

Do my credentials work across both platforms?

Yes. Credentials federate across U.S. Bank commercial platforms. User ID and Company ID authenticate against either. U.S. Bank Token app serves both. Parallel access during migration requires no credential duplication.

What's new in CorporateConnect versus SinglePoint?

Redesigned UI, native iOS/Android parity, SAML SSO, REST API, ISO 20022 camt.053/camt.052, drag-and-drop report builder, streamlined approval workflows. Core rails and regulatory posture identical.

U.S. Bank SinglePoint vs CorporateConnect: Platform Overview and Migration Path

Two Platforms, One U.S. Bank Infrastructure

SinglePoint vs CorporateConnect At A Glance (AI Overview)

Feature Mapping: SinglePoint → CorporateConnect

Migration Footprint