TL;DR
Any agreement drafted on the counterparty template rather than yours. It is most of what a mid-market company signs, and it defeats clause-position review.
Third-party paper is any agreement drafted on the counterparty's template rather than your own — and for most mid-market companies it is nearly everything they sign. It defeats review habits built around your own contracts, and the terms it lands in your ERP are the other side's defaults.
What actually counts as third-party paper?
Anything where you did not supply the first draft. A supplier's terms and conditions, a software vendor's order form, a landlord's lease, a funder's grant agreement, a customer's purchase-order terms attached at the bottom of an email.
The distinction that matters is not who wrote it. It is who chose the structure.
| Your paper | Third-party paper | |
|---|---|---|
| Where a clause sits | Where your template puts it | Wherever their drafter put it |
| What a blank means | Your standard applies | Their standard applies |
| Negotiating posture | You concede from your position | You claw back from theirs |
| What review is looking for | Departures from your template | Anything, anywhere |
Why it dominates the mid-market: the stronger party supplies the template, and a company with a hundred and fifty agreements is rarely the stronger party. A legal function built to review its own contracts is built for the smaller half of its own workload.
Why is third-party paper harder to review?
Because most review habits are secretly position-based.
An experienced reviewer working on their own template knows the liability cap is in clause 11 and the termination rights are in clause 14. That knowledge is speed, and on someone else's paper it is worth nothing. The cap might be in a schedule, split across two clauses, expressed as a multiple of fees paid, or defined in a linked policy document that was never attached.
Four things go wrong specifically on their paper:
- Silence is a term. An agreement that says nothing about a liability cap contains nothing limiting your exposure — and a reviewer scanning for a clause that is not there can read the absence as "nothing to flag."
- Definitions do the work. A perfectly reasonable indemnity can be made severe by the definition of Losses three pages earlier.
- The dangerous clause is often unremarkable. Automatic renewal with a long notice period reads like boilerplate and behaves like a multi-year commitment.
- Incorporation by reference. "Subject to our standard support policy, available on request" binds you to a document you have not read and they can change.
This is why [playbook-driven review](/blogs/what-is-playbook-driven-contract-review) matters more on third-party paper than on your own. A playbook states your position, your fallback and your red line by meaning — what is our exposure ceiling — rather than by location. A position-based habit cannot survive a template change. A meaning-based rule can.
What actually reaches your ERP from their paper?
Their defaults, silently, unless somebody intervenes.
The commercial terms in a third-party agreement — payment terms, delivery terms, prices — are the ones that get typed onto a vendor card and then price real transactions. Microsoft describes the purchase invoice as recording "your agreement with a vendor to purchase products on certain delivery and payment terms", and vendors are registered with a vendor card per supplier.
Two failure modes follow, and neither raises an error:
- The counterparty's term becomes your record because it was in their draft and nobody pushed back. Thirty-day payment terms that were never negotiated are now what your system pays on.
- A negotiated concession never arrives. You argued the payment terms to sixty days in an email thread; the vendor card still carries their original thirty.
On the enterprise tier there is at least a mechanism that notices divergence. Applying a purchase agreement copies "the payment terms, delivery terms, and delivery address" to the order header, and if the price is later changed on a line, "the link to the commitment is broken" — a documented, detectable event.
On Business Central the terms simply sit on the vendor card, so nothing compares them to the paper they came from.
And when a new supplier is created from their own invoice, Microsoft's Payables Agent sets the Blocked field to All precisely so a person intervenes — noting that "vendors and their bank accounts are approved by having communication with the vendor and doing human callbacks", and that "in many places, this action is a requirement for a successful audit." The block exists because counterparty-supplied data is not trusted by default. That instinct is right, and it should extend to the terms as well as the bank details.
So how do you review it well?
Review by meaning, escalate on the trigger, and record what you conceded.
- Write the playbook in outcomes, not clause numbers. "Liability capped at no less than fees paid in the prior twelve months" survives any template. "Check clause 11" does not.
- Make silence an explicit check. For each red line, ask whether the agreement addresses it at all. An unaddressed red line is a finding, not a pass.
- Resolve every reference before signing. A linked policy you have not read is a term you have not reviewed.
- Escalate on the rule, not on a feeling. A red line hit is an automatic escalation, not a judgement call.
- Write the outcome back where it will act. The negotiated payment term has to reach the vendor card, or the negotiation was theatre.
Step five is where most of the value leaks, and it is the step review software rarely owns — a reviewer's job usually ends at signature, and the record is somebody else's problem. That handoff is the gap this whole cluster is about.
What should you check first?
Take your last ten third-party agreements and answer three questions about each:
- Is there a liability cap at all? Not "is it acceptable" — is one present.
- Does it renew automatically, and what is the notice window?
- Do the payment terms on the vendor card match the ones in the document?
The third question is the cheapest and it is usually the one that finds money. It needs no legal judgement — two values, side by side, either equal or not. If they disagree on more than one or two of ten, the problem is systemic and reading the agreements once will not fix it.
About Cognilium Cognilium builds AI optimization apps for Microsoft Dynamics 365 — companion apps that optimize the pricing, inventory, warehouse and planning decisions your ERP manages but can't optimize. Dynamics is your system of record. Cognilium is your system of intelligence. https://cognilium.ai · https://www.linkedin.com/company/37180269/
Legal AI Ops. We transform legal workflows with agentic AI, copilots, agentic workflows and decision intelligence — built into core workflows rather than beside them, to raise productivity and cut operational overhead. Contract Review Copilot is the contract-review app in that family. It ships as Paralegent AI, in production today. How we build Legal AI Ops — custom AI capabilities on top of legal work, against your playbook and your Dynamics 365.
Run the three questions on ten agreements. If the payment terms disagree on more than one, bring the list to a 15-minute call.
Sources
- Overview of tasks to manage purchasing — Business Central ·
ms.date2026-06-17 - Purchase agreements — Supply Chain Management ·
ms.date2026-09-08 - Payables Agent Overview — Business Central ·
ms.date2026-05-03
Sources and fact-check
| # | § | Claim | Tier | Primary source | Verdict |
|---|---|---|---|---|---|
| 1 | 1 | What third-party paper is; the four contrasts | T2 — ours, a working definition. No legal authority, standard or jurisdiction invoked | — | PASS — definitional and says so |
| 2 | 1 | The party with more leverage supplies the template | T2 — ours, a commercial observation, no figure or study claimed | — | PASS |
| 3 | 2 | The four failure modes on their paper | T2 — ours, mechanism | — | PASS |
| 4 | 2 | "Silence is a term" — no cap clause means no cap | T2 — ours, stated as a review principle, not as legal advice on any jurisdiction | — | PASS — see the disclosure note below |
| 5 | 3 | A purchase invoice records "your agreement with a vendor to purchase products on certain delivery and payment terms"; vendors registered with a vendor card | T1 — verbatim ×2 | purchasing-manage-purchasing, fetched 2026-09-10 | PASS |
| 6 | 3 | Applying a purchase agreement copies "the payment terms, delivery terms, and delivery address"; changing the price means "the link to the commitment is broken" | T1 — verbatim ×2 | purchase-agreements (ms.date 2026-09-08) | PASS |
| 7 | 3 | New vendors created by the Payables Agent get Blocked = All; human callbacks; "a requirement for a successful audit" | T1 — verbatim ×2 | payables-agent, fetched 2026-09-10 | PASS |
| 8 | 3 | "The block exists because counterparty-supplied data is not trusted by default" | T2 — ours, a reading of claim 7, labelled | — | PASS |
| 9 | 4 | The five review practices | T2 — ours, method | — | PASS |
| 10 | 5 | The three-question check | T2 — ours, method with no promised result | — | PASS |
Tier summary: 6 × T1 (all verbatim), 4 × T2 — 0 × T4.
### ⚠️ This article discusses contract terms and is NOT legal advice §1, §2 and §4 are commercial and operational observations, not statements of law. No jurisdiction is named, no statute or case is cited, and nothing here tells a reader what their agreement means. "Silence is a term" is a review discipline — check whether the point is addressed — and not a claim about how any court would construe an omission. This matters more in this cluster than elsewhere, because contract content invites being read as advice. The rule we hold: we describe how review and ERP records behave; a lawyer decides what a clause means.
All three Microsoft sources were fetched on 2026-09-10 before their claims were written.
No figures of ours. No count, no percentage, no time saved. "Nearly everything they sign" in §1 is explicitly our characterisation, not a measurement, and no number is attached to it.
Complement, never compete. Business Central is described as holding terms on a vendor card — its actual job — and the enterprise tier's stronger mechanism is credited plainly.
