Staff charge a configured terminal against the payment record or record cash, checks, and money orders as offline collections. Both have receipt detail available for review. Recording an offline payment does not deposit or electronically clear it: your agency continues to deposit those funds through its existing banking process. Confirm staff permissions and balancing procedures during setup.
Start with the case, account, or application reference. Staff can review transaction status, receipt, and remaining balance; finance can inspect the settlement statement and transactions behind the deposit. Cash and checks appear in collection reports but are deposited separately by the agency, so they should not be counted as part of an electronic payout.
The payment record retains the obligation’s balance and history. An installment or partial payment reduces the outstanding balance; it does not mean the full obligation has been satisfied. Review the remaining balance and schedule as well as the receipt. Administrators configure whether partial payments are allowed for each payment type.
Administrators enable partial payments for the relevant payment type, and staff review the balance and history with the client’s arrangement. Each successful electronic charge has its own processing fee and minimum, so review the effect on small installments before setting a schedule. Cash and money orders recorded by staff carry no processing fee.
Review current pricing and terms
The client record shows balances, arrangements, and payment history, and reports can identify past-due payments. Use those records to document what was paid and what remains outstanding. A payment status is not a determination about compliance, ability to pay, or a supervision action; those decisions remain with authorized staff under agency policy.
Mobile and counter terminal payments are tied to the payment record with receipt and balance details. Staff can also record office cash and money orders for review alongside electronic payments. Use the client’s payment history to prepare for a meeting rather than relying only on a terminal receipt or the last payment date.
Staff can print the client’s payment history with dates, methods, and receipt references and review the outstanding balance and arrangement. Confirm the fields and date range your court needs during evaluation. Staff remain responsible for checking completeness and any required hearing format.
Administrators configure accepted methods at the portal and partial-payment settings for payment types. Review that combination for each workflow, especially obligations with agency-specific restrictions. Confirm the supported configuration before publishing rather than assuming every method or amount restriction can be applied at every level.
Cashier users record these collections with reference and receipt details, with no processing fee. They appear alongside electronic payments in collection and reconciliation views, but the agency deposits them through its own banking process. Finance reconciles those deposits separately from the ACH payouts and settlement statements for electronic collections.
Check the account reference, current transaction status, and remaining balance, then verify whether payment has posted back to the billing system. CSV requires staff to perform that handoff; automated exchange depends on the confirmed integration. A submitted payment alone does not establish that every billing or service-status update occurred. Service decisions remain governed by utility policy.
Review transaction status, outstanding balance, enrollment amount, and the next collection date. Enrollment does not confirm that a charge succeeded or a changed billing balance reached GovPayPlan. During evaluation, confirm balance-update handling, failed-collection notifications, and any retry behavior for your workflow; do not assume automatic retries.
Identify whether your agency collects on submission or requires approval before finalizing payment. The forms workflow supports a staff-approval requirement, but test the intended sequence with your application scenario. Confirm when payment is authorized or finalized and what applicants see before publishing; payment status does not itself authorize a permit or license.
Configure the application, license, or recording reference on the payment workflow. Staff can review that reference with the payment and receipt in the payer’s history. Test the fields your records system needs so a paid receipt can be matched to the right application rather than treated as proof of approval.
Staff can add a pay link or QR code with configured fields, amounts, and limits. Test whether it points to an existing obligation or collects information for a new record, and confirm its license reference. A generic link should not be assumed to perform duplicate detection or update a separate licensing system automatically.
GovPayPlan provides forms and payment tools, references, receipts, and financial reporting. It should not be assumed to replace your permitting, inspection, issuance, or official records system. Identify which system owns application decisions and what payment information it needs, then confirm CSV or Enterprise exchange during evaluation.
Review integration options
Authorized staff draft checks, select a client or manual payee, issue and print checks, download PDFs, and record void reasons. Agency settings control numbering and bank details. The feature does not provide bank clearing or mailing; the agency remains responsible for banking, check stock, approval procedures, and delivery.
Staff can create gift card records, select a brand or recipient choice, and send redemption information by text or email, with delivery history and notes. Review your authority to provide cards, recipient eligibility, funding, approvals, and recordkeeping before use. The management feature does not establish that a particular program meets those requirements.
Staff can prepare QR-coded decals, posters, and table tents linked to a portal or payment service, in English, Spanish, or bilingual wording. Download print-ready files or request shipped materials. Check the destination, agency wording, and payment workflow before distribution; a printed QR code does not change collection rules.
Confirm the agency account, portal, and terminal configuration each obligation uses before collecting. Preserve the correct account and payment reference and record cash and checks under the appropriate workflow. Review shared-counter scenarios during setup, especially with different bank accounts; a common physical counter does not remove separate settlement requirements.