Teller Government Cashiering posts receipts to the general ledger by separating two events that finance teams often blur together: the A/R update (which credits a specific invoice or account in the source system) and the GL deposit entry (which records the cash movement in the ledger). A single counter payment can drive both, in real time, even when A/R and the GL live in different systems.

‍

What is the difference between A/R posting and GL deposit entry?

‍

These are two distinct postings that happen from one transaction, and understanding the split is the key to understanding how any government cashiering layer feeds the ledger.

‍

• A/R posting settles a specific obligation. When a cashier collects on a utility bill, a permit fee, or a tax installment, the receipt is applied against that invoice or account in the billing or ERP system so the balance reflects payment.
• GL deposit entry records the accounting effect. The same money has to land in the general ledger as a debit to cash and a credit to the appropriate revenue or liability account, coded to the correct fund, department, and account string.

‍

In many agencies these two systems are not the same product. A county might run utility billing in one platform, permitting in another, and its general ledger in a third. Teller sits at the counter between them and routes each half of the transaction to where it belongs.

‍

One payment, two postings: the account gets credited in the source system, and the ledger gets a coded deposit entry. Teller keeps both in sync from the same receipt.

‍

‍

How does GL coding get applied at the counter?

‍

Cashiers do not need to know account strings. That is a deliberate design choice, because expecting front-counter staff to pick the right fund and revenue code by hand is a reliable source of errors and reclass work later.

‍

In Teller, GL coding is driven by the revenue type or the item being paid, not by the person keying it in. Each payment line is mapped to a set of accounting attributes behind the scenes:

‍

• Payments pulled from an integrated system inherit their GL coding from that system's data. When a receipt applies to an ERP invoice, the fund and account information travels with it.
• Miscellaneous receipts and over-the-counter items are configured against pre-defined revenue types, so selecting the reason for payment determines the coding automatically.
• Distributions across multiple accounts, common when one fee splits between funds or departments, are set up in configuration rather than reconstructed at the register.

‍

The result is that the cashier collects money and the correct accounting follows from what they collected, not from a code they had to remember.

‍

‍

Does Teller post to the ledger in real time?

‍

Teller is in production with a large integration footprint, and where the target system supports it, posting happens in real time rather than as an overnight batch. Teller supports over 96 third-party integrations in production, including the major government ERPs such as Workday, Oracle, PeopleSoft, SAP, and JD Edwards, alongside tax, utility billing, and permitting platforms.

‍

Real-time posting matters for two reasons finance teams feel directly:

‍

• Accounts reflect payment immediately. A resident who pays at the counter should not still show a balance due when they walk out or when a second clerk checks the account moments later.
• The ledger stays current. Deposit entries flow as receipts are taken, so end-of-day is a confirmation step rather than a reconstruction.

‍

Where a downstream system only accepts periodic files, Teller batches and formats the deposit entries to match that system's import requirements. The mechanism adapts to what the ledger can accept.

‍

‍

How do deposit entries reach a separate general ledger?

‍

This is the workflow that treasury teams care about most, because the GL is frequently a different system from the one that generated the invoice.

‍

Teller aggregates the day's receipts into deposits and produces the corresponding GL entries. Those entries carry the full coding, cash to one side and coded revenue or liability accounts to the other, so the ledger records not just that money arrived but where it belongs. Depending on the environment, entries are delivered through:

‍

• A direct integration that writes journal or deposit entries into the general ledger system.
• A formatted file or interface that the GL imports on its own schedule.
• A summarized batch tied to a specific deposit, so the ledger entry reconciles cleanly against the bank deposit.

‍

Because A/R settlement and GL deposit entry are handled as separate routes, an agency can credit an account in one system while feeding the deposit to an entirely different ledger, without double entry and without staff rekeying anything.

‍

‍

What does GL posting look like at end of day?

‍

End-of-day is where the two postings come together into something an auditor can trace. A typical close in Teller runs like this:

‍

1. Cashiers balance their individual drawers, reconciling counted cash, checks, and card totals against what Teller recorded.
2. Balanced drawers roll up into a deposit for the day or the batch.
3. Teller generates the deposit's GL entries, coded and totaled, ready for the general ledger.
4. Finance reviews and confirms, then the entries post to or export toward the ledger.

‍

Every receipt carries a full audit trail from the point of collection through the A/R update and into the GL deposit entry, so the amount posted to the ledger can be traced back to the individual transaction that produced it. That traceability is what lets a controller answer the question every auditor eventually asks: which receipts make up this deposit, and how were they coded?

‍

‍

Why does the A/R and GL split matter for government finance?

‍

Governments handle many revenue streams across many departments, and the accounting rules differ from commercial retail. Whereas a retail point-of-sale records a sale, a government counter has to satisfy fund accounting, restricted revenue, and the segregation of A/R settlement from cash accounting.

‍

Teller is built for that distinction rather than adapted to it. Keeping A/R posting and GL deposit entry as separate, configurable routes is what allows one counter to serve tax, utilities, permits, court, and miscellaneous receipts while still delivering clean, correctly coded entries to whatever general ledger the agency runs. For finance and treasury teams, that is the difference between a cashiering system that collects money and one that also keeps the books right.