What is the form used for?

It documents the comparison of card system totals to ledger balances for a specified period, records variances, and captures corrective actions so accounts are accurate and auditable.

Who must sign the completed form?

Typically the preparer and a supervisory approver sign and date the form; organizations may require additional signatories for high-value adjustments or grant-funded revenue reconciliation.

What if totals do not match?

Document each discrepancy, attach supporting reports or transaction samples, and record the remediation steps. Escalate unresolved items according to the variance policy and retain evidence of follow-up.

Can this form be signed electronically?

Yes — electronic signatures are generally valid under the ESIGN Act and UETA in most states. Ensure signer intent, consent to electronic records, attribution, and reliable retention are in place.

Is notarization required?

Notarization is not routinely required for reconciliation forms. Use a notary or RON only when specific contract, grant, or legal authorities mandate authentication.

How long should records be kept?

Retain reconciliations per finance policy and applicable law: at least three years for tax purposes and longer where contracts, grants, or state rules require extended retention.

Electronic Signature
Templates
Miscellaneous
Metro Card Reconciliation Form

Metro Card Reconciliation Form

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

METRO CARD RECONCILIATION FORM

This Metro Card Reconciliation Form documents the reconciliation of fare media and associated funds between the Agency and the Card Provider/Operator for the report period specified below. The parties acknowledge that completion of this form is required to substantiate deposits, adjustments, and variances and to support payment and settlement obligations.

WHEREAS

WHEREAS, Agency Name: operates and administers transit services and is responsible for monthly reconciliation of fare media; and

WHEREAS, Card Provider Name: issues Metro Cards and/or processes transactions and collects funds on behalf of the Agency; and

WHEREAS, the parties desire to reconcile card inventory, transaction totals, deposits, adjustments, and any variances for the specified report period and to document agreed settlement amounts and responsibilities.

RECONCILIATION SUMMARY

Report Period: From to .

Metro Card Batch / Series Number of Cards Reconciled

FINANCIAL TALLY

Starting Card Balance: $ Total Sales / Fare Collected: $

Refunds Issued: $ Adjustments (Chargebacks, Corrections): $

Cash/Payment Collected and Deposited: $ Expected Ending Balance: $

Reported Ending Balance: $ Variance (Expected - Reported): $

Variance Explanation (if any)

SUPPORTING DOCUMENTS

Please indicate attached documentation supporting this reconciliation:

Receipts / Cash Count Sheets

Transaction Logs / Settlement Reports

Deposit Slips / Bank Statements

Other (describe):

SCOPE OF WORK

Reconciliation Procedure Description

PAYMENT TERMS

Settlement Amount Due to Vendor / Agency (as applicable): $.

Payment Schedule

Late Fee: . Late charges calculated on overdue balance until paid in full.

TERM AND TERMINATION

Term Commencement Date: . Term Expiration Date: .

Either party may terminate this reconciliation process upon written notice delivered to the other party at least prior to the intended termination date. Termination does not relieve either party of obligations accrued prior to termination, including settlement of variances and repayment obligations.

CONFIDENTIALITY

Each party shall keep confidential and shall not disclose to any third party any nonpublic information received from the other party in connection with this reconciliation, including transactional records, cardholder data and internal accounting records, except as required by law or regulation. Confidential information shall be used solely for purposes of reconciliation and settlement. Reasonable safeguards shall be maintained to prevent unauthorized access.

GOVERNING LAW

This reconciliation form and any dispute arising out of it shall be governed by and construed in accordance with the laws of the State of , without regard to principles of conflicts of law.

ENTIRE AGREEMENT

This Metro Card Reconciliation Form, together with any attachments or schedules referenced herein, constitutes the entire agreement between the parties regarding the subject matter and supersedes all prior oral or written statements and agreements relating to reconciliation for the specified report period.

CERTIFICATION

I certify under penalty of perjury that the information contained in this reconciliation form is true, accurate and complete to the best of my knowledge and that supporting documentation is held on file and will be provided upon request for audit or review.

