Skip to main content
Retail accounts represent the account references that energy retailers assign to your connections. They are the key link between your internal account structure and the retailer’s billing system — they are how incoming invoices get matched to the correct account and connection.
UMS Retail Accounts list showing retailer account references

Retail accounts list

The Retail Accounts page displays all retail account references in your organisation in a data grid. Tabs across the top filter the list:
  • Retail Accounts — All active retail accounts
  • Active — Status ACTIVE only
  • Inactive — Status INACTIVE only
  • Transfer Pending — Accounts in transition (PENDING_ACTIVE, PENDING_INACTIVE, or DRAFT)
ColumnDescription
Retail Account No.The retailer’s account reference (supplier_account_id)
SupplierThe energy retailer that issued the account
AccountYour internal account the retail account belongs to
StatusLifecycle status (see below)
ConnectionThe linked connection identifier (NMI / MIRN)
Invoice ValidationWhether automated invoice validation is enabled for this account
Gap CheckWhether billing-period gap detection is enabled
Match ToleranceAllowable variance when matching invoice values during validation
Expected Billing FrequencyCadence the retailer is expected to bill at (used by gap checks)
Open Date / Close DateWhen the account reference was opened and closed with the retailer

Status meanings

StatusMeaning
ACTIVECurrently billing — the live account for the connection
PENDING_ACTIVEActivation in progress (for example, a transfer-in not yet confirmed)
SUGGESTED_ACTIVESystem-suggested as the likely active account, awaiting confirmation
PENDING_INACTIVEClosure in progress (transfer-out not yet confirmed)
INACTIVEClosed — no longer billing
DRAFTCreated but not yet activated

Toolbar actions

The header provides:
  • New Retail Account (+) — Open a drawer to create a retail account
  • Update from CSV — Bulk-update existing retail accounts from a spreadsheet
  • Generate Retail Accounts — Auto-generate accounts from existing connection data
  • Merge Retail Accounts — Combine duplicate accounts (see below)
  • Merge Recommendations — Review system-suggested merges of likely-duplicate accounts

Creating a retail account

Click New Retail Account to open a drawer. You supply the retailer reference (supplier_account_id), and link the Supplier, Account, and Connection. You can also set the open/close dates, status, validation and gap-check toggles, match tolerance, expected billing frequency, and payment terms.
A retail account links one connection to one retailer reference. When a connection transfers between retailers, a new retail account is created and the old one is closed — keeping a full billing history per retailer.

Retail account detail page

A retail account detail page with its tabbed interface and details panel
Clicking a retail account opens the detail page with a tabbed interface:
TabDescription
OverviewAccount details, key dates, and summary statistics
ValidationInvoice-validation and gap-check toggles, run validation, and open gaps (badged)
InvoicesInvoices billed against this retail account, with document preview
LedgerFinancial ledger of charges and payments, with an outstanding balance
AgreementsEnergy agreements linked to this retail account
TariffsTariff rates assigned to this retail account
ScenariosTariff-review scenarios and modelling
SettingsAccount-specific configuration
Header actions let you Add a Tariff, create a Retail Sub-Account (a child account under this one), Activate the account, or Close it. Activating an account also closes any other Active or pending accounts on the connection; closing prompts for a close date and can be marked as Deactivation Pending.

Merging retail accounts

When duplicate retail accounts exist for the same connection, merge them into a single root. The merge is irreversible — all agreements, connections, invoices, and related data move into the chosen root account.
1

Select

Choose the root account to keep, then select the other accounts to merge into it.
2

Review

Confirm the root and the accounts being merged. Each shows its supplier reference and open/close dates.
3

Merge

Run the merge. Data is reassigned to the root and the merged accounts are processed.
4

Results

Review per-account Success/Failed results. Download the results as JSON, resolve any exceptions, and delete successfully-merged accounts as needed.
Use Merge Recommendations to let UMS surface likely duplicates automatically instead of selecting them by hand.