The document discusses Inovis Scorecarding capabilities which allow buyers and sellers to track partner performance. It describes how scorecards can be automatically created from transaction data validation to monitor partners. Over 50 built-in business rules cover content, structure, data integrity, and process mismatches that are used to calculate metrics and create scorecards displaying key performance indicators. The scorecards can then be shared and drilled down to find root causes of issues in order to drive partner remediation programs.

1. Inovis Scorecarding Capabilities How Buyers and Sellers Can Track Partner Performance Using Inovis Actionable Intelligence

2. Inovis Partner Performance Suite CUSTOMER SUPPLIER Electronic Transactions Purchase Orders Shipment Notifications Invoices Deductions Community Management Deductions Management Operations Management Scorecarding Management Four on-demand software modules to manage trading partners

3. How Actionable Intelligence works Inovis Actionable Intelligence Validation engine Supplier Customer B2B Data B2B Data carbon copy Drill-down Workflow/Alerts Dashboards/Scorecards Compliance guides browser browser transactions

4. About Scorecarding Automate your scorecards Partner scorecards are created and shared automatically from data validation, enabling a portfolio approach to partner management. Track partner performance Create scorecards by product category, process or facility and kickoff remediation programs to fix chronic transaction problems. Leverage over 50 built-in business rules: Content Rules (missing ASN field) Global Structure Rules (shipments must contain at least one order) Process Rules (PO quantity must match ASN quantity) Timing/ Process Rules (Missing proof-of-delivery)

5. Scorecarding Screenshot Example Linking scorecard metrics to root-cause data.

6. Track Deductions by Partner Track Remediation Programs Collaborate with Partner Scorecarding Example: Linking scorecard metrics to root-cause data.

7. Drill-down to problem transactions

8. Shared visibility to root-cause data helps partners quickly fix underlying problems

9. Built-in Scorecarding Metrics Common Timing Errors, Document Errors & Process Errors

10. Global Structure Rules A shipment must contain at least one order An order must reference a shipment Missing required segments (i.e., BSN, HL, TD5, LIN, etc.) Duplicate segments (where duplicates are not allowed) Unpaired segments (i.e., address must come with name in an N1/N4 pair) Pick Pack Detail ASN (Shipment/Order/Pack/Item) An order must contain at least one tare or pack A tare must contain at least one pack or item A pack must contain at least one item Items must reference a pack or tare (should not reference an order) Packs must reference a tare or order Tare must reference an order Standard Pack Detail ASN (Shipment/Order/Item/Pack) An order must contain at least one item An item must contain at least one tare or pack Packs must reference a tare or item Tares must reference an item Items must reference an order Summary ASN (Shipment/Order/Item) Summary ASNs should not contain tare or pack information An order must contain at least one item Items must reference an order Examples of Built-in Mapping/Structure Rules

11. Examples of Built-in Data Integrity Rules ASN Content Errors Invalid sender ID or vendor number Invalid transaction purpose code Invalid shipment number Invalid structure code Invalid date/time format Invalid carrier reference number Invalid BOL number Invalid SCAC code Invalid payment terms (FOB) Invalid ship from / ship to location Invalid tare or pack number Invalid count, total, or quantity Invalid item number format Invalid unit of measure Other conditional field pairs (i.e., time / time zone, qualifier / value) Other code list validations Other required field validations

12. Process (PO/ASN) The PO number in the ASN must reference a valid PO The PO number in the ASN should not reference a canceled PO The item number and quantity in the PO must be matched by the ASN (short fill) The item number in the ASN must exist on the PO (unknown item / substitution) The shipped unit of measure in the ASN does not match the ordered unit of measure The payment terms in the ASN must match the payment terms in the PO For collect shipments, the SCAC in the ASN must match the SCAC specified in the PO (or a preferred carrier list) The ship date in the ASN must be after the start ship date in the PO The ship date in the ASN must be before the cancel date in the PO The ship to location in the ASN must match the ship to location in the PO The mark for location in the ASN must match the mark for location in the PO Process (ASN/Shipment Status) The carrier pickup notification must be received within XX hours of the shipment date specified in the ASN The carrier delivery notification must be received within XX hours of the delivery date specified in the ASN A carrier pickup notification was received for an unknown shipment (missing ASN) Process (ASN/ASN) Only one ASN marked as original can be sent per shipment (duplicate) A replacement ASN cannot be received prior to an “original” ASN The ASN create date and time in the replacement ASN is earlier than in the previous ASN received A replacement ASN was not received within XX hours of rejecting the original ASN The ASN was not received within XX hours of the ship date and time (late ASN notification) Examples of Built-in Process Mismatch Rules