Answers for your agency’s payment evaluation

Work through the questions your operations, finance, IT, and purchasing teams need to resolve. Explore daily workflows, financial controls, system handoffs, and launch responsibilities.

Evaluating fit and switching providers

Decide what your team needs to see before committing.

What stays in our existing systems, and what moves into GovPayPlan?

GovPayPlan handles collection, payment arrangements, payment records, and settlement reporting. Your case management, billing, or finance system can remain in place. Staff can exchange balances and payment records by CSV on every plan; automated exchange requires a confirmed Enterprise integration. During evaluation, identify which system owns each balance and which records must return to it.

Review integration options

What should our agency test before committing?

Test a typical payment, an installment arrangement, an offline collection, and the reports finance needs for reconciliation. Include an exception your staff handle today, such as an incorrect reference. Test-account payments are simulated: no money moves and no card or bank information is required. Our team reviews requests and emails access details.

Request an agency test account

What should operations, finance, and IT evaluate together?

Operations should validate collection and exceptions; finance should trace payments to settlement statements and posting exports; IT should confirm record references, exchange methods, and access. Purchasing and legal should review the agreement and mandatory requirements. Use the same sample workflow so each team reviews the handoffs, not just its own screen.

Open the evaluation checklist

What can we validate in a test account, and what needs a separate review?

Test portal configuration, access, simulated payments, arrangements, and reporting without moving money. This does not prove live settlement, site connectivity, or support for a specific third-party integration. Confirm how required hardware, automated exchange, or a specialized allocation scenario will be demonstrated.

How is test access arranged, and what assistance is available?

Our team reviews requests and emails access details; form submission does not automatically provision access. Written guides are available, and you can request a walkthrough. Confirm the access period and any additional training or integration assistance, especially when your evaluation must fit a procurement deadline.

Who should attend a walkthrough from our agency?

Include someone who handles daily collections and someone who reconciles deposits. Add IT for system exchange or identity, and purchasing or legal for agreement requirements. A sponsor can focus on outcomes while staff validate handoffs. You do not need a completed requirements document to begin.

What should we provide to make a walkthrough relevant?

Share payment types, current systems, collection locations, one difficult workflow, and the report finance needs at the end. Use fictional or sanitized examples; do not send credentials or sensitive records through the form. Our team follows up by email to arrange the walkthrough.

Staff workflows and payment arrangements

What changes for staff who collect at a counter or record mailed checks?

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.

How do staff follow a payment from the obligation through collection and settlement?

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.

How do clerks distinguish a partial payment from a completed obligation?

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.

How should staff use payment records when reviewing a supervision case?

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.

How do office and field collections appear in a client’s history?

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.

What payment history can staff prepare for a review hearing?

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.

Can our agency restrict payment methods or partial payments for particular obligations?

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.

How should utility staff verify payment before a service-disconnection action?

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.

What should staff review when an AutoPay payment fails or a balance changes?

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.

How do we decide whether payment occurs before or after staff approval?

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.

Can a renewal notice lead to payment without creating a duplicate obligation?

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.

What does check printing include, and which steps remain our responsibility?

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.

What should our agency evaluate before using gift cards for a program?

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.

What changes for staff at a counter that collects for several offices?

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.

Agency costs and commercial terms

Can volume from our current provider qualify us for a tier or waiver immediately?

New agencies can qualify from day one using documented prior-year gross payment volume from current-provider statements or agency financial reports. Provide records during evaluation so tier placement, subscription-waiver qualification, and volume-based terminal eligibility can be reviewed before the Service Plan is finalized.

How do minimum fees affect small payments and installments?

Each electronic charge uses the percentage fee or the minimum, whichever is greater—not both. Minimums are $2.00 for card and wallet and $1.00 for ACH. Each installment is a separate charge, so smaller, more frequent payments can incur more minimum fees than one larger payment. Review total payer cost when selecting schedules.

How do separate agency accounts affect subscriptions and volume qualification?

Each subscription covers one agency account with unlimited staff users. An office needing its own portal, reconciliation, and payout account has its own subscription, subject to the $250,000 waiver threshold. Do not assume departments’ volume can be pooled for qualification; confirm the proposed structure and qualification treatment during commercial review.

What happens to our rates when payment volume changes?

Tier placement is reviewed at each renewal using trailing 12-month gross payment volume. Agencies that qualify move to the better rate at renewal. Rates do not change mid-term. Provide volume records when reviewing the next term and have purchasing confirm renewal terms in the agreement. A volume change during the current term does not trigger an immediate rate change.

How can finance reconcile the principal separately from convenience fees?

The convenience fee is disclosed separately before confirmation and added to the obligation. Under that model the agency receives the full principal. Review transaction detail and settlement statements to distinguish the obligation from fees, refunds, or disputes; receiving principal does not mean a transaction is immune from later reversal.

Deposits, reconciliation, and audit

How can finance verify that collections match the money deposited?

Use the settlement statement and its underlying transactions, refunds, and adjustments. Compare the total to the ACH deposit and export records for posting. Review reports by department, method, and date. Reconcile agency-deposited cash and checks separately rather than expecting every collected payment in the electronic payout.

When do departments need separate agency accounts rather than a shared account?

Each agency account settles to one registered bank account; a deposit is not split across bank accounts. Offices needing separate portals, payouts, and reconciliation can have separate accounts under one organization. If funds share a deposit, allocation reporting is different from separate settlement. Review that distinction with finance before configuration.

How should restitution, bonds, and fees be separated when their banking requirements differ?

Identify obligations needing different bank accounts versus separate accounting within one deposit. Separate bank settlement requires separate agency accounts. Restitution, bonds, and custodial funds also need a specific handling review and are excluded from the default distribution policy. Collection support is not authorization to combine or distribute those funds.

How can finance reconcile departments with different bank accounts?

Review each agency account’s settlement statements against its own bank deposits, then export records for the general ledger. Accounts sit under the organization but retain their own payout account, portal, and reporting. Establish account-to-bank and department-to-ledger mappings before launch rather than assuming one consolidated deposit meets every requirement.

How do payment timestamps and settlement dates differ for deadline-day collections?

The payment record and later settlement describe different events. Review transaction status and the parcel or account reference separately from the payout date. Your office determines which timestamp and status meet its deadline rules. Confirm reporting fields and integration handoffs rather than using a bank-deposit date as proof of timely payment.

What records can finance provide to explain a deposit or support an audit?

Finance can provide settlement statements, transaction exports, filtered reports, and payment and receipt references. Distributions adds sealed batches, control totals, allocation traces, and journal and recipient exports. Confirm required fields and periods with your auditor; an export does not replace the agency’s record-retention obligations.

Distributions and financial controls

How does a distribution batch differ from the bank deposit our agency receives?

Merchant settlement deposits available funds into the registered agency account on its plan schedule. A distribution batch calculates allocations among funds or recipients and retains supporting records. It is not a bank deposit or proof that recipients have been paid. Finance reconciles settlement and allocation as related but distinct steps.

What steps remain outside GovPayPlan when paying distribution recipients?

Distributions calculates allocations and produces recipient reports and journal-entry exports. It does not currently transfer funds between bank accounts. Your agency handles recipient remittances through its banking process and verifies those payments. A recipient report or completed allocation batch is not confirmation of a bank transfer.

How can finance validate an allocation policy before activating it?

Preview matching transactions, simulate ordered rules on sample amounts, and inspect recipient totals and exclusions in a dry run. Compare fixed amounts, percentages, remainders, and rule order with your approved policy before activation sign-off. Sealed batches retain the policy used and transaction-level allocation traces.

What keeps held or ineligible transactions out of a distribution run?

Finance configures transaction scope, eligibility conditions, and payment-method holds. Preview and dry-run results let staff inspect qualifying records before batch creation. Review exclusions and exceptions rather than assuming every collection belongs in the next run. Your agency must confirm that the configured policy expresses its financial requirements.

How are policy changes, exceptions, and reruns documented for audit review?

