Section 20 Threshold Limits for Qube Customers

Nico
Nico
· Updated

Qube alarm threshold validation

In general, section 20 works in this way within Dwellant. But for Qube customers, it differs a bit as shown below -

 

Qube

 

Dwellant

 
  • Fund
    • Heading 1
      • Schedule heading A
    • Heading 2
      • Schedule heading A
    • Heading 3
      • N/A
  • accounting_schedule 1
    • expense_type 1
      • Linked through alarm_threshold_id
    • expense_type 2
      • Linked through alarm_threshold_id
    • expense_type 3
      • alarm_threshold_id would be NULL.
 

When the accounting data plugin runs, it imports the funds and headings and stores them as schedules and expense types. It also stores the relationship between which expense types belong to which funds.

 

The Alarm threshold amount unlike in default, can only be set at the moment by spreadsheet upload. The buttons are only available to Qube managing agents. The buttons are different from the ones in default.

 

How is it setup

  • Accounting data uploader plugin only imports schedules, expense types, creates the alarm threshold and relates the alarm threshold to the accounting schedule expense type. Note: amounts are not populated via accounting data plugin.
  • Setup → Accounting Data → Static Data → Upload alarm thresholds
     
  • The file suffix is _alarmThreshold.

NOTE: Unlike the default, group schedules are split into their internal cost assignments and each cost assignment is checked against is alarm threshold limit

Case 1 (would be different from default): Qube - Breach - Cached - Case 1.xml

Work order estimated price is £600. Schedule alarm threshold called “alarm1” is £400. Both accounting_schedule_expense_type relate to the same alarm threshold called “alarm1”)

If we have two 50% allocated cost assignments. Each cost assignment will then count for £300. 
Given 2x£300 = £600 and £600 > £400, then the alarm threshold will trigger an alert

Case 2:Qube - Breach - Cached - Case 2.xml

Work order estimated price is £600. Schedule alarm threshold called “alarm1” is £200. Both accounting_schedule_expense_type relate to the same alarm threshold called “alarm1”)

If we have two 50% allocated cost assignments. Each cost assignment will then count for £300. 
Given 2x£300 = £600 and £600 > £200, then the alarm threshold will trigger an alert.

Case 3 (would be the same as default):Qube - Breach - Cached - Case 3.xml

Work order estimated price is £600. Schedule alarm threshold called “alarm1” is £400. Schedule alarm threshold called “alarm2” is £500.
Going two cost assignments each one related to a different alarm threshold. 50% allocated cost assignments. Each cost assignment will then count for £300. 
Given cost assignment 1: £300 < $400 
Given cost assignment 2: $300 < $500

None of the allocations will exceed the thresholds, so no alarm would be triggered.

Good to know

  • Alarm threshold validation does not take place when creating contracts nor when auto-approving invoices at the moment.

Was this article helpful?

0 out of 0 found this helpful
Have more questions? Submit a request
Return to top