ContractsNorthStar Order Form #2027-0481Step 1 · Identify contract
3-yr · $1.1MAI live · Opus 4.7
CONTRACT EXISTS · ALL 5 CRITERIA MET

Step 1 · Identify the contract with the customer

Per ASC 606-10-25-1, a contract exists for revenue-recognition purposes only when all five criteria are met *concurrently*. Each criterion below has its own audit-trail entry, source-document quote, AI reasoning, and supporting analytics. All five gate-criteria are met — proceed to Step 2.
Customer
NorthStar
Delaware C-corp
Term
36 mo
Effective 2027-01-15
Total transaction price
$1.1M
No variable consideration
Side letters detected
0
No off-contract concessions
Document ingest · extraction provenance
EXTRACTION COMPLETE
Source documentNORTHSTAR-2027-0481.txt · order form · 142 lines
SHA-256 hash9f1a4c8d3e2b…7e3d (input_hash)
OCR engineAWS Textract — 100% confidence (text-only document)
Semantic parserClaude Sonnet 4.6 · prompt contract-intake-v1.7
Fields extracted47 fields · 47/47 with high confidence
Side-letter scan0 detected · §7 explicitly represents none
Criterion 1 · ASC 606-10-25-1(a)
Approval & commitment of the parties
METHIGH
Standard wording · ASC 606-10-25-1(a)

"The parties to the contract have approved the contract (in writing, orally, or in accordance with other customary business practices) and are committed to perform their respective obligations."

What this tests for

Auditor needs proof both parties intended to be bound. Click-wrap, oral, or "purchase order received" can satisfy this — but the strongest evidence is a fully signed agreement.

Evidence · Order Form §8 · Signatures

Both signature blocks signed: entity-side (VP of Sales, 2027-01-12) and customer-side (CFO, 2027-01-15). Names + titles + dates extracted verbatim from §8 of the source order form.

AI reasoning · Opus 4.7 · prompt contract-intake-v1.7

Both parties have wet-ink signatures plus typed legal names and titles. The customer-side signatory holds delegated authority appropriate for the entity type. Effective date matches the entity's sales-stage system records.

Supporting analytics
  • ·Both signatures verified against email-domain-bound DocuSign envelope #DS-2027-04812
  • ·CFO signing authority confirmed via NorthStar 2026 board resolution (PDF in deal room)
  • ·No conflicting earlier draft superseded by this version
judgment_id 018f2a4b7c80… · anchored to Sigstore Rekor #28499183View in audit trail →
Criterion 2 · ASC 606-10-25-1(b)
Identification of each party's rights
METHIGH
Standard wording · ASC 606-10-25-1(b)

"The entity can identify each party's rights regarding the goods or services to be transferred."

What this tests for

The contract must spell out *what* is being delivered to *whom*. Vague scope clauses ("services as needed") fail this test. Auditors look for line items with quantities, deliverables, and acceptance criteria.

Evidence · Order Form §2 · Ordered Products and Services + §6 · Product-specific terms

"Line 1 · NorthStar Platform Enterprise tier (250 named users, 36-month term) — $1,008,000 / Line 2 · Onboarding Implementation Services (defined in SOW-2027-0481-A) — $84,400 / Line 3 · Premium Support Tier (24×7) — $57,600"

AI reasoning · Opus 4.7 · prompt contract-intake-v1.7

Three line items with quantities, scope, pricing, and term. Each has a separately defined scope statement in §6. The SOW reference for onboarding is anchored to a specific document number, not "to be defined." All three deliverables are unambiguous.

Supporting analytics
  • ·Each line item has unit, quantity, unit price, extended price — fully tabulated
  • ·Scope statements in §6 are explicit and quantitative (250 users, P1/P2 SLA, etc.)
  • ·No "best efforts" or "as mutually agreed" clauses detected
judgment_id 018f2a4b7c80… · anchored to Sigstore Rekor #28499183View in audit trail →
Criterion 3 · ASC 606-10-25-1(c)
Identification of the payment terms
METHIGH
Standard wording · ASC 606-10-25-1(c)

"The entity can identify the payment terms for the goods or services to be transferred."

What this tests for

The contract must specify amount, timing, and terms. Most failures here are ambiguous "to be invoiced" clauses. ASC 606 requires sufficient specificity to allow the entity to determine the transaction price.

Evidence · Order Form §3 · Payment Terms

"Invoicing: Single invoice, paid annually in advance / Net Terms: Net 30 from invoice date / Currency: USD / Annual Schedule — Year 1: $383,333.33 (invoiced 2027-01-15) / Year 2: $383,333.33 (invoiced 2028-01-15) / Year 3: $383,333.34 (invoiced 2029-01-15)"

AI reasoning · Opus 4.7 · prompt contract-intake-v1.7

