This article walks you through how to investigate and fix Time Bank balance discrepancies in Pace Scheduler. You will use this process when balances do not match between views, reports, exports, or expected payroll calculations.

 

Most discrepancies are caused by date context, timing rules, pending transactions, manual adjustments, or known display/export defects. Following a consistent validation flow helps you identify the true source quickly and apply the correct fix without introducing new balance errors.

---

Prerequisites

• You have admin access to your Pace site.
• You can open Reports → Time Bank Usage.
• You can open Admin Panel → Banks and Balances → Bank Balances.
• You have at least one affected user example with:
  • User name
  • Time Bank name
  • Expected balance vs displayed balance
  • Date(s) where mismatch appears
• You can run/export the same date range more than once for comparison.

---

Before you begin

• Confirm you are comparing the same effective date context.
  • Some views show current balance as of today.
  • Some report outputs show projected or range-based totals.
• Confirm your Time Bank deduction timing rule.
  • Some banks deduct on submission/approval.
  • Others deduct on day of shift/time off date.
• Check whether pending transactions are included.
  • A mismatch may appear only when Include Pending Transactions is enabled.

 

Do not correct balances until you finish root-cause review. Many discrepancies are display-context issues, not actual balance errors.

---

Steps

Part 1: Reproduce the discrepancy with matched filters

1. Run Time Bank Usage for the affected user and bank.
   • Go to Reports → Time Bank Usage.
   • Use a date range that includes the reported mismatch period.
   • Run once with pending included and once without pending included.
2. Compare against Bank Balances and Grid/bubble values.
   • Open Admin Panel → Banks and Balances → Bank Balances for the same user.
   • Record whether mismatch is between current balance, projected balance, report total, or Grid bubble display.
3. Expand history far enough back to include carry and manual activity.
   • Include prior-year dates when rollover, negative carry, or historical adjustments may affect current totals.
   • Look for outlier dates (for example, wrong year entry such as 1924 instead of 2024).

 

Part 2: Validate common configuration causes

4. Verify deduction/accrual timing settings for the Time Bank.
   • Confirm whether deduction occurs on submission/approval or on day of shift.
   • Reconcile expected changes against that timing rule.
5. Validate overtime-to-Comp Time multiplier behavior (if applicable).
   • If Comp Earned is incorrect, review overtime/Shift Differential configuration.
   • Confirm multiplier override is set correctly (for example, 1.5x when expected).
6. Check for stale or invalid pending records.
   • Investigate old duplicate/invalid shift records that still affect pending-inclusive totals.
   • Remove invalid duplicate records while preserving valid historical entries.

 

Part 3: Apply correction safely

7. Use Bank Balances for direct current-balance correction when needed.
   • Go to Admin Panel → Banks and Balances → Bank Balances.
   • Click the pencil icon for the user, enter corrected balance, then save.
   • Use this for current-balance correction when report-level adjustments are inconsistent.
8. Use Time Bank Usage adjustments for transaction-style corrections.
   • Use report adjustments when you need chronological movement rather than direct replacement.
   • For upload workflows, remember uploads are date-level snapshots, not timestamped transactions.
9. Re-run all comparison views after correction.
   • Recheck Time Bank Usage, Bank Balances, and any user-facing balance bubbles.
   • If mismatch remains and reproducible, escalate with evidence for development patch review.

 

Part 4: Prevent recurrence

10. Set an internal upload/approval cutoff process.
    • Approve same-day usage before running date-based balance uploads.
    • If payroll source is prior-cycle, backdate upload to cycle-end date per your process.
11. Document expected interpretation for your team.
    • Define when to use current balance vs projected/range values.
    • Train admins to compare like-for-like date context before reporting discrepancies.

---

Confirm it worked

• Time Bank Usage and Bank Balances now reconcile for the same user/date context.
• Grid/bubble balance matches expected current balance behavior.
• Pending-inclusive and non-pending values differ only by valid pending items.
• Comp Earned calculations match expected multiplier behavior.
• Exports no longer show known incorrect negative or rounding anomalies for the tested case.

---

Troubleshooting

• Grid/bubble balance does not match Time Bank Usage.
  • Check for bad historical manual adjustment dates.
  • Re-run report with expanded history and verify correction after date cleanup.
• Current value and report value look different.
  • Confirm whether one value is current and the other is projected/range-based.
  • Run both views with aligned date intent before concluding there is an error.
• Balances change only when pending is included.
  • Inspect pending transactions for stale/invalid entries.
  • Remove invalid duplicates and retest.
• Upload created unexpected offsets.
  • Treat upload date as a full-day snapshot, not a timestamped transaction layer.
  • Run uploads after usage posting, or use report adjustments for mid-day correction needs.
• Small decimal mismatch (for example, 15.999 vs 16.0).
  • Capture exact user/bank/example and escalate as potential rounding/display defect.
  • Retest after patch deployment.
• Bank Balances export shows negative values but page values are correct.
  • Treat as export-layer discrepancy and escalate with exported sample.
  • Use on-screen Bank Balances and Time Bank Usage as source of truth until patch is applied.

---

FAQ

• Which page should I trust for direct current-balance correction?
  Use Admin Panel → Banks and Balances → Bank Balances for direct current-balance corrections.
• Why does projected balance differ from current balance?
  Projected values are date-range/forecast based, while current values reflect present-state balance.
• Does opting to include pending transactions change totals?
  Yes. It includes unfinalized activity and can reveal stale entries that are not visible in current-only totals.
• Can I fix discrepancies only by editing reports?
  Not always. Use report adjustments for transaction logic, and use Bank Balances for direct current-balance correction when appropriate.