Policy versions and activation records identify the rules used. Run history shows results and batch references, while exceptions support resolution notes. A sealed batch retains control totals and transaction-level allocation traces, with recipient and journal exports. Review the original issue and resulting treatment before rerunning.

What evidence explains how collections were allocated among funds or recipients?

The allocation trace identifies the policy, rule, calculation basis, amount, and running remainder for a transaction. Sealed batches retain control totals and recipient allocations with summary, detail, and journal exports. Use them to explain the calculation, then separately verify remittances through the agency’s banking process.

Corrections, refunds, and disputes

What happens when an application is rejected or its fee changes after payment?

Application decisions and fee changes follow agency policy. Review payment status and the applicable refund process separately; rejection does not imply an automatic refund. Authorized users can process refunds, and processing fees are non-refundable once the original charge has settled. Confirm the approval and refund sequence before launch.

What happens when a payment is recorded against the wrong obligation?

Eligible paid, non-terminal transactions can move to another outstanding payment for the same client within the same agency. A reason is required; the move cannot overpay the target and is blocked for distribution-allocated transactions. Terminal and cross-client moves are not supported by that workflow. Review eligibility before deciding on the appropriate correction.

How are recording mistakes, refunds, and disputed payments handled differently?

A correction changes how an eligible transaction is applied; it does not refund the payer. An authorized agency user initiates a refund. The issuer or bank investigates and decides a chargeback, not the agency. Review the current status and intended outcome so a record correction is not confused with moving money.

Which fees remain after a refund, returned payment, or chargeback?

Processing fees are non-refundable after the original payment settles with the network. Chargebacks can return funds to the payer, with the issuer or bank deciding the outcome. Review the Service Plan and applicable network terms for returned-payment or dispute charges; do not assume those events have identical costs or that every fee is returned with principal.

How are refunds and disputes reflected when finance reconciles collections?

Review transaction status, refund detail, chargeback activity, and settlement statements to explain the deposit. Refunds and disputes can change available funds after the original payment was recorded. Follow the affected transaction through the relevant reporting period instead of assuming its original receipt still represents retained funds.

When should staff treat a submitted card or ACH payment as completed?

Review current transaction status and the outstanding balance, not only whether payment was submitted or a receipt exists. Collection, settlement, and later reversals are different events, and bank payments can be returned. Establish which statuses support each agency action and confirm the source-system handoff before launch.

What should staff do if a bank payment is returned after appearing successful?

Review transaction status, the obligation balance, and financial reports before collecting again. Confirm whether the return reached your billing or case system, especially with staff-managed posting. Establish the return-handling process, payer follow-up, and applicable charges during evaluation; do not assume an automatic retry or a particular agency action.

What remains our agency’s responsibility when a payment is suspected of fraud?

Networks screen payments and can flag or block suspected fraud, but screening does not guarantee against losses. Authorized users can review records and initiate refunds where appropriate. Follow your internal escalation process and review disputes in reporting. The card issuer or bank determines chargeback outcomes.

Counter and field equipment

What should IT confirm before we choose counter or mobile terminals?

Describe staffed windows, field sites, connectivity, and the portals or accounts each device will serve. Terminals ship configured, but confirm connection and site requirements for the supplied device before ordering. Do not assume offline acceptance, cellular coverage, or compatibility with existing hardware without that review.

How do staff ensure a terminal payment is applied to the correct obligation?

Initiate the charge against the correct payment record, agency, reference, and outstanding amount. The result and receipt support that record. Practice shared-counter scenarios during setup: a successful charge does not establish that staff selected the right obligation, and terminal transactions cannot use the transaction-move correction workflow.

What should staff do if connectivity is lost or a payment outcome is unclear?

Check the payment record and transaction status before charging again, and escalate unresolved outcomes to agency support. Do not assume a disconnected terminal accepted payment offline or that a missing receipt means no charge occurred. Confirm device-specific recovery procedures during onboarding to help avoid duplicate collection.

What happens when a terminal is damaged or stops working?

For countertop terminals: Purchased units carry the manufacturer’s one-year hardware warranty. Rented units include advance replacement. For mobile terminals: Subscriptions include advance replacement. With advance replacement, a configured unit ships before the defective device is returned. Contact support to confirm the applicable terms for loss, damage, or other circumstances.

Systems integration and data exchange

Which system should own balances, adjustments, and payment status?

Agree on a source of record for each data element. Your billing or case system may originate obligations while GovPayPlan records collections and arrangements. Document how adjustments, returns, and refunds flow between systems, including identifiers and timing. Do not assume every field is synchronized in both directions.

What happens when an import or automated exchange fails?

CSV provides validation and preview before import. For automation, agree on failure detection, investigation, reconciliation, and safe reprocessing for the actual interface. Confirm these responsibilities during integration review rather than assuming every connection has automatic retries, duplicate prevention, or identical alerting.

What information should our agency prepare for an integration review?

Identify the source system and version, record identifiers, data to import, events to return, and report fields finance needs. Include the exchange schedule and technical contact. Use sanitized samples; do not send passwords, tokens, payment credentials, or unapproved personal data in the initial request.

How does GovPayPlan work with the eCourtDate Case Management System?

GovPayPlan is the supported payment processor for the eCourtDate Case Management System, with payments, refunds, and adjustments tied to the case ledger. Agencies with a different case system can evaluate GovPayPlan independently. Confirm the posting workflow for your configuration rather than assuming the same connection applies to every system.

How does GovPayPlan work with eCourtDate notifications?

Payment reminders, receipts, plan notifications, and past-due notices use the eCourtDate communications platform for text and email with payment links. Review notification schedules and their relationship to payment records during evaluation. GovPayPlan is a standalone payment solution; a separate case management product is not a prerequisite.

Implementation and launch readiness

What training and support should our team expect before and after launch?

Onboarding includes live training, videos, and written guides. Have collection staff practice payment and receipt tasks and finance staff practice reconciliation and exports. After launch, staff can use the Help Center and submit support requests from the app. Agency support hours are Monday through Friday, 8:00 a.m. to 8:00 p.m. Eastern, excluding federal holidays. Agree on your team’s readiness checks before launch.

What should we establish before expanding across several offices?

Map each office’s payment types, bank account, portal, reporting, permissions, and system handoffs. Name configuration and reconciliation owners, then test a representative workflow for each office. Confirm account-level subscription and equipment requirements and review the rollout sequence rather than assuming one setup can be copied unchanged.

Which agency staff should participate, and what decisions does each own?

Name an implementation lead and operations, finance, IT, and purchasing contacts. Operations validates collections and training; finance approves account structure and reconciliation; IT confirms access and exchange; purchasing coordinates agreement review. Registration and bank verification also need authorized contacts. Establish owners before scheduling launch.

What sample data can we safely provide during evaluation?

Use fictional or sanitized records with the formats and edge cases your staff need. Simulated payments require no card or bank information. Do not upload live credentials, sensitive case details, or personal information without agency authorization and an agreed handling process. A representative sample does not need to identify real people.

Which scenarios should pass before we authorize live payments?

Validate payment references, balances, receipts, permissions, installments, and required imports or integrations. Include an exception and have finance inspect export fields and the expected settlement workflow. Assign owners to unresolved issues. Complete registration, verified payout details, training, and agency approval before publishing live links.

How should we coordinate the changeover without duplicate collections?

Inventory links, notices, QR codes, recurring arrangements, and posting jobs. Agree when each changes, which system owns final balances, and who checks new records. Confirm whether existing enrollments or saved methods can move; do not assume automatic transfer. Test the cutover with operations and finance before setting the public launch date.

What must finance verify during the first settlement cycle?

Confirm bank details, the plan schedule, and available-funds threshold. Match the deposit to its statement, inspect transactions and adjustments, and verify posting exports against the source system. Reconcile cash and checks through the separate agency deposit process. Review Distributions control totals separately from settlement.

What is required to move from testing to live collection?

Live collection requires registration, agency and bank verification, agreed configuration, and trained staff. Confirm which settings or records should carry forward; do not assume demonstration data or test arrangements belong in production. Finance should review payout readiness and IT should confirm production exchange before live links are published.

