How can we help? 👋

Audit features in Scaler

An overview of Scaler’s audit-support features, including validation rules, emissions factor transparency, audit trails, and controlled access for auditors.

Purpose

This article explains how Scaler supports assurance, verification, and audit processes across the full data lifecycle, from initial data input and validation to report generation and access transparency.


Validated input fields

Scaler enforces data integrity through built-in validation.

Field validation includes:

  • Field types
    • Numeric, date, dropdown, and boolean fields are constrained to appropriate formats.

  • Consumption logic
    • Every consumption record must include:

    • Start date
    • End date
    • Consumption , Production, or Meter reading values
      • Date ranges cannot overlap.

  • Mandatory classifications
    • Consumption data must be categorised by:

    • Energy type
    • Subcategory
    • Area type
    • Operational control

This ensures consistent Scope 1, 2, and 3 assignment.


Emission factor transparency

Scaler provides default emission factors sourced from recognised databases, including:

  • CRREM
  • Australia NGA
  • US EPA eGRID

Users can override default factors where permitted and can provide a Reference for auditability and traceability.



Framework reports with full metadata and audit trail

Framework-based report generated in Scaler include a metadata section and audit-trail sheets containing:

  • Timestamp of generation
  • Emission factor set used
  • Full emission factor values
  • Raw input data
  • All calculations applied

This enables step-by-step verification of reported results.


Raw data exports

Users with access to the Data Collection Portal can export raw, meter-level data, including:

  • Meter type
  • Energy/water/waste Subcategories and Sources
  • Area type
  • Monitoring method
  • Consumption format
  • Consumption , Production, or Meter reading values

This supports line-by-line auditing and reconciliation.


Data request workflow

Scaler’s Data Request feature supports controlled data collection by:

  • Assigning specific fields to internal or external contributors
  • Tracking who submitted each value
  • Requiring review or approval before finalisation

Requested fields follow the same validation rules as standard data entry.


User action log

Scaler maintains a user action log showing:

  • Who entered or edited a value
  • What was changed
  • When the change occurred

This supports traceability and accountability.


Auditor access controls

Auditors can be granted access to Scaler at no additional cost.

This would allow auditors to:

  • Review and export raw data
  • View historical values
  • Access reports and metadata

These features work together to make data more traceable, auditable, and transparent—supporting both internal data assurance and external verification requirements.

Did this answer your question?
😞
😐
🤩