How Attorney Fee rules vary in Brazil

5 min read

Published April 15, 2026 • By DocketMath Team

What varies by jurisdiction

Attorney fee rules in Brazil aren’t one-size-fits-all. Even when the case type stays constant (for example, a civil lawsuit or an enforcement proceeding), the outcome can change because Brazil applies overlapping fee regimes that vary by phase, party position, and court posture. DocketMath’s jurisdiction-aware attorney-fee calculator for BR (Brazil) is designed to reflect those moving parts so you can model likely fee ranges rather than relying on a single static assumption.

The biggest Brazil-specific variables

Below are the inputs that most often change the attorney-fee result in Brazil’s legal workflow:

  • Whether the claim is fully, partially, or not successful
    • Brazilian fee-shifting (“sucumbência”) commonly tracks the degree of success.
  • Whether the matter is in a litigation phase governed by the CPC fee framework
    • Fees can differ between initial suit, appeals, and certain post-judgment steps.
  • Whether “sucumbência” fee-shifting is implicated
    • The CPC sets baseline rules on who pays the other side’s legal costs and how those fees are calculated.
  • Whether contractual fees (contingency or hourly arrangements) are also present
    • Separate from court-awarded fees, parties may have a contract with their own lawyer.
  • Timing and procedural conduct
    • Some scenarios increase exposure (for example, the consequences of losing after an appeal).

Note: A court-awarded “sucumbência” fee (what one side must pay to the other) is conceptually different from what a client pays their own lawyer under a contract. DocketMath can help you model both categories if you enter the right inputs.

Typical Brazil fee frameworks you’ll see in practice

In Brazil, the main legal sources for fee mechanics include:

  • Brazilian Civil Procedure Code (CPC) — Law No. 13.105/2015
    • Sets a default framework for attorney fees (including fee-shifting and the calculation structure).
  • Special procedural contexts that may adjust costs/fee mechanics
    • Certain procedural tracks (including some consumer contexts or other specialized proceedings) can introduce exceptions or different treatment of costs and fees.
  • **Labor law (if the case is in the labor court system)
    • Labor proceedings often follow a different procedural structure than ordinary civil courts.

Because your calculator inputs control which “path” DocketMath applies, you’ll want to verify the case type and procedural phase before you rely on the output.

What to verify

Use this checklist to make sure DocketMath’s attorney-fee outputs match your Brazil matter. The goal is accuracy—and avoiding fee models that assume the wrong procedural track.

  • The governing rule or statute for the jurisdiction.
  • Any local rule overrides or administrative guidance.
  • Effective dates and whether amendments apply.

1) Confirm the jurisdictional track: civil vs. labor vs. special procedure

DocketMath’s BR calculator is jurisdiction-aware, but it still needs the right pathway.

Verify:

  • Is the case in an ordinary civil court under the CPC framework?
  • Or is it in labor courts, where fee rules can differ?
  • Does the matter fall under a special statute that adjusts costs/fees?

2) Identify the relevant procedural stage for fees

Fee exposure can shift as the case progresses.

Verify:

  • Which stage you’re modeling: first instance, appeal, or post-judgment steps.
  • Whether the output should reflect fees awarded in the judgment only, or also fees associated with further procedural actions.

3) Determine the “degree of success” assumptions

In Brazil, fee-shifting responsibility is commonly linked to success outcomes—often proportionally for partial wins.

Verify:

  • Did the plaintiff win fully, partially, or lose?
  • If partial: what is the percentage of success you want DocketMath to model?

4) Separate court-awarded fees from client contractual fees

Many Brazilian matters involve both:

  • Court-awarded fees (“sucumbência”): paid to the other side based on the judicial decision.
  • Contractual fees (your own lawyer): paid to your own counsel by agreement.

Verify:

  • Whether you want DocketMath to estimate:
    • court-awarded fees, client contractual fees, or both
  • If contractual fees exist: whether they are fixed, hourly, or contingency/percent, and when they apply (for example, on milestones or outcomes).

5) Check value and currency inputs tied to the CPC calculation method

Brazil attorney-fee rules can reference the economic value of the dispute or the amount established by judgment.

Verify:

  • The claim value you’re using (the one stated in the lawsuit, and/or updated later).
  • Whether the output should use the judgment value rather than the initial petition value (a common mismatch).

Pitfall: Feeding the calculator the initial claim amount when the judgment later reduced or increased the economic value can materially change the fee estimate. DocketMath can’t know which figure your court used—enter the value aligned to the decision you’re modeling.

How to use DocketMath in practice (inputs → outputs)

When you open the tool, you’ll typically provide:

  • Case value / judgment value (BRL)
  • Procedural stage (if supported in the UI)
  • Success outcome (win/lose/partial)
  • Whether to model sucumbência, contractual fees, or both
  • Any contingency/hourly parameters if applicable

Expected result behavior:

  • Higher success for the claimant generally reduces the claimant’s fee exposure and can increase the defendant’s payment obligation (through sucumbência logic).
  • Partial wins typically produce proportional outcomes in fee-shifting models.
  • Switching from “first instance only” to “include appeal” can increase the modeled exposure if the fee scheme triggers at each procedural phase.

Access DocketMath directly here: **/tools/attorney-fee

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