How to Escrow Deposits Against Witnessed Acceptance for Reserved B300

Consider an illustrative procurement failure: a founder approves a deposit for a reserved Supermicro HGX B300 award. The supplier calls the funds “held against acceptance,” but the wire goes into its operating account. When the witnessed test is postponed, procurement requests a refund. The supplier says the deposit has already funded upstream commitments.

The problem is not the invoice date. It is custody and release authority. A promise to refund money is different from keeping that money outside the supplier’s control.

For Pacific Intelligent Technologies, Inc., the procurement lesson is straightforward: negotiate the funds-control mechanism alongside the award, not after the deposit request arrives. The checklist below is for commercial planning and counsel review, not legal advice.

1. Identify who actually controls the deposit

Start with a three-party escrow arrangement—or another counsel-approved structure—that identifies the buyer, supplier, and independent funds holder. Do not assume an account labeled “escrow” creates the protection procurement expects.

Before wiring, ask counsel and treasury to confirm:

• Custody: Who owns and administers the account, and are funds segregated from operating cash?
• Instructions: Which signed agreement governs deposits, releases, refunds, fees, and account changes?
• Authority: Can the supplier withdraw, pledge, redirect, or otherwise access funds without the agreed authorization?
• Failure exposure: What happens if the supplier or escrow provider becomes insolvent?
• Verification: How will treasury independently authenticate account details and changes?

Distinguish money deposited with an escrow holder from a buyer-retained holdback that has not been paid. Both can restrict supplier access, but their administration and legal treatment differ.

If the supplier needs some money immediately to secure upstream inventory, identify that amount explicitly as an advance—not protected escrow after release. Counsel should review separate recovery protections, including any proposed guarantee or security arrangement.

2. Make release depend on a documented witness record

Acceptance criteria define what must pass. Escrow instructions define what evidence permits money to move. Keep those documents linked without asking the escrow provider to judge GPU performance.

Reference the executed acceptance exhibit by version and require a release packet containing:

• The award identifier and applicable Supermicro HGX B300 configuration.
• A serial-number manifest identifying the units covered.
• The witnessed acceptance report, test date, witness identities, and required signatures.
• The supporting logs or evidence location specified in the exhibit.
• An exception register showing unresolved items.
• A release certificate stating the exact amount authorized and remaining balance.

Define the authorized witnesses and approvers before testing. Supplier-only screenshots or an invoice marked “accepted” should not replace the agreed witness record.

Procurement should also resolve whether remote witnessing is permitted, how substitutions are approved, and how incomplete packets are rejected. The escrow holder generally checks specified documents and instructions; it should not be expected to resolve technical disagreements.

For the award context, review reserved GPU capacity information, then carry the negotiated evidence requirements into the actual escrow instructions.

3. Allow partial release only against separable accepted units

Partial release can keep a usable portion of an order moving without surrendering leverage over everything else.

Attach a release allocation table to the escrow agreement. Each row should connect an identifiable unit or lot to its allocated deposit, required release packet, and residual holdback. Require a reconciliation after every release.

Do not let “most systems passed” authorize release of the entire deposit. Likewise, avoid an arbitrary percentage deduction that leaves unresolved units with little money behind them.

Partial release works only when the accepted portion is genuinely separable under the agreed scope. If system-level operation remains unproven, component-level evidence may not support a system-level release.

Remember that released escrow funds are no longer held as protection. Any amount retained for later obligations needs its own defined release condition, rather than an indefinite reference to “final satisfaction.”

4. Freeze disputed amounts and define the exit path

The agreement should distinguish a missing document from a disputed result. Both may block release, but they need different resolution steps.

Ask counsel to review:

• Notice: Who can object, by what channel, and with what required detail?
• Freeze scope: Which disputed amount remains held, and when may an undisputed amount move?
• Cure: What corrected evidence or witnessed retest is required?
• Escalation: Who resolves technical questions, and what instruction or determination binds the funds holder?
• Outside date: What happens if acceptance remains unresolved beyond the agreed deadline?
• Refund: What specifically authorizes return of funds to the buyer?

Avoid a structure where release requires buyer approval but refund always requires supplier consent. That can replace unsecured-prepayment risk with an indefinite escrow deadlock.

Counsel should also examine any silence-equals-approval clause. Administrative inaction should not casually substitute for the objective evidence the buyer negotiated.

5. Close the custody gap before issuing the award

Have procurement, treasury, and counsel reconcile the purchase agreement, acceptance exhibit, and escrow instructions before funding. Confirm precedence where documents conflict, the net refund treatment of fees, and who maintains the release ledger.

A milestone invoice may establish when payment is requested; it should not independently override escrow restrictions. Nor should a supplier reservation acknowledgment count as witnessed acceptance.

If acceptance timing threatens operations, assess bridge-capacity options separately rather than weakening release controls to solve a scheduling problem.

Before authorizing the deposit, schedule a procurement planning call to organize custody questions, evidence ownership, and unresolved commercial decisions.

FAQ

Is an acceptance holdback the same as escrow?

No. A holdback usually remains with the buyer; escrow places funds with an agreed holder. Coordinate either approach with the reserved B300 payment-milestone checklist, while keeping release authority explicit.

Should escrow instructions repeat every acceptance test?

Usually, reference the controlled exhibit and specify the release documents. Use the reserved B300 acceptance-criteria guide to separate technical requirements from funds administration.

Does escrow guarantee deposit recovery?

No. Protection depends on custody, enforceable instructions, provider risk, and dispute mechanics. Learn more about Pacific Intelligent Technologies, Inc., and have qualified counsel review the proposed arrangement before funding.