Selecting cashiering software is a key decision. The solution you choose will have a major impact on how cashiers work, how citizens pay, how finance reconciles, and how IT maintains the system. State and local governments understand this, but it can be difficult to evaluate the full effects of such a wide-ranging decision. This guide walks through what to evaluate, what questions to ask, and what separates solutions that work from solutions that create new problems.

‍

‍

Why This Decision Matters

‍

Government cashiering software sits at the intersection of three critical functions:

‍

1. Citizen service — The system shapes how residents experience paying their government
2. Financial control — Every dollar collected must be accounted for, reconciled, and audited
3. Operational efficiency — Cashiers use this system all day, every day

‍

A system that fails any of these creates cascading problems: frustrated citizens, reconciliation nightmares, unhappy staff, and audit findings. A system that succeeds at all three will have a meaningfully positive impact on your operations for a decade or more.

‍

The stakes are real. Choose well, and you get a system that makes operations smoother, collections more efficient, and citizens happier. Choose poorly, and the consequences can be profound.

‍

The good news: dozens of state and local governments across the country - from small cities to counties serving millions of residents - have successfully navigated this process and arrived at solutions they are extremely happy with. The path is well-worn if you know what to look for.

‍

‍

Understanding Your Options

‍

Government cashiering solutions generally fall into three categories:

‍

ERP Cashiering Modules

‍

Many ERP systems (Tyler Munis, Oracle, Workday, SAP) include cashiering or point-of-sale modules. These offer tight integration with the financial system but often compromise on:

‍

• Cashier experience — Designed by finance people for finance purposes, not optimized for frontline usability
• Payment flexibility — May lag on modern payment methods (contactless, mobile wallets)
• Multi-department support — Built for one GL structure, awkward for complex organizations

‍

Best for: Agencies with simple cashiering needs who prioritize ERP consistency over cashier experience.

‍

‍

Retail POS Adapted for Government

‍

Some agencies use retail point-of-sale systems (Square, Clover, generic POS software) adapted for government use. These offer:

‍

• Modern interface — Designed for consumer-facing transactions
• Quick deployment — Often SaaS-based with minimal configuration

‍

But they typically lack:

‍

• Government-specific features — Fund accounting, GL distribution, compliance requirements
• Integration depth — Basic or no connectivity to government ERPs
• Audit capabilities — Not built for public-sector scrutiny

‍

Best for: Very small agencies with minimal compliance requirements and simple fee structures.

‍

‍

Purpose-Built Government Cashiering

‍

Solutions designed specifically for government cashiering combine:

‍

• Cashier-optimized interface — Built for the actual work of processing government payments
• Government-specific architecture — Fund accounting, multi-department, audit trail by design
• Deep ERP integration — Native connections to Tyler, Oracle, Workday, and other government systems

‍

Purpose-built platforms have typically been deployed across dozens or hundreds of state and local governments, refining their capabilities based on real-world requirements and feedback received from public servants.

‍

Best for: Agencies that need both strong cashier experience and robust financial integration.

‍

‍

Build vs. Buy

‍

Some larger agencies consider building custom solutions. This rarely makes sense:

‍

• Development cost — Custom government software is extremely expensive to create, even if everything goes according to plan
• Ongoing maintenance — You own every bug, every security patch, every upgrade
• Opportunity cost — IT resources spent maintaining cashiering aren't available for other priorities
• Risk — No user base means no track record; you're the pilot customer for your own software

‍

Unless you have needs so unique that no commercial solution can meet them, buying beats building.

‍

‍

Essential Capabilities

‍

Regardless of which category you're evaluating, look for these core capabilities:

‍

Payment Processing

• All payment types — Cash, check, card (EMV + contactless), ACH
• Split tender — Multiple payment methods in one transaction
• Partial payments — Accept less than the full amount when policy allows
• Fee handling — Convenience fees with clear disclosure

‍

Cash Management

