Worked example: Closing Cost in Oklahoma
5 min read
Published April 15, 2026 • By DocketMath Team
Example inputs
This worked example shows how DocketMath calculates closing cost in Oklahoma using a jurisdiction-aware rule set labeled US-OK. Since “closing costs” can be modeled in different ways depending on what your workflow treats as part of the total, this example uses a practical, common approach: settlement/closing fees + lender/origination charges + appraisal & inspection + prepaid items (optional) + any net adjustment.
Note: This walkthrough illustrates how to use DocketMath’s closing-cost calculator logic and Oklahoma timing defaults. It’s not legal advice and doesn’t determine what costs you “can” or “must” collect in a specific transaction.
Fixed rule used in this example (Oklahoma time default)
For Oklahoma, the general/default statute of limitations (SOL) period referenced by DocketMath’s jurisdiction-aware settings is:
- 1 year under 22 O.S. § 152 (general SOL period)
Your jurisdiction data also indicates: no claim-type-specific sub-rule was found, so this example applies the general/default period (not a specialized timeline). Source for the general SOL framing: https://www.findlaw.com/state/oklahoma-law/oklahoma-criminal-statute-of-limitations-laws.html
Variables we’ll plug into DocketMath
Below are the inputs used in the example. Adjust them to match your transaction model and your organization’s definition of what to include.
| Input (example) | Meaning | Example value |
|---|---|---|
| Settlement/closing fees | Title, escrow, settlement processing, notary, recording fees (as you define them) | $1,250.00 |
| Lender/origination charges | Origination, underwriting, and lender processing fees you include | $600.00 |
| Appraisal & inspection | Appraisal, inspection, and related third-party charges included in closing cost | $450.00 |
| Prepaid items (optional category) | Interest paid in advance, prepaid insurance, taxes held in escrow at closing (include or exclude consistently) | $2,000.00 |
| Tax/finance charges adjustment | Net adjustment for prorations/discounts in your model | -$100.00 |
For this demo, we treat:
- Closing Cost = (Settlement/closing fees) + (Lender/origination charges) + (Appraisal & inspection) + (Prepaid items) + (Tax/finance charges adjustment)
That’s the arithmetic model for this worked example. DocketMath then produces a single total based on the inputs you provide.
Tool CTA
Start here in your workflow: /tools/closing-cost
Example run
Let’s run the example using DocketMath with the inputs shown above for US-OK.
Step 1: Sum the cost categories
Using the example values:
- Settlement/closing fees: $1,250.00
- Lender/origination charges: $600.00
- Appraisal & inspection: $450.00
- Prepaid items: $2,000.00
- Tax/finance charges adjustment: -$100.00
Compute:
- Subtotal before adjustment
$1,250.00 + $600.00 + $450.00 + $2,000.00 = $4,300.00 - Apply adjustment
$4,300.00 + (-$100.00) = $4,200.00
Step 2: Oklahoma jurisdiction-aware setting (SOL default)
DocketMath’s jurisdiction-aware configuration in US-OK incorporates the general/default SOL period of 1 year under 22 O.S. § 152.
Key point for this worked example:
- The provided jurisdiction data indicates no claim-type-specific sub-rule was found.
- Therefore, DocketMath uses the general/default SOL timing entry rather than branching into specialized timelines.
In many “closing cost” workflows, the SOL timing does not change the dollar total—instead, it supports any workflow features that rely on jurisdiction-aware deadlines (for example, scheduling, reminders, or deadline tracking).
Result: DocketMath output (example)
- Total closing cost (example): $4,200.00
- Oklahoma default SOL setting applied: 1 year (22 O.S. § 152)
Compact breakdown you can reuse:
| Category | Amount |
|---|---|
| Settlement/closing fees | $1,250.00 |
| Lender/origination charges | $600.00 |
| Appraisal & inspection | $450.00 |
| Prepaid items | $2,000.00 |
| Adjustment | -$100.00 |
| Total | $4,200.00 |
Sensitivity check
Now we test how the closing-cost output changes when you vary inputs—especially the categories that commonly move between transactions.
1) Prepaid items sensitivity (largest driver in this example)
Because prepaid items are $2,000.00, this category often changes based on proration/tax/insurance treatment.
- If prepaid items increase by +$500.00:
New total = $4,200.00 + $500.00 = $4,700.00 - If prepaid items decrease by -$500.00:
New total = $4,200.00 - $500.00 = $3,700.00
What changes in DocketMath output: total closing cost moves dollar-for-dollar with prepaid items because the model is additive.
2) Fees/charges sensitivity (settlement/title/processing changes)
Suppose settlement fees rise by +$150.00 (for example, additional recording or escrow processing):
- New total = $4,200.00 + $150.00 = $4,350.00
If lender/origination charges drop -$200.00:
- New total = $4,200.00 - $200.00 = $4,000.00
What stays the same: unless you change the inputs you enter, the Oklahoma default SOL is still the general 1-year period under 22 O.S. § 152 (and the jurisdiction data still indicates no claim-type-specific sub-rule for this example).
3) Adjustment sign check (negative vs. positive)
The -$100.00 adjustment reduces the total. A common mistake is entering a credit with the wrong sign.
Pitfall: If you enter a credit as + $100.00 instead of - $100.00, the total becomes $200.00 higher than intended.
To illustrate:
- Intended adjustment: -$100.00 → total $4,200.00
- Mistaken adjustment: +$100.00 → total $4,400.00
That $200.00 swing comes from changing the sign on the adjustment input.
Oklahoma timing sensitivity (jurisdiction-aware default)
Even though the dollar total usually doesn’t depend on SOL, jurisdiction-aware settings can affect any deadline logic tied to Oklahoma’s default SOL.
Because the provided jurisdiction data indicates no claim-type-specific sub-rule was found, this example continues to apply the general/default 1-year period. If future configuration adds a claim-type-specific rule, you’d want to re-run with that expanded logic.