Skip to content

Systems and records

Utility customer move dataset: splitting one billing cycle

By SourceX Editorial · Reviewed by Noah Loul ·

9 sections

Short answer

Fix the effective move date from the tariff's notice rule and the market transactions, split the cycle's usage by a method the tariff allows, prorate each side by days, and confirm the two bills sum to the meter. A utility customer move dataset packages that timeline: requests, notices, reads, transactions, the split method, both bills, the approval and the reconciled outcome.

License terms

Utility customer move

This page covers utility customer move dataset: splitting one billing cycle.Illustrative

Key takeaways

  • The effective move date comes from tariff notice rules and market transactions, not just the customer's requested date.
  • Tariffs name the allowed ways to split usage; record the method and apply it to both sides of the period.
  • Two bills that sum to the meter, with day counts that cover the cycle once, are the outcome to grade.
  • Backdated starts, no-customer periods and wrong-premise moves are routing tasks for a person.
  • Aggregate interval data to the account periods in shared packets, because it can reveal occupancy.

What does a mid-cycle move look like as a dataset task?

A mid-cycle move turns one meter's billing period into two account periods that meet at a move date. The task is to fix that date from the records, assign usage to each side by a method the tariff allows, prorate the fixed charges by days, and produce a closing bill for the departing customer and an opening bill for the arriving one, with any gap or overlap between them stated rather than hidden.

That makes it a good timeline test for an AI agent. The answer cannot be read off a single status field: the account may show closed while a backdated move-in is still pending, or the new customer may appear active from a date the utility never accepted. The agent has to reconcile requests, notices, meter reads, transactions and tariff rules that each carry their own date.

A utility customer move dataset packages real or illustrative moves so that test is repeatable. Each case starts from a known service state, links the evidence an operations analyst would open, names the rule that applies, records the decision a person approved, and keeps the outcome check that shows whether the two bills actually reconcile to the meter.

Which date ends one customer's bill: the request, the notice or the read?

The move date is the date the tariff and the market rules make effective, which is often not the date the customer said. Record every candidate date separately and let the packet show which one the approved decision used and why.

Tariffs make the difference explicit. Pacific Gas and Electric's discontinuance rule says a customer who asks to end responsibility may be held responsible for service at the premises until a set number of days after the utility receives the notice, or until the termination date stated in the notice, whichever is later. A customer who calls on the day they leave can therefore still own the last few days of usage. The notice period itself has differed between published versions of the rule, so the packet should cite the tariff sheet in force on the case date rather than a remembered number.

Competitive markets add transaction dates. ERCOT's Retail Market Guide defines a backdated transaction as a move-in or move-out whose requested date is earlier than the date ERCOT receives it, and the move-out's service period end comes from the distribution utility's response rather than from the retailer's request. A dataset drawn from Texas retail records should keep the requested date, the received date and the confirmed service end as three fields.

Which date ends one customer's bill: the request, the notice or the read?
Candidate dateWhere it comes fromWhat it can decideCommon mistake
Requested stop or start dateCustomer call, web form or retailer enrollmentThe date the customer asked for, subject to tariff limitsTreating the request as the effective date without checking notice rules
Notice received dateContact center log or order system timestampWhen a notice period starts running under the tariffUsing the call date when the notice arrived through a later channel
Scheduled meter read dateField order or market transaction responseThe read that closes or opens an account periodAssuming the scheduled read happened on schedule
Actual read date and valueMeter data management systemThe registration used to split usageMixing an estimated read with an actual one in the same calculation
Transaction received dateMarket registration or retailer systemWhether the move is backdated and needs special handlingLosing the difference between requested and received dates

How should usage be split when nobody read the meter on moving day?

Use the method the tariff names, and record which one was used. PG&E's Electric Rule 9 lists three ways to set the energy assigned to an opening or closing bill: the recorded meter registration on the date the customer asked service to start or end, average daily use over the billing period multiplied by the days the customer received service, or actual usage.

Those methods give different answers when usage was uneven. A household that ran heating every day before leaving and an empty unit after it will split very differently under a read-based method than under an average-daily method. Neither answer is wrong if the tariff allows it; the error is applying one method and labeling the result with another, or switching methods between the two sides of the same period so the totals no longer match the meter.

The same rule says opening and closing bills, and monthly bills for periods shorter than 27 days or longer than 33 days, are computed under the applicable rate schedule with prorating by days. The packet should therefore carry the day count for each side and the rate schedule version, so a grader can confirm the proration rather than trust a final figure.

Interval meters make a read-based split possible without a field visit, because the meter data system can sum usage on each side of the effective date and time. Green Button's ESPI model expresses a billing period as a DateTimeInterval with a start and a duration, so a split period becomes two intervals that must together cover the original one. Store both intervals, plus the original, so the dataset can check that no hours were lost or counted twice.

What should the administrative billing and service state task pack include?

It should hold every dated input for both customers, the rule references, the approved split and a reconciliation check. The schema below is written so a utility or retail energy team can use it as a case template; rename the systems to match its customer information, meter data and market transaction tools.

