Commercial Contract Negotiation: Issue Matrix and Concession Log

A foreign business negotiating with an Israeli counterparty may have several versions of the contract but no clear record of what each concession bought. A price reduction appears in one email, a longer payment period in another, and a liability exception in the latest redline. Before signature, someone needs to check whether those changes still form an acceptable bargain.

This guide focuses on two working documents: the issue matrix and the concession log. It complements our guide to negotiating a commercial contract with an Israeli company. It is a preparation method, not a standard contract or a statement that any proposed clause will be enforceable.

A redline records the words that changed. A concession log should record why they changed and who approved the trade.

Start with one issue matrix

The matrix should put the business team and legal team on the same page. Use a separate entry for each material issue, rather than a row for every sentence in the draft. For a supply agreement, the first entries might cover acceptance, payment timing, delivery responsibilities, liability and the exit process.

For each issue, record:

• Business objective: what the business needs to achieve.
• Current proposal: the actual wording or commercial position on the table.
• Exposure: the financial, operational or legal risk that needs review.
• Preferred position: the opening proposal, with a short reason.
• Fallback: the alternative that may be acceptable, subject to its stated conditions.
• Approval owner: the person who can approve a departure from that position.
• Status: open, agreed in principle, awaiting approval or reflected in the controlling draft.

A fallback is not permission to accept it in every setting. A longer payment period might depend on a deposit or a lower credit limit. Keep that condition beside the fallback so that it is not lost when the negotiation moves quickly.

Make each concession a traceable exchange

The concession log follows the negotiation over time. Record the date, draft version, issue, movement proposed, reason, reciprocal change requested and approval status. If the other side accepts only part of a package, mark the remaining conditions as open.

Consider a hypothetical buyer asking for a longer acceptance period. The supplier might consider that change if the parties also define the acceptance test, identify the reviewer and address payment for undisputed work. These are proposed negotiating options, not terms that apply automatically. The signed documents and applicable law still need review.

Do not mark a package as agreed merely because one clause now contains the preferred wording. Check the related schedule, purchase order and commercial email. A concession can lose its intended value if another document reverses it.

In our experience, the log is most useful when it explains the commercial reason for a change in plain language. A later reviewer should be able to understand the decision without reconstructing the entire email chain.

Keep valuation honest

Where possible, describe the cost of a proposed change using the transaction’s own information: payment dates, order volumes, implementation work, stock commitments or transition tasks. Separate an estimate from an agreed amount, and record the assumptions behind it.

Some risks cannot sensibly be reduced to one number. Confidentiality, data use and dependency on a critical supplier may require a separate review. The matrix should make that uncertainty visible, not hide it behind an invented market benchmark.

For an additional commercial perspective on data-use trade-offs, see the SourceX guide for dealmakers. It is not a substitute for checking the governing law, privacy duties and the proposed data use.

Separate internal approval from an external offer

Name who may propose a change, who may approve it and who may communicate the approved position. Keep internal discussion separate from messages sent to the counterparty. An approval inside the business should identify the conditions it covers and the version reviewed.

For AI-assisted drafting or procurement workflows, use the same discipline. Define which outputs need human review, which people may approve a proposed commitment and how the business records the final document. Do not assume that a system-generated message establishes authority or resolves attribution. Those questions need transaction-specific advice.

Review the whole bargain before signature

Before signing, compare the issue matrix, concession log and final agreement. Confirm that each accepted package appears in the correct document, unresolved points have not been silently treated as agreed, and the people responsible for implementation understand the result.

• Does the payment clause use the acceptance process actually negotiated?
• Do delivery responsibilities match the selected delivery term and named place?
• Do liability provisions, remedies and exit arrangements work together?
• Is there a clear hierarchy between the main agreement and its schedules?
• Are the relevant entities, signatories and notice details correct?
• Have any open legal, tax, regulatory or enforcement questions been referred for advice?

Where delivery terms are relevant, the U.S. International Trade Administration’s explanation of Incoterms and the ICC’s Incoterms materials are starting points for further reading. They do not replace the agreed contract or advice on the transaction.

Carry the record into implementation

After signature, give finance and operations the agreed obligations, owners and relevant dates. Keep the final agreement with its schedules and approval record. A working log should support implementation, not become a second, conflicting version of the contract.

If a payment dispute later arises, preserve the agreed documents, performance records, invoices and correspondence. A separate guide for unpaid invoice claims discusses another jurisdiction’s process; it does not establish the procedure or remedies available in Israel.

Additional background reading

The original research resources below cover different samples and markets. No numerical benchmark from them is relied on in this article, and none establishes Israeli legal requirements: research on dispute-resolution clauses; contract-management research; AI-agent adoption research; a non-official electronic-signature overview; and contract benchmarking discussion. Electronic execution and signatory authority should be checked separately before reliance.

For help reviewing the issue matrix or the proposed trade-offs in an agreement with an Israeli counterparty, contact our team. Start with the contract type, parties’ jurisdictions and the next decision date. Sensitive documents can follow through an appropriate channel. RNC Group advises businesses on commercial agreements and disputes.

Further background resources: rnc.co.il

Disclaimer: This article provides general information only, is not legal advice and does not create an attorney-client relationship. It may contain omissions or errors. Applicable law, contract wording and the facts must be reviewed before taking or refraining from action.