Damages Allocation reference snapshot for Brazil

6 min read

Published April 15, 2026 • By DocketMath Team

Rule or statute summary

Run this scenario in DocketMath using the Damages Allocation calculator.

In Brazil, “damages allocation” in a civil case generally breaks into two practical buckets:

  1. Compensatory damages (material damages and, where applicable, moral damages). These are the amounts intended to compensate the injured party, subject to Brazilian civil law standards.
  2. Monetary update (correction) and interest applied to judgments and delayed obligations. These mechanics can vary depending on the claim type, how/when the obligation became due, and when “mora” (delay) starts.

For a jurisdiction-aware reference snapshot in DocketMath (tool: damages-allocation), the key modeling idea is to separate:
(a) what the damages category is (material vs. moral, and sometimes what’s included beyond principal), from (b) how the judgment amount accrues over time (update/correction and interest segments). The same nominal principal can produce meaningfully different totals once Brazil’s time-based update/interest rules are applied.

This is not legal advice—treat it as a workflow and budgeting aid to understand how assumptions and inputs can change outputs.

What you generally allocate in a damages model (Brazil)

Use inputs/categories to keep the calculation structured and consistent:

  • Material (actual) damages: expenses or losses supported by documents/valuation.
  • Moral damages: often scenario-based where the court award is not yet fixed; can be modeled as an estimate range.
  • Claim framing (contract vs. tort/extra-contractual): can affect which accrual mechanics apply (especially around delay/default and update logic).
  • Key timeline dates (these often control the accrual window):
    • Event date: date of incident/unlawful act (a common anchor for certain update concepts).
    • Due/default date: relevant when the obligation is contractually due or when “mora” is triggered.
    • Judgment/settlement date: the point your model treats as the end of the accrual window or as a transition between pre- and post-judgment treatment.
    • Payment/calculation end date: if your workflow treats accrual differently before vs. after judgment.

Common pitfall: If you enter only a single “total damages” number without splitting material vs. moral (and without key dates), the calculator can’t correctly apply update/interest logic for Brazil.

Citations

Brazilian civil liability and the mechanics of delay and indemnification are anchored in the Brazilian Civil Code. Commonly referenced provisions for liability and damages include:

  • **Brazilian Civil Code (Código Civil)

    • Art. 186 (unlawful act causing damage)
    • Art. 187 (abuse of right)
    • Art. 927 (duty to repair; obligation to pay damages)
    • Art. 389 (non-performance and indemnification in obligations)
    • Art. 395 (mora/default—delay framework)
    • Art. 405 (interest in delay—often cited for delay interest mechanics)
    • Art. 406 (legal interest rate framework)
  • **Brazilian Civil Procedure Code (Código de Processo Civil)

    • Art. 523 (payment after judgment—timing can affect practical accrual/payment modeling)
    • Art. 85 (attorneys’ fees in judgments; sometimes modeled separately from principal damages)

Because “damages allocation” outputs can include different components, it helps to track what you’re modeling:

  • Principal damages only (material + moral)
  • Principal + update/interest
  • Principal + update/interest + fees (if you choose to model attorneys’ fees as add-ons)

Those choices affect what number you should treat as the model’s “total.”

Sources and references (TODO placeholders if needed)

  • TODO: Confirm the exact update/correction and interest mapping used by DocketMath for Brazil by claim type (e.g., material vs. moral; contract vs. tort; delay start assumptions like event date vs. due/default date).
  • TODO: Add jurisdiction-specific notes on which correction index/rate assumptions apply for your scenario once you specify the claim facts and dates.

Use the calculator

Use DocketMath’s damages-allocation tool to structure Brazil damages into allocable components and compute totals based on your dates and claim categories.

Run the Damages Allocation calculation in DocketMath, then save the output so it can be audited later: Open the calculator.

1) Open the tool (and keep scope consistent)

Start at: /tools/damages-allocation
In DocketMath, choose the output scope to match what you want to estimate:

  • Principal allocation only (material + moral), or
  • Allocation including monetary update + interest (recommended for settlement planning), and optionally
  • Fully loaded allocation including fees if your workflow treats fees as separate line items.

2) Enter Brazil claim categories (material vs. moral)

Typical tool inputs you’ll provide:

  • Material damages amount (BRL) (documented/quantified)
  • Moral damages amount (BRL) (if applicable)
    • If moral damages are not fixed, run scenario ranges (low/expected/high) rather than forcing a single “fact” number.

Practical tip: Even a modest shift in the moral estimate can amplify the effect of update/interest if the timeline window is long.

3) Provide key dates that control accrual

Populate the dates that align with your claim narrative and the accrual mechanics you want to model:

  • Event date (incident/unlawful act)
  • Due/default date (if there is contractual default or delay trigger)
  • Judgment date (if your workflow uses a pre-/post-judgment split)
  • Calculation end date (often the settlement/payment assumption)

Why it matters: Two scenarios with identical principal can yield different totals if one scenario uses an earlier delay/default anchor.

4) Review outputs and interpret what changes

After running the calculator, record:

  • Allocated principal (material vs. moral)
  • Update/correction amounts (if shown)
  • Interest amounts (pre-judgment and/or post-judgment components, depending on tool settings)
  • Total estimate (principal + accrual components)

Quick sensitivity guide:

Input you changeLikely effect on Brazil totalWhy it changes
Event date earlierTotal increasesLonger update/interest accrual window
Due/default date earlierTotal increases more sharplyDelay/mora-based interest can start earlier
Add/remove moral damagesTotal changes roughly proportionallyMoral is a separate principal bucket
End date laterTotal increasesMore time for update/interest accrual

5) Run scenarios (recommended workflow)

Instead of a single output, run at least 3 scenarios:

  • Base: best-estimate material + moral, with your most defensible date assumptions
  • Conservative: lower moral and/or shorter accrual assumptions
  • Aggressive: higher moral and/or earlier due/default assumptions

Scenario checklist:

Sources and references

Start with the primary authority for Brazil and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

Related reading