What should the administrative billing and service state task pack include?
Packet fieldContentsTypical sourceCheck before use
case_id and versionStable case key, packet version, preparation date, real or illustrative labelDataset build logIllustrative cases are labeled in the packet itself
premise and meterPseudonymous premise key, meter key, meter type, read cycle, multiplierAsset and meter data recordsMeter in place for the whole cycle, or a swap is recorded
outgoing_accountPseudonymous account key, rate schedule, stop request, notice received dateCustomer information system and contact logsNotice channel and timestamp agree
incoming_accountPseudonymous account key, rate schedule, start request, enrollment verification statusCustomer information or retailer enrollment recordsStart request is verified before it is relied on
market_transactionsMove-out and move-in transaction types, requested, received and confirmed datesMarket transaction archive, where one existsBackdated flag computed from requested versus received
readsOpening read, move read (actual or estimated), closing read, interval totals if availableMeter data management systemEach read carries its type and timestamp
split_methodRead-based, average daily or actual usage, with the tariff referenceBilling rule configurationOne method applied to both sides of the period
billsClosing bill and opening bill periods, day counts, usage, rate schedule versionBilling systemDay counts and usage sum to the meter period
approvals and exceptionsWho approved the split, any dispute, any routing decisionException queue and case notesApprover is a person, with role and date
outcomePosted bills, any rebill, any later correction and whyBilling historyOutcome is checked against the meter, not a status

Which service states can a premise pass through between two customers?

A premise can be served by an outgoing customer, an incoming customer, a landlord, or nobody, and each state carries different billing consequences. Name the states in the packet so the agent's job is to identify the right one at each date, not to guess from an account flag.

At a glance

Which service states can a premise pass through between two customers

Texas retail records show why this matters. ERCOT's TX SET training material lists the move-in (814_16) and move-out (814_24) transactions among those that start a business process, and the Retail Market Guide defines a de-energized status at ERCOT as one where no retail electric provider is of record for the premise. The guide also carries operating rules for continuous service agreements, under which a property owner can keep service in place between tenants after a move-out. Texas rule 25.474 adds a front-end constraint: a retailer may not submit a move-in or switch request until it has the applicant's verification of the enrollment.

  • Active, outgoing customer: usage belongs to the departing account until the effective stop date.
  • Stop pending: a notice exists, but the tariff or market process has not yet made it effective.
  • Final billed: the closing bill has posted; later evidence can still force a rebill.
  • No customer of record: no account or retailer is responsible; usage in this state is an exception, not a split.
  • Owner continuous service: a landlord agreement carries the premise between tenants.
  • Start pending: a move-in exists but is unverified, backdated or awaiting its read.
  • Active, incoming customer: usage belongs to the arriving account from the effective start date.

Illustrative case: a tenant leaves on day 12 of a 30-day cycle

This case is illustrative: the dates, readings and usage are invented to show the packet in use, and the rule references assume a tariff written like PG&E's Rules 9 and 11. A residential tenant's cycle runs 30 days. On day 12 the tenant calls to stop service that same day. A new tenant at the same premise starts service from day 15. The meter is an interval meter, and no field read was taken at either move.

Starting state: one active account, one pending stop dated day 12, one pending start dated day 15, an opening read of 0 kWh relative to the cycle and a closing read showing 600 kWh for the full 30 days. Linked evidence: the call log timestamp for the stop notice, the start request with its verification record, interval totals of 260 kWh for days 1 to 12, 30 kWh for days 13 and 14, and 310 kWh for days 15 to 30.

Decision: the tariff's notice period means the outgoing tenant remains responsible past day 12, and in this illustration the effective stop lands on day 14, so days 13 and 14 fall to the outgoing account rather than to nobody. Using the read-based method from interval data, the closing bill covers 14 days and 290 kWh, the opening bill covers 16 days and 310 kWh, and both are prorated by days under the rate schedule. The two periods total 30 days and 600 kWh, matching the meter.

Verified outcome: both bills posted with those day counts, a billing analyst approved the split, and no rebill followed in the next cycle. The task's correct answer is the split and its reasons, not the account status of closed.

Counterexample: the same facts, except the incoming tenant's start request arrives on day 20 with a requested date of day 15, after the outgoing closing bill has posted. Now the start is backdated. The correct output is not to silently reassign days 15 to 20 but to flag the backdated start, confirm the incoming tenant's verification, and route the case so a person decides whether the closing bill needs correction. An agent that simply moves usage between posted bills has made a billing decision it was not allowed to make.

What shows the two bills landed on the right accounts?

The proof is the pair of posted bills reconciled to the meter, plus the approval and the rule reference that justify the split. A closed status on the old account, or a friendly confirmation message to the new customer, proves nothing about whether the usage landed in the right place.

Green Button's ESPI UsageSummary carries a billingPeriod, bill amounts, itemized cost lines, a quality-of-reading field and a required status timestamp. Those fields help pin each bill to its period and to the moment its summary was produced, which is what a grader needs to decide which version of the facts the agent was entitled to see.

