AI System for Comparing B2B Orders with Contracts

The problem

When orders, contracts, pricing appendices and account details are held in different sources, their fields must be matched manually before a list of term differences and required approvals can be prepared.

The commercial operations specialist must compare every suggestion in the list of term differences and required approvals with the source record; missing or conflicting evidence must not replace the final decision.

If a newer protocol or campaign is not referred for separate review, invalid terms may be accepted; the record must not proceed without a human decision.

What we set out to improve

• Time taken for the draft list of term differences and required approvals to reach the commercial operations specialist for review with its supporting evidence
• Outcomes of records referred for human review because a newer protocol or campaign exists
• Number of suggestions corrected after identifying the risk of accepting invalid terms

How the system works

1. 01 Retrieve the order, contract, pricing appendix and account details from authorised sources using the record identifier
2. 02 Link source, date and version details to the shared work record
3. 03 Validate fields and units
4. 04 Prepare the list of term differences and required approvals with its supporting evidence
5. 05 Check for the exception: a newer protocol or campaign exists
6. 06 The commercial operations specialist accepts, amends or rejects the draft
7. 07 Write the approved decision and its source to the audit log

Methods we used

• A source-referenced shared data schema for the order, contract, pricing appendix and account details
• A decision structure that separates deterministic rules from AI suggestions
• A review screen showing the list of term differences and required approvals alongside the underlying evidence
• A mandatory human review queue when a newer protocol or campaign exists
• An event identifier that prevents duplicate processing

Where people stay involved

Data and security

Only the fields required for this decision should be processed from the order, contract, pricing appendix and account details. Access to source systems should be authorised separately from the commercial operations specialist role; personal, commercial and technical secrets should not be passed into the model context unnecessarily. Reads, suggestions and human decisions should be logged separately.

Who this suits

Frequently asked questions