Overview
Understanding University of Pennsylvania integration
Who this is for: Vendors, contractors and service providers that bill University of Pennsylvania, and their finance teams. You receive a vendor order and PO number, send the invoice and receive payment.
Scope: Penn'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 University of Pennsylvania, 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. Penn buys through many schools and departments, so each invoice must carry the coding and PO reference that identify who ordered.
Penn takes invoices through its Penn Marketplace vendor portal or by email, and mailed paper invoices are no longer accepted. The portal supports PO Flip, which turns a PO into an invoice, and CSV uploads for multiple transactions. U.S. vendors can ask for cXML. Email invoices go to the invoice mailbox as one PDF per invoice with the PO number on the invoice. Terms depend on the payment method: ePayables Net 10, ACH Net 30 and check Net 45 from the approved invoice. Penn lists processing at three to five 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.