Guides
Part of Apartment EV charging billing reviews: records, routes, roles and costs to check
How to build a preliminary apartment EV charging billing budget worksheet
A preliminary worksheet for apartment EV charging billing budgets, with cost bands, Oklahoma's charger tax receipt rule, NIST data roles and approval gates.
A preliminary apartment EV billing budget describes the work needed to reach a decision. It is not a fee policy and not a promise about what a resident pays. Separate record collection, provider scope, payment setup, and resident notices. Then handle contract review and open local questions.
What to take away
- Oklahoma requires covered public charger operators to state a specific tax on the receipt or invoice, per the Alternative Fuels Data Center entry. Confirm whether your site is a covered operator with the Oklahoma Tax Commission before you treat that line as a project cost.
- Give every budget line a boundary, a source, an amount or range, an uncertainty note, an approval owner, and a next trigger. Mark a line "pending source" rather than burying it in contingency.
- Use the NIST Privacy Framework to ask three questions before account or payment work enters scope: what is the data purpose, who holds access, and who reviews it.
- Keep the estimate, its assumptions, its approval, and the version it replaced together, following the National Archives records-management introduction.
- Ask the provider to split recurring charges from one-time setup, field work, and migration work, and to date every rate assumption.
What the Oklahoma receipt rule actually covers
The AFDC entry describes a state rule that applies to covered public charger operators. Those operators must state the listed tax separately on a receipt or invoice.
Oklahoma sets that tax at 3 cents per kilowatt-hour of electricity dispensed at a public charging station. A 40 kilowatt-hour session carries about $1.20 in state tax at that rate.
It does not reach every charger and does not reach every apartment property. Before you book a tax or receipt line as settled, identify the jurisdiction, whether the equipment is publicly accessible, and which documents the rule requires.
That determination belongs to the Oklahoma Tax Commission and to a CPA, not to a budget worksheet. Record the question, the answer, and the date you asked.
What changes by 2027
Nothing in the worksheet changes because of the year. What changes is how many assumptions expire before 2027.
Today you price work you can quote now. A plan that runs into 2027 carries quotes that expire and contracts that renew.
- Hardware, labor, and field quotes typically hold 30 to 90 days.
- A network contract signed in 2026 often renews in 2027 at the provider's then-current rate.
- Utility energy and demand charges reset on their own schedule. Date each to the tariff sheet you used.
- The federal refueling property credit under section 30C is not allowed for property placed in service after June 30, 2026, and it covers eligible census tracts only. Confirm with a tax adviser.
Data purpose and access roles before payment setup
The NIST Privacy Framework matters once a budget includes account setup, payment support, or reporting. It does not set what a property must spend. It forces three questions before sensitive information enters the operating scope.
Data purpose and access roles
- What is the stated purpose for collecting the data?
- Which role can see or change it?
- Who reviews access, and on what schedule?
Answer those in writing and attach them to the estimate. A processor quote that omits data retention and staff review looks cheaper than it is.
Worksheet columns
| Column | What goes in it |
|---|---|
| Task | The specific work, not a category |
| Boundary | What the property controls and what it does not |
| Source | The document, quote, or rule the number came from |
| Amount or range | A figure, a range, or "pending source" |
| Uncertainty | What would move the number |
| Approval owner | Who can authorize this line |
| Next trigger | The event that reopens it |
A line marked "pending source" is honest. A line folded into contingency hides work you have not scoped.
Typical U.S. planning bands, not quotes:
Cost estimates
- $1,500 to $4,500per portNetworked Level 2 hardware
- $2,000 to $15,000per siteElectrical work and service upgrade
- $10 to $30per port per monthNetwork or software fee
- 2 to 4percent of session revenuePayment processing
- $3 to $10per port per monthResident support and dispute handling
- $500 to $5,000per siteSetup, commissioning, and data migration
- 3cents per kilowatt-hourOklahoma public charging tax
Replace each band with a written number from your provider before the line is approved.
The Department of Energy's electric-vehicle financial considerations training notes that charging costs span multiple elements. It is not a budget model for an apartment service. Read it as a reason to name the input behind each line.
Approval gates
Place a gate before each stage. A gate can approve source collection, request missing terms, authorize one limited setup task, or stop work while a local review is open.
Worksheet columns to fill
- Taskspecific work, not category
- Boundarywhat property controls
- Sourcedocument, quote, or rule
- Amount or rangefigure or pending source
- Uncertaintywhat would move the number
- Approval ownerwho authorizes the line
- Next triggerevent that reopens it
At each gate, record what changed, the date, the source, the owner, and whether the change is approved, proposed, or still under review. A new support requirement, a resident notice, a billing route, or a shifted provider responsibility can move the budget without making the first estimate careless.
Split the cost by responsibility
Separate these areas:
- configuration
- data access
- resident support
- dispute handling
- payment processing
- reporting
- closeout
One quote, split two ways
An example quote dated January 12, 2026 covers four ports. Recurring: $18 per port per month for network and support, plus 3 percent of session revenue for card processing. One-time: $2,400 for setup and commissioning, $900 for field verification, $600 for account migration.
The recurring rate holds through December 31, 2026, and later field work bills at time and materials.
If the owner changes the billing model later, build a revised option instead of treating the original setup estimate as a running operating price.
Worked example: one line, revised
A property budgets resident support at a flat monthly figure. The provider later confirms support covers only business hours, and after-hours calls route to the property's own staff.
The revision names the new boundary (property staff absorb after-hours), the source (the provider's current terms), the owner (the board or owner who approves staff time), and the trigger (a signed agreement). Nothing about the first estimate was careless; the boundary simply moved.
Common questions
Is a provider quote the complete billing budget?
No. It is one source among several. Compare its stated scope, exclusions, data needs, resident support, and local-review assumptions against what the property has actually decided.
When should the budget change?
Revise it when the property boundary, provider arrangement, payment route, or policy changes. Revise it when the jurisdiction or approval condition changes. Each of those is a trigger, and each should appear in the worksheet before it fires.
Who can approve the next step?
The property should name the person or process authorized for that decision and keep the approval record with the estimate it authorized. That record is what lets a later manager see why the work changed.
Does a Level 1 program change this budget?
It can. A Level 1 charging program shifts cost from networked payment hardware toward resident communication and outlet-level controls, so the line items move even when the total does not.
