A cross-dependency is a contract term where something about one product depends on something about another. They are increasingly common in large service contracts because they reward overall commitment. They are also among the least enforced terms we see.
Three common examples
Bundle discounts. Beverages drop from $3.20 to $2.60 a unit once total meal volume passes 150,000 a month. The person checking the beverage invoice has no view of meal volume.
Conditional waivers. Equipment rental of $12,000 per site is waived once volume passes 100,000 a month across all sites, with a 50% waiver from 80,000. The rental invoice arrives on the first of the month, before anyone knows the volume.
Sliding surcharges. A special-meals surcharge is capped at 15% while special meals stay under 8% of volume, but rises to 22% above that. This one can cut both ways, so you need to watch it as volume moves.
Why they fail
Each of these needs information from two places at once: the invoice for the affected item and the running total of the triggering metric. In most organisations, those sit with different people, in different systems, at different times of the month.
Making them enforceable
ContractSense keeps running totals for every contract and period. Each time a transaction arrives, totals update and every cross-dependency is re-checked. When a threshold is crossed, the affected price or waiver changes, and any invoice that does not reflect it is flagged with the clause and calculation.
See all three working together in the airline catering example.