Glossary

Terms to better understand the relationship between yourself (Customer), the companies of which you want collect data (Clients), and APIs to unlock that data.

Customer: A company that pays PortalDuct for their platform and services.

A Customer could be a Trade Finance company, a Bank Supply Chain Finance department

Customer Employee User: A team member of the company that has access to view data

A Customer Employee User would be like Gavin the engineer who is leading the PortalDuct integration.

Customer Client: this is the entity (another company in a B2B transaction) of which they do business and need to view their procurement data (purchase orders, invoices, and remittance

Customer Client User: A team member of the Client that is providing credentials to give the Customer access to their Portals

Client Vendor Portal: the procure to payment portal where the Client can upload purchase orders and invoices with corporate/brand (e.g. Target) that will owe or does the Customer Client future payment. Sometimes called a “debtor” in a financial transaction.

Client EDI Portal: an aggregation platform that a Client uses to map several Client Vendor Portals to once centralized location, and connection via EDI file transfer. For example, SPS Commerce.

Procurement System: The platform of which the procurement portal is hosted. This could be Custom (e.g. Walmart Retail Link), an EDI Portal, or a product (Coupa, Ariba, Tradeshift).

Customer Instance: The walled offering with all of the Customer company data that the Customer