• Drawer tracking — Opening counts, activity tracking, reconciliation
• Over/short reporting — Document and investigate discrepancies
• Safe/vault support — Multi-level cash tracking for larger operations
• Deposit preparation — Batch for bank pickup

‍

Receipt Management

• Flexible formatting — Department-specific branding and content
• Multiple delivery — Print, email, or both
• Reprint capability — Retrieve any historical receipt
• Receipt journal — Complete record for audit

‍

Financial Distribution

• GL coding — Automatic distribution to correct accounts
• Fund accounting — Public-sector fund structure support
• Multi-department — Different GL structures for different departments
• Split distributions — Complex payments coded to multiple accounts

‍

Reporting

• Real-time dashboards — Current activity at a glance
• Standard reports — Daily, weekly, monthly operational reports
• Custom reporting — Build reports for specific needs
• Export capability — Get data out in standard formats

‍

Audit Trail

• Complete logging — Every transaction, every action, every user
• Tamper-proof — Audit records that can't be modified after the fact
• User attribution — Who did what, when
• Export for auditors — Standard format for external review

‍

‍

Integration Requirements

‍

Cashiering doesn't exist in isolation. The system must connect with your existing infrastructure:

‍

ERP Integration

‍

This is often the most critical integration. Questions to ask:

‍

• Native connector or custom? — Native integrations are more reliable and maintainable
• Real-time or batch? — Real-time posting reduces reconciliation lag
• Bi-directional? — Can you pull balances from the ERP, or only push transactions?
• Which ERPs supported? — Verify your specific system and version

‍

The best platforms support extensive integration libraries — 90+ systems in some cases — covering the ERPs government agencies actually use.

‍

‍

Payment Processing

• Processor relationships — Can you keep your current processor, or must you switch?
• Semi-integrated vs. integrated — Semi-integrated keeps you out of PCI scope
• EMV certification — Verify chip card support is certified, not "coming soon"

‍

‍

Billing Systems

‍

If you have department-specific billing systems (utility billing, court case management, permitting), can the cashiering system:

‍

• Look up balances in real-time?
• Post payments back to the source system?
• Handle system-specific business rules (late fees, payment plan structures)?

‍

‍

Authentication

• SSO support — Integrate with your existing identity provider (Azure AD, ADFS)
• Role-based access — Permissions based on user roles, not individual accounts
• Audit of access — Track who logged in when

‍

‍

Document Management

• Receipt storage — Where do receipts live long-term?
• Integration with DMS — If you have a document management system, can receipts flow there?

‍

‍

Deployment and Operations

‍

How the system runs matters as much as what it does:

‍

Hosting Model

‍

Cloud/SaaS advantages:

‍

• No infrastructure to maintain
• Automatic updates and patches
• Disaster recovery included
• Typically lower upfront cost

‍

On-premise considerations:

‍

• Full control over data location
• May be required by policy
• You own maintenance and updates
• Higher upfront, potentially lower long-term

‍

Hybrid options:

‍

• Cloud hosting with data residency guarantees
• Private cloud environments for sensitive agencies

‍

Most agencies today choose cloud deployment for faster implementation and reduced IT burden.

‍

‍

Reliability

• Uptime commitment — Look for 99.9%+ SLA
• Redundancy — What happens when the primary system fails?
• Disaster recovery — RPO (how much data can you lose) and RTO (how fast can you recover)
• Track record — Ask for uptime history, not just promises

‍

For reference, leading platforms maintain AWS-hosted infrastructure with primary and disaster recovery regions, offering RPO measured in minutes and RTO within one business day.

‍

‍

Security

• SOC 2 certification — Third-party validation of security controls
• PCI compliance — How do they handle payment card data?
• Encryption — In transit and at rest
• Penetration testing — Regular security assessment

‍

‍

Updates and Maintenance

• Update frequency — How often does the system improve?
• Update process — Do updates require downtime? How much notice?
• Backwards compatibility — Will your integrations break with updates?

