Choosing the right Settlement Allocator tool for Brazil

Choose the right tool

Run this scenario in DocketMath using the Settlement Allocator calculator.

Selecting a Settlement Allocator tool for Brazil isn’t just a software decision—it’s a workflow decision. In practice, your allocator has to handle how Brazilian matters are documented, how parties and claim categories are identified, and how settlement amounts are split across relevant buckets (such as claim value/damages and any ancillary components). DocketMath helps you run that allocation using jurisdiction-aware rules, so your inputs and outputs stay consistent with a Brazil-focused workflow.

To choose the right setup, start by deciding what “settlement allocation” means for your matter type. In Brazil, the operational question is usually: What portion of the settlement corresponds to each claim/cause of action (and, where applicable, costs/fees or other line items), and how should your allocation be documented for internal review and disclosure?

1) Confirm your allocator’s Brazil coverage (BR-specific workflows)

Before you commit, verify the tool supports a Brazil workflow end-to-end:

• Jurisdiction code support: The tool should explicitly operate under BR rulesets.
• Entity and category mapping: You should be able to attach allocation lines to plaintiffs/defendants, claim categories, or matter participants without forcing awkward workarounds.
• Currency formatting and rounding controls: Brazilian settlement workflows often require clean, auditable rounding—particularly if you later reconcile the allocation with payment instructions.
• Document-friendly outputs: A good allocator produces results you can paste into emails, settlement summaries, or internal memos (without reformatting gymnastics).

With DocketMath, you can begin immediately via the primary calculator interface: /tools/settlement-allocator.

2) Match the tool configuration to your allocation design

Different settlements require different “allocation shapes.” DocketMath supports the practical pattern you’ll commonly use in Brazilian matters: split a single settlement amount across multiple allocation lines, then carry those amounts into a totals view.

Use this checklist to decide what to configure before you start:

These choices directly affect how DocketMath outputs will look—especially totals, rounding differences, and the clarity of what drove each line item.

3) Understand the input → output relationship in DocketMath

Even if you’re not a developer, your results will only be trustworthy if you control the key inputs. In DocketMath’s Settlement Allocator calculator, your main operational inputs typically include:

• Total settlement amount: the gross figure you want to allocate
• Allocation lines: the items you want to distribute across (claims/cost buckets)
• Allocation weights or basis: how each line gets its share
• Rounding / reconciliation approach: how line rounding behaves relative to the grand total

Here’s what to expect when you change inputs:

If the numbers don’t behave the way you expect, don’t rush to “fix” them manually—return to the basis/weights and rounding settings first.

4) Don’t ignore jurisdiction-aware rules when allocating for Brazil

Brazil matters often require consistent classification and recordkeeping. A jurisdiction-aware tool helps because it can enforce consistent assumptions about how amounts are expressed and tracked in a BR-aligned workflow.

In practical terms, choosing the right tool means:

• You reduce the likelihood of reformatting errors (for example, mismatched totals after rounding).
• You keep your outputs aligned to a Brazil-facing settlement summary structure.
• You can standardize inputs across matters, so internal review is faster and comparisons are fair.

If your allocator isn’t jurisdiction-aware, you may end up doing manual adjustments outside the tool—exactly where errors creep in.

5) Use the right DocketMath workflow for your stage

Allocator accuracy depends on when you use it:

• Early evaluation: You may want flexible weights and quick scenario comparisons.
• Draft settlement package: You’ll want stable rounding and line-by-line traceability.
• Final reconciliation: You need a clean “sum of lines = total” guarantee—with documented rounding adjustments.

To streamline the process, connect your allocation work to the broader DocketMath workflow where applicable. If you’re starting right now, use /tools/settlement-allocator and then carry the allocation table forward into your internal package.

Next steps

Ready to pick the right setup in DocketMath? Follow these steps to go from “we think we need allocation” to “we have a usable, auditable allocation table”:

1. Open the calculator

   • Start with: /tools/settlement-allocator

2. Define your allocation lines

   • Create a line for each claim bucket or settlement component you plan to report internally.
   • Keep the number of lines manageable; 5–12 lines is often easier to review than 30+.

3. Set your allocation basis

   • If you have agreed fixed splits, use those.
   • If you’re allocating proportionally, assign weights that reflect the agreed basis.

4. Choose a rounding approach

   • Prefer an approach that produces a reconciled grand total automatically.
   • If your team requires per-line rounding, set it first, then reconcile totals.

5. Run a scenario check

   • Modify one key weight by a small amount (e.g., ±5%) to see whether outputs respond as expected.
   • This catches mis-mapped lines and prevents silent spreadsheet-style mistakes.

6. Lock your draft output format

   • Ensure your output includes:

     • line items
     • amounts per line
     • totals
     • a reconciliation note (especially for rounding)

7. Perform a “reasonableness” review

   • Verify no line becomes negative.
   • Confirm the largest lines align to your expected claim buckets.
   • Check that totals match the settlement amount to the cent/real as required by your process.

Finally, keep a brief internal record of:

• what you used as the allocation basis,
• what rounding approach you applied, and
• what scenario (draft vs. final) the output represents.

That makes it far easier to explain the allocation table during internal review or when reconciling payment instructions. (And, as always, align the final presentation with your organization’s documentation requirements.)

Related reading

• Settlement Allocator Guide for Alabama
• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for Colorado