Why Closing Cost results differ in Delaware

5 min read

Published April 15, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

The top 5 reasons results differ

If you’re seeing different Closing Cost results in Delaware (US-DE) using DocketMath, the cause is usually not “math”—it’s inputs and Delaware-specific data handling inside the calculator workflow. Below are the most common reasons outputs diverge, even when two people think they entered the same scenario.

Note: Delaware’s general limitations period is 2 years under 11 Del. C. § 205(b)(3). This guide uses that as the default because no claim-type-specific sub-rule was found in the provided jurisdiction data.

1) Loan / deal inputs don’t match exactly

Closing-cost calculations are sensitive to line items such as:

Lender credits and borrower-paid charges
Recording-related fees
Estimated vs. final settlement charges

Even a small difference (for example, $150 in one fee category) can shift totals—especially when the tool groups fees based on whether they are treated as paid by the borrower versus credit offsets.

2) The “paid by” attribution changes the total

Two settlements can show the same gross fees but allocate them differently across parties. DocketMath will reflect that allocation because it’s commonly derived from the “paid by” semantics of the data you enter (or that the calculator prompts you to categorize).

Practical example: a fee that one run treats as borrower-paid may be treated as a credit to the borrower in another run, changing the net “Closing Cost” output.

3) Delaware timeframe assumptions affect what set of costs is included

Some workflows treat “closing costs” as components that must fall within a measurable window driven by underlying event dates. In Delaware, your workflow may rely on the general 2-year SOL:

11 Del. C. § 205(b)(3): 2 years as the general/default period

If your scenario includes dates (for example, closing date, discovery date, or another event date), selecting different date inputs can change which components are included/excluded under that windowing logic.

4) Rounding and fee normalization

Settlement statements often list fees with different levels of precision or break out fees into components that may be consolidated. DocketMath normalizes numbers according to its calculator rules, so totals can differ if:

Fees are copied with different rounding (e.g., $1,234.56 vs. $1,235.00)
Items are entered as “bundled” in one run and “itemized” in another

5) Missing or swapped fields create silent recalculations

This is more common than it sounds. If an entry is blank—or a fee is mapped to the wrong cost bucket—the output can change without an obvious error. Typical examples include:

A fee placed in the wrong category (so it’s excluded/included differently)
A swapped “paid by” field (borrower vs. lender/other party)
An “other/misc” bucket used inconsistently between runs

How to isolate the variable

Use this diagnostic checklist to find what’s driving the difference—without guessing.

Freeze the jurisdiction and tool settings so both runs use the same rule set.
Compare one input at a time (dates, rates, amounts) and re-run after each change.
Review the breakdown to see which segment or assumption drives the difference.

Step 1: Lock the SOL assumptions to the default

For Delaware (US-DE), rely on the provided general rule:

General SOL period: 2 years
Statute: **Title 11, § 205(b)(3)
Default application: No claim-type-specific sub-rule was found in the provided data

If one run used a different limitation period or a different assumption set, that can alone cause differences in time-windowed inclusion logic.

Step 2: Compare inputs as a table, not as “I entered the same thing”

Export or record the fields you used in DocketMath and do a side-by-side check.

Input category	Run A value	Run B value	Difference?
Borrower-paid fees			☐ Yes ☐ No
Credits to borrower			☐ Yes ☐ No
Recording-related charges			☐ Yes ☐ No
Date fields (closing/event)			☐ Yes ☐ No
Any “other”/misc bucket			☐ Yes ☐ No

Step 3: Re-run with one controlled change

Change only one input at a time (for example, adjust only the recording fees) and observe the delta in output totals.

Goal: identify the single field that shifts the Closing Cost result most.

Step 4: Validate categorization

If the difference is large, it usually means categorization—not arithmetic. Confirm each fee line is assigned to the same “bucket” across runs.

Pitfall: If one run treats a charge as a borrower-paid fee and another treats it as a credit offset, totals can swing even if the dollar amounts look close.

Step 5: Confirm date logic aligns with Delaware’s general 2-year period

If dates are used in your process, ensure the dates in both runs fall into the same inclusion window keyed off the 2-year general SOL (11 Del. C. § 205(b)(3)).

Next steps

Run /tools/closing-cost with a “frozen” set of inputs (same fee categories, same date fields).
If the result still differs, repeat using the controlled-change method (one variable per run).
Keep your captured inputs and output deltas—this speeds up reconciliation when you compare with a second version or settlement statement.

If you want a direct place to reproduce your numbers, use: /tools/closing-cost.

Gentle note: This is not legal advice. SOL and cost-inclusion logic can depend on case facts and claim specifics.