Skip to main content

    For multi-site businesses

    From utility invoice to approved payment file, across every site.

    Validate utility invoices, prepare approved payment files in ABA, SAP journal or AU_STD format and track budgets for every site in UMS.

    Illustrative UMS payment file for a multi-site business: a batch of validated invoices in ABA format awaiting the second of two approvals, with the total split across head office, store and distribution cost centres.

    Illustrative data

    How does UMS help a multi-site business manage utility bills?

    UMS checks each supported utility invoice against the tariff its connection should be on, then batches validated bills into payment files in ABA, SAP journal, AU_STD or CSV format. Groups can require dual approval, and site-level cost splits post each charge to the cost centre that incurred it. Settlement stays with your bank.

    • Payment files in ABA, SAP journal, AU_STD or CSV format
    • Dual approval with a separate-approver rule and per-line rejection
    • Company, vendor and cost-centre codes with site-level cost splits
    • Utility budgets with drift alerts and seasonal forecasts
    • Emissions preparation where the ESG module is enabled

    The finance problem

    Why multi-site utility bills eat finance time

    Many accounts, suppliers and due dates land on a team that also has to explain the numbers.

    • Invoices finance can't validate

      Bills arrive from many suppliers with no systematic way to check them, so billing errors are suspected but rarely proven.

    • Payment runs built by hand

      Each bill is keyed into a payment run and coded to a cost centre manually, and a re-sent invoice can slip through and be paid twice.

    • Overruns found after the invoice

      The energy team often learns a site is over budget only when the bill arrives, with no forward view to plan against.

    • Contracts that roll over untested

      Contracts renew without a competitive process, and a credible tender is hard to build without clean consumption history.

    How Utilified helps

    Payments first, then budgets, reporting and tenders

    UMS runs the bill-to-payment workflow finance relies on, and the same data feeds budgets, emissions and your next tender.

    Payment files for your bank and ERP

    Prepare payment files in ABA, SAP journal, AU_STD or CSV format, with company, vendor and cost-centre codes and site-level cost splits. Groups can require dual approval by a separate approver, and lines can be rejected and reissued. Settlement stays with your bank, and general accounting stays in your accounting system.

    Payment files in UMS

    Validation before anything is paid

    UMS works out the tariff each connection should be on, prices the bill against it and classifies every difference. Duplicate bills are caught across formats, and missing bills are flagged from each account's billing cadence.

    Invoice validation

    Budgets and seasonal forecasts

    Build utility budgets, track actuals and get an alert when a line drifts. Seasonal forecasts project consumption and cost for the year ahead, and budgets project from the same model.

    Budgets and forecasting

    Emissions preparation, where enabled

    Where the ESG module is enabled, the same validated invoices and meter reads become emissions activity data, with NGER, NPI, ASRS S2 and GHG Protocol report preparation. Methodology and professional review stay with your team or adviser.

    Emissions preparation

    Run tenders through your broker on EMP (pilot)

    EMP, the Energy Marketplace, is in pilot. Your broker runs the C&I electricity tender in the EMP pilot, and you review the recommended offer and runner-up for each lot through a client review link with no account needed, then accept, decline or request changes.

    Explore EMP (pilot)

    Questions

    Questions finance and procurement teams ask

    Can UMS prepare payment files for our bank or ERP?

    Yes. UMS batches validated bills into payment groups on your schedule and produces files in ABA, SAP journal, AU_STD or CSV format, with company, vendor and cost-centre codes and site-level cost splits. Groups can require dual approval by a separate approver, and lines can be rejected and reissued. Settlement stays with your bank and accounting system.

    Does UMS pay our suppliers?

    No. UMS prepares and approves payment files, and your bank settles them. General accounting stays in your accounting system. Before a file is released, a pre-flight workbench checks GST and retail account numbers, in-credit invoices are netted so credits are used, and copies of bills you've already paid are held for review.

    Can we track utility budgets by site?

    Yes. Build utility budgets, track actuals against them and get an alert when a line drifts, with per-event alert filters so the right people hear about it. Seasonal forecasts project consumption and cost for the year ahead as a forward band on the consumption graph, and budgets project from the same model.

    How do we run an energy tender through the EMP pilot?

    Through your broker. EMP, the Energy Marketplace, is in pilot, covering large-market NEM electricity tenders. Your broker can import the sites they manage for you in UMS, compare retailer offers side by side and send you a review link, with no account needed, to accept, decline or request changes for each lot.

    See a payment run

    Walk through a payment run on your sites

    We'll take a set of bills from validation to an approved payment file, on a portfolio shaped like yours.

    Next step

    Estimate your ROI

    Model the value of validation and reporting work across your portfolio with the ROI calculator.