I certify the information above and have attached supporting documentation as indicated.

CONTACTS

Prepared By (Name & Title) Department / Division Contact Phone / Email

Agency Representative:

By:

Date:

Card Provider / Operator:

By:

Date:

What the Metro Card Reconciliation Form Is and Why It Exists

The Metro Card Reconciliation Form is a standardized record used to compare card-based transit revenue and account activity against ledger balances for a defined reporting period. It aggregates beginning balances, reloads, fare deductions, refunds, and transaction adjustments so finance teams can identify variances, document corrections, and prepare audit-ready records for transit authorities, employers, or third-party processors.

Primary Purpose and Key Advantages

A clear reconciliation form reduces accounting errors, supports timely variance resolution, and provides an auditable trail for internal controls and external reviewers. It speeds month-end close, improves transparency for fund custodians, and documents corrective actions to limit future discrepancies.

Who Typically Completes This Form

Transit finance teams, fare collection vendors, and auditors most commonly prepare and review these reconciliations.

Transit finance staff reconcile card aggregates to general ledger and bank deposits.
Third-party fare processors provide transaction exports and reconciliation support.
Internal and external auditors verify completeness and control procedures.

Smaller employers or campus transit programs may use the same form scaled for lower transaction volumes.

Step-by-step: Completing a Metro Card Reconciliation Form

Follow a consistent sequence to ensure totals align, variances are explained, and supporting records are attached before submission.

01

Prepare data: Export transaction reports and bank statements for the date range.
02

Enter balances: Record beginning balance, sales, reloads, adjustments, and ending balance.
03

Compare totals: Match ledger entries to card system exports and identify differences.
04

Document reasons: Attach receipts, error reports, and corrective action notes.

Essential components of a professional reconciliation form

A thorough form combines numeric fields, supporting documentation, and signatory attestations to create an auditable record.

Header

Clear reporting period, entity name, and system identifier so reviewers can immediately confirm scope and data source without manual lookups.

Summary totals

Beginning balance, gross receipts, reloads, refunds, adjustments, and ending balance presented in a single row for fast verification.

Transaction detail

Breakouts or attachments showing daily totals, transaction counts, and sample transaction IDs to support spot checks and exception investigations.

Variance analysis

Dedicated section explaining differences between system and ledger totals, including corrective entries and responsible staff for follow-up.

Supporting attachments

Included provider reports, bank statements, refund logs, and any error reports that substantiate reconciled numbers and adjustments.

Sign-off block

Named preparer and approver fields with signature, title, and date to create accountability and an audit trail for approvals.

Security and compliance checklist

Encryption: TLS 1.2/1.3 in transit

Data at rest: AES-256 encryption

Audit trail: Timestamped activity logs

Access control: Role-based permissions

Retention policy: Configurable archival rules

Regulatory options: BAA and 21 CFR available

Common preparation challenges to watch for

Mismatched identifiers between provider extracts and internal charts of accounts that prevent automated matching and require manual adjustment.
Rounding differences between systems causing cent-level variances that accumulate over many transactions and complicate audit sampling.
Missing or late provider reports that delay reconciliation and can push variances into the next accounting period.
Incomplete variance explanations or missing supporting documentation that trigger auditor queries and extend audit timelines.

How reconciliation data typically flows

A consistent data flow from card system to ledger reduces friction and preserves traceability for reviewers and auditors.

Export: Provider exports transaction batches for the reporting period.
Import: Finance imports CSV or fixed-file data into reconciliation template.
Match: Automated or manual matching links transactions to ledger entries.
Approve: Preparer and approver sign off and archive completed file.

Digital workflow configuration for online completion

Configure these settings to streamline electronic completion, review, and storage of reconciliation forms.