What shows the two bills landed on the right accounts?
What is gradedPass conditionEvidence that settles itFalse pass to watch for
Effective stop dateMatches the tariff's notice rule and the notice timestampContact log, tariff sheetUsing the requested date when notice rules extend it
Effective start dateMatches a verified start, with backdating flaggedEnrollment verification, transaction datesAccepting an unverified start because the account looks active
Usage splitEach side uses the stated method and the two sides sum to the meterReads, interval totals, split method fieldRight totals reached by mixing methods
Day counts and prorationDay counts cover the cycle with no gap or overlapBill periodsCounting the move day on both sides
Exceptions routedNo-customer, backdated and disputed cases sent to a personException queue entriesResolving a backdated start by editing a posted bill
Final outcomePosted bills and any rebill match the approved decisionBilling historyA status of closed treated as the outcome

Where the agent must stop: field work, disputes and occupancy data

The agent prepares a decision from records and stops at anything that needs a field visit, a dispute ruling or a change to service. It never schedules a disconnection or reconnection, never tells a customer to read, open or touch metering equipment, and never decides who lived at a premise when the records conflict.

Two market situations should always route to a person. A move-in on the wrong premise is a known pattern in Texas retail, where ERCOT's guide defines an inadvertent gain as a change to a retailer other than the customer's expected choice; correcting it runs through a market process, not a billing edit. Usage in a no-customer-of-record state needs the utility's own policy, because it may involve a landlord agreement, an unauthorized occupant or simply a gap in paperwork.

Interval data can reveal when a home was occupied, so a shared packet should aggregate usage to the two account periods unless the task needs finer detail. Replace names, service addresses, account numbers and meter serials with stable pseudonymous keys that keep the outgoing and incoming accounts linked to the same premise. Customer usage may be covered by state privacy rules and commission orders as well as the utility's own terms; counsel should confirm permitted use, and de-identification does not on its own give the utility a right to license the records.

  • Stop and route when the stop and start requests overlap and both customers dispute the days in between.
  • Stop and route when a start request lacks the verification the market or tariff requires.
  • Stop and route when usage appears in a period with no customer or owner of record.
  • Stop and route when the case involves possible unauthorized use or any field safety note.

Offering move and transfer history for licensing

Move histories are common, dated and checkable, which is what makes them useful for testing agents that work across billing, customer and market systems. For utilities and retail energy suppliers, SourceX handles the sourcing, rights review, contracting, preparation, delivery and payment involved in licensing selected move histories as datasets for AI.

An energy retailer or utility can start with a short company assessment that needs no data upload. The company approves the scope and terms and signs before anything is delivered, and large interval archives can remain in its own storage or travel on encrypted drives instead of being hosted by SourceX.

Frequently asked questions

What is a utility customer move dataset?

It is a set of cases in which one premise passes from an outgoing customer to an incoming one during a billing cycle. Each case links the stop and start requests, notice and transaction dates, meter reads, the split method, the two bills and the approved outcome, so an agent can be tested on reconstructing the timeline.

Does the outgoing customer pay until the day they ask to stop?

Not always. Some tariffs, including PG&E's, let the utility hold a customer responsible until a set number of days after it receives notice, or the termination date in the notice if that is later. The packet should cite the tariff sheet in force on the case date.

How is usage divided without a meter read on moving day?

Tariffs name the allowed methods. PG&E's Rule 9 allows the recorded registration on the requested date, average daily use times days of service, or actual usage. Interval meters let the utility sum usage on each side of the effective date.

What is a backdated move-in?

In ERCOT's retail market it is a move-in whose requested date is earlier than the date ERCOT receives the transaction. In a dataset it is a flag that the start may overlap a period already billed to someone else, so a person should decide any correction.

Should cases with no customer of record be included?

Yes, as routing tasks. The correct output is to identify the gap and send it to the team that applies the utility's policy, not to assign the usage to the nearest account.

Can illustrative cases replace real moves?

They are useful for documenting the packet and testing the grader when they are labeled illustrative. Claims about how an agent performs should rest on approved real cases from the company's own records.

Sources

  • PG&E Electric Rule 9 sets three methods for the energy on opening and closing bills and prorates bills for periods under 27 or over 33 days. Source
  • PG&E Electric Rule 11 lets the utility hold a customer responsible for service until a set period after it receives a termination notice, or the stated termination date if later. Source
  • ERCOT's Retail Market Guide defines backdated transactions, de-energized status and inadvertent gains, and carries continuous service agreement operating rules. Source
  • ERCOT's TX SET training lists move-in (814_16) and move-out (814_24) as transactions that start a business process. Source
  • Texas PUC rule 25.474 bars a retailer from submitting a move-in or switch request before it has the applicant's enrollment verification. Source
  • The Green Button ESPI UsageSummary summarizes a billing period with bill amounts, cost line items, reading quality and a required status timestamp. Source
  • The ESPI DateTimeInterval expresses a period as a start and a duration, with the end derived. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies