Ask a team what it is entitled to under a software agreement and the answer usually comes from a spreadsheet someone keeps, not from the paper. The spreadsheet holds one figure. The order form, the amendment and the renewal between them may hold another.
The Entitlement Agent is the part of Vera AI by VendorBenchmark that reads the paper itself. It keeps one register of what each contract grants, with the page behind every line. Here is what it lists, how it ties the documents together and where it stops.
Every priced line, as the order prints it
The read answers 27 terms on every contract and keeps the sentence and the page behind each answer. On every priced line it captures what the paper states, and nothing it does not:
| Field | What the read keeps |
|---|---|
| Product and family | As the order names it, with its family in the vendor's own naming, such as Sales Cloud |
| Edition and part number | The tier, such as E5, and the part number where the order prints one |
| Quantity and metric | How many, and the metric the line is counted in |
| List and net price | The unit price paid, and the list price where the contract prints one |
| Discount | Computed from list and net, and only where a list is printed |
| Dates and ramp | The line's own start and end, any yearly price ramp, and the day signed |
| Source | The page and the words the line was read from |
The SKUs and discounts tab sets every line out that way, with the discount as a meter and the value as a bar. A unit price stated in another currency stays in that currency.
The register, in sample figures. Three Salesforce documents signed by three Salesforce companies, filed as one vendor. Each line keeps its quantity, the list and net price the order prints and the discount between them. Where the order prints no list, the line says so and keeps the net rate.
One vendor, however many companies signed
Large vendors sign through local companies. A UK order, an Irish order and a US master agreement are one relationship, even when three legal names sit on the paper. The agent files a document by the company you negotiate with, not the entity on the signature page, so all Salesforce is one Salesforce and all Oracle is one Oracle.
The other names are kept. They are listed once on the vendor's row as also filed as, and the estate workbook carries a sheet of legal entities: your companies, and the vendor companies that signed with each.
The documents connect, and the gaps show
An order form rarely stands alone. The Structure tab draws the estate the way the paper does: your organization at the root, a branch for each vendor, the master agreement on each branch, and every order, renewal, amendment and addendum under the document it names. Hover the line between two documents and the sentence that links them appears.
A document that names an agreement you do not hold draws as a dashed node and lands on Missing documents, with the document that names it, the page, the sentence and the annual value that rides on it. Request drafts the email to the vendor from those facts; Upload adds the paper.
Spend by year comes from the dates on the paper
Because every line carries its own dates, the agent can say what the estate costs in a given year without anyone keeping a forecast. Spend history adds up by year and vendor, prorated by the days each document is in force, with one time fees in the year they were signed.
The Inventory opens on eight figures, from documents on file and annual spend in force to SKUs and the weighted discount. Each vendor gets a page of its own, with the price history of each product across its orders, and Data on every chart opens the rows behind it.
The register holds what the paper grants, line by line, with the page it came from.
It reports what the paper says, and stops there
The agent reports what your contracts say and nothing else. When the read cannot settle a field, two competing amounts or handwriting, it goes to Review with the passage, the reading and the reason. You enter the value, confirm the reading or mark it as not in the document, and the answer is saved with your name and the page.
The register then feeds the agents that do other work. A right click on a document sends it to Human benchmark or to the Benchmark Agent. Holding installs against the lines you own is the work of Software Discovery+, and placing a price against what comparable buyers pay is the work of the Benchmark Library.
Where it sits among the contract agents
The register is the record the other agents read from.
- The day one read fills it: 500 contracts uploaded in the morning and read by evening.
- The Document Agent asks every contract the same question, with the clause on its page.
- The Contract Agent reviews one document clause by clause.
For the app itself, see the Entitlement Agent page. Our earlier post explains why the agent works like an application, with the report as its output.
What to do first
- Open the sample. Sample data shows the whole agent on a sample estate of 58 documents signed by 26 legal entities, with the links between them drawn.
- Upload one vendor's paper. The master, the orders and the amendments together, so Structure can tie them up.
- Settle the Review list. Confirm or correct each value the read was unsure of, starting with the lines that carry the most money.
- Export the workbook. Export workbook writes the register to Excel: documents, SKUs, spend by year, term ends, key terms and what is not on file.
Questions buyers ask
What does the Entitlement Agent read from each line?
The product and its part number, the quantity and metric, the unit price, the list price where the order prints one, the edition, the line's own dates and any price ramp, each with the page it came from.
Does it compute a discount when no list price is printed?
No. A discount is shown only where the contract prints a list price beside the net. Where it does not, the line keeps the net rate the paper states.
How does it treat a vendor that signs through several companies?
They file as one vendor. A contract signed by a vendor's UK or German company sits under the one vendor, and the other names are listed once on its row.
What if a document names an agreement we never uploaded?
It lands on Missing documents with the document that names it, the page, the sentence and the annual value under it. Request drafts the email to the vendor; Upload adds the paper.