Your customer paid a WeeConnectPay pay link and got their receipt, but the invoice in Zoho Books still shows a balance. This is the one case where the card payment succeeds and the invoice does not follow, and your dashboard flags it so you can settle it.
First, what is already true. The card was charged, the money is in your Clover account, and your customer has their receipt. Nothing about the payment is in doubt. What is outstanding is the record on the invoice, and everything below is about getting that right.
Where you find it
On the Zoho Books page in your dashboard, the organisation's row shows an Attention count reading "[number] to review". Click View on that row to open Connection details, and look under Recent payment attempts.
Each attempt that needs you shows the invoice, the amount, the transaction, a plain sentence saying what Zoho Books said, and the actions available to you.
WeeConnectPay does not email you about this. The count on the row is the signal, so it is worth a glance when you open the page.
What the reason means
WeeConnectPay retries a recording on its own for several hours before it lands here, so an attempt in this list is one that Zoho Books answered with something a retry will not fix, or one that ran out of retries.
| What the attempt says | What happened |
|---|---|
| The invoice was voided | Someone voided the invoice in Zoho Books after the pay link went out. |
| The invoice was already paid in full | The invoice was settled in Books before we got there. |
| Another payment landed on the invoice first | The remaining balance in Books is now smaller than the amount your customer paid. |
| The invoice is no longer available | Books can no longer find the invoice in this organisation. |
| The payment currency did not match | Books would not accept a payment in this currency on this invoice. |
| The invoice's branch could not be accessed | The Zoho login that holds the connection cannot reach the branch the invoice belongs to. Grant it access in Zoho Books. |
| The connection is missing a permission | The Zoho authorisation predates a permission we now need. Reconnect the organisation to grant it. |
| The Clover Charge UUID field could not be confirmed | That field on Payments Received is what stops a payment being recorded twice, so we stop rather than risk it. Fix the field in Zoho Books, re-check it on the connection, then retry. |
| Recording did not go through after repeated attempts | Zoho Books stayed unreachable or kept refusing for the whole retry window. |
What you can do about it
Three actions are offered on a failed attempt, and which ones appear depends on the reason. Each opens a confirmation showing the amount and the reason before anything happens.
Retry recording. Puts the recording back in the queue and asks Zoho Books again. Use it once you have fixed the cause: granted the branch access, reconnected the organisation, sorted out the Clover Charge UUID field, or simply waited for Zoho Books to come back. Offered on the reasons a fix can clear.
Refund the charge. Returns the full charge to your customer's card through Clover. The refund bills its own transaction fee and the original fee stands, and it cannot be undone. Offered on every failed attempt, because giving the money back is always an option.
Record as credit in Books. Records the payment on the customer in Zoho Books without touching the invoice, where it sits as unused credit that you apply to an invoice from Books. Your customer keeps nothing back and you keep the money. Offered where Books will accept the credit, which is the reasons about the invoice itself rather than about the connection.
Choosing between them
If the reason is something you can fix, fix it and retry. That leaves the invoice looking the way everyone expected.
If the invoice is gone or already settled, the question is whether your customer should keep their money on account with you or get it back. Recording it as credit keeps it with you and lets you apply it to the right invoice from Zoho Books. Refunding returns it. Either way your customer is whole.
Once you act, the attempt shows what you chose, either "Refunded to the card on [date]" or "Recorded as unapplied credit in Zoho Books on [date]", and the organisation's attention count goes down by one.
Frequently asked questions
Will my customer be charged again if I retry? No. A retry only asks Zoho Books to record the payment that already happened. Nothing touches the card.
Can I record the payment in Zoho Books by hand instead? You can, and it is a reasonable thing to do. Settle the attempt in your dashboard as well so the count clears and the payment does not end up recorded twice.
Does this stop other invoices from being paid? No. A failed recording is settled on its own, and the invoice it belongs to can take a new pay link while it is outstanding.
I do not recognise the transaction on the attempt. Show in Transactions on the attempt opens that payment in your dashboard, with its full detail and its Clover transaction id.
None of the three actions is right for my situation. Email support@weeconnectpay.com with the invoice number and the organisation, and a person will work through it with you.