Spreadsheet checks before running Small Claims Fee Limit in Philippines

What the checker catches

Before you run DocketMath’s Small Claims Fee Limit (PH) calculator, a quick spreadsheet review can prevent avoidable errors—especially when your sheet mixes currencies, dates, and fee categories. DocketMath applies jurisdiction-aware rules, but the usual rule still holds: if the spreadsheet inputs are inconsistent, the math will be inconsistent too.

Below are the main issues the spreadsheet-checker workflow is designed to catch for Philippines (PH) small claims fee-limit calculations:

• **Wrong fee base (wrong column / wrong label)

  • Example: your spreadsheet intends to calculate based on the principal/subject amount, but the selected column actually points to a miscellaneous fee or a different “fee-like” line.

• Summing “all fees” instead of the fee subject to the limit

  • Many worksheets include multiple components (court fees, service fees, other charges) in one running total. The checker helps you confirm you’re not feeding the calculator an “over-inclusive” total.

• Currency mismatch

  • If one tab uses PHP and another tab uses USD (or contains values formatted with “$”), the checker should flag that your thresholds may not be applied correctly.

• Character/format errors

  • Values stored as text (e.g., 1,250 imported from PDF, or copied from email) can cause silent miscalculations.
  • Even if the spreadsheet looks right, the checker can detect data-type issues that affect how thresholds are computed.

• Missing or inconsistent PH/jurisdiction-related fields

  • If your workflow tracks court/venue or case “track” but PH-specific fields are blank (or inconsistent), the checker may not be able to confirm you’re applying the intended PH pathway.

• Wrong court / wrong division

  • If your spreadsheet supports multiple venue options (e.g., different court types or divisions), the checker can help ensure your selected court/venue fields match what the PH rules assume for the fee-limit logic.

• Duplicate rows and double-counted principal/subject amount

  • Duplicates happen when transactions are imported more than once or when invoices appear multiple times due to line-item breakdowns. The checker can flag totals that don’t reconcile cleanly to the underlying line items.

Pitfall to watch: A spreadsheet can look correct visually while being numerically wrong—particularly after importing from PDFs or copying between workbooks. When amounts are stored as text, you may get incorrect thresholds or unexpected “capped vs uncapped” behavior.

A fast reconciliation table (what you should verify)

Use this quick checklist before running the calculator:

Inputs the checker typically validates (and how outputs change)

In practice, your workflow usually has two stages:

1. Spreadsheet validation (checker stage)

   • Output: a list of warnings/errors such as “amount looks like text,” “currency inconsistent,” or “selected amount base may be incorrect.”

2. Fee-limit computation (DocketMath calculator stage)

   • Output: the computed fee-limit result and/or whether the amount triggers cap-related behavior.

When the checker finds issues, the calculator output can change in predictable ways:

• Fixing text-to-number problems often corrects totals that were previously treated inconsistently.
• Correcting a wrong column/amount base can move you from below threshold (uncapped) to at/over threshold (capped)—or vice versa.
• Removing duplicates can reduce the subject amount so the fee-limit logic no longer triggers (or triggers later than before).

When to run it

Run the spreadsheet-checker before you compute anything with the Small Claims Fee Limit (PH) calculator. The timing matters because spreadsheets evolve—imports, edits, and reclassification can introduce errors at any point.

Recommended moments to run the checker:

• After importing or copying data

  • Example triggers: pasted amounts from emails, accounting exports, scanned document extracts, or copy/paste from other workbooks.

• After you edit amounts or change fee assumptions

  • Example triggers: revising claim principal, reclassifying expenses into “other charges,” or adjusting the column you consider the subject amount.

• Before filing a batch of cases

  • If one workbook contains multiple matters, run the checker once per batch so a systemic formatting issue doesn’t repeat across many rows.

• After any jurisdiction-related edits

  • If you switch courts/venues, change which sheet/tab represents PH inputs, or alter court/track fields, re-run the checker immediately.

A practical cadence that works:

• Step 1 (per workbook refresh): Run checker → fix flagged rows.
• Step 2 (per case): Run the calculator for that row/case after warnings are resolved.
• Step 3 (audit): Spot-check 2–3 cases against your source documents (e.g., invoice/receipt tables or the pleadings worksheets your spreadsheet was built from).

Try the checker

You can test the full workflow using DocketMath’s Small Claims Fee Limit (PH) tool with the spreadsheet-checker setup.

1. Open the calculator entry point:

   • Primary CTA: Run Small Claims Fee Limit (PH)

2. Use the spreadsheet-checker flow to validate your inputs:

   • Confirm the subject amount column selection (the amount the calculator should evaluate)
   • Confirm all numeric fields are truly numeric (not stored as text)
   • Confirm currency assumptions (PHP)
   • Confirm intended PH jurisdiction settings (court/venue or jurisdiction-related fields)

3. Re-run the calculator after fixing checker warnings:

   • Compare results before vs after the changes
   • If behavior flips (e.g., uncapped → capped), record the reason—most often a corrected amount base or a corrected amount value.

To make your test meaningful, try three controlled experiments:

• Experiment A: formatting

  • Temporarily treat one amount as text (or note if it already is) and verify the checker flags it.

• Experiment B: column selection

  • Switch from using “principal/subject amount” to a different total (like “total charges”) and observe how the computed fee-limit outcome changes.

• Experiment C: duplicates

  • Duplicate one line item, then remove it and confirm totals reconcile and whether the checker warns appropriately.

A simple decision view:

• ✅ Checker clean → run fee limit
• ⚠️ Checker warnings → fix inputs; re-run
• ❌ Checker errors → stop and correct before calculating

For internal consistency, keep a one-line audit note per case (even if it’s just a quick log):

• Date processed
• Workbook version
• Main amount used
• Checker status (clean / warnings fixed)

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