Understanding Discrepancies in Payment Records and Financial Tracking in Moovs
Moovs users may encounter discrepancies in financial data or reservation records, particularly when comparing charges, payouts, and reconciliations across different reports in the app. Below, we summarize key scenarios and provide guidance to resolve common issues.
Payments Not Appearing in the Finances Section or Payouts
If a customer charge is processed using the "credit card" option under Payment Methods (i.e., the generic credit card option instead of a Moovs-linked payment method), the transaction may not appear in Moovs' Finances section or future payouts. This happens because: The 'Generic Card' option is a placeholder indicating that the payment was processed outside of Moovs using a separate payment processor. When this option is used, the funds will not appear in Moovs Finances, payouts, or the manifest, and the reservation status may incorrectly show as paid even though no funds were collected.
The charge was handled by an external payment processor, not Moovs' native processing system.
The booking contact does not have a card stored in the Moovs app for payment.- Payments marked with 'Generic Card' will not be reflected in Moovs' internal financial tracking systems, requiring manual corrections to ensure accurate records.
In such cases, users should ensure that payment processing is conducted through Moovs to track financials seamlessly. If a reservation is incorrectly marked as paid using the 'Generic Card' option, users should refund the payment entry to reset the reservation status to unpaid and then re-charge the trip using the customer’s actual payment method to ensure proper processing and recording.
Understanding Report Discrepancies and Reservations Marked as Paid or Unpaid
Users may observe differing payment statuses across Moovs' reports. For example, reservation records might display trips as paid, while the "All Reservations Table" report flags some as unpaid. Similarly: Payments marked with 'Generic Card' may also contribute to discrepancies, as they can cause reservations to appear as paid even though no funds were collected.
The "Drivers Table" report may show all trips as paid in terms of driver earnings, while "All Reservations Table" reflects discrepancies.
This occurs due to differences in how Moovs structures these reports and their fields.
Resolving Report Discrepancies
To reconcile such mismatches, follow these steps:
Identify the purpose of each report: Confirm whether the "paid" field reflects customer reservations, driver payments, or other metrics.
Align your queries with the appropriate field: Understand what the "paid" or equivalent fields represent to avoid misinterpretation of payment statuses.
Compare the fields with payables: Perform a detailed review of the affected booking and payment fields before concluding.4. For 'Generic Card' discrepancies, refund the payment entry to reset the status to unpaid, and re-charge the trip using a valid payment method to ensure accurate tracking.
Using this approach, users can streamline financial reconciliation and better interpret Moovs’ report data.
Summary
Discrepancies in Moovs financial tracking often arise from the use of non-Moovs payment processors or misaligned interpretations of report data. By ensuring payments are processed within Moovs and carefully comparing report fields, users can maintain accurate financial records and resolve inconsistencies efficiently. Additionally, understanding and properly handling the 'Generic Card' option is crucial for maintaining accurate payment records and ensuring smooth financial operations.