Security, accessibility, and agency responsibilities

How can collection, finance, and administration responsibilities be separated?

Assign individual accounts and roles matching duties, with feature-specific permissions for Distributions and check printing. Sensitive configuration can require a second administrator’s approval. Subscriptions include unlimited staff users, but access still needs deliberate review. Test permitted and restricted actions before launch.

Which PCI responsibilities remain with our agency?

Card processing uses PCI DSS Level 1 certified infrastructure, tokenization, and encrypted terminals to keep full card numbers out of agency systems. This reduces exposure but does not remove every agency obligation. Review your actual channels, devices, procedures, and applicable documentation with security staff; do not infer a blanket agency compliance certification.

What payment information is visible to staff or stored on agency systems?

Agency records display masked payment information. Saved payment-method views are read-only, not a way to enter or edit full credentials. Processing uses tokenization and encryption. Confirm the data flow for your portals, devices, and integrations in security review; staff should not copy full credentials into notes or support requests.

How are sensitive changes such as payout bank-account changes verified?

Adding or changing a payout account requires dual verification by two authorized contacts. Sensitive configuration can also require secondary approval, and controlled recipient details used by an active distribution policy require another user’s approval. These are separate controls for separate workflows. Confirm authorized contacts and permissions before launch and when responsibilities change.

What should IT confirm before using agency single sign-on?

Single sign-on is an Enterprise option configured during onboarding while GovPayPlan permissions remain in effect. Identify your identity provider, user groups, and access rules and confirm support. Plan access testing and administration rather than assuming every identity-provider feature is supported unchanged.

How should our accessibility team evaluate the public payment experience?

The portal is built to WCAG 2.1 Level AA and supports more than 100 languages. Request conformance information and test the configured flow, instructions, and agency content. Language support and a design standard do not replace evaluation or establish that every uploaded agency document is accessible.

Procurement and vendor review

What renewal, termination, and data-export provisions should counsel review?

The Service Plan has a one-year term with fixed processing rates during that term. Review the agreement’s renewal, notice, termination, and continuing obligations. CSV exports are available, but confirm required data, timing, access, and retention for an exit; an export feature alone is not a complete offboarding commitment.

How are agency-specific contractual requirements reviewed before signature?

Provide required clauses, purchasing procedures, and legal or security questionnaires during evaluation. Counsel can review the current agreement before commitment. Requested changes need explicit review and agreement; do not assume a procurement method, clause, or exception is accepted simply because the platform supports government payments.

How can our agency submit an RFP or RFQ for review?

Send the solicitation to [email protected] with deadlines, instructions, and required attachments. Responses use current pricing and Service Plan terms so the committee can compare the proposal with the agreement. Flag mandatory requirements and demonstrations rather than treating an unanswered requirement as an implied commitment.

Which requirements should be demonstrated rather than accepted as a written claim?

Demonstrate references, installments, permissions, corrections, report fields, and allocation controls with simulated records and an exception case. Verify live-settlement terms, hardware requirements, and specific integrations through their documentation and review. A test-account screen alone cannot prove those dependencies.

How do we distinguish an available capability from a proposed customization?

Record whether each requirement is supported now, depends on configuration, needs a confirmed integration, or requires development. Obtain evidence and a written scope for additional work, with responsibilities and acceptance criteria. Do not mark a future request as current support merely because it has been discussed.

What evidence should finance require for reconciliation and allocation controls?

Trace representative payments through transaction detail, a settlement statement, and a posting export. For allocations, review a policy, dry-run totals, exclusions, approvals, and a sealed batch with recipient and journal detail. Confirm these meet your accounting requirements and distinguish calculation evidence from proof of a transfer.

Which unresolved items should prevent approval or launch?

Do not launch with unverified payout details, an untested required integration, unresolved references, incomplete access controls, or an unreconciled reporting workflow. Resolve mandatory contract, security, and accessibility requirements before approval. Assign owners and acceptance criteria to gaps rather than treating a successful demo as complete readiness.

Questions not covered here

Call (877) 831-1755 or email [email protected]. Finance, security, and procurement questions are answered in writing.