Automations / Contract Reconciliation

Contract Reconciliation

Needs attention

Customer service agreement terms read out of the signed documents in SharePoint, compared with what Salesforce holds, and pushed back once a person approves them.

OwnerDana WhitfieldCadenceWeekly, Monday 06:00Last run23 min ago · 36 customers evaluated, 7 held on conflicts or missing fieldsNextin 6 d
Held for review
15customers
3 with conflicting documents · 5 missing required fields
Ready to push
14customers · 37 fields
Every required check passed. Approval is by customer.
No unique account
1customer
Two Salesforce accounts share the legal name

Last run

Every customer against the run before. The filters above do not narrow this row.

Customers evaluated
36
+1vs 35 · 72 source files
Fields populated, median
46/62
+2vs 44 · 74% of the schema
Pushed to Salesforce
6
−18vs 24 · updates logged
Held or blocked
16
+12vs 4 · writeback held
How customers were matched
72%on an exact signal
ReadyHeld
Where customers stand
3672 source files in view
ReachedStopped here
Documents read100%36 cust.
Account matched1 stopped97%35 cust.
Fields extracted97%35 cust.
Reconciled with Salesforce15 stopped97%35 cust.
Approved56%20 cust.
Pushed17%6 cust.

Customer queue

Open one for the fields read from its documents, what Salesforce holds today, and the clause each value came from.

36 customers
36 customers
Recent runs
Full log
  • 36 customers evaluated, 7 held on conflicts or missing fieldsSep 8, 6:42 AM · 18m 12s · 36 items · 7 flagged
  • 24 pushed to Salesforce, 4 heldSep 1, 6:00 AM · 19m 41s · 36 items · 4 flagged
  • GATX Amendment 2 indexed and re-readAug 25, 6:00 AM · 21m 8s · 35 items · 3 flagged
Reads from
Connections and approved data points.
Data Tree
Microsoft SharePointSalesforce
Business objectCustomer ContractsDimensionCustomersDimensionTime
Setup
What the next run applies, and how it reads.
Extraction profile
Eagle contract schema · 62 fields
Evidence package
Citation and original wording
Auto-accept threshold
High confidence
Conflict precedence
Newest signed document
Review gate
Hold conflicts and missing required fields
Writeback mode
Approval required by customer
Trigger
A new or amended document in the Customer Contracts library, plus a weekly sweep of every active customer
AI role
Field extraction with a citation for every value, and plain explanations of each conflict
Rules
  • The newest signed document wins when a master agreement and an amendment disagree
  • Every extracted value keeps the clause it was read from and the original wording
  • A customer is only pushed once a person approves it, and the replaced value is retained