Basic transaction agreements and individual orders

Hello, this is Legal Agent.

A basic transaction agreement often gets treated as background paperwork once a company has signed one with a familiar counterparty, on the theory that the real terms live in each purchase order. In practice it is the foundation for every order placed under it, and a weak basic agreement is hard to fix through individual orders alone.

What a basic transaction agreement covers

A basic transaction agreement sets the common conditions for a continuing supply relationship between, for example, a manufacturer and a parts supplier, or a SaaS company and a development vendor. It typically fixes how individual orders are formed, delivery and acceptance, payment terms, non-conformity liability, title and risk transfer, IP, confidentiality, subcontracting, damages, termination, anti-social-forces exclusion, and governing law, so that the parties do not renegotiate these points with every order.

Priority against individual orders

The first practical question is how the basic agreement relates to each purchase order or SOW. A ten-business-day acceptance period in the basic agreement can conflict with a five-day period in an individual order; a damages cap based on annual volume can conflict with an order-level cap in an SOW. Review should confirm which document forms the individual contract, how conflicts are resolved, and whether informal order changes by email match the process the contract describes.

Delivery, acceptance and non-conformity liability

For agreements covering goods, manufacturing or development work, review should check whether specifications are fixed in the contract or an exhibit, whether the acceptance period and deemed-acceptance conditions are realistic, and how remedies for non-conforming performance (cure, replacement, price reduction, damages and termination) relate to each other and to the applicable time limits.

Payment terms and damages sized to the relationship

Because a basic agreement governs many transactions over time, payment timing, late-payment interest and rights to suspend performance affect day-to-day collections, not just disputes. Damages caps should be considered against realistic exposure: whether the cap applies per order or annually changes the outcome considerably when several orders overlap, and confidentiality or IP breaches are commonly carved out as exceptions.

Checking operations against the paper

A common gap is reviewing the basic agreement in isolation from how orders actually happen: informal email orders where the text requires a purchase order and acknowledgment, or routine use of subcontractors where prior consent is technically required. Reviewing purchase orders, specifications, acceptance records and existing workflows alongside the contract closes this gap. Because the agreement stays in force for years, it is also worth revisiting at renewal, particularly once transaction volume or the categories of data handled have grown since signing.