Spreadsheet checks before running Small Claims Fee Limit in Brazil

What the checker catches

Run this scenario in DocketMath using the Small Claims Fee Limit calculator.

Running Brazil’s Small Claims Fee Limit calculation is easiest when you confirm the spreadsheet inputs first. DocketMath’s small-claims-fee-limit approach works best when the sheet aligns with what the calculator expects—especially around value fields, document/type fields, and any “jurisdiction-aware” flags you maintain for your docket workflow.

Before you press calculate, use the spreadsheet checks below to catch issues that commonly lead to wrong limits, broken totals, or misleading outputs.

Common spreadsheet problems this checker is designed to prevent

• Currency/format mismatches

  • Values stored as text (e.g., "R$ 8.500,00") instead of numbers.
  • Mixed separators (comma vs dot) causing partial parsing.
  • Rounding inconsistencies (storing cents inconsistently across rows).

• Incorrect “case value” basis

  • Using an offer amount where the checker expects the case value used for the fee-limit assessment.
  • Summing the wrong set of line items (e.g., including fees, excluding damages, double-counting adjustments).

• Missing or blank fields

  • Empty cells for key variables (case type, filing date, or the “fee-limit relevant” indicator you keep in your sheet).
  • Rows with blanks that are included in totals via ranges like SUM(A2:A200).

• Unit and scaling errors

  • Amounts entered “in thousands” (e.g., 85 meaning R$ 85.000) while the sheet assumes raw reais.
  • Percentage fields mistakenly treated as currency fields (or vice versa).

• Duplicate case rows

  • Exported spreadsheet data duplicated after a split/merge, causing totals to be inflated.
  • Multiple “versions” of the same case (e.g., corrected data added without removing the old row).

• Date logic failures

  • Filing or reference dates stored in a format the calculator can’t interpret (strings instead of actual dates).
  • Wrong day/month order (common when data is copied from PDF exports).

Output symptoms you should watch for

When the checker finds issues, you’ll typically see one or more of these before (or instead of) a final limit:

• The computed fee-limit threshold is unexpectedly low or high relative to the case value.
• Totals jump by a factor (often 100 or 1,000) due to scaling errors.
• A “run” fails because a required field is blank or non-numeric.
• The checker flags a mismatch between what your totals imply and what the calculator expects.

To reduce friction, treat the checker as a preflight step that validates the spreadsheet’s structure, not just the numbers.

When to run it

Run DocketMath’s spreadsheet checks at the moments when input quality can change. For a Small Claims Fee Limit workflow in Brazil, that usually means:

Run the checker before importing a spreadsheet into the Small Claims Fee Limit workflow. It is especially helpful when you have multiple entries or when a teammate provided the inputs.

Recommended checkpoints

• Before the first calculation for a case

  • Especially right after importing data from a form, PDF, or spreadsheet export.
• After any edits to monetary fields

  • For example, after correcting damages, adding interest components, or changing the case value basis.
• Whenever you update the jurisdiction-aware flags

  • If you maintain columns for case type or filing context, re-run checks after toggling those values.
• Before batch calculations

  • If you calculate for 20–200 cases at once, a single malformed row can skew results or break batch runs.

Practical rule of thumb

Use a simple cadence:

• Per case: run checks once before calculating the limit.
• Per batch: run checks on the whole sheet, then rerun only the rows that fail.

Inputs to confirm in your sheet

Use this quick checklist to verify that the spreadsheet is “calculator-ready”:

Gentle note: This is a data-quality workflow to reduce mistakes in spreadsheet calculations. It’s not legal advice and doesn’t replace jurisdiction-specific review.

Try the checker

You can run the Small Claims Fee Limit calculator workflow directly here: /tools/small-claims-fee-limit.

Before you calculate, mirror the preflight mindset below inside your spreadsheet:

Upload the spreadsheet, review the warnings, and then run the calculation once the inputs are clean: Try the checker.

A mini workflow you can follow in 10–15 minutes

1. Clean currency fields

   • Convert "R$ 8.500,00" style entries into numeric reais.
   • Remove stray symbols and ensure 1.234,56 is parsed as 1234.56.

2. Verify the case value components

   • Ensure your totals align with the case value basis you intend to use.
   • If your sheet has sub-lines (damages, corrections, interest), confirm the subtotal included in “case value” is consistent.

3. Standardize dates

   • Confirm the filing/reference date column contains actual dates.
   • If importing from CSV, check day/month ordering.

4. Rerun checks

   • Confirm the checker no longer reports non-numeric cells, blanks, or mismatched sums.

5. Run DocketMath’s calculation

   • Once inputs are stable, your output should move predictably when you change a case value or date.

How outputs typically change when inputs change

Understanding this behavior helps you detect spreadsheet issues quickly:

• Increase the case value → the computed fee-limit threshold should generally increase or remain consistent (based on the threshold mechanics in the calculator).
• Fix formatting of a monetary field → if the previous cell was text, the recalculated value often “jumps” from 0/blank to the intended number.
• Correct dates → if fee-limit eligibility or reference periods depend on dates, the calculator output may shift after date normalization.
• Remove duplicates → batch totals should drop to the expected level and per-case outputs should align with a single case row.

Keep your sheet calculator-aligned

If you use DocketMath with spreadsheets, consistency is your best safeguard. For example:

• Use one “case value” column that every row feeds from (rather than recalculating ad hoc totals).
• Keep one canonical date field for computation.
• Avoid ranges that accidentally include header rows, notes columns, or “scratch” rows.

For direct tool access, start from: /tools/small-claims-fee-limit.

Related reading

• Small claims fees and limits in Rhode Island — Full how-to guide with jurisdiction-specific rules
• Small claims fees and limits in United States (Federal) — Full how-to guide with jurisdiction-specific rules
• Small Claims Fee & Limit Calculator Guide for Alabama