Inputs you need for Closing Cost in Brazil

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.

Inputs you will need

To calculate closing cost in Brazil with DocketMath (jurisdiction code BR), you’ll typically assemble a small “deal stack” of numbers: transaction basics, property/tax facts, and the payment setup. The closing-cost calculator is designed to turn those inputs into an estimate you can sanity-check before you sign.

Use the checklist below to gather what DocketMath’s closing-cost tool expects for BR. If you don’t have a figure yet, add your best known value and revisit once the definitive quote arrives.

Input checklist (Brazil / BR)

Gentle note: Closing costs can swing materially depending on where the property is located (municipality/UF) and how the contract allocates expenses to the buyer. Use this as a planning estimate, not legal or tax advice.

Where to find each input

Collect inputs in this order to reduce rework: property location → sale price → tax bases/transfer tax → financing and Cartório quotes. Here’s a practical source map for each input you need for DocketMath in Brazil.

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

1) Purchase price (drives many proportional components)

Where to find it: purchase agreement (compra e venda), offer letter, or the bank’s financing quotation.
What to watch: if the price includes items like furniture, parking storage, or separately described components, confirm whether your contract treats them as part of the “consideration” base the tool should use.

2) Municipality and UF (needed for local fee logic)

Where to find it: address in the purchase agreement, listing details, or the property’s matrícula information from the registry.
What to watch: entering only UF (state) when the tool expects a full municipio can materially change local-calculation results.

3) Property type (documentation path can differ)

Where to find it: property description in the purchase agreement and the registry documents.
What to watch: “apartment” vs “house” vs “commercial” can affect which fee components get applied in the BR workflow.

4) ITBI / transfer tax estimate (municipality-linked)

Where to find it: municipal tax notices, an ITBI simulation from the prefeitura process, or your conveyancing professional’s estimate.
What to watch: ITBI can depend on the municipality’s tax base and whether any qualifying special circumstances apply (when applicable in your case). If you have an ITBI number from the municipality, using it usually tightens the estimate.

5) Financing inputs (switches the deal from “cash” to “financed”)

Where to find it: the bank’s financing proposal/simulation, including principal amount and any cost breakdown.
What to watch: some financing costs show up as package fees or “administrative” components. Match the breakdown to whatever fields DocketMath provides for BR.

6) Cartório / registry fees (best sourced from a quote)

Where to find it: cartório quotation for escritura/registro and any referenced acts, or a cost sheet from your real estate lawyer/conveyancer.
What to watch: Cartório costs may come as multiple lines (e.g., escritura, registration, certifications). If DocketMath expects a consolidated figure, use the total from the quote.

7) Buyer-paid fees allocation (contract-controlled)

Where to find it: the purchase agreement clauses that assign closing expenses between buyer and seller.
What to watch: expense allocation varies by negotiation. The calculator can only reflect what the buyer is paying based on what you enter.

If you’re cross-checking numbers against other workflows, you can also use DocketMath’s other tools for planning (for example, affordability/budget screens), but the closing estimate itself should be handled by /tools/closing-cost in BR.

Run it

Now you’re ready to use DocketMath.

Open the closing-cost tool: **/tools/closing-cost
Choose jurisdiction: BR (Brazil) if the interface asks.
Enter the inputs from your checklist:
- purchase price
- property type
- municipality + UF
- financing = yes/no and financing amount (if applicable)
- ITBI estimate (if known)
- Cartório/registration quote totals (if you have them)
- any buyer-paid fees (if your contract/quote assigns them to the buyer)
Run the calculation and review the breakdown.

How outputs typically change when inputs change

Use these “cause-and-effect” expectations while comparing scenarios:

Input you change	Likely impact on closing cost estimate
Higher purchase price	Increases proportional components tied to transaction value
Different municipality (same UF)	Can change ITBI and local fee assumptions
Financing vs. cash	Adds bank/admin components and changes the overall mix
Entering a specific ITBI value	Replaces assumptions and often tightens the estimate
Entering a Cartório quote	Moves from modeled registry steps to your real quoted numbers, reducing estimation error

Pitfall to avoid: If the interface offers multiple ways to handle ITBI (e.g., “compute” vs “use provided”), choose the option that matches your data to avoid double-counting.

Quick scenario workflow (recommended)

Baseline: your best-known purchase price + city/UF + property type.
Scenario A (cash): financing = no.
Scenario B (financed): financing = yes and financing amount = bank-proposed amount.
Scenario C (with Cartório quote): replace modeled registry numbers with your cartório totals.

Then compare totals and focus on the line items that move the most—typically ITBI and registry/acts components, since they are often value-linked and location-sensitive in Brazil.