Skip to main content
Sign in
Français

Accounting Data Change Thresholds

  • Updated

What this feature does

The Accounting Data Change Thresholds feature protects your system from accidental large-scale changes (like mass tenant deletions or property removals) that could damage your data.
It does this by checking incoming data from your Accounting System against configurable percentage thresholds for additions, modifications, and deletions.

If a change exceeds the set threshold, the data file is automatically quarantined instead of being applied to your database.

Thresholds and Options You Can Change

  • Default thresholds: The system has built-in defaults for each type of data (tenants, contractors, properties, etc.) but you can override these and choose your own.
  • Types of thresholds:
    • Additions % – how much new data can be added at once
    • Modifications % – how much existing data can change at once
    • Deletions % – how much data can be removed at once

 

Tip: If you set a threshold too high, damaging changes might slip through. Too low, and you’ll have to review more files than necessary. Aim for a balance.

 

When You Get Alerts

  • Thresholds are checked when the background job (ReadDataJob) runs.

  • If the changes exceed thresholds:

    • An Accounting data alarm request is created.
    • The request is assigned to your Accounting Data group, or to Administrators if no group exists. You will be emailed if you're in these groups and have emails configured.
    • The related data files are placed in quarantine. These are accessible in the Setup menu.

     

Managing Quarantined Files

  1. Go to the Quarantined Files page. This is found under Setup > Accounting.
  2. Click on a row to download the spreadsheet showing:
    • Additions
    • Modifications
    • Deletions
  3. Review the changes:
    • External Id columns show unique identifiers from your Accounting System.
  4. Decide how to act:
    • ✅ If the changes are correct, tick the row and click OK for Dwellant to process.
      • The red ❌ changes to a green ✅ after refresh.
      • At the next background job run, the file will be processed.
    • ❌ If the changes were accidental, correct the issue in your Accounting System.
      • When the system detects the correction (for example, tenants being restored after deletion), the alarm is cleared and the quarantined file is automatically removed.

Examples

  • Large deletion prevented: If 300 tenants are deleted in error, the file is quarantined before any harm is done. If the tenants are restored later, the system clears the quarantine automatically.
  • Catch rare deletions: Setting a deletion threshold of 0 for “Properties” ensures you are alerted whenever a property is deleted, since these changes are uncommon and potentially disruptive.

Related articles