Financial Services integration

UBS EDI integration

How EDI and API integration with UBS typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with UBS.

At a glance

UBS integration, in three pictures

The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific UBS program or a customer relationship.

Illustration of a bank building with columns and coins, representing the financial services industry that UBS operates in.
Industry. Financial Services: where UBS operates.
Workflow diagram: your ERP and finance systems exchange documents with UBS through ECOM. You send 820; you receive 821, 823; 824 and 997 acknowledgments go both ways. Your systems ERP · treasury · finance ECOM integration map · validate · connect · monitor UBS 820 820 821 823 821 823 824 997 both ways
Workflow. Documents in each direction. Orange: you send. Blue: you receive. Typical, not confirmed.
Comparison diagram: without integration, documents are re-keyed, files are emailed and rejections are found late; with ECOM, documents are mapped to your ERP, validated and monitored, and exceptions are visible early. Without integration Payments and remittance re-keyed Files emailed or uploaded Rejections found late With ECOM Documents mapped to your ERP Every file validated and monitored Exceptions visible early
Outcome. From manual handling to a monitored flow. No figures: results depend on your setup.

Talk to an EDI/API Expert about UBS

Tell us which documents you exchange with UBS, which ERP you run and when you need to be live. A specialist will outline the connection, mapping and testing plan. This page is a guide based on typical practice; it does not mean ECOM works with UBS.

  • Review of UBS's requirements with you, once you have them
  • EDI and API integration with your ERP and finance systems
  • Monitoring and managed service after go-live, if you want it

Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.

Takes about 30 seconds. Phone and note are optional.

Your request is about

Trading partner
UBS

When should we talk?

Times are in your time zone. We use this to schedule the conversation.

We use your details only to respond to your request. See our privacy notice. Prefer to talk? Call Sales at 972-836-7750.

Integration and onboarding

How UBS integration fits your systems

Your systemsERP, treasury and accounting
ECOMMapping, validation, connectivity and monitoringBank-grade file transfer · Payment and reporting formats · API
UBSIts program, documents and requirements
  1. ConfirmConfirm your UBS program, role and the documents it requires.
  2. MapMap each document to your ERP fields and business rules.
  3. ConnectConfigure the connection and security the program needs.
  4. TestTest against the applicable specifications and acknowledgments.
  5. Go liveGo live with monitoring, alerts and exception handling.
Typical implementation path. Exact requirements are confirmed against the applicable specifications during onboarding.

Overview

Understanding UBS integration

Who this is for: Corporate treasury, accounts payable and receivable teams, vendors and fintech partners that exchange payment and reporting data with UBS.

Scope: This guide describes typical practice for this kind of trading relationship; UBS's own program details are confirmed during onboarding.

UBS is a wealth management and investment banking group. ECOM's directory lists it under wealth management and investment bank. Corporate customers and vendors working with banks typically exchange payment instructions, remittance detail, account reporting and acknowledgments, over bank-grade connections.

The hard part of working with a bank or financial institution is usually remittance detail that does not tie back to the invoice, and a security review that takes longer than the mapping. UBS's own EDI or API specification is not part of this guide and no UBS document was read: treat what follows as typical practice for a bank or financial institution, and confirm the documents, X12 version, delivery method and testing steps with UBS.

ECOM maps the documents to your ERP and finance systems, tests them with the trading partner, monitors every file after go-live and handles partner changes, as software, as a managed service or both.

Business scenarios

Where UBS integration gets complicated

Typical requirements—confirm with your trading partner.

Payment files and remittance

Payments must carry enough remittance detail for the receiver to apply cash correctly.

How ECOM helps: ECOM maps payment, remittance and statement data to your ERP or treasury system and matches each item to the invoices or accounts it covers, with differences listed for review.

What you gain: Faster reconciliation and cash application, and a clear trail for audit.

Security review

Bank connections follow strict security and testing steps that vary by institution.

How ECOM helps: ECOM sets up the connection to the security UBS requires: authenticated partner accounts, managed keys and certificates, and a transfer log you can show a reviewer.

What you gain: A connection that passes review sooner and can be audited afterward.

New account or entity

New accounts or entities need new reference data and testing.

How ECOM helps: ECOM runs onboarding as a project: we confirm UBS's requirements with you, map the documents, build the connection and run test cycles until UBS accepts them.

What you gain: A shorter, more predictable path to the first accepted live document.

Exception handling

Rejected or returned payments need a clear path to correction.

