Approve the older account’s Funding Machine sources
Open Sources & coverage before refreshing the older account. Its source policy is Approved Funding Machine only. The newer account’s source policy is All transactions. Approve an exact Stripe subscription ID or charge ID, choose FM owner or FM usage, and provide a label and approval reason. A subscription target includes its associated Funding Machine charges and their refund and dispute cash movements. A charge target includes that exact charge and its related movements. Customer-wide inclusion is not supported: sharing a customer does not prove that another product’s payments belong to Funding Machine. A reviewed target registry can also be imported as versioned JSON. Validate its format and preview the exact target count and classifications before saving it. The registry contains identifiers and review reasons, never provider credentials. Registry approval changes which records future manual refreshes may read; it does not start a payment, change a subscription, or alter CRM records. Disable a target with a reason to stop including new activity from it, or re-enable it with a reason. Disabling keeps the approved historical cash already saved in the report. Old-account coverage describes the approved targets and selected dates; Approved scope verified never means the entire old account was reconciled. Editing the approved registry makes saved old-account coverage provisional until a refresh or verified import checks the current registry. Location cash is also provisional when no snapshot is available or the selected dates are invalid. Keep target labels and reasons specific enough for another administrator to review. Add exact Location IDs and Location binding evidence when the source can be linked to a CRM Location. Use Edit target evidence to correct a saved mapping; this preserves the target’s enabled state. Multiple candidate IDs remain ambiguous, and clearing IDs removes that target’s mapping. Review the binding details in the Locations view before assigning cash to a Location. The Sources view also lists old-account invoice payment exceptions, including externally recorded invoice payments and invoices without a verified Stripe charge. Open the invoice evidence link to investigate. These records are excluded from Stripe gross and net cash until a real processor movement is established.Refresh a selected period
Select a date range and choose Refresh selected dates. Dates use UTC, including both selected days. The source status shows which accounts were checked, the period covered and when the data was retrieved. Refreshes are manual. Larger historical reads from the newer account resolve invoice identities in pages to avoid a separate lookup for every payment. The older account remains limited to approved exact sources. If the selected source scope cannot be completely read, the last successful snapshot stays available with an error that names the cause, such as a read limit or a provider rejection. A missing connection is never reported as zero revenue. Narrow the period and retry if the read reaches its limit. Use the account and currency filters to inspect each source. Currencies remain separate. The report uses each cash movement’s own date: a refund in October for a September sale reduces October collections, rather than rewriting September.Read the totals
- Gross collections are actual captured payments.
- Refunds are refund withdrawals. Failed refunds returned by the processor appear as adjustments.
- Disputes show withdrawals separately from money reinstated after a win.
- Fees include the fees on those movements and separate processor fee entries.
- Net cash is the signed activity after fees, excluding bank payouts, internal transfers, and reserve or authorization holds.
- Payouts transfer money already collected; they are not additional revenue.