Field	Configuration
Auto-fill fields	Map provider CSV columns to form fields for one-click population.
Conditional fields	Show variance explanation field only when discrepancy exceeds threshold.
Signer authentication	Use email plus SMS code or enterprise SSO for approvers.
Archive destination	Save final PDF to secure cloud storage with retention tag.

Paper vs electronic completion: immediate differences

Consider legal and operational differences when choosing paper or electronic execution methods for reconciliations.

Format	Paper	Electronic
Legality
Authentication	manual id	email/sms/kba
Audit trail	limited	robust
Storage	physical	encrypted cloud

Typical submission timing and processing expectations

Set a regular cadence for reconciliations and allow time for variance investigation, approvals, and filing in line with accounting close schedules.

Monthly close:

Complete reconciliations within five business days after period end.

Variance follow-up:

Investigate and resolve differences within ten business days.

Approvals:

Require preparer and approver sign-off before posting adjustments.

Archival:

Archive signed form within 48 hours of final approval.

Audit readiness:

Maintain attachments and notes to support sampling requests.

Key milestones in the reconciliation lifecycle

Track these sequential stages from data receipt to archived approval to meet internal control and audit requirements.

01

Data receipt

Provider reports received and logged for the reporting period.

02

Initial matching

Automated or manual matching performed and unmatched items flagged.

03

Variance remediation

Research discrepancies and document corrective entries or dispute requests.

04

Final approval

Approver signs off and posts journal entries where applicable.

Consequences of inaccurate or late reconciliations

Regulatory fines: Possible monetary penalties

Backup withholding: Withholding obligations may apply

Audit findings: Formal audit exceptions

Cash misstatement: Material balance errors

Payment delays: Vendor or settlement delays

Reputation: Stakeholder trust erosion

Multi-vendor pricing and feature comparison for eSignature use with reconciliations

Compare starting prices and core capabilities for commonly used eSignature vendors; signNow is listed first per standard vendor comparison practice.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	7-day free trial	Varies by plan	Varies by plan	Varies by plan	Varies by plan
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Representative use cases

Real-world examples show how the form supports diverse operational models and audit needs.

City Transit Agency

The agency runs daily batch exports to feed reconciliations and automates variance flags for investigation

The vendor provides a consolidated file
This reduced manual matching and improved month-end close while preserving full audit trails for federal grant reviewers.

University Campus

Campus parking and transit services reconcile student card reloads monthly

Transactions are sampled for refunds and adjustments
The reconciled forms link to student account billing and support internal dispute resolution without delaying ledger posting.

Typical signatories and roles

Preparer — Staff Accountant

The preparer compiles provider reports, completes numeric fields, and attaches supporting documents. They are responsible for initial variance notes and for escalating unresolved items.

Approver — Finance Manager

The approver reviews reconciled totals and variance explanations, authorizes adjustments, and certifies the form for posting and archival under internal control procedures.

Frequently asked questions about the Metro Card Reconciliation Form

Answers to common questions on execution, electronic signing, and resolving mismatches.

Need help? Contact support

What is the form used for?
It documents the comparison of card system totals to ledger balances for a specified period, records variances, and captures corrective actions so accounts are accurate and auditable.
Who must sign the completed form?
Typically the preparer and a supervisory approver sign and date the form; organizations may require additional signatories for high-value adjustments or grant-funded revenue reconciliation.
What if totals do not match?
Document each discrepancy, attach supporting reports or transaction samples, and record the remediation steps. Escalate unresolved items according to the variance policy and retain evidence of follow-up.
Can this form be signed electronically?
Yes — electronic signatures are generally valid under the ESIGN Act and UETA in most states. Ensure signer intent, consent to electronic records, attribution, and reliable retention are in place.
Is notarization required?
Notarization is not routinely required for reconciliation forms. Use a notary or RON only when specific contract, grant, or legal authorities mandate authentication.
How long should records be kept?
Retain reconciliations per finance policy and applicable law: at least three years for tax purposes and longer where contracts, grants, or state rules require extended retention.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now