A contract manufacturer's customers are large, and large customers buy through portals. The PO arrives as an Ariba or Coupa notification with the PDF attached, a confirmation is due within 48 hours, the ASN goes in the portal, and the Invoice is a PO flip with the price locked. Each step is the same information retyped. STRYKE enters the Order from the PO and does the rest from the Order.
What arrives
The portal paper trail.
Ariba notifications with a Process Order button and the PO PDF attached; Coupa, Jaggaer and Oracle iSupplier their own versions
Change notices listing up to three changed items with the original value
EDI 850s from the customers that run a VAN, and emailed PDFs from the ones that print from Outlook
Blanket POs with releases, and an acknowledgment clause of 48 hours, 72 hours or two business days
Vendor Invoices from component distributors and outside processors
What STRYKE does
Enter the Order, then answer the portal from it.
Each PO line matched to your part number and your quote; a price or revision that differs is held before anything is confirmed
The acknowledgment deadline and the customer's channel learned from your history, so the clock is watched
A change notice applied to the open Order with a revised acknowledgment, or held when it pulls a date in
The PO flip Invoice built from the Packing list, within the PO quantity the portal enforces
Vendor Invoices three-way matched to the PO and the Receiver
Where it lands
The ERP is the record; the portal is a channel.
The Order and the Job in JobBOSS², Epicor, Global Shop, Infor VISUAL, Made2Manage or your ERP
The Bill in QuickBooks Online or Desktop, Sage or Xero
The portal PO PDF, the confirmation number and the ship notice stored with the Order
Nothing installed in either system
What goes back out
Into the portal, from the Order.
Order confirmation in Ariba, Coupa, Jaggaer or Oracle with the confirmation number and estimated ship date
Ship notice with the packing slip number, carrier and tracking when the Packing list closes
Invoice as a PO flip, an 810 or a PDF, depending on the customer
Payments applied in the books when the remittance arrives, with deductions held open
“Four OEM customers, three different portals, and a two-hour window from one of them for approving a change inside lead time. We were missing confirmations. Now the confirmation is in the portal within the hour, from the Order, and the flip Invoice goes in the day the Packing list closes.”
Questions shops ask
Does it log into Ariba and Coupa for us?
Yes. It reads the PO from the notification and the attached PDF, enters the Order, and then confirms in the portal with the fields the buyer's form asks for. It does the ship notice and the Invoice flip from the same Order. A light account that can only reach the PO through the email link works too.
What about a change notice?
A change that moves a quantity or pushes a date out is applied to the open Order and re-acknowledged. A change that pulls a date in, or changes a price, is held for a person, because that is a promise or a margin decision.
Our customer gives us two hours to approve a change. Can STRYKE keep up?
The change is read and either applied or held within minutes of arriving; a held change is on the review list with the clock showing. What STRYKE will not do is approve a pulled-in date on its own.
$500 a month, flat
Every portal, every PO, every flip. Not per document, not per seat, not per system. Month to month. What the one price covers.
