%402x.svg)
No results.
Revenue Submission is an add-on module of Teller Government Cashiering that lets low-volume departments submit collected revenue to Finance digitally, instead of walking cash and checks to a central cashier counter with a paper deposit slip. A parks office, a small clerk's window, or a satellite building enters what it collected, and the entry flows to Finance for review, posting, and reconciliation.
It solves a specific problem. Not every office in a government generates enough transactions to justify a full cashiering station and a trained cashier. Yet those offices still take in money, and that money still has to be counted, deposited, and posted to the general ledger. Revenue Submission gives them a lightweight digital path into the same workflow the main cashiers use.
The module is built for outlying and low-volume departments, the kind of offices that collect revenue occasionally rather than all day. Common examples include:
The users are typically department staff, not dedicated cashiers. Finance and treasury teams sit on the receiving end, reviewing submissions and posting them. That split is important: the department does the collecting and the initial entry, and Finance keeps control of the deposit and the ledger.
Without a tool like this, a small office usually collects cash and checks, fills out a manual deposit form, and physically carries the deposit to Finance, often days after the money was taken in. That creates delays, transcription errors, and gaps in the audit trail. Reconciliation becomes a hunt for paper slips.
Revenue Submission replaces the paper handoff with a digital one. The department records what it collected, categorizes the revenue against the correct accounts, and submits it. Finance receives a structured entry it can verify and post, rather than a handwritten slip to re-key.
The point is not to turn every department into a cashier. It is to get outlying revenue into Finance's system quickly, accurately, and with a trail, without adding hardware or headcount at every window.
The workflow generally follows a predictable path:
The core Teller cashiering interface is a point-of-sale built for staff who take payments constantly. It supports cash drawers, check scanners, receipt printers, integrated card processing, and end-of-day balancing. That level of tooling makes sense for a busy front counter, but it is more than a low-volume office needs.
Revenue Submission is deliberately lighter. It is oriented around submitting what was collected rather than processing live transactions at speed. Departments do not need a full cashiering station, and IT does not need to provision devices for every occasional collection point. In practice that keeps the module simple enough for non-cashier staff to use without extensive training.
For a controller or treasurer, the value is centralization and control. When outlying revenue arrives as a structured digital submission instead of a paper slip, Finance gets three things that are hard to achieve with manual deposits: a consistent audit trail, faster posting, and fewer re-keying errors.
It also brings revenue that used to live outside the system into one place. Payments collected at a remote parks office and payments collected at the main counter end up in the same receipting, reporting, and reconciliation flows. That single view is often the reason finance teams pursue the module: it closes the blind spots created by departments that were never on the cashiering platform to begin with.
Revenue Submission fits Teller's broader design philosophy. The platform is browser-based, cloud-hosted, and IT-light, so extending revenue capture to more offices rarely means new hardware or heavy setup at each location. It is one more way a government can pull scattered collection points into a single, auditable cashiering and revenue management layer.
