Staff create a one-time charge for a resident, such as a permit fee, a license renewal or a parks program, and the resident pays it in the app. There is nothing to set up on the resident's side beyond the city app. Receipts and invoices stay in their account.
Create a service account for a utility address, import accounts from a CSV, and link residents to them, with staff approving each link. Send a statement PDF for any date range. Staff post charges to a service account, and an administrator reviews and approves them before any resident sees them.
A permit or license fee is billed by staff and paid in the app. Recreation program registrations charge through the same engine. Facility booking requests are approved by staff; facility fees are handled by your office today and are not charged in the app.
Rolling out this year with Bloomz Pulse for Cities: a city sees collections by department in one view: collected, outstanding, and past due for every department with payments turned on and a payment account set up, including departments nested under another department or under a neighborhood. The figures match the city's own Payments summary, and each department admin can open their own department's view.
No. Bloomz does not calculate metered charges and does not generate bills on a schedule. Your utility system works out the amounts, and staff post them to a service account as draft charges for review. Residents view and pay what is posted and can download a statement PDF.
No. A resident pays on their own account in the city app. Staff bill them directly.
Bloomz collects the fee. The application and inspection steps stay in your permitting system.
Your city is onboarded to a payment processor first. That is part of launch.
No. Payments are part of the subscription, not metered by population. Card and bank-transfer processing fees are passed through.
A short call focused on your city's size, your priorities and the systems you use today, not a generic pitch.