Payment reversal improvements

One needs to reverse a payment under the following circumstances:

  1. wrong payment type used (ie cheque instead of EFT, etc)
  2. wrong amount entered
  3. wrong customer used (in Hong Kong this is quite possible because the local banking system does not provide the ability to add Reference information to any bank transfers, and hence when $123 arrives in the practice's account, the only way to figure out who paid it is to look for customers owing $123)
  4. bounced cheque or credit card declined

In the first three cases the screw up is ours and we want to hide our errors from the customer, ie not show them on the customer's statement. In all 4 cases, it would be useful to be able to edit the Notes and Reference fields of the Refund transaction so as to provide a rationale for the refund.

Hence we would like a project created to:

  1. provide the ability to edit the Reference and Notes field (which defaults to 'Reversal of payment nnnnn') of the Refund transaction
  2. add a flag to the transaction which can be used to suppress the reversing and reversed transactions in the customer's statement. Thus the reversal confirmation screen would display the Reference and Notes fields for the reversing transaction, and also a 'Hide in Statement' checkbox (default unticked).  If this was ticked then both the reversing transaction and the reversed transaction would have this flag set. To take advantage of this facility the statement items jrxml would need to be adjusted to not print items with the Hide flag set. If the jrxml was not updated then things would work as presently - ie all your screw ups visible to the customer.

Note that the above discussion is essentially aimed at the reversal of a payment (which generates a refund). However, I suspect that the same facilities would be of benefit when reversing other types of transactions.

Finally a note on the adjustment of the customer statement to suppress printing of the transactions with the Hide flag set. If the transaction being reversed is in the current period, then there is no problem - both the reversing and reversed transactions will be suppressed leaving the balance unaltered.  However, if the reversed transaction is in a prior accounting period, then we have a problem and really do need to show the reversing transaction (otherwise the opening balance plus the sum of the printed transaction amounts will not match the balance owning). I think that the answer to this lies in sorting the transaction on the hide flag and showing this with the Hide flag set at the bottom of the statement only if their total is non zero.

 

Can others please comment so that I can ask Tim A to create and cost a project for this.

Note that the initial request from the practice manager was for a facility to delete finalised payment transactions. However, after some discussion this morphed into the above design which allows the full set of transactions to be kept but allows the errors to be hidden from the customer.

Regards, Tim G

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: Payment reversal improvements

From a reporting perspective, I think it would be better to only allow transactions to be hidden that are in the current accounting period.

This way, the report template can just suppress all transactions that have hide=true.

What happens if the hiding is screwed up? Does there need to be a facility to hide/unhide reversals after the event?

Re: Payment reversal improvements

Tim A - apologies for the delay in replying - as you know we are travelling.

'Can only hide stuff in current period': I agree with the concept (ie you should not be able to turn on 'hide' on a transaction that appeared on a previous statement), however, I am not sure how one would implement this.

If you say 'back to previous Closing/Opening Balance', then you will block 'hides' in the period between running Reporting|Debtors|End Period and when the statements are printed. However, I suppose that this is acceptable - we just need to warn that if you want to preview statements to look for cases where payment/reversals should be hidden, then this needs to be done prior to running End Period.

'Need an unhide facility': On the basis that screwups are always possible, then I think that the answer is yes. I suspect that the hide/unhide facility should only be available to those with category Administrator (like the customer merge and other 'must be admin' facilities). Ideally, the facility should only work on pairs of transactions - but this probably means adjusting the archetypes to as to record the id of the other transaction in the pair.

Note that on the reporting side, I see that the only 'reports' that will need adjustment will be the statements. Any other report (eg customer transaction listings) should show the both hidden and non-hidden transactions - however, here it might be wise to flag any hidden transactions.

Regards, Tim G

Re: Payment reversal improvements

Re: Payment reversal improvements

I agree that would like some changes to the Statements - our nurses make a variety of errors when processing payments and though I would like them not to I would also like the Statements to read better for clients - I struggle to understand them. When  a client pays their account they rightly assume they have paid it correctly and in full. Sometimes our nurses do not pay attention to a previous balance that goes missed - we are trying to ensure they read the box on the side when they check a patient but at times it goes missed.

This is an example of a recent Statement and I must say we are embarrased by it 

Im sorry but cannot seem to place it here but as an attachment.

Thanks Anna

 

 

 

 

 

 

 

 

 

 

 

 

 

 

AttachmentSize
statement.pdf 163.87 KB

Re: Payment reversal improvements

Anna - I think that I can fix your statement problem - but not until after mid June when I return to Australia. Below is sample statement tweaked for Cahir King in Ireland (who needs the ex- and inc-VAT columns). [The product names are anonymised because this was generated using my anonymised database.] You will see that the product type information is used to group all the like products together and control the print order.  Hence, if you want to use this type of statement, you need to have the product type data set up (ie the product types set up, and a product type assigned to each product).

Here  is the last page showing the remittance advice slip. Obviously, this needs tweaking for your practice.

You also need to think about the GST data and how you want that presented. Do you want just an Inc-GST column, or do you want GST and Inc-GST, or what.

If you want to take this further, contact me via tim dot gething at bigpond.com

Regards, Tim G

Syndicate content