Specialist technology and software for state and local government info@hqt.orgCommunitiesGlossarySearch

Print and mail

Statement and Notice Print and Mail

Utility bills, tax notices, delinquency letters, and the other high volume mail an agency sends on a cycle.

What this covers

Statement and notice print and mail is the production mail an agency sends on a cycle: utility billing statements, property tax notices, delinquency and shutoff notices, and renewal reminders. Every run has a release date, a population it must reach, and a payment deadline that depends on the mail arriving on time.

None of it originates in a print shop. The documents come out of utility billing, tax and assessment, permitting, case management, and records systems. The work begins where one of those systems produces an extract or print file and ends at acceptance by the Postal Service. Most of the difficulty sits upstream of the press: which accounts are suppressed, which inserts go to which group, how a payment posted after the extract is reflected, and who approves the cycle before it releases.

Buyers are usually utilities, finance and treasurer offices, tax collectors, clerks, and courts. IT is normally involved, because the interface, the data handling, and the archive integration are its responsibility even when another department holds the contract.

Typical activities

  • System handoff and data mapping. Defining the extract the source system produces, mapping each field to its place on the page, and agreeing on control totals, arrival windows, and a check that stops a short or malformed file before it prints.
  • Document composition. Building the templates that turn records into a print-ready file, commonly AFP, PostScript, or PDF, with remittance stubs, sequence marks for insert integrity, Intelligent Mail barcodes, and an address block placed for postal automation.
  • Address hygiene and presort. Standardizing addresses with CASS certified software, applying move update processing such as NCOALink, and presorting for automation rates. Postal rules change, so confirm them against current Postal Service publications.
  • Proofing and cycle approval. Pulling a sample from real cycle data, including the cases that break layouts: credit balances, zero amounts due, final bills, and estimated reads. Approval is recorded against a named approver before release.
  • Suppression and reprint handling. Applying the exclusions that must happen before print, among them paperless enrollment, bad address flags, bankruptcy, deceased account holders, and legal holds, then running defined reprints without re-releasing the cycle.
  • Inserts and selective inserting. Handling the inserts everyone receives and the selective ones for a subset, such as an assistance program notice, with mark driven matching so the right pages and inserts stay with the right account.
  • Reconciliation and return mail. Tying pieces printed and mailed back to the input count, resolving every record to mailed, suppressed, held, or failed, and posting undeliverables and address corrections back to the source system.

What you receive

  • Composed templates and print-ready output files, with mapping documentation showing how each field reaches the page.
  • A proof set for each cycle and the approval record naming who signed off and when.
  • Postal documentation and reconciliation reports covering input counts, suppressions, pieces produced, and pieces mailed, in a form that can be retained for audit.
  • A searchable archive of rendered documents by account and cycle, retrievable by staff and by a self service portal.
  • A runbook with the cycle calendar, handoff checks, approvals, and the fallback for a late or failed file.

Considerations for public agencies

A missed cycle is a cash flow event. Revenue arrives in response to mail, and penalty, interest, and lien dates are often fixed by statute or ordinance rather than by the department. Build the calendar backward from those dates and decide in advance when a cycle will be held.

Notice content and timing are frequently prescribed by law. Shutoff notices, delinquency notices, and notices carrying appeal rights may have required wording, a minimum lead time, and a required delivery method such as certified mail. Treat that text as legal content controlled by counsel, and confirm it against the current statute or ordinance.

The data is sensitive and the output is itself a record. Account numbers, consumption history, and payment status are personally identifiable information an outside party will handle, while the mailed document, proof approvals, and suppression lists may be public records or fall under a retention schedule. Settle in writing where data is stored, who may access it, and how long it is kept.

Release authority is a financial control. Put in writing who may release a cycle, suppress an account, or order a reprint, and log each use.

Accessibility and language access apply to printed output. Agencies commonly need alternate formats on request, and language assistance for covered populations, so decide how a request is received, flagged in the source system, and reflected in the output. Obligations vary, so confirm them with counsel.

Postage is a cost set by the Postal Service and belongs apart from service pricing in a contract. Because volumes shift with growth and paperless adoption, pricing should say how it responds to volume. Require that templates, mapping documentation, suppression logic, and the archive come back in a usable format when a contract ends.

Working with HQT on this

HQT works on the system side of production mail: the extracts and interfaces out of billing, tax, court, and permitting systems, document composition, suppression and approval rules, reconciliation reporting, and the archive that staff and portals read from. An engagement usually begins with a review of one current cycle, from the file leaving the source system to the point where it waits or fails.

Frequently asked questions

Our billing system already produces a print file. Isn't that most of the work?

The print file is usually the straightforward part. The harder parts are the rules applied before and after it: which accounts are suppressed, which inserts go to which group, how late payments and adjustments are reflected, who approves the run, and how every record is accounted for afterward. Those rules live between the billing system and the mail, and they are where cycles go wrong.

What should we check before approving a cycle for release?

Proof against a sample drawn from the actual cycle data, not test data, and include the accounts that break layouts: credit balances, zero amounts due, final bills, estimated reads, and long or multi page accounts. Confirm that totals reconcile to the extract, that the suppression list was applied, and that each insert reached the intended group. Record the approval against a named person so the decision is traceable later.

What happens if the extract from the source system is late or fails validation?

Decide that in advance rather than during the run. The handoff should include a validation check that stops a short, duplicated, or malformed file, and a documented decision point for whether to hold the cycle, release a partial run, or shift the schedule. Because penalty, interest, and lien dates are often fixed by statute or ordinance, the fallback needs to be reviewed against those dates and with counsel before it is needed.

Does paperless billing remove the need for this service?

It reduces the volume but rarely eliminates it. Enrollment is partial and shifts over time, and many statutory notices still require paper, and in some cases certified mail or another specified delivery method. Confirm which notices may be delivered electronically against the current statute or rule and with your counsel, because the answer varies by state and by program.

How should postage be handled in the contract?

Postage is a cost set by the Postal Service, so it is normally treated as a pass through and kept separate from the service price. Ask for the postal documentation and qualification reports from each mailing so the agency can verify what rates the mail actually qualified for. Postal pricing and presort requirements change, so confirm current rules against Postal Service publications before relying on a rate assumption in a budget or a solicitation.

Get in touch

Have a project or a solicitation coming up?

Talk with an HQT engineer. We respond to agency, corporate, and partner inquiries promptly.