How can we help? πŸ‘‹

SFTP file delivery requirements

What your organization and your data provider need before sending consumption files to Scaler over SFTP: accepted files, roles and onboarding checklists.

Purpose of this article

This article covers what your organization and your data provider need in place before sending consumption data to Scaler as files over SFTP. Your provider's technical team finds how to connect, upload files and read the results in Sending files to Scaler over SFTP.

Use SFTP when your data provider has no API but can export files on a schedule, for example daily or monthly. If your provider has an API, see API integration requirements review instead.

Files deliver consumption data: consumption, meter readings, redelivery to grid, production and cost. Scaler creates the assets and meters a file names. A file does not update asset details such as floor area or property type.

The standard setup: your provider uploads files in the Scaler template to Scaler's SFTP server. A different file format, or Scaler collecting files from your own server, needs agreement with your Scaler client service team before onboarding starts.


How file delivery works

  1. Set up. Your provider sends Scaler a public SSH key. Scaler creates a login with its own private folder and sends the login details. The password for the web upload page arrives as a one-time link.
  1. Send a file. Your provider uploads a file to the inbox folder.
  1. Scaler reads it. Scaler reads each file when it arrives, stores the consumption, and creates the assets and meters the file names.
  1. You get an answer. Within minutes, Scaler writes a receipt to the receipts folder, or an error file to the errors folder.
  1. The data shows in Scaler. Your admin users map new assets and meters to your portfolio once, on the Automations page. After that, data from each new file shows in Scaler with no manual step.
ℹ️

A meter that appears in a file for the first time is stored, but shows in your portfolio only after it is mapped. Map new meters as soon as their first file arrives. See Mapping assets and meters on the Automations page.


Accepted files

Scaler accepts the Scaler template, as XLSX or CSV. Your client service team sends you the template workbook.

Format
Accepted
Scaler template, XLSX or CSV
Yes. No setup work at Scaler.
NEM12, Australian interval meter data in AEMO's format
Yes, once agreed with your client service team. Scaler sets the time zone on your login. See NEM12 files below.
Any other layout
Only after agreement with your client service team. Scaler reviews a sample file first. Some layouts, for example months or meters across the columns, need development work at Scaler before they can be read. Any layout needs one row per meter and period, a header row, and asset and meter IDs that never change.

Scaler template columns

Column
Required
What to put in it
Asset ID
Yes
Your ID for the asset. It must never change.
Meter ID
Yes
Your ID for the meter. It must never change.
Unit
Yes
The unit of the values, for example kWh
Start Date, End Date
For period values
First and last day of the period, yyyy-mm-dd
Consumption
At least one, see below
Consumption in the period. Write 0 when there was none.
Redelivery To Grid
At least one, see below
Energy exported to the grid in the period. It can share a row with Consumption.
Production
At least one, see below
Energy produced on site in the period, for example by solar panels
Meter Reading, Reading Date
At least one, see below
A register reading and its date. Use the template's readings sheet.
Record ID
No
Your own ID for the row, unique per meter. Send a row again with the same ID to correct its value or its period.
Asset Name, Meter Description, Meter Type, Cost, Currency, Notes
No
Meter Type takes Electricity, Gas, Water or Waste. Leave unused columns empty.

Every row needs at least one of four values: Consumption, Redelivery To Grid, Production or Meter Reading.

File rules

  • One file can hold many meters and periods, with one row per meter per period.
  • For each meter, always use the same period boundaries, for example calendar months. Periods of one meter must not overlap: a row whose period overlaps another period of that meter, already stored or in the same file, is set aside.
  • The header is the first row of the sheet, with no title rows above it. Column order is free.
  • Dates as yyyy-mm-dd, or Excel date cells. Numbers as plain digits with a dot for decimals, without thousands separators or units.
  • CSV in UTF-8, separated by commas or semicolons. In an XLSX workbook, Scaler reads every sheet that carries the template header. Older .xls files are refused.
  • Give every upload a new file name, for example companyname_2026-10.xlsx. Names starting with assets_ or meters_ are refused.
  • Up to 32 MB per file. For historical data, send one file per month.
  • Write the export fully before you transfer it, so Scaler never reads a half-written file.

Roles and responsibilities

Who
Responsible for
Your organization
A named owner and a backup, confirming scope and start date, mapping new assets and meters on the Automations page, telling your provider about acquisitions and disposals
Your data provider
Uploading on schedule, reading receipts and errors, re-sending corrected files within one business day, notice of export changes, keeping its SSH keys current and reporting when a key holder changes

Changes to your files or portfolio

Tell Scaler at least 30 days before your export changes, and send a sample file in the new layout. Examples: renamed or added columns, a new meter type, a new file format version. Without notice, files in the new layout can be refused until Scaler updates its setup.

Change
Example
What to do
Export layout changes
Your provider adds a column or a new meter type
Your provider tells your client service team, with a sample file
Portfolio changes
You acquire an asset, or sell one whose meter is still in the files
Map the new meters on the Automations page. Ask your provider to stop sending meters of assets you sold.

Before onboarding

Checklist for your organization

Cost and agreement

☐ Confirm the one-time and monthly fees for the file integration

Ownership

☐ Name an owner and a backup who coordinate with Scaler and your provider

Scope

☐ Confirm the number of assets and meters to be delivered

☐ Confirm the data types, for example electricity, water, redelivery to grid and cost

☐ Confirm the first date of historical data

Historical data

☐ Agree with your provider on one file per month from the start date up to go-live

Sign-off

☐ Agree the acceptance check: one month per meter in Scaler matches your provider's totals

Checklist for your data provider

☐ A real sample file in the Scaler template

☐ Your public SSH key

☐ How you will upload: scheduled export, SFTP program or the web upload page

☐ Your delivery schedule and the time of day

☐ Two named contacts

☐ For NEM12: the state your meters are in, so Scaler sets the time zone

☐ Your plan for sending historical files

NEM12 files

NEM12 files are read in a fixed Australian time zone, AEST or AWST, without daylight saving, as AEMO specifies.

How Scaler reads NEM12 files
Stream suffix
What it measures
Stored in Scaler as
Starting with E, for example E1
Electricity drawn from the grid
Electricity consumption
Starting with B, for example B1
Electricity sent back to the grid
Redelivery to grid
Starting with W
Water volume, in the unit the file states
Water consumption
K, Q
Reactive energy
Not stored. Listed as set aside in your receipt.
  • Each NMI and stream suffix becomes its own meter, for example NMI123_E1.
  • Each NMI arrives as its own asset, which you map to the matching asset in your portfolio.
  • Readings marked as estimated in the file show as estimated in Scaler. Missing intervals stay empty, not zero.
  • A file must end with its 900 end-of-file record. Files without it are refused as incomplete.

Additional resources

Did this answer your question?
😞
😐
🀩