Manage Seller-Facilitated Order (SFO) Rejections by Approvers Internally Within Requesting Agency

With this release, manage seller-facilitated order rejections by internal approvers within the requesting agency. When a seller-facilitated order (SFO) requires approval and an approver rejects it, the rejection can be handled inside the requesting agency process. When a servicing agency initiates an SFO and sends it to the requesting agency for approval, the buyer or contracting officer may change some of the order details before sending it to the requesting agency’s internal approvers (program official and funding official).

Internally, when a buyer submits the SFO, it can be rejected by the approver on the approval notification. This is treated as internal rejection for buyer to edit and resubmit the order for approval again. The program official or funding official can reject the order internally in the approval hierarchy. The buyer or contracting officer updates the order with additional information and resubmits it for approval so that program official and funding official approvers the order. When the order is rejected by the requesting agency approver, the order will not be sent to G-Invoicing instead it can be edited by preparer and submitted for approval again.

This feature gives agencies better control over rejection governance. Approvers can stop an SFO that does not meet internal policy, funding, GT&C, timing, or documentation requirements, while buyers can review the rejection and decide whether correction, resubmission, or partner communication is needed.
The enhancement is important because SFOs begin from partner-side activity but still require requesting-agency accountability. Internal rejection handling gives the requesting agency a structured way to document the decision, preserve approval history, and avoid sending incomplete or unexplained responses back to the servicing agency.

Steps to enable and configure

You don't need to do anything to enable this feature.

Tips and considerations

  • Review IGT order approval workflow and roles for SFO rejection handling.
  • Test SFO rejection scenarios for approver rejection, buyer review, and final routing.
  • Capture clear rejection reasons so the buyer can determine whether to correct, resubmit, or route the rejection to the servicing agency.
  • Monitor approval history for SFOs that are rejected internally to avoid stalled transactions.

Key resources

Transfer of Information
R12.2.13 TOI: Implement and Use Contract Lifecycle Management for Public Sector - G-Invoicing