How to run Closing Cost in DocketMath for North Carolina

Step-by-step

This guide walks you through running Closing Cost in DocketMath for North Carolina (US-NC) using jurisdiction-aware rules. It’s written to help you get consistent results using the tool—not to provide legal advice.

1) Open the Closing Cost calculator

1. Go to the DocketMath tool:

   • Primary CTA: Run Closing Cost in DocketMath
2. Confirm you’re using North Carolina (US-NC) as the jurisdiction in the calculator (if the tool asks you to select it).

2) Enter the core purchase details (these drive the base math)

In DocketMath, you’ll typically provide inputs such as:

• Purchase price / contract price
• Property type (if prompted—choose the option that best matches your transaction)
• Closing date or effective date (if prompted)

If your deal is financed, you may also see fields for loan terms or amounts. Those inputs generally affect non-tax closing-cost components in many closing-cost models; the key tax component for North Carolina is the conveyance excise tax tied to the transfer of real property.

3) Add the North Carolina transfer tax component (conveyance excise tax)

North Carolina imposes an excise tax on conveyances under:

• N.C. Gen. Stat. § 105-228.30 (Excise Tax on Conveyances)

In DocketMath’s US-NC closing-cost run, this is the jurisdiction-aware tax logic applied during the calculation.

Because DocketMath is designed for practical estimates, you should still verify that the tax-related input(s) you enter reflect how your transaction is structured—especially whether the tool uses:

• your entered purchase price as the conveyance/consideration base, or
• a separate conveyance/consideration base field (if one is provided)

If the calculator offers both, don’t assume they are the same—use the value that matches the tool’s label for the conveyance tax base.

4) Review who pays what (output allocation)

Even when a tax is assessed on the conveyance, the economic burden can be reflected differently in a real transaction depending on contract terms and closing statement conventions.

DocketMath will usually show:

• Tax line items computed using N.C. Gen. Stat. § 105-228.30
• Estimated closing-cost totals and subtotals

Use the breakdown to separate:

• what’s driven by the tax calculation (statute-based), and
• what’s driven by non-tax fees (tool-based assumptions)

5) Run a sensitivity check using updated numbers

If you’re trying to understand how changes affect the totals:

1. Update purchase price and re-run.
2. If the tool distinguishes tax bases, adjust the conveyance/consideration base field accordingly (if available).
3. Compare the output changes for:

   • the tax subtotal, and
   • the overall closing cost total

This makes it easier to confirm that the North Carolina conveyance tax component is scaling the way you expect under N.C. Gen. Stat. § 105-228.30.

6) Save or export the result (for your closing estimate workflow)

If DocketMath provides a way to:

• save the calculation,
• download a summary, or
• copy results,

do that now so you can reference the figures later (for example, when you update estimates based on a final contract price).

Common pitfalls

Closing-cost outputs can look “wrong” even when the underlying math is correct. When running US-NC in DocketMath, watch for:

• Using the wrong jurisdiction

  • Double-check that the jurisdiction is set to North Carolina (US-NC) before entering numbers.
• Forgetting that NC tax logic follows the general/default period

  • There’s no claim-type-specific sub-rule found for this calculator logic. If your situation would normally require a different sub-rule, DocketMath will only follow the default/baseline logic unless the tool explicitly asks for additional parameters.
• Entering an incomplete or mismatched tax base

  • If DocketMath requests both purchase price and a separate conveyance/consideration base, don’t treat them as interchangeable. Enter values that match the tool’s exact labels.
• Expecting the tax to stay constant across scenario changes

  • Under N.C. Gen. Stat. § 105-228.30, the tax calculation generally scales with the conveyance consideration used as the base. If you update deal value inputs, the tax portion will typically change too.
• Comparing estimates vs final numbers

  • Closing costs are often estimates at the time of disclosure. If your purchase price changes after the initial estimate, rerun to avoid comparing stale totals to updated assumptions.

Try it

You can run the calculator directly here: Run Closing Cost in DocketMath

To get a quick feel for the North Carolina logic (including the conveyance excise tax under N.C. Gen. Stat. § 105-228.30), try this mini-workflow:

1. Enter a baseline purchase price (for example, your estimated contract price).
2. Run the calculation and record:

   • Total closing cost
   • Tax subtotal(s)
3. Increase the purchase price by a fixed amount (for example, +$10,000) and re-run.
4. Compare:

   • how much the tax subtotal changes, and
   • how much the overall total changes

Then validate your understanding of the allocation:

• If the tax line items increase in a consistent way with the updated base, your tax-base entry is likely aligned.
• If the tax line items don’t change as expected, revisit which field DocketMath uses as the conveyance tax base (purchase price vs a separate consideration field).

If you’re doing this alongside other estimating steps, you can also review related DocketMath guidance and workflows (for example, input consistency across runs).

Related reading

• How to calculate Closing Cost in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Closing Cost in Philippines — Worked example with real statute citations
• Inputs you need for Closing Cost in Philippines — Input checklist with sourcing guidance