Overview
Understanding Columbia University integration
Who this is for: Vendors, contractors and service providers that bill Columbia University, and their finance teams. You receive a vendor order and PO number, send the invoice and receive payment.
Scope: Columbia'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 Columbia 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. Columbia buys through many schools and departments, so each invoice must carry the coding and PO reference that identify who ordered.
A vendor must be set up in the University vendor master file before an invoice can be paid, and some purchases need a PO created in the CU Marketplace first. Electronic invoices from catalog vendors are matched to automated payments once approvals are complete. Invoices must show the vendor name, remit-to address, tax ID, invoice date, amount and a description, with Columbia University as the bill-to party. Some units, such as Teachers College, run their own systems. Catalog vendors are paid automatically after approval. Other invoices are paid by departments through a PO voucher.
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.