Legacy Billing Data Version History
The following table lists updates to the billing data specification by version number and date. The latest version number should be used in the file name that you send to Oracle Utilities. See Legacy Billing Data File Name Conventions for more information.
| Update | Specification Version Number | Date |
|---|---|---|
| Update Legacy Billing Data File Name Conventions to be clearer about file name length limit and what file name components are required. | v1-19-0 | 04/11/2022 |
| Clarify that zip files should only contain one file each. | v1-18-0 | 11/23/2021 |
Update Usage Fields section
to clarify that the usage_value field supports negative
values. Update Account
Fields, Service Point Fields, and Usage Fields sections
to use two-column table format.
|
v1-17-0 | 09/14/2021 |
Update Customer Fields section to clarify the
customer_type field and
business_name field descriptions.
|
v1-16-0 | 06/09/2021 |
| Update a few terms to use more inclusive language. | v1-15-0 | 05/12/2021 |
Update Customer
Fields section to clarify the customer_type description
and convert table to a simpler two-column format.
|
v1-14-0 | 10/09/2020 |
| Move information about the file retention policy to a more prominent place. | v1-13-0 | 05/14/2020 |
Update titles
and naming conventions where applicable to rebrand the specification as
a legacy version. Clarify file extension requirements and expectations.
Clarify that the service_unit field is required in the
case of multi-unit premises.
|
v1-12-0 | 11/12/2019 |
Update the list
of allowable values in the customer_type field in the
Customer Fields section. Clarify purpose of the
duration field in the Usage Fields
section.
|
v1-11-0 | 06/14/2019 |
Clarify that
commas cannot be used in usage_value field. Fix typo in
active_date description. Update supported values
for customer_type, meter_type, and
meter_unit fields.
|
v1-10-0 | 04/10/2019 |
| Edit sections and headings to simplify content and clarify instructions. No substantive changes to technical specifications. | v1-9-0 | 12/12/2018 |
| Updated file retention section to reflect regional differences. | v1-8-0 | 05/08/2018 |
Updated the
descriptions for meter_type and
meter_units. Added statement about valid
end-of-line separators.
|
v1-7-0 | 03/19/2018 |
| Updated description of file transfer process. Added information about correcting file upload errors and Oracle file retention policy. | v1-6-0 | 03/03/2018 |
Added new
ccb_account_id field in Customer table. Removed
duplicate account_id field from Usage table.
|
v1-5-0 | 01/12/2018 |
| Updated definition of the bldg_sq_foot value to clarify that it does not generally include spaces such as the garage, unfinished basement, or porch. | v1-4-0 | 06/26/2017 |
Added a
statement about the utility's data obligations. Removed information
about register_id.
|
v1-3-0 | 03/31/2017 |
| Added document number and updated branding. | v1-2-0 | 02/10/2017 |
| Added legal notices. Updated document branding. | v1-1-0 | 01/11/2017 |
Added baseline
specification version number to the document. Updated naming conventions
to include instructions on how to specify a population token and
specification version number in the data file. Added more detail to
language_preference description.
|
v1-0-0 | 09/22/2016 |
Added note to
the is_estimate description to clarify that
user-reported reads are treated as estimated reads and to standardize
the default value for all locales. Updated the
usage_value description to change the upper bound
from 999999 to 999,999,999.
|
Not applicable. | 05/27/2016 |
| Clarified that data from the utility's production system is required. Fixed minor typos. | Not applicable. | 05/09/2016 |