Utility bill OCR
Bills in. Readings out.
Upload an electricity, gas, water or phone bill, forward it by e-mail or send it to the API. Parsevix returns the supplier, account, billing period, meter readings, consumption and charges as structured data, ready for cost tracking or re-billing.
- Meter readings, consumption and unit
- Charges, previous balance and amount due
- Personal data masked automatically before the AI step
No credit card · 20 free pages every month
What you get back
Supplier, meter and charges, already defined.
The built-in Utility Bill category returns 25 fields: the service, the supplier, the account, the bill details, the meter and consumption, and the charges. Use it as it is, or change it in your project.
Dates come back as ISO dates and readings and amounts as plain numbers, however the bill prints them; the unit comes back as printed. A field the bill doesn't show, such as the supplier's website, is left out, not guessed.
Service
- service_typestring
Supplier
provider_infoobject
- provider_namestring
- provider_addressstring
- provider_phonestring
- provider_websitestring
Account
account_infoobject
- account_numberstring
- account_holderstring
- service_addressstring
Bill details
bill_detailsobject
- bill_numberstring
- bill_datedate
- due_datedate
- billing_periodstring
- currencystring
Meter and consumption
meter_infoobject
- meter_numberstring
- previous_readingnumber
- current_readingnumber
- consumptionnumber
- unit_of_measurestring
Charges
chargesobject
- usage_chargenumber
- fixed_chargenumber
- tax_amountnumber
- total_duenumber
- previous_balancenumber
- amount_paidnumber
- balance_duenumber
Your own fields
A name, a type and one sentence on what it is.
- tariff_name
- reading_type
- contract_end_date
- co2_emissions
Made for recurring bills
Every month's bill, comparable.
Utility bills arrive every month from many suppliers, each with its own layout and units. This is what Parsevix does with them.
Consumption over the months
Each bill's meter readings, consumption and unit come back as fields of their own. Collect them per site or meter, and your own tool can chart consumption and cost month by month, or pass them on for energy reporting or for re-billing tenants.
- 02
Electricity, gas, water, internet, phone
The same category reads every kind of utility bill. The service type says which one it is, and the unit comes back as the bill prints it: kWh, m³ or another.
- 03
Any supplier's layout
There is no template per supplier. A bill from a supplier you have never had before fills the same fields as every other one.
- 04
What is still open
Previous balance, payments received and balance due are fields of their own, next to the charges of the period, so arrears don't hide in a total.
- 05
Many sites, one inbox
Send the bills of every building to the same project address. The supply address and the meter number tell them apart in your data.
- 06
Names and addresses masked
Account holder names and supply addresses are masked automatically before any text goes to the AI model and put back in your result. Detection catches most personal data, not necessarily every item.
- 07
Every value linked to the page
Each value is linked to the spot on the bill it came from. Click it in the dashboard to see where it was printed.
How bills get in
Upload them, forward them or send them from your system.
Dashboard
Upload bills as PDFs or scans. Check each result next to its page, with every value marked where it was printed, and approve it.
E-mail address
Paid plansEvery project gets its own address. Have suppliers send their bills there, or forward them: each attachment becomes a document.
API
Send bills from your property or facility system and get the JSON in the same response, or receive results by signed webhook or through Zapier.
Request
curl https://parsevix.com/api/v1/extract \ -H "X-API-Key: $PARSEVIX_API_KEY" \ -F file=@electricity-bill.pdf \ -F category="Utility Bill"
The request stays open until the document is read and answers with the JSON.
- POST /documentsUpload without waiting; the result arrives by webhook or callback.
- POST /extract-autoNo category: every field Parsevix finds, named as in the document.
- POST /classifyOnly the document's category, for 1 credit.
Response · trimmed
Security & compliance
- PII maskedautomatically, before the AI step
- Encryptedin transit and at rest
- No AI trainingon your documents
- API files deletedafter processing
Priced per page, not per feature.
Every plan reads, sorts and masks documents the same way. Picking the category is included, and a document that fails costs nothing.
See pricing- credit per page
- 1
- free pages every month
- 20
- a month for 500 pages
- $39
Utility bill FAQ
Utility bills,
answered.
What teams ask before they send their first bills.
PDF, Word (DOCX), PNG, JPG and TIFF, up to 10 MB and 30 pages each. Scans and phone photos of paper bills work too; every page is read as an image.
Not out of the box: the category has no field for it. Add one to the category in your project, such as reading_type, with a sentence saying what to look for, and it is filled whenever the bill prints it.
Put one bill in each file. A PDF with several bills is read as one document, so their readings and charges would end up in one result.
Yes. Change the Utility Bill category in your project and add the fields you need, such as the tariff name, the contract end date or the CO₂ figure the bill prints, each with a sentence on what it is. A field is filled only from what the bill shows.
One credit per page: a two-page bill uses two. Choosing the category is included, and if a document fails, its credits are given back.
Bills uploaded in the dashboard or sent by e-mail stay in your project until you delete them. Files sent through the API are deleted after processing unless you turn on keeping them for the project. Your bills are never used to train AI.
Related use cases