HomeGuidesAPI ReferenceChangelog
Log In
Guides

Estimate Consumption from a Bill Total

Use Bill Solve with Account Cost Calculation to estimate kWh usage from a monthly or annual utility bill total.

Use Bill Solve with Account Cost Calculation to estimate kWh usage from a monthly or annual utility bill total.

A common issue when analyzing a potential project is that you need to know how much electricity a home or business is using but cannot get access to meter data or good-quality usage numbers. Most customers don't know how much electricity they're using. They may know how much they pay for electricity, but not how that translates into kWh.

Use Bill Solve with Account Cost Calculation to estimate a customer's energy usage for a single billing period using the total cost of their bill. Similarly, if your customer knows their annual electricity cost, Bill Solve can estimate their annual kWh consumption.

Use the Account Cost Calculation endpoint for these Bill Solve calculations.

Bill Solve workflow

  1. Create or confirm an account with location, utility, and tariff data.
  2. Choose monthly or annual Bill Solve.
  3. Send a total property input with unit set to cost.
  4. Include baselineType set to typicalElectricity as the initial usage guess.
  5. Read the estimated kWh from results[].summary.kWh.
  6. Optionally validate the estimate by sending the estimated consumption back into the calculator.

Key parameters

ParameterUseNotes
fromDateTimeBilling period startUse the exact bill start date when available.
toDateTimeBilling period endUse the exact bill end date when available.
billingPeriodBilling-period charge handlingUse true for one bill. Use false for an annual or multi-period analysis.
propertyInputs[].keyName=totalBill amount to solve fromSet unit to cost so the calculator interprets the value as dollars instead of kWh.
baselineType=typicalElectricityInitial usage guessHelps provide an hourly usage shape and can improve convergence for TOU customers.

Choose monthly or annual Bill Solve

Use caseRecommended optionWhy
Customer has one or more exact billsMonthly Bill SolveUses exact bill dates and reduces annual distribution assumptions.
Customer only knows annual electricity costAnnual Bill SolveEstimates annual kWh when bill-level data is unavailable.

How Bill Solve works

Bill Solve estimates kWh usage by working backward from total bill amounts. It applies the correct tariff rates and structures for the specified billing period, determining how much energy consumption (kWh) would have been required to generate the given bill total.

Use the monthly option with exact billing dates for the highest precision. Calculating usage for one bill yields more precise results than an annual calculation. The annual option requires assumptions about how a customer's usage is distributed over the year, which can introduce additional uncertainty.

What Bill Solve does well

Use Bill Solve with straightforward electricity tariffs, particularly those with fixed rate structures.

Supports standard tiered tariffs

  • Works well when a tariff has clearly defined, fixed kWh tiers (e.g., 0–500 kWh, 501–1,000 kWh, etc.).
  • Best suited for cases where energy charges are the main component of the bill and do not fluctuate due to demand-based adjustments.

Handles time-of-use (TOU) rates

  • Can estimate kWh distribution across fixed TOU windows (e.g., Off-Peak: 10 PM – 6 AM, On-Peak: 2 PM – 7 PM).
  • Ideal when TOU rates are the primary driver of bill variation and demand-based components are minimal.

Accounts for basic fixed fees and simple demand charges

  • Handles fixed monthly fees and basic demand charges that do not influence energy tier breakpoints.
  • Works best when charges follow a fixed structure and do not introduce historical usage dependencies.

When Bill Solve may not be a good fit

Bill Solve estimates usage under most standard tariff structures, but it may not provide accurate results for tariffs with complex, demand-based, or historical pricing rules.

Tariffs with demand-dependent tiering

  • If the kWh tier structure changes based on a customer's peak demand history, Bill Solve cannot correctly allocate usage across those tiers.
  • Example: A tariff where the second tier starts at 80% of the customer’s highest demand in the past 12 months
    • Bill Solve does not track historical demand, so it cannot determine the correct tier placement.

Complex demand charges that influence kWh allocation

  • Some tariffs adjust kWh rates based on measured demand (e.g., higher per-kWh pricing for high-demand customers).
  • Bill Solve assumes a standard energy rate structure and does not model demand-based rate shifts.

Ratchet-based pricing or dynamic tiering

  • If a tariff includes historical peak demand ratchets (e.g., where past demand affects current pricing), Bill Solve does not retain past demand values and may misplace consumption into incorrect rate categories.

When to use Bill Solve vs. alternative methods

Use Bill Solve if your tariff has clear, fixed kWh tiers and TOU periods, and you need an approximate usage estimate. Most standard residential tariffs are a good fit for this functionality.

Consider alternative methods if your tariff includes demand-based pricing, historical ratchets, or shifting tier structures.

circle-question

If you're unsure whether Bill Solve is a good fit for your use case, contact support for guidance. If a Bill Solve request failed, include its requestId so the support team can investigate.

Monthly Bill Solve request

Use this template for a monthly Bill Solve request:

