Reference · built on requestOperator by FibricProperty & tenants

Vendor SLA Watch

Work-order clocks compared with each vendor's contract terms, with an escalation, a chargeback, or a reassignment proposed on breach.

Request accessPricing ↗

About

A vendor contract says how fast they answer and how fast they finish. The work order says when they actually did. Vendor SLA Watch reads both. It reads Create, Assigned, Pick Up, Start, and Complete events and DtDue from Corrigo Enterprise, WORK_ORDER_STATUS_CHANGE and WORK_ORDER_OVERDUE events from MaintainX, and status updates from UpKeep or Limble CMMS. It reads the terms per vendor, trade, and priority from the SharePoint list, Google Sheet, or Smartsheet where you keep them, and the vendor's bills in QuickBooks Online or Corrigo.

On a breach it proposes the response: escalate with a note to the vendor, dispute the bill, or reassign the order. You approve the response. It withholds no payment and cancels no contract.

This is a reference listing. It documents what Fibric would read from Vendor SLA Watch and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Work order events from Corrigo Enterprise: Create, Assigned, Pick Up, Start, On Hold, Complete, and Cancel, with DtDue and LastActionDateUtc per order
  • MaintainX WORK_ORDER_STATUS_CHANGE and WORK_ORDER_OVERDUE events, UpKeep WORK_ORDER_STATUS_UPDATED events, and Limble task scheduled windows and completion dates
  • Contract terms per vendor, trade, and priority from a SharePoint list, a Google Sheets range, a Smartsheet sheet, or an Airtable table
  • Vendor bills: WorkOrderCost with ApStatus in Corrigo, Bill records with VendorRef in QuickBooks Online, and bills with WorkOrderId in AppFolio Property Manager
  • Vendors and their specialties in Corrigo and vendor contacts in MaintainX, for the alternative on a reassignment
  • On Hold reasons and notes on the order, so a delay the vendor did not cause is not counted against them

Proposed actions

  • Target capability: propose an escalation: a priority raise through Corrigo WoPriority, a WoNote to the vendor, and SendWorkOrderCommand so they are notified
  • Target capability: propose a chargeback: move the Corrigo WorkOrderCost to Disputed through ApStatusChangeCommand, or a VendorCredit in QuickBooks Online, with the breach cited
  • Target capability: propose reassignment to another vendor through Corrigo Assign, an UpKeep worker or team assignment, or a Limble task update
  • Target capability: propose a breach row in your terms table, as a SharePoint list item or an appended Google Sheets or Smartsheet row
  • Target capability: propose a comment on the MaintainX or Limble work order recording the clock, the term, and the decision

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Escalate the order the vendor has not picked up

    A Corrigo work order passes the response time in your SharePoint terms list with no Pick Up event. The operator proposes a priority raise, a WoNote, and SendWorkOrderCommand for your approval.

    With Corrigo Enterprise, Microsoft SharePoint

  • Dispute the bill for a late completion

    The Complete event lands after the completion term in your Google Sheet. The operator proposes moving the Corrigo WorkOrderCost to Disputed and a row in the sheet recording the times.

    With Corrigo Enterprise, Google Sheets

  • Reassign after the same vendor runs late again

    MaintainX sends WORK_ORDER_OVERDUE for the same vendor again. The operator proposes reassignment to the alternate named in your Smartsheet terms and a comment on the order.

    With MaintainX, Smartsheet

  • Credit the invoice, not the relationship

    An UpKeep work order completed late has a Bill in QuickBooks Online. The operator proposes a VendorCredit for the amount your terms specify, with the order times attached.

    With UpKeep, QuickBooks Online

Requirements

  • A CMMS or work order platform with timestamps per status: Corrigo Enterprise, MaintainX, UpKeep, or Limble CMMS
  • Contract terms in a readable table: a SharePoint list, Google Sheets, Smartsheet, or Airtable, with vendor, trade, priority, response time, and completion time columns
  • A finance connector holding vendor bills, where chargebacks are proposed: QuickBooks Online, or Corrigo AP statuses
  • Your clock rules: business hours, holidays, and which hold reasons pause the clock
Authentication
It reads orders, terms, and bills through the maintenance, file, and finance connectors you attach, with the scopes each grants; it holds no vendor portal login and no bank access.

Limits

  • It reads terms from a table you maintain. A clause that lives only in the signed contract PDF is not read.
  • Clocks run on the CMMS timestamps. A vendor who worked before pressing Start looks late, and the proposal shows each timestamp.
  • A dispute is a status or a credit record you approve. It pays no bill, withholds no payment, and ends no contract.
  • It reads the vendor's own portal nowhere. Their view of the clock is theirs to raise.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Vendor SLA Watch ↗

Questions and answers

What am I approving on a breach?
The escalation, the dispute, or the reassignment, with the evidence beside it: the order's timestamps, the term it broke, the hold reasons it excluded, and the bill if one exists. Approve, pick a different response, or mark the breach excused.
What is written down afterwards?
A receipt per breach: the order id, each timestamp, the term row cited, the response chosen, the note or command sent to the vendor, the AP status or credit id, the row added to your terms list, and who approved it.
Will it dispute a bill or drop a vendor without me?
It will not. A dispute is a proposed status change or credit that waits for approval. Reassignment waits too. It cannot pay, withhold, or terminate. Contract decisions remain with your staff.
Ask about Vendor SLA Watch

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy