Reference · built on requestOperator by FibricSales, quotes & revenue

Contract Lapse

Catches orders placed against expired agreements or lapsed negotiated prices and proposes an extension, a requote, or a hold.

Request accessPricing ↗

About

Contract Lapse checks each new sales order against the agreement that set its prices. The agreement may be a Salesforce Contract with EndDate and StatusCode, a signed document in Docusign read through Envelopes:listStatusChanges, a PandaDoc document with expiration_date, or a price sheet in SharePoint or Google Drive that carries a valid-until date.

When an order arrives in Business Central or NetSuite for a customer whose agreement has ended, or whose lines use a negotiated price the sheet no longer supports, it proposes one of three things: extend the agreement, requote the order at current prices, or hold the order. Sales or finance chooses. The order is untouched until then.

This is a reference listing. It documents what Fibric would read from Contract Lapse 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

  • New Business Central salesOrders with customerNumber, orderDate, and lines carrying unitPrice and discountPercent; NetSuite sales orders through the REST record q filter
  • Salesforce Contracts with AccountId, StartDate, EndDate, StatusCode, Pricebook2Id, and SpecialTerms
  • Signed agreements in Docusign through Envelopes:listStatusChanges, with status, completedDateTime, expireDateTime, and custom_field values; Connect events as status changes
  • PandaDoc documents through GET /public/v1/documents with status, date_modified, and expiration_date
  • Price sheets in a SharePoint library through driveItem children, or in Google Drive through files.list, read for item, price, and valid-until columns
  • Current list prices in the ERP: Business Central items with unitPrice and lastModifiedDateTime, for the requote

Proposed actions

  • Target capability: propose an extension draft: a Docusign agreement from a template through Envelopes:create with status created, or a Salesforce Contract with a new EndDate
  • Target capability: propose a requote: each order line shown with the lapsed price and the current unitPrice, applied through PATCH salesOrderLine only after approval
  • Target capability: propose a hold on the order, recorded as a task and a customer note, so fulfilment waits until a person decides
  • Target capability: propose a task for the account owner naming the agreement, its end date, and the order waiting on it

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

What you can build

  • Salesforce Contract ended, Business Central order arrives

    Match the order's customer to the Account, read the Contract's EndDate and StatusCode, and propose extend, requote at current unitPrice, or hold.

    With Salesforce Sales Cloud, Microsoft Dynamics 365 Business Central

  • Docusign expiry against NetSuite orders

    Read completedDateTime and expireDateTime through Envelopes:listStatusChanges, filter NetSuite orders by customer, and propose an extension draft from your template.

    With Docusign eSignature, NetSuite

  • Price sheet in SharePoint

    Read the customer's price sheet from the library, compare each order line's unitPrice with the sheet and its valid-until date, and propose the requote.

    With Microsoft SharePoint, Microsoft Dynamics 365 Business Central

  • PandaDoc agreement lapsed

    List documents with status document.completed and an expiration_date in the past, and propose a hold plus an owner task for any order placed after it.

    With PandaDoc, HubSpot

Requirements

  • An ERP that exposes new sales orders and their lines by API: Business Central or NetSuite
  • Agreements with an end date somewhere readable: Salesforce Contract, Docusign, PandaDoc, or a dated price sheet
  • A rule for what counts as negotiated: a price book, a sheet, or a discount field on the customer
  • An approver in sales for extensions and requotes and one in finance for holds
Authentication
An ERP API user with sales order read and line write rights, a CRM token with contract scopes, an e-signature integration key with read access, and drive read permission such as Files.Read or drive.readonly.

Limits

  • It reads end dates that exist as fields. A scanned agreement with the date only in the text is flagged as unreadable, not judged.
  • A requote uses the ERP's current unitPrice. Tiered or volume pricing outside the item record is not computed.
  • It never sends an agreement. A Docusign draft is created with status created and waits for a person to send it.
  • Orders already shipped are outside its scope. It watches orders as they arrive.

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 Contract Lapse ↗

Questions and answers

What does sales or finance approve?
One of three proposals: extend, requote, or hold. Each shows the order, the agreement and its end date, and the lines whose price rests on it. A requote shows the lapsed and current price per line. The person picks one or rejects all three.
Does it change prices on the order by itself?
No. A requote is a proposal with both prices shown. Lines are updated only after approval, and the entry keeps the original price so it can be restored.
What record is left?
Order id, customer, the agreement read and where it lives, its end date, each line compared, the proposal, the decision, who made it, and when. If an extension draft was created its id is recorded so it can be voided.
Ask about Contract Lapse

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