POST /rest/v1/accounts/pid/{providerAccountId}/calculate/
{
  "fromDateTime": "{billingPeriodStart}",
  "toDateTime": "{billingPeriodEnd}",
  "billingPeriod": "true",
  "propertyInputs": [
    {
      "fromDateTime": "{billingPeriodStart}",
      "toDateTime": "{billingPeriodEnd}",
      "keyName": "total",
      "dataValue": "{billTotal}",
      "unit": "cost"
    },
    {
      "fromDateTime": "{billingPeriodStart}",
      "toDateTime": "{billingPeriodEnd}",
      "keyName": "baselineType",
      "dataValue": "typicalElectricity"
    }
  ]
}

Use the monthly option for this example customer:

  1. Residential customer in the Xcel Energy - Colorado service area on the "R" tariff (masterTariffId 599)
  2. Actual bill of $60.49 for the period 2024-08-15 to 2024-09-15

To solve for this customer's monthly consumption value, send the following request to Account Cost Calculation:

POST /rest/v1/accounts/pid/xcel-colorado-customer/calculate/
{
    "fromDateTime": "2024-08-15",
    "toDateTime": "2024-09-15",
    "billingPeriod": "true",
    "propertyInputs": [
        {
            "fromDateTime": "2024-08-15",
            "toDateTime": "2024-09-15",
            "keyName": "total",
            "dataValue": "60.49",
            "unit": "cost"
        },
        {
            "fromDateTime": "2024-08-15",
            "toDateTime": "2024-09-15",
            "keyName": "baselineType",
            "dataValue": "typicalElectricity"
        }
    ]
}

The following parameters control the monthly Bill Solve request. You can see the full documentation for Account Cost Calculation.

Important parameters

  1. Before this call, create an account called xcel-colorado-customer with the customer's ZIP code, utility, and tariff. For this example, use Xcel Energy - Colorado's "R" tariff (masterTariffId 599).
  2. Set fromDateTime to 2024-08-15 and toDateTime to 2024-09-15. Use the actual dates on the bill for the most accurate results.
  3. Set billingPeriod to true to include monthly charges, if any, in the calculation.
  4. Add 2 entries to propertyInputs. For the first entry, set keyName to total, dataValue to 60.49, and unit to cost so the calculator interprets the bill amount as dollars instead of kWh.
  5. For the second entry, set keyName to baselineType and dataValue to typicalElectricity to use Typical Baselines for the initial usage estimate. A typical profile can start closer to the customer's actual usage, reducing the number of guesses and response time. It also provides hourly data for more accurate results for time-of-use (TOU) customers.

Run the calculation

Run the request. This response snippet has been shortened to show the estimated usage in summary.kWh:

