Brokerage ops

Forward a photo of a shared utility bill and n8n reads the bill with AI vision, splits the total across rental units by occupancy weight, and emails each tenant their share

An n8n template by Khairul Muhtadin for landlords with units on one shared utility meter. An email-forwarding rule or intake form posts the bill image to an n8n webhook, and OpenAI's vision model reads the provider, billing dates, period, and total amount from the bill photo. Bills the model cannot read, or bills without a positive total, are logged to Postgres and flagged to the team on Discord and Gmail instead of being split. For valid bills, the workflow loads the tenant roster from Postgres and splits the total across units in proportion to each unit's occupancy weight, with cent-accurate rounding done in code rather than by the model. The workflow stores the bill and the per-unit charges in Postgres, posts a summary to Discord, emails the owner the full breakdown, emails each tenant the tenant's own charge, and marks the bill done. A daily sweep posts a follow-up list of any bills not marked done (or an all-clear) to Discord and the owner.

At a glance

Tools used
n8nOpenAIPostgresGmailDiscord
Category
Brokerage ops
Audience
landlord, property manager
Difficulty
Builder
Source
Split shared rental utility bills with gpt-5.6-terra Vision, Postgres and Gmail
Khairul Muhtadin (n8n creator) · n8n template · Sep 3, 2026
First step
Create the ub_tenants, ub_bills, and ub_meter_readings tables in Postgres, fill ub_tenants with each unit's tenant name, email, and occupancy weight, connect OpenAI, Postgres, Gmail, and Discord credentials, then post one past utility bill photo to the utilitybill webhook and compare the split against your own spreadsheet before telling tenants.

Compliance note: Check your lease and your state or city rules before billing tenants for shared utilities, since some places restrict ratio utility billing or require the split method to be written in the lease, and keep the bill images and tenant emails in a database only you and your manager can access.

Suggested prompt

Written by this directory, inspired by the source. Replace the [bracketed] parts.

Read the attached utility bill image and return JSON with: provider, account_number_last4, service_period_start, service_period_end, bill_date, due_date, total_amount_due (number only), and currency. If any field is not printed on the bill or is not legible, set that field to null instead of guessing, and add a field called unreadable_notes that says which part of the bill image was unclear. Do not calculate any per-unit split; return only what is printed on the bill.

Share on X Read the source

← All use cases