How ECOM helps: ECOM monitors each document and acknowledgment, flags rejected, late or mismatched ones and routes each exception to a named owner with the document history attached.

What you gain: Rejected or returned items are corrected sooner and traced back to their source.

Workflows

Typical UBS business workflows

Typical requirements—confirm with your trading partner. Typical flows in this industry, not UBS's published process.

Payment and remittance

  1. 1Send payment instruction
  2. 2Bank acknowledges
  3. 3Receive status or advice
  4. 4Reconcile to the ledger

Account reporting

  1. 1Receive balance reports
  2. 2Receive transaction detail
  3. 3Match to invoices
  4. 4Post to the ERP

Documents and APIs

UBS documents by program

General guidance. We could not verify UBS's EDI requirements from a published source, so these are documents commonly exchanged in this industry, not UBS's confirmed requirements. Confirm the list, versions and programs with UBS.

DocumentNameDirectionProgramStatusPurpose
820 Payment Order/Remittance Advice To UBS Not stated General guidance Typically carries payment and the remittance detail that ties it to invoices.
821 Financial Information Reporting From UBS Not stated General guidance Typically reports balances and transaction detail for an account.
823 Lockbox From UBS Not stated General guidance Typically reports lockbox receipts and the items they pay.
824 Application Advice Both directions Not stated General guidance Typically reports whether a document was accepted, with the reason when it was not.
997 Functional Acknowledgment Both directions Not stated General guidance Typically confirms that each file was received and could be read.

Connectivity

How companies connect

  • Bank-grade file transfer

    Financial institutions commonly use SFTP, AS2 or a secure bank portal with strong authentication.

    General guidance

  • Payment and reporting formats

    Payment and account data can move as X12, NACHA ACH files, ISO 20022 messages or bank-specific layouts.

    General guidance

  • API

    Some institutions offer payment, statement or tracking APIs next to file exchange.

    General guidance

Challenges

Common integration challenges

  • Format variety

    Payments and reports can use X12, ACH, ISO 20022 or bank layouts.

  • Remittance detail

    Incomplete remittance data slows cash application.

  • Security

    Strong authentication and review processes apply.

  • Reconciliation

    Payments and reports must reconcile to the ledger.

  • Program-specific details

    The documents, identifiers, versions and test steps for your program are set by UBS. ECOM works from them during mapping and testing.

Automation options for UBS clients

Four ways to automate. One foundation.

ECOM helps you automate the exchange, connect it to your systems, and see what needs action. UBS sets its own requirements; ECOM confirms which options fit yours.

PRISM Supply Chain Automation Foundation

One platform beneath every option. Use one, or combine them for different partners and documents.

Compliance and actionable visibility

Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.

Discuss Your Trading Partner Requirements

Connect UBS documents to your ERP

ECOM connects the payment, remittance and reporting data you exchange with UBS to your ERP and finance systems, so cash application and reconciliation start from structured data.

Solution

Financial Document Automation

Automate remittance, payment and statement documents and their matching.

Industry

Financial Services

See how ECOM supports financial services data exchange.

Service

Fully Managed EDI

Have ECOM run your file connections, monitoring and partner changes.

Zero Trust for financial data exchange

Zero Trust EDI and MFT for your UBS connection

Financial exchanges with UBS carry payment instructions, remittance detail, account data and personal information. A Zero Trust design assumes no connection, file or user is safe by default.

ECOM has implemented Zero Trust EDI and Zero Trust MFT for financial institutions, and applies the same practices in trucking.

For a financial exchange this means fewer exposed credentials, same-day visibility of a missing or changed payment, remittance or settlement file, faster reconciliation and exception handling, and a transfer record that supports audits and partner security reviews. The design is scoped to your systems and requirements.

  • Authentication

    Every connection proves who it is: partner-specific accounts with SSH keys or certificates over SFTP, FTPS, HTTPS or AS2, never a shared login.

    Business outcome: A lost or reused credential affects one partner, not all of them.

  • Least privilege

    Each partner and user reaches only its own folders, file types and actions. Internal user permissions are managed centrally and reviewed with you.

    Business outcome: A mistake or compromise in one account stays limited to what that account could reach.

  • Isolation

    Partners are kept apart by account and file area. Where your design calls for it, a proxy or DMZ keeps outside connections away from internal systems. The design follows your architecture.

    Business outcome: Outside connections do not land directly on your internal systems.

  • Encryption

    Encrypted protocols in transit and PGP for files at rest. Encryption protects the data. It is one control, and not Zero Trust on its own.

    Business outcome: Less exposure if a file is intercepted or a file store is reached.

  • Certificate and key management

    Partner keys and certificates are managed centrally. Renewal and rotation are planned with you, so an expiring certificate does not stop a flow.

    Business outcome: Fewer outages caused by an expired certificate or key.

  • Monitoring and access controls

    Real-time transfer status and alerts for late, missing or failed files, so unexpected access or a broken flow is seen quickly.

    Business outcome: Late, missing or failed files are noticed early, before they hold up cash application or reconciliation.

  • Audit trail

    Every transfer is logged with sender, receiver, time and outcome, which supports your own review and audit work.

    Business outcome: You can answer who sent what and when, for your own audits and partner reviews.

