State licensing and regulatory agencies
Licence, permit and tag fees calculated by the agency's rules and taken at the district office counter.
Public sector payment solutions that complete your Salesforce platform
Manage counter payments and cash registers inside Salesforce, with transactions linked to the people, applications and permits your agency already manages.
Many state and local agencies run applications, cases, inspections and licensing records in Salesforce, while payments and the cash register stay in a separate cashiering tool. Eposly brings them into Salesforce: cash drawers, mixed tender, receipts and end-of-day reconciliation, with fees set by rules configured for the agency's fee schedule and each payment linked to the applicant's records.
- Cash register management in Salesforce: drawers, tender, receipts and end-of-day reconciliation.
- Fees set by pricing rules configured for the agency's fee schedule, with adjustments recorded on the transaction.
- Payments linked to the applicant's records, under your Salesforce permissions and audit controls.
- Selected by California DMV for permit and registration payments on Salesforce Government Cloud.
Which public sector agencies does Eposly work with?
Eposly fits agencies that run, or are moving onto, Salesforce for applications, cases or permits, and still take fees in person. Choose your agency type.
Cities and municipalities
Permit, licence, tax and parking payments at the city's counters, linked to the applicant's records.
Motor vehicle agencies: see how California DMV runs permit and registration payments in Salesforce
What does a public sector counter need from a payment solution?
A public sector counter needs a payment solution that runs inside the platform the agency already chose, so fees, payments and cash drawers are managed in Salesforce, linked to the cases they belong to.
Many agencies run applications and cases in Salesforce and take payment in a separate cashiering or payment tool. Salesforce then learns that something was paid, but not how the fee was reached or how the drawer balanced. Reconciliation and audit preparation span more than one system.
A public sector counter needs to
How Eposly handles it
Capability
Manage the cash register
Cash drawers with logged opens and per-user attribution, mixed tender, receipts printed from Salesforce and end-of-day reconciliation across drawers and offices
Calculate fees by policy
Pricing rules configured for the agency's fee schedule, applied as the order is built
Record discretion
Waivers and adjustments recorded on the transaction; agencies manage the required approvals with their Salesforce processes
Take payment at the desk
Cash, card, cheque or a split in one step, with partial payments where the agency allows them
Link the payment to the case
The order and payment are created in Salesforce, linked to the applicant and the case
Report across offices
Every transaction and drawer is in Salesforce, ready for reports and dashboards by office and cashier
A permit at the counter
How does one counter payment work from start to finish?
One flow in Salesforce, from the fee to the closed drawer.
How are fees calculated and adjusted with approval?
Policy-driven fees, documented discretion. Pricing rules configured for the agency's fee schedule handle fee tables and tiers, so the clerk does not calculate fees by hand. Where discretion is allowed, such as a waiver, an adjustment or a partial payment, it is recorded on the transaction. Agencies can use their Salesforce processes to manage the required approvals.
Situation
How it is paid
Fee at the counter
Cash, card, cheque or a split, in one step
Partial payment
Part of the fee now, the balance later, on the same order
How many systems does a public sector counter actually need?
Fewer than many agencies run. When the counter transaction runs inside Salesforce, the separate cashiering database and the reconciliation between it and Salesforce drop out.
Layer
Typical agency stack
With Eposly in Salesforce
Applications, cases and applicant records
Salesforce
Salesforce
Counter payments and cash register
A separate cashiering system
Eposly, inside Salesforce
Card payments
Payment gateway, linked to the cashiering system
Supported PCI-compliant gateway, linked to Eposly in Salesforce
Reconciling the two
Manual or batch, across systems
No separate cashiering database to reconcile
Finance and ERP
Finance system
Unchanged, fed with structured data from Salesforce
Eposly does not replace the finance or ERP system. Salesforce stays the system of record for the transaction, and finance receives structured data from it.
What does the record and audit trail show?
After every counter transaction, Salesforce shows:
- Who paid, for which application, licence or permit.
- Which clerk took the payment, at which office and from which drawer.
- How the fee was reached, and any waiver or adjustment recorded on the transaction.
- How it was paid: cash, card, cheque or a split, and any partial or scheduled payment.
- The receipt, and refunds against the original transaction.
- The drawer's opens and its end-of-day reconciliation.
These are standard Salesforce records, so they follow your Salesforce permissions and audit controls. Card details are tokenised by the connected PCI-compliant payment gateway and kept out of the applicant's record.
Which public sector agencies already run on Eposly?
California DMV selected Eposly's Salesforce-native Point of Sale and Cash Register module for permit and registration payments on Salesforce Government Cloud.
Public sector one-pager
Take this page to your team
The key points of this page in one document to share with your team, including the agency types we cover.
By downloading, you agree to our privacy policy.
Is Eposly the right fit for your agency?
Eposly fits agencies that:
- run, or are moving onto, Salesforce for applications, cases, licensing or permits;
- take fees in person, with cash in the drawer;
- take payment in a separate cashiering or payment tool today;
- need fees, discretion and the cash drawer managed in Salesforce, alongside the case.
Another option is a better fit when:
- Salesforce is not in play for cases or permits;
- payments are online only, with no counter;
- the agency needs a full licensing, permitting or finance system rather than the payment and the cash register.
One note for planning: every clerk who takes payment in Eposly needs a Salesforce user licence.
FAQ
Each drawer is managed in Salesforce, with logged opens, per-user attribution, mixed tender and receipts printed from Salesforce. At the end of the day, drawers are reconciled in Salesforce, and reports show the position across cashiers and offices.
Salesforce on its own does not manage a physical cash drawer. With Eposly, drawer opens, tender, receipts and end-of-day reconciliation are recorded in Salesforce, on the same platform as the agency's cases.
Yes. California DMV selected Eposly for permit and registration payments on Salesforce Government Cloud.
Payment apps take card payments, often online. Retail POS systems can handle cash drawers, but they keep them in their own system. Eposly runs the counter transaction, including the cash register, inside Salesforce, so cash events take part in the agency's Salesforce processes and permissions.
Complete your Salesforce platform at the counter
See how a counter transaction runs inside Salesforce.