Supplier Management and Supplier Portal
Supplier model
A supplier is a business relationship; a supplier site is the address and remit-to used for purchasing and payments. Each site has assignments and business classifications, and a Pay site flag. Invoices are entered against a supplier site, so an inactive or non-pay site blocks payment even when the supplier is active. Tax organization type and withholding tax group are set at supplier or site level and drive tax and withholding.
Registration and onboarding
Suppliers can be registered internally or through Supplier Portal registration, which routes through an approval workflow before the supplier becomes active. Internal users manage addresses, contacts, bank accounts, and qualifications; bank account changes are typically controlled and approved.
Supplier Portal
Portal users are provisioned per supplier and site and assigned roles. Suppliers can view purchase orders, create and submit invoices against them, and view payment status and remittance. Portal invoices enter Payables as invoices and follow normal validation and approval; the portal does not bypass holds or tolerances.
Supplier merge
Supplier merge moves transactions from a duplicate supplier or site to a target. Run merge before payments are built; merging after payment changes the audit trail and can split balances confusingly.
Worked example
A supplier's remit-to site is changed but the old site stays active with a different bank account. A PPR built against the old site pays the wrong account. Correct by inactivating the old pay site and updating the site assignment before building payments.
Traps
Adding a portal user does not grant visibility to all sites; site assignment is required. A supplier site is not automatically a pay site. Changing a supplier name is not a merge.