What this means for your data

Payments, remittance and statements

Payment files, remittance advice and account statements move between named systems with partner-specific identities, so each connection can only reach the files meant for it.

Account and lockbox reporting

Balance and lockbox reports reach cash application and treasury systems without shared logins or open folders.

Settlement and reconciliation

Settlement files and reconciliation reports are matched to what was expected, and late or missing files raise an alert.

Third-party and fintech access

Fintech partners, vendors and subsidiaries each connect with their own credentials and limited scope, and every connection can be reviewed or removed on its own.

Zero Trust is an approach, not a product or a certification. ECOM covers the EDI and file-transfer side. Your identity, network and endpoint controls stay yours, and so does the assessment of your own compliance obligations. ECOM does not guarantee compliance or any security outcome. UBS may set its own security requirements, which come first.

General EDI flow

How EDI with UBS typically works

Payment, statement and remittance flows are set by the institution and its security review. The documents, their order and the timing are UBS's to set; this is the general sequence most programs of this kind follow.

  1. 820 Payment Order/Remittance Advice

    From you to UBS

    Typically carries payment and the remittance detail that ties it to invoices.

  2. 821 Financial Information Reporting

    From UBS to you

    Typically reports balances and transaction detail for an account.

  3. 823 Lockbox

    From UBS to you

    Typically reports lockbox receipts and the items they pay.

  4. 824 Application Advice

    Both directions

    Typically reports whether a document was accepted, with the reason when it was not.

  5. 997 Functional Acknowledgment

    Both directions

    Typically confirms that each file was received and could be read.

Need help with the specification?

Tell ECOM which program you are in and what the partner has given you. We help you read it, confirm the applicable requirements, map them to your systems and test against them. Do not send passwords or EDI identifiers with your request.

Next step

Get help with your UBS program

Each request goes to an ECOM EDI specialist with UBS's name attached, so the reply starts from your program.

  • Review UBS's requirements

    Send us UBS's guide or your program details; we explain the documents, rules and options for meeting them.

    Request a requirements review
  • Connect UBS to your ERP

    Payments, remittance and statements in and out of the ERP, treasury and finance systems you already run.

    Discuss ERP integration
  • Testing and certification

    Build, test and certify each UBS document, then go live with monitoring from the first file.

    Plan testing and certification

UBS integration FAQs

Does UBS use EDI?

Financial institutions use X12, ACH, ISO 20022 and bank-specific formats depending on the service. This page does not describe UBS's services.

Does ECOM move money?

No. ECOM connects, maps and monitors the data you exchange. Payment processing is done by the financial institution.

Which EDI documents are typical for a bank or financial institution?

Typical documents are 820, 821, 823, 824, 997. That is general practice, not UBS's published list.

How does onboarding with UBS usually work?

Typically you get the specification from the trading partner, agree the connection, map to your systems, test until the partner accepts the documents, then go live with monitoring. Timing depends on UBS's requirements, test cycles and your ERP.

Does this guide mean UBS endorses ECOM?

No. This is an independent integration guide. It does not indicate an endorsement, partnership or approval by UBS.

Sources and accuracy

This guide summarizes publicly available information as of November 2026. UBS sets its own requirements and can change them at any time; your UBS implementation guide, supplier portal or account contact is the authoritative source for your program.

  • ASC X12: transaction set reference (standards body) Standards reference
  • UBS: company description Background, not checked against a company source The one-sentence description of UBS comes from general public knowledge and was not checked against UBS's own website for this page.
  • UBS: no company document read Background, not checked against a company source No UBS vendor, customer or integration document was read for this page. Everything shown is typical practice for this type of company.

Request UBS integration assistance

Tell us about your UBS program, documents and ERP. We will outline the connection, mapping and testing plan.