Payments sometimes end up with the wrong status in OfficeRnD, not because of a system error, but because of events outside the system. A bank rejected a charge after the fact. A member never completed authentication. An invoice was paid twice. When that happens, the payment status in OfficeRnD no longer reflects reality, and your invoice balances and revenue reporting are off until it's corrected.
This article explains the most common situations in which marking a payment as failed is the right action, so you can quickly identify them and resolve them without opening a support ticket.
In this article:
Understand why payment statuses fall out of sync.
Identify the 6 most common scenarios that require a status correction.
Know what each scenario means for your invoices and next steps.
Why payment statuses fall out of sync
OfficeRnD records payment status based on what it receives from your payment gateway or accounting software. When something changes on the other side—a bank rejects a charge, a sync fails, a member disputes a transaction—that update does not always reach OfficeRnD automatically. The result is an invoice that shows as paid when it isn't, or a payment stuck in a state that blocks your next action.
Marking the payment as failed corrects the record so you can move forward: re-trigger a charge, expose the Pay Now button again, reconcile your books, or write off a bad debt.
A bank rejected the payment after it was processed
A direct debit or ACH payment may appear successful in OfficeRnD but be bounced or rejected by the bank due to insufficient funds or other issues. When the gateway does not sync the payment rejection back to OfficeRnD, the invoice remains marked as paid even though the funds never arrive.
Mark the payment as failed to correct the invoice balance and accurately reflect the bounced status.
A payment is stuck in "Awaiting Payment"
If a member did not complete 3D Secure authentication or the authorization link expired before they acted, the payment remains pending indefinitely. While a payment is pending, the Pay Now button is hidden in the Member Portal, so the member cannot pay, and you cannot re-trigger the charge.
Mark the payment as failed to clear the pending state and restore the member's ability to pay.
The wrong payment method was charged
Operational mistakes happen: a manual payment was logged incorrectly, or the system automatically charged an old or inactive card instead of a new one. The invoice shows as paid, but the charge went to the wrong place.
Mark the payment as failed so you can process a refund on the incorrect card and charge the correct one.
An invoice was paid twice
A member pays via automated charge and also sends a bank transfer for the same invoice. OfficeRnD records both, but only one is the real payment. OfficeRnD records both, but only one is the real payment.
Mark the duplicate payment as failed so the invoice accurately reflects the actual payment method used.
A payment sync from your accounting software created an incorrect record
When a sync issue occurs with QuickBooks or Xero, incorrect payment data can be pulled into OfficeRnD. Even if you delete or correct the record in your accounting software, the payment status in OfficeRnD remains locked.
Mark the payment as failed to reconcile the record and bring OfficeRnD back into alignment with your books.
A payment was disputed or reversed by the bank
A member disputed a charge, and the operator lost the dispute, or the bank reversed the transaction directly. OfficeRnD still shows the invoice as paid.
Mark the payment as failed to reflect the reversal. From there, you can write off the invoice as bad debt or apply a security deposit to the newly unpaid balance.