Skip to main content
Best answer by TaliaI

Hello Wright,

 

Removing the bank feed transaction will not effect anything - the transaction is recorded correctly within your account, all that the process of matching does is allow you to double check yourself. It will still show within your reconcile etc. If they were unable to help you to get it matched, then removing it will be the only option.

 

Thanks,

 

Talia

2 replies

T
TaliaIAnswer
April 3, 2019

Hello Wright,

 

Removing the bank feed transaction will not effect anything - the transaction is recorded correctly within your account, all that the process of matching does is allow you to double check yourself. It will still show within your reconcile etc. If they were unable to help you to get it matched, then removing it will be the only option.

 

Thanks,

 

Talia

R
Richard Green
April 4, 2024

If you have this issue, like we did, it's worth checking that the VAT Refund has been recorded in the correct account, i.e. Bank Account (not Cash, nor PayPal etc.). It's easy to miss the drop-down menu at the top of the Record Refund page.

We were puzzled as to why QB sometimes found a match and sometimes didn't; but when we corrected that, it found the match straight away when we refreshed the Bank Transactions page.

 

To check, go to:

  QB > Taxes > Payments tab > [row for the payment in question] View

Check "Account" shows the correct Bank Account.  If not, delete the payment, then redo the Record Refund process, taking care to select the correct account from the drop-down at the top of the page, as well as the other details:

  QB > Taxes > Returns tab > [row for the Return in question - Action column] Record Refund

 

G
GeorgiaC
April 4, 2024

Hi Richard, thanks for popping on this thread to share your solution. It's quite an easy oversight to select the wrong account when recording the VAT payment, so we appreciate you detailing the steps to correct this. 

 

If anyone requires any further help in recording or correcting VAT payments, please drop-in below. 

Terms & ConditionsAccessibility statement