PO number on the invoice
NYU cannot issue payment if the PO number is missing from the invoice.
How ECOM helps: ECOM adds the PO reference from your order data and checks each invoice before it is sent.
What you gain: Fewer unpaid invoices.
Financial Services integration
NYU pays vendors against POs through its published invoice channels. This guide shows what it publishes and how ECOM automates invoices, payments and matching.
At a glance
The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific New York University program or a customer relationship.
Tell us which documents you exchange with New York University, 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 New York University.
Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.
Integration and onboarding
Overview
Who this is for: Vendors, contractors and service providers that bill New York University, and their finance teams. You receive a vendor order and PO number, send the invoice and receive payment.
Scope: NYU's published vendor pages describe the channels above. X12 specifications, if any, are agreed with its procurement or accounts payable team; those items are marked typical.
If you bill New York University, the exchange that matters is an invoice that carries the right PO number and reaches the right channel, and a payment you can match to it. NYU buys through many schools and departments, so each invoice must carry the coding and PO reference that identify who ordered.
NYU runs iBuy NYU, powered by JAGGAER, and vendors need an active profile there before an invoice can be paid. Invoices go by email to the central invoice mailbox with the PO number on the invoice, one attachment per email. Vendors also have a vendor portal to submit invoices electronically and update banking and tax details. A voucher is generally created within three business days. For punchout orders, the vendor submits the invoice automatically after the item ships or is delivered. Vendors keep banking and tax details in the vendor portal, and a voucher is generally created within three business days.
ECOM helps vendors connect their billing and finance systems to these channels. ECOM maps invoices and payments to your ERP, tests with the university, and monitors every file after go-live.
Business scenarios
Typical requirements—confirm with your trading partner.
NYU cannot issue payment if the PO number is missing from the invoice.
How ECOM helps: ECOM adds the PO reference from your order data and checks each invoice before it is sent.
What you gain: Fewer unpaid invoices.
Punchout vendors invoice automatically once goods ship or are delivered.
How ECOM helps: ECOM triggers the invoice from your shipment or delivery event.
What you gain: Invoices arrive on time without manual billing.
Workflows
The steps summarize the documents below. Where a step is not in New York University's published documents, it reflects common practice.
Documents and APIs
Every document this guide names, with the program it applies to and its status. Required, optional and conditional come from New York University's published documents cited below; documents marked general guidance are common in this industry but not confirmed for New York University.
Scroll sideways to see every column. With a keyboard, select the table and use the left and right arrow keys.
| Document | Name | Direction | Program | Status | Purpose |
|---|---|---|---|---|---|
| 850 | Vendor Order | From New York University | Not stated | General guidance | Commonly the order that a PO number refers to. The university requires that PO number on the invoice. |
| Invoice by email (PDF, TIF, DOC, JPG) | Both directions | Not stated | Named; level not stated | NYU accepts invoices by email with the PO number on the invoice, one attachment per email. | |
| 810 | Punchout invoice (electronic) | To New York University | Not stated | General guidance | Vendors on punchout orders submit invoices automatically after shipment or delivery. NYU does not name X12 810. |
| ACH | ACH payment | Both directions | Not stated | Named; level not stated | NYU pages reviewed do not name an electronic payment format; bank details are kept in the vendor portal. |
| 820 | Payment Order/Remittance Advice | From New York University | Not stated | General guidance | Commonly used to explain which invoices a payment covers. Not named in the pages reviewed. |
Connectivity
Vendors register, submit invoices electronically and update banking details.
From New York University's published documents
Central mailbox, one attachment per email.
From New York University's published documents
Where a university supports EDI, vendors commonly connect directly or through a value-added network.
General guidance
Challenges
Invoices without a valid PO number are commonly rejected or returned.
Each department orders for itself, so coding and approvals vary.
Portal, email and electronic channels must not produce duplicate invoices.
Payments must be matched to the invoices they clear.
Automation options for New York University clients
ECOM helps you automate the exchange, connect it to your systems, and see what needs action. New York University sets its own requirements; ECOM confirms which options fit yours.
Automate trading partner transactions and ERP integration through our iPaaS, SaaS, and EDI Team as a Service offerings.
Learn more about Fully Automated EDI/APIReceive orders and manage trading partner transactions through a browser-based portal, without requiring direct ERP integration.
Learn more about WebEDIConvert documents received through email or in PDF, Excel, Word, JPG, PNG, and other supported formats into structured data for automated processing, reducing manual data entry.
Learn more about SmartConvertAutomate repetitive order processing and transaction tasks in third-party portals such as SAP Ariba, Coupa, and other customer or supplier portals, reducing the work customer service representatives must log in and complete manually.
Learn more about WebConnectPRISM Supply Chain Automation Foundation
One platform beneath every option. Use one, or combine them for different partners and documents.
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.
ECOM connects invoices and payments you exchange with New York University to your ERP and finance systems, so documents move without re-keying and exceptions are visible early.
Connect vendor orders, receipts and invoices for a procurement operation.
SolutionAutomate invoices, remittances and payment matching.
Zero Trust for financial data exchange
Financial exchanges with New York University 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.
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.
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.
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.
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.
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.
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.
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.
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.
Balance and lockbox reports reach cash application and treasury systems without shared logins or open folders.
Settlement files and reconciliation reports are matched to what was expected, and late or missing files raise an alert.
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. New York University may set its own security requirements, which come first.
Talk to an EDI/API Expert about Zero Trust Managed file transferSecure proxy and DMZ designSecurity at ECOM
General EDI flow
The documents, their order and the timing are New York University's to set; this is the general sequence most programs of this kind follow.
850 Vendor Order
From New York University to you
Commonly the order that a PO number refers to. The university requires that PO number on the invoice.
PDF Invoice by email (PDF, TIF, DOC, JPG)
Both directions
NYU accepts invoices by email with the PO number on the invoice, one attachment per email.
810 Punchout invoice (electronic)
From you to New York University
Vendors on punchout orders submit invoices automatically after shipment or delivery. NYU does not name X12 810.
ACH ACH payment
Both directions
NYU pages reviewed do not name an electronic payment format; bank details are kept in the vendor portal.
820 Payment Order/Remittance Advice
From New York University to you
Commonly used to explain which invoices a payment covers. Not named in the pages reviewed.
Tell ECOM which program and documents apply to you. We read the published specification with you, map it to your systems and test against it. Do not send passwords or EDI identifiers with your request.
Next step
Each request goes to an ECOM EDI specialist with New York University's name attached, so the reply starts from your program.
Send us New York University's guide or your program details; we explain the documents, rules and options for meeting them.
Request a requirements reviewThe documents you exchange, in and out of the ERP and operating systems you already run.
Discuss ERP integrationBuild, test and certify each New York University document, then go live with monitoring from the first file.
Plan testing and certificationNYU runs iBuy NYU, powered by JAGGAER, and vendors need an active profile there before an invoice can be paid. Invoices go by email to the central invoice mailbox with the PO number on the invoice, one attachment per email.
Vendors keep banking and tax details in the vendor portal, and a voucher is generally created within three business days.
The pages reviewed do not publish an X12 specification beyond what is marked official on this page. Confirm other documents with its procurement or accounts payable team.
Vendor order, invoice and remittance advice, with payment by ACH where offered. Items marked typical are general practice, not the university's published list.
This is an independent integration guide. It does not indicate an endorsement, partnership or approval by New York University.
This guide summarizes publicly available information as of November 2026. New York University sets its own requirements and can change them at any time; your New York University implementation guide, supplier portal or account contact is the authoritative source for your program.
New York University is a trademark of its owner. Its mention does not imply endorsement of, or a partnership with, ECOM Specialist.
Related integrations
Yale pays vendors against POs through its published invoice channels. This guide shows what it publishes and how ECOM automates invoices, payments and matching.
Columbia pays vendors against POs through its published invoice channels. This guide shows what it publishes and how ECOM automates invoices, payments and matching.
Cornell pays vendors against POs through its published invoice channels. This guide shows what it publishes and how ECOM automates invoices, payments and matching.
Emory pays vendors against POs through its published invoice channels. This guide shows what it publishes and how ECOM automates invoices, payments and matching.
Harvard pays vendors against POs through its published invoice channels. This guide shows what it publishes and how ECOM automates invoices, payments and matching.
Johns Hopkins pays vendors against POs through its published invoice channels. This guide shows what it publishes and how ECOM automates invoices, payments and matching.
Tell us about your New York University program, documents and ERP. We will outline the connection, mapping and testing plan.