Transactions & payments
Payments
Every payment recorded once, against the service it paid for.
Record a permit fee, a citation, a water bill, and a rec registration against the same bilingual ledger. Each payment is tied to the thing it paid for, every payer gets a receipt in their language, and finance reconciles once — not four times. Card payment is on the roadmap; today the module records and reconciles the payments your office takes by check and at the counter.
The challenge
A typical local government collects money through four or five systems that don't talk to each other — one for utilities, one for the court, one for permits, plus the cash drawer. Finance staff lose days every month stitching deposits together, and when a resident asks where their payment went, nobody can answer from one screen.
In practice
Four payments, one Friday, one ledger
On a Friday, a contractor's permit fee, a resident's water bill, a driver's citation, and a parent's two summer-ball registrations all come in — by check and at the counter. Each is recorded against the service it paid for, and each payer gets a receipt in the language on their profile. Four different services, one ledger — not four spreadsheets to reconcile later.
On Monday, the finance director opens that one ledger and sees all of it: permits, fines, fees, and utilities, every payment tied to its source. A duplicate from the weekend is corrected from the same record, with the ledger and the receipt updated together. Reconciling against the bank deposit takes minutes, and the month-end report comes from data that was never scattered across systems.
What it does
- 01
One ledger for every service
Permit fees, fines, utility bills, and registrations are all recorded in the same bilingual ledger, each tied to what it paid for.
- 02
Built to add card payment
The module is built on a payment provider integration so online card payment can switch on when your entity is ready — recording and reconciliation work today regardless.
- 03
Receipts in the payer's language
Every payment is confirmed with a receipt in English or Spanish, matching the payer's language.
- 04
One ledger across everything
Each dollar posts to a single ledger, tied to the permit, bill, fine, or registration it paid for.
- 05
Corrections and refunds on the record
Handle a refund or correction right where the payment lives; the ledger and the receipt update with it.
- 06
Reconciliation in minutes
Match the bank deposit against the ledger without exporting and re-stitching spreadsheets.
- 07
Reports finance can stand behind
Revenue by service, department, and period — from one source, not five.
How it works
A payment comes in
By check or at the counter, against any module — recorded in English or Spanish.
The receipt goes out
A bilingual receipt confirms the payment in the payer's language.
The ledger records it once
The payment posts to one ledger, linked to whatever it paid for.
Finance closes the loop
Reconcile the deposit, handle refunds when needed, and report from a single source.
English and Spanish
Bilingual by design
The confirmation, the receipt, and any refund notice all follow the payer's language. A contractor whose account is in Spanish gets a Spanish receipt he can file with his records — every time, on every service.
Premium AI add-on
CiVQ AI: a second set of eyes on the ledger
CiVQ AI watches the ledger for anomalies — duplicate entries, amounts that break the pattern — and flags them before finance has to hunt them down. It speeds reconciliation by suggesting matches against the deposit, and it can answer a payer's "what is this charge?" in English or Spanish, straight from the payment record.
Get started
See CiVQ in your language.
Book a 30-minute walkthrough with our team in Rio Grande City. We'll tailor it to your city, county, or district.
Bilingual support included at every tier.