Where Is Teller Hosted, and How Reliable Is It?
Teller runs on AWS (Oregon primary, Virginia DR) with a 99.9% business-hours SLA, annual SOC 2 Type 2, and 5-minute RPO.
No results.
Teller government cashiering treats voids, refunds, and adjustments as core back-office workflows, not afterthoughts. Each correction is captured in the transaction record, governed by configurable permissions, and synced back to the connected ERP. Because Teller integrates bidirectionally, a void or adjustment updates both Teller and the back-office system, so records stay aligned.
In a government cashiering context, the three corrections serve different situations:
Teller supports all three as distinct, recorded actions rather than as informal edits to a transaction.
Yes. Teller's integration with government ERPs is bidirectional, so corrections flow both ways. When a payment posts, the receipt updates the back-office system; when that payment is later voided or adjusted in Teller, the correction syncs back as well. This keeps the cashiering record and the ERP record aligned without staff re-keying the change in a second system. For more on how this connects to your general ledger and reporting, see Management Reporting.
Corrections are exactly where governments need control and a clear trail, and Teller is built for that:
The result is that a supervisor can correct a mistake quickly while finance retains a complete, reconciled record of what happened and why.