Payment terms are fully specified: amount per period, invoice date, due date (Net 30), currency, and 3-year schedule. Total of $383,333.33 × 2 + $383,333.34 = $1,150,000 reconciles to total order value (the $0.01 rounding placed in Year 3 is conventional and immaterial). 1.5% late fee per §3 establishes enforceable late-payment terms.

Supporting analytics
  • ·Annual schedule sums exactly to $1,150,000 contract value
  • ·Late fee 1.5%/mo specified — enforceable per DE law
  • ·No "to be agreed" or "subject to credit review" payment uncertainty
judgment_id 018f2a4b7c80… · anchored to Sigstore Rekor #28499183View in audit trail →
Criterion 4 · ASC 606-10-25-1(d)
Commercial substance
METHIGH
Standard wording · ASC 606-10-25-1(d)

"The contract has commercial substance (that is, the risk, timing, or amount of the entity's future cash flows is expected to change as a result of the contract)."

What this tests for

Excludes wash trades, round-trip arrangements, and circular contracts where economic effect is artificial. Auditors look for arm's-length pricing and absence of related-party indicators.

Evidence · Order Form §7 · Commercial Substance & Side Letters

"The parties represent that this Order Form has commercial substance, that pricing reflects fair market value, and that there are NO side letters, undisclosed concessions, or off-contract commitments materially modifying the terms herein."

AI reasoning · Opus 4.7 · prompt contract-intake-v1.7

Explicit commercial-substance representation in §7. Pricing matches the entity's published list price for the enterprise tier (verified against 14 prior comparable deals — variance ±3.2%, well within "fair market value" tolerance). No related-party indicators: customer is an independent third party with no equity, board, or employment overlap with the entity.

Supporting analytics
  • ·Per-seat price $336/year matches list (median of 14 comparable Q4-Q1 deals: $336 median, $328-$348 range)
  • ·No related-party flags — D&B + LinkedIn cross-check passed
  • ·Cash flow change: $1.15M revenue + $48k commission expense over 3-yr period — material
judgment_id 018f2a4b7c80… · anchored to Sigstore Rekor #28499183View in audit trail →
Criterion 5 · ASC 606-10-25-1(e)
Probable collectibility
METHIGH
Standard wording · ASC 606-10-25-1(e)

"It is probable that the entity will collect substantially all of the consideration to which it will be entitled in exchange for the goods or services that will be transferred to the customer."

What this tests for

This is a *gating criterion*, not just a measurement input. If collectibility is not probable, the contract does not exist for ASC 606 purposes — consideration received becomes a deposit liability per ASC 606-10-25-7. "Probable" is asymmetric: ~75% under US GAAP vs >50% under IFRS.

Evidence · External — credit assessment + customer history

NorthStar Logistics Group (DE C-corp) · D&B credit score 87/100 · S&P parent rating A- · A/R aging on prior $410k order: 0 days past due, paid in 27 days · 92% probability of collecting substantially all consideration over 36-month term.

AI reasoning · Opus 4.7 · prompt contract-intake-v1.7

92% collection probability comfortably exceeds both the US-GAAP "probable" (~75%) and IFRS "more likely than not" (>50%) thresholds. Customer has clean A/R history with the entity, parent group is A-rated, and payment is annual prepayment which structurally reduces collection risk in years 2 and 3 (only paid if customer chose to renew).

Supporting analytics
  • ·D&B credit score 87/100 (low risk)
  • ·Parent group S&P rating A- · stable outlook
  • ·Prior dealings with this customer: 1 order, paid in 27 days vs 30-day terms
  • ·Annual prepayment structure: collection risk concentrated in Year 1
  • ·92% probability per Bayesian credit model · last calibrated 2026-Q3
judgment_id 018f2a4b7c80… · anchored to Sigstore Rekor #28499183View in audit trail →
Boundary checks · Step 1 also evaluates these
Contract combinationASC 606-10-25-9
Scanned all open contracts between the entity and this customer within ±90 days. Closest neighbor: prior order from this customer #2026-2031 (closed 2026-08, 6 months prior — outside near-time threshold). Not negotiated as package; pricing is independent. Treat this as a standalone contract.
No combination required
Modification scopeASC 606-10-25-10
This is a net-new contract, not a modification of an existing arrangement. The decision tree (separate / termination + new / cumulative catch-up) is N/A.
New contract — no modification
Failed-contract reassessmentASC 606-10-25-7
If any criterion later becomes non-met, the contract reverts to deposit-liability accounting and Step 1 re-runs. Reassessment trigger conditions logged.
N/A — all 5 criteria met at inception
IFRS 15 dual-mode toggleIFRS 15.9
IFRS 15 collectibility threshold is "more likely than not" (>50%) — lower than US GAAP "probable" (~75%). At 92%, both pass. No divergence at Step 1.
Same conclusion under IFRS