Why Interest results differ in Brazil
5 min read
Published April 15, 2026 • By DocketMath Team
The top 5 reasons results differ
Run this scenario in DocketMath using the Interest calculator.
If your DocketMath interest results don’t match your expectation in Brazil (BR), the mismatch usually comes from jurisdiction-aware inputs and how interest is applied across scenarios. Even when the headline inputs look the same, a few mechanics can change the outcome significantly.
| Reason interest differs | What changes | Typical symptom in DocketMath output |
|---|---|---|
| 1) Incorrect base date | Whether interest starts on data de início (e.g., citation date, payment date, or another contractual/legally relevant date) | Interest appears too early or too late by weeks/months |
| 2) Wrong principal definition | Whether the base is gross principal, net principal, or an amount adjusted before interest | Output scale is off consistently (e.g., always “too high”) |
| 3) Compounding vs simple interest | Brazil interest may be modeled with compounding/accumulation depending on the configured approach | Growth looks “accelerated” compared with simple-rate expectations |
| 4) Rate vs index behavior | Some flows use a stated rate; others use an index-like approach where the effective rate is not constant | Output diverges over longer periods, even if early months match |
| 5) Day-count convention | Different day-count conventions (e.g., 360/365, or business-day logic) | Minor-to-material differences that increase with duration |
Note: In Brazil, the “same” interest rate can yield different totals if your interest start date, compounding method, or day-count convention differs—even when the rate field looks identical.
Also watch for scenario drift. Two people may both say “interest on the amount,” but one is calculating interest-only while the other is calculating interest on an adjusted balance. DocketMath can still be correct; the inputs just may not describe the same cash-flow reality.
How to isolate the variable
To isolate the cause quickly, treat this like a controlled diagnostic. Use DocketMath (via /tools/interest) to run a tight set of tests, changing only one input per run.
Start with a baseline run
- Enter the amount as you intend the principal to be.
- Set the start date and end date you believe govern interest accrual in your BR scenario.
- Use the rate model your workflow assumes (stated rate and/or compounding settings).
- Confirm whether the calculation uses the same calendar logic as your comparison method.
Then do a five-run “single-change” sequence:
Run A (baseline)
Use your current inputs exactly as-is.Run B (base date only)
Change only the interest start date by a small, known delta (e.g., move the start date forward 7 days).- If the total shifts by roughly rate × principal × (days/your day-count base), your base date is a likely culprit.
Run C (principal only)
Modify only the principal input (e.g., adjust by the exact difference between gross and net principal).- If results track proportionally, your mismatch is likely principal definition.
Run D (compounding model only)
Toggle compounding/simplified mode (if your DocketMath BR configuration supports it for your case).- A larger difference for longer durations suggests compounding behavior is driving the change.
Run E (day-count only)
Keep all dates the same but switch day-count logic (where available in the calculator/config).- If the gap grows with longer periods, day-count convention is likely the driver.
When you review outputs, log:
- Total interest
- Any intermediate accumulation (if shown)
- Effective duration (number of days counted)
- Any rounding differences (Brazil workflows often surface rounding at different stages)
If you want a quick starting point, try the DocketMath calculator here: /tools/interest.
Next steps
Once you identify which input causes the difference, move from “diagnose” to “standardize.”
Lock your interest start rule
Decide and document a single trigger date concept (e.g., “start accruing on X date used by our process”). Your goal is to remove team-to-team interpretation differences.Define principal consistently (gross vs net)
Create one rule for what constitutes the principal base. If you work with invoices, define whether taxes/fees are included or excluded before interest starts.Fix your rate model and compounding assumption
If your process uses a stated annual rate, ensure the calculation method matches (simple vs compounding). Keep the compounding frequency consistent across runs.Align day-count and rounding
Choose a day-count convention and the rounding stage (per-period vs final total). This often eliminates “mystery cents” that persist across reports.Run a comparison checklist before approvals
Use this checklist every time you re-run interest in Brazil:
If your numbers still diverge after these controls, the workflow assumption itself may differ (for example: whether the balance is adjusted before interest accrues). In that case, revisit the scenario definition—not just the entered inputs.
Gentle disclaimer: This guidance is for practical calculation troubleshooting, not legal advice. If a case has specific contractual or regulatory requirements, ensure your inputs reflect the applicable agreed interpretation.
Related reading
- Interest rule lens: Maine — The rule in plain language and why it matters
- Common interest mistakes in Rhode Island — Common errors and how to avoid them
- Worked example: interest in Maine — Worked example with real statute citations