Overview
Understanding Johns Hopkins University integration
Who this is for: Vendors, contractors and service providers that bill Johns Hopkins University, and their finance teams. You receive a vendor order and PO number, send the invoice and receive payment.
Scope: Johns Hopkins'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 Johns Hopkins 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. Johns Hopkins buys through many schools and departments, so each invoice must carry the coding and PO reference that identify who ordered.
Johns Hopkins accounts payable asks for PO invoices by email as one invoice per PDF, with the PO number and no more than five PDFs per email. Invoices without a PO go to the ordering department contact. Monthly statements are submitted once every 30 days as a spreadsheet. A University Finance newsletter says some customers use electronic invoicing systems and receive payment by ACH, and approved PaymentWorks vendors can see payment status in their account. Vendors should allow 30 days before asking accounts payable about status.
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.