‍

‍

Vendor Evaluation

‍

The software matters, but so does the company behind it:

‍

Stability and Focus

• How long in business? — Longevity indicates sustainability
• Government focus — Is government their core market, or a sideline?
• Customer count — Enough customers to fund ongoing development and ensure stability of operations
• Financial health — Will they be around in 10 years?

‍

Look for vendors with decades of government experience and customer bases large enough to sustain development (50+ state and local governments) but focused enough to provide personal attention.

‍

‍

Support Model

• Support hours — When can you reach someone?
• Response time — How fast for urgent issues?
• Support channels — Phone, email, chat, ticket system?
• Escalation path — What happens when first-level support can't help?

‍

‍

Reference Customers

• Similar agencies — Ask for references from agencies like yours (size, complexity, ERP)
• Recent implementations — Talk to customers who went live recently, not just long-term users
• Honest conversations — Ask references what didn't go well, not just what did

‍

The most telling metric: client retention. Buyers vote with their feet when they are unhappy. Vendors with 100% retention have proven they can deliver over a long period of time.

‍

‍

Implementation Approach

• Who does the work? — Vendor staff, partners, or DIY?
• Methodology — What does their implementation process look like?
• Timeline — Realistic? What drives the schedule?
• Training — What's included, and what costs extra?

‍

‍

Total Cost of Ownership

‍

The purchase price is often the smallest part of the total cost:

‍

Direct Costs

• Software licensing — Perpetual or subscription
• Implementation — Configuration, integration, data migration
• Training — Initial and ongoing
• Hardware — Receipt printers, cash drawers, card terminals, workstations

‍

Ongoing Costs

• Annual maintenance/subscription — Typically 15-25% of license cost annually
• Support tiers — Premium support often costs extra
• Transaction fees — Some systems charge per transaction
• Integration maintenance — When your ERP upgrades, does the integration need work?

‍

Hidden Costs

• Internal staff time — Project management, testing, training delivery
• Customization — Anything non-standard will cost more
• Future modules — Will you need features not in the base price?
• Exit costs — What happens if you need to switch?

‍

Cost Comparison

‍

When comparing vendors, normalize the comparison:

‍

