Supplier Portal.

What is the ETHX Softcon Supplier Portal for Oracle Fusion and E-Business Suite?

The ETHX Softcon Supplier Portal is a self-service portal for suppliers that supports PO collaboration, advance shipment notices, invoice submission, payment visibility, and supplier onboarding, writing directly into Oracle Fusion Cloud or E-Business Suite. Suppliers can acknowledge, query, request changes to, and split-ship open purchase orders, and submit ASNs that are matched to receipts in Oracle. Invoices can be uploaded as PDF, XML (UBL or Peppol), CSV, or structured e-invoices, with OCR applied to PDFs for line extraction and 3-way matching with status tracking.

Suppliers can view payment schedules and remittances and raise disputes through a built-in workflow. Onboarding lets suppliers self-register, upload tax and bank documents, and move through a configurable approval workflow with KYC checks and bank validation. The portal is multi-language, multi-currency, and multi-entity, and supports multi-tier supplier hierarchies with delegated access. It can replace or sit alongside the standard Oracle Supplier Portal, and rollout typically starts with a pilot group of 10–20 strategic suppliers.

What should you evaluate before adding a supplier portal to Oracle Fusion or EBS?

First confirm what Oracle's standard supplier portal already does, because much of the core is included in the procurement suite. Oracle Supplier Portal gives suppliers a secure work area with agreements, purchase orders, advance shipment notices, invoices and negotiations, and Oracle iSupplier Portal on E-Business Suite supports online invoice submission and payment history. A separate portal is usually justified by specific gaps, such as onboarding with third-party bank or tax checks, suppliers who serve several of your ERPs, or a simpler experience for small vendors, rather than by rebuilding standard functions.

Next, plan for e-invoicing mandates. In a growing number of countries, invoices must be exchanged in structured formats over networks such as Peppol, where buyers and suppliers connect through accredited service providers in a four-corner model. Oracle Fusion supports Peppol UBL invoice messages and partner e-invoicing integrations, so a portal that accepts PDF uploads must not become a parallel channel that conflicts with the route your tax authority requires. Decide which suppliers submit through the portal and which through a network, and how duplicate invoices are detected.

Finally, treat identity, data security and adoption as design topics, not afterthoughts. Supplier users are external, so someone must own account provisioning, sign-in policy and removal of access when a contact leaves the supplier. Every screen must restrict a supplier to its own sites, orders and payments, and that rule should be tested explicitly, for example against the OWASP Application Security Verification Standard. Suppliers deal with many customers' portals, so segmenting them by volume, onboarding in waves and keeping a fallback channel during transition all affect whether they actually use it.