TOPS [ONE] Assessment Ledger Duplicate Charges: Causes & Fixes

Duplicate assessment charges in TOPS [ONE] almost always happen because the same assessment was posted twice from two different places (manual post plus automatic schedule), or because a recalculation/regen was run after settings changed and the old entries were not reversed. Even if everything “looks correct” now, older duplicate postings can remain on the ledger until they are voided/reversed.

 

Most common causes (what creates the second charge)

 

• Manual posting + recurring assessment: someone posted a one-time charge to the unit, then the recurring assessment schedule also posted for the same period.
• Two assessment rules: two different assessment items (or two schedules) point to the same units and dates (example: “Monthly Dues” and “HOA Dues” both active).
• Assessment regeneration: after changing the amount, start date, frequency, or unit list, a “recalculate/regenerate” action posts again instead of adjusting the original entries.
• Import duplication: opening balances or transactions were imported, then imported again, or imported and also entered manually.
• Ownership/ledger transfer issues: when a unit changes owners, charges may be copied forward and also re-posted to the new owner account.
• Reversal not applied: a prior correction was attempted, but the original charge was not voided; a credit memo/payment was added instead, making it look like two charges exist.

 

How to confirm what happened (fast checks)

 

• Open the unit’s assessment ledger and compare the two lines: same date, same amount, same description usually means double-posting.
• Click into each charge and look for source (manual entry vs assessment run vs import batch) and any batch/run ID.
• Check whether one charge has a different assessment item/code even if the description looks similar.

 

How to fix it safely (without breaking reports)

 

• Do not delete if TOPS [ONE] uses audit trails; use void/reverse so financial history stays clean.
• Void/reverse the duplicate entry (the one from the wrong source or later run). Add a short note like “Duplicate assessment posted via recurring schedule.”
• If duplicates exist across many units, correct the rule/schedule first, then run the platform’s recommended mass reversal or adjustment process.
• Re-run statements or delinquency reports to confirm totals match expected balances.

 

If all settings are correct now but duplicates still show

 

• The duplicates are likely historical postings from an earlier setup, import, or regen. Fixing the rule stops new duplicates but does not remove old ones.
• Filter the ledger by date range and identify the first month duplicates began; that usually points to the exact change/import that caused it.

 

When to contact TOPS [ONE] support

 

• Duplicates were created by a system-wide regen and affect many units.
• You cannot see the posting source/batch, or voiding is locked due to period close.
• Charges tie to integrated modules and reversals must be done in a specific order to keep GL in balance.