• Same time horizon (5-year TCO is more meaningful than Year 1 cost)
• Same scope (include all modules you'll need)
• Same assumptions (transaction volumes, user counts)

‍

‍

Implementation Considerations

‍

How you implement matters as much as what you implement:

Phased vs. Big Bang

‍

Phased rollout:

‍

• Lower risk — problems affect fewer users
• Learning opportunity — apply lessons to later phases
• Extended timeline — longer to full value
• Integration complexity — may need to run parallel systems

‍

Big bang:

‍

• Faster to full value
• Simpler — no parallel systems
• Higher risk — problems affect everyone
• Requires more upfront preparation

‍

Most agencies benefit from a phased approach, starting with a pilot department. This is how successful implementations typically proceed — building confidence and expertise before expanding.

‍

‍

Data Migration

• What data moves? — Transaction history, account balances, configuration
• Data quality — Garbage in, garbage out; clean data before migration
• Validation — How will you verify the migration worked?
• Cutover timing — When does the old system stop and the new one start?

‍

‍

Change Management

‍

Technology is the easy part. People are harder:

‍

• Stakeholder buy-in — Finance, IT, departments, cashiers all have interests
• Training adequacy — Don't underestimate training time
• Communication — Keep everyone informed throughout
• Post-go-live support — Extra support during the transition period

‍

‍

Success Criteria

‍

Define what success looks like before you start:

‍

• Specific metrics (transaction time, error rate, cashier satisfaction)
• Timeline milestones
• Stakeholder sign-off criteria

‍

‍

Evaluation Checklist

‍

Use this checklist when evaluating solutions:

‍

Core Functionality

- [ ] All payment types supported (cash, check, card, ACH)

- [ ] Split tender transactions

- [ ] Partial payment support

- [ ] Cash drawer management and reconciliation

- [ ] Complete audit trail

- [ ] Flexible receipt formatting

- [ ] Real-time and historical reporting

‍

Integration

- [ ] Native integration with your ERP (specify: _____________)

- [ ] Semi-integrated payment processing (PCI scope reduction)

- [ ] SSO/identity provider integration

- [ ] API availability for custom integrations

‍

Operations

- [ ] Cloud/SaaS option available

- [ ] 99.9%+ uptime SLA

- [ ] SOC 2 Type 2 certification

- [ ] Documented disaster recovery (RPO/RTO)

‍

Vendor

- [ ] 10+ years in government market

- [ ] 50+ government customers

- [ ] References from similar agencies

- [ ] Transparent pricing

- [ ] High client retention rate

‍

Implementation

- [ ] Vendor-led implementation available

- [ ] Phased rollout supported

- [ ] Training included

- [ ] Post-go-live support plan

‍

‍

How Teller Can Help

‍

Teller Government Cashiering checks every box on this evaluation — and has proven it across 80+ state and local government deployments.

‍

‍

Purpose-Built for Government

‍

Teller isn't adapted retail software or an ERP afterthought. It's designed from the ground up for government revenue collection:

‍

• Fund accounting — Proper GL distribution across funds and departments
• Multi-jurisdiction — Support for shared services, regional authorities, multi-entity agencies
• Government compliance — SOC 2 Type 2 certified, PCI-compliant semi-integrated architecture
• Audit-ready — Complete, tamper-proof transaction logging

‍

‍

Integration Depth

‍

With 90+ pre-built integrations, Teller connects to what government agencies actually use:

‍

• ERPs — Workday (43 deployments), Oracle, Tyler Munis, SAP, PeopleSoft
• Billing systems — Harris NorthStar, Tyler Incode, CIS Infinity
• Permitting — Accela, Tyler EnerGov, CentralSquare
• Tax systems — Tyler iasWorld, Aumentum

‍

Real-time, bidirectional integration — not just file exports.

‍

‍

Proven Scale

‍

Teller supports state and local governments across the population spectrum:

‍

• Small cities — Under 50,000 residents
• Mid-size counties — 500,000+ residents
• Major metropolitan areas — Millions of residents

‍

Teller is a proven system that handles millions of transactions for some of the largest cities and counties in the United States.

‍

‍

100% Client Retention

‍

This is the number that answers "will this work for us?" Every state and local government that has chosen Teller has stayed.

‍

100% retention across 80+ clients.

‍

That includes:

‍

• Tulsa County, OK (650,000 pop.) — Replaced a legacy system
• Clark County, WA (508,000 pop.) — 7+ year partnership, expanded over time
• City of Ontario, CA (176,000 pop.) — Full Workday integration
• City of Miami, FL (454,000 pop.) — Salesforce integration

‍

When agencies stay, it's because the platform works and the partnership delivers.

‍

‍

Implementation Expertise

‍

Teller's implementation team has guided 80+ successful deployments:

‍

• Phased rollouts — Reduce risk, build confidence
• Proven timelines — Based on real experience with agencies like yours
• Training — Cashiers typically comfortable within hours
• Integration — Pre-built connectors accelerate go-live
• Ongoing support — Partnership that doesn't end at launch

‍

‍

Cloud-First Operations

‍

Teller is hosted on AWS with:

‍

• Primary region — Oregon
• Disaster recovery — Virginia
• RPO — 5 minutes (minimal data loss in disaster)
• RTO — 1 business day (fast recovery)
• SOC 2 Type 2 — Annual third-party security audit

‍

Cloud deployment means faster implementation, automatic updates, and no infrastructure burden on your IT team.

‍

‍

Ready to evaluate Teller for your agency? Contact us for a demo and to discuss your specific requirements.