Prepare a shared evaluation for your agency
Use this checklist to bring purchasing, finance, security, and IT requirements into the same review. Confirm costs, collection workflows, data exchange, and the documents your agency needs before selecting GovPayPlan.
Agency evaluation checklist
Check the items your team has reviewed, print a working copy, or download the text version for your procurement file. This is an evaluation aid, not a substitute for the one-year Service Plan agreement. Checked items are not saved when you leave or reload this page.
Agency requirements
Describe the payment operation your agency is evaluating.
Pricing and contract review
Review the published commercial terms against your agency’s volume and account structure.
Security and accessibility review
Request the materials your agency uses for vendor review.
Systems and reconciliation review
Connect the payment workflow to the records finance and operations already use.
Evaluation and vendor file
Use the test account and document request to complete your agency’s evaluation.
Prepare a document request
Send your agency name and required documents to [email protected]. Include the following information to explain the review your team needs to complete.
- Agency name
- Agency type and state
- Payment types and collection channels
- Annual gross payment volume, if available
- Documents requested
- Questions for finance, security, or procurement review
The button opens a draft in your email application. Review it before sending. Do not include payment credentials or personal payment records.
Procurement review questions
Compare agency and payer costs using the same volume, payment mix, transaction sizes, and number of accounts. Include minimum fees, software waivers, equipment, integration requirements, and refund treatment. Also compare payout frequency and staff reconciliation work. A headline percentage alone does not show the full financial or operating impact.
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.
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.
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.
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.
Evaluate the agency workflow
Invite the staff who collect payments and reconcile deposits to review GovPayPlan. Use simulated payments while your purchasing team reviews the documents.