{
    "status": "success",
    "count": 1,
    "type": "CalculatedCost",
    "requestId": "edec3be8-d471-4ca5-ad2e-940367b0ea33",
    "results": [
        {
            "calculatedCostId": "bac2e4d0-0117-4ff3-970b-dbc238a8a038",
            "masterTariffId": 599,
            "tariffName": "Residential",
            "totalCost": 60.49000000,
            "fromDateTime": "2024-08-15T00:00:00-06:00",
            "toDateTime": "2024-09-15T00:00:00-06:00",
            "currency": "USD",
            "summary": {
                "subTotalCost": 60.49,
                "taxCost": 0.00,
                "totalCost": 60.49,
                "adjustedTotalCost": 60.49,
                "nonBypassableCost": 7.10,
                "kWh": 358.03,
                "kW": 1.03
            }
      ...  

Read the estimated usage from results[0].summary.kWh. This example returns 358.03 kWh for the billing period.

To validate the estimate, send the estimated consumption value back into the calculator and compare the returned bill cost:

POST /rest/v1/accounts/pid/xcel-colorado-customer/calculate/
{
    "fromDateTime": "2024-08-15",
    "toDateTime": "2024-09-15",
    "billingPeriod": "true",
    "propertyInputs": [
        {
            "fromDateTime": "2024-08-15",
            "toDateTime": "2024-09-15",
            "keyName": "consumption",
            "dataValue": "358"
        }
    ]
}

The abbreviated results are:

{
    "status": "success",
    "count": 1,
    "type": "CalculatedCost",
    "requestId": "30bc8d6f-e009-4c20-b158-ba07649cf3bf",
    "results": [
        {
            "calculatedCostId": "8972c045-2b65-48db-8e4a-bf1b6342f229",
            "masterTariffId": 599,
            "tariffName": "Residential",
            "totalCost": 60.49000000,
            "fromDateTime": "2024-08-15T00:00:00-06:00",
            "toDateTime": "2024-09-15T00:00:00-06:00",
            "currency": "USD",
            "summary": {
                "subTotalCost": 60.49,
                "taxCost": 0.00,
                "totalCost": 60.49,
                "adjustedTotalCost": 60.49,
                "nonBypassableCost": 7.10,
                "kWh": 358.00,
                "kW": 0
            } 
      ...

That's how a monthly Bill Solve request works. You can also estimate consumption based on a year's electricity cost.

Annual Bill Solve request

triangle-exclamation

You can use an annual Bill Solve request to turn your customer's annual cost into usage, then run a Savings Analysis with annual usage to calculate solar savings.

Use this template for an annual Bill Solve request:

POST /rest/v1/accounts/pid/{providerAccountId}/calculate/
{
  "fromDateTime": "{analysisStart}",
  "toDateTime": "{analysisEnd}",
  "billingPeriod": "false",
  "propertyInputs": [
    {
      "fromDateTime": "{analysisStart}",
      "toDateTime": "{analysisEnd}",
      "keyName": "total",
      "dataValue": "{annualBillTotal}",
      "unit": "cost"
    },
    {
      "fromDateTime": "{analysisStart}",
      "toDateTime": "{analysisEnd}",
      "keyName": "baselineType",
      "dataValue": "typicalElectricity"
    }
  ]
}

Use the annual option for this example customer:

  1. Residential customer in Baltimore Gas & Electric's territory on the "R" tariff (masterTariffId 674)
  2. Estimated annual cost of $1,700 for the period 2016-10-15 to 2017-10-15

To solve for this customer's annual consumption value, send the following request:

POST /rest/v1/accounts/pid/bge-cust/calculate/
{  
  "fromDateTime": "2016-10-15",  
  "toDateTime": "2017-10-15",  
  "billingPeriod": "false",  
  "propertyInputs": [  
    {  
      "fromDateTime": "2016-10-15",  
      "toDateTime": "2017-10-15",  
      "keyName": "total",  
      "dataValue": "1700",  
      "unit": "cost"  
    },  
    {  
      "fromDateTime": "2016-10-15",  
      "toDateTime": "2017-10-15",  
      "keyName": "baselineType",  
      "dataValue": "typicalElectricity"  
    }  
  ]  
}  

Important parameters

  1. Before this call, create an account called bge-cust with the customer's ZIP code, utility, and tariff. For this example, use Baltimore Gas & Electric's "R" tariff (masterTariffId 674).
  2. Set fromDateTime to 2016-10-15 and toDateTime to 2017-10-15. As with monthly Bill Solve, use the day of the month from the bill to improve precision.
  3. Set billingPeriod to false because this calculation includes multiple billing periods. This matters for tariffs with fixed monthly charges.
  4. Add 2 entries to propertyInputs. For the first entry, set keyName to total, dataValue to 1700, and unit to cost so the calculator interprets the $1,700 annual bill amount as dollars instead of kWh or kW.
  5. For the second entry, set keyName to baselineType and dataValue to typicalElectricity to use Typical Baselines for the initial usage estimate. A typical profile can start closer to the customer's actual usage, reducing the number of guesses and response time. It also provides hourly data for more accurate results for TOU customers.

Run the calculation

Run the request. This response snippet has been shortened to show the estimated annual usage in summary.kWh:

{  
  "status": "success",  
  "count": 1,  
  "type": "CalculatedCost",  
  "results":[  
    {  
      "masterTariffId": 674,  
      "tariffName": "Residential",  
      "totalCost": 1702.21,  
      "fromDateTime": "2016-10-15T00:00:00-04:00",  
      "toDateTime": "2017-10-15T00:00:00-04:00",  
      "currency": "USD",  
      "summary": {  
        "subTotalCost": 1702.21,  
        "taxCost": 0,  
        "totalCost": 1702.21,  
        "adjustedTotalCost": 1702.21,  
        "kWh": 11108.53,  
        "kW": 3.75  
      }  
      ...  

Read the estimated usage from results[0].summary.kWh. This example returns 11108.53 kWh, approximately 11,109 kWh, for the year starting October 15, 2016.

To validate the estimate, send the estimated consumption value back into the calculator and compare the returned bill cost:

POST /rest/v1/accounts/pid/bge-cust/calculate/
{  
  "fromDateTime": "2016-10-15",  
  "toDateTime": "2017-10-15",  
  "billingPeriod": "false",  
  "propertyInputs": [  
    {  
      "fromDateTime": "2016-10-15",  
      "toDateTime": "2017-10-15",  
      "keyName": "consumption",  
      "dataValue": "11109"  
    }  
  ]  
}  

The abbreviated results are:

{  
  "status": "success",  
  "count": 1,  
  "type": "CalculatedCost",  
  "results": [  
    {  
      "masterTariffId": 674,  
      "tariffName": "Residential",  
      "totalCost": 1708.23,  
      "fromDateTime": "2016-10-15T00:00:00-04:00",  
      "toDateTime": "2017-10-15T00:00:00-04:00",  
      "currency": "USD",  
      "summary": {  
        "subTotalCost": 1708.23,  
        "taxCost": 0,  
        "totalCost": 1708.23,  
        "adjustedTotalCost": 1708.23,  
        "kWh": 11109,  
        "kW": 0  
      }  
      ...  

Next steps

After estimating usage from a bill total, you can:


Did this page help you?