For readers new to back-office ops

Glossary

Terms used across the four models, in plain language. If a word in a guide or workbench sends you here, this is meant to be the last stop, not another rabbit hole.

Legal · contract review

Playbook: A company's written list of acceptable and unacceptable contract positions — what liability cap it will sign, what IP terms it won't. A playbook exists so two different reviewers reach the same answer on the same clause.
Redline: A tracked-changes edit to a contract clause, showing exactly what's being added, removed, or changed from the counterparty's draft.
Fallback language: The pre-approved alternate wording a company will offer when its first-choice position gets rejected — decided in advance, not improvised mid-negotiation.
MSA: Master service agreement — the umbrella contract that sets the general terms between two companies, usually with individual work orders sitting underneath it.
Indemnification / liability clause: The part of a contract that decides who pays if something goes wrong — a data breach, a missed deadline, a third-party lawsuit — and how much.
DPA: Data processing addendum — a contract attachment specifying how one company may handle another's data, usually required alongside any agreement involving personal information.

Finance · invoice & close

3-way match: Checking that an invoice, the purchase order that authorized it, and the receipt confirming goods arrived all agree — on item, quantity, and price — before an invoice is approved for payment.
Accrual: Recording an expense or revenue in the month it actually happened, even if the invoice or cash hasn't moved yet. Month-end close can't finalize until unresolved invoices are either matched or accrued.
GL coding: Assigning a transaction to the correct line in the general ledger — the company's master record of every account. Miscoded invoices distort every report built from that ledger.
Vendor master: The company's system-of-record list of approved vendors and their payment details. Changing it is treated as sensitive, because it's a common target for payment fraud.
Close certification: The controller's formal sign-off that a month's books are complete and accurate — the last human step before financials go out.

Procurement · vendor risk

Non-renewal notice window: The deadline by which a company must formally decline to renew a contract, or it automatically continues. This date is usually earlier — sometimes much earlier — than the renewal date itself.
Addressable spend: The portion of total spend that could realistically be renegotiated, resourced, or consolidated — as opposed to spend locked in by regulation, single-source supply, or long-term contracts.
Counteroffer: A drafted response to a supplier's price or terms proposal, built from the company's negotiating position — a starting point for a buyer, not a final answer.
SOC 2 / ISO certification: Independent audits a vendor undergoes to prove it handles data or quality securely. Both expire and need renewal — a lapsed certificate doesn't mean a vendor got worse, but it does mean nobody's currently checking.
Renewal cap: A contractual limit on how much a vendor can raise its price at renewal — the number a new quote should be checked against before anyone assumes an increase is normal.

Audit · expense & card

Split purchase: Breaking one purchase into several smaller charges, each staying just under an approval threshold — sometimes intentional, sometimes an artifact of how a vendor processes payment.
Duplicate receipt: The same purchase submitted for reimbursement twice, often under different filenames or slightly different descriptions, which is why matching by image content — not filename — catches it.
Anomaly / confidence score: A number expressing how strongly a transaction or pattern matches known risk indicators. High confidence means "look at this first," not "this is proven."
Continuous audit: Screening every transaction as it happens, instead of reviewing a sample after the fact. The tradeoff isn't accuracy — quarterly sampling is accurate on what it checks — it's coverage.
Pre-settlement hold: Pausing a transaction before the card payment finalizes, so a suspicious charge can be reviewed while recovery is still simple, instead of after the money has moved.

Across all four

Shadow mode: Running a model's recommendations alongside — not instead of — a human's actual decisions, to see how often they'd agree, before anything is allowed to act on its own.
Exception: Anything that doesn't automatically clear — a mismatched invoice, a flagged clause, a risky vendor, a linked transaction. The whole point of these models is shrinking the noise around exceptions, not the exceptions themselves.