Troubleshooting: distinguish native and manual collection
ManyRequests documents Stripe support and describes manually managed alternatives. A payment made through an external method is not the same as a native integrated transaction. Establish which system actually received the money and which record represents the client’s obligation. Do not assume that a portal status updates automatically for every method, or that an unpaid label proves the customer has not sent funds through the agreed external route.
Match more than the amount
Use the invoice reference, client, currency, date and payment identifier where available. Two invoices can share an amount. A screenshot of a transfer request may not prove completed settlement, and an amount arriving without a reference may need clarification. Keep sensitive account details limited to authorized staff. Our reconciliation framework is operational guidance, not accounting advice or a guarantee that a particular payment provider treats every transaction identically.
Avoid duplicate collection
Before sending another payment request or creating a replacement invoice, check the original outcome. If the transaction is pending or uncertain, communicate that state and the next verification step. Do not ask the client to pay twice merely to remove a warning in the portal. Preserve the original invoice and payment evidence while deciding the supported correction. A clean dashboard should never take precedence over an accurate record of what the customer has paid.
Close the discrepancy with evidence
When the payment is confirmed, apply the documented status update and keep a short explanation of the manual reconciliation. Verify whether the related service or allowance also needs a supported update rather than assuming one field controls everything. If the amount or currency is wrong, resolve that difference explicitly. The finished record should let another authorized person understand the payment, the invoice and the remaining obligation without relying on someone’s memory or private chat.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- ManyRequests supported payment gateways — Merchant documentation · help.manyrequests.com · Merchant-controlled · checked 2026-09-19
- ManyRequests agency billing — Merchant documentation · manyrequests.com · Merchant-controlled · checked 2026-09-19
- ManyRequests managing requests and exporting data — Merchant documentation · help.manyrequests.com · Merchant-controlled · checked 2026-09-19