[freeside] Void payment problem with batch-card invoice event

[Gerald V. Livingston II]

Here it sounds like "voiding" the payment in Freeside is actually what you
do need. If voiding a payment removes it from your records as if it was
never made -- and resets the balance to reflect the unpaid status of the
order the payment was originnaly applied to -- that is exactly the behavior
you need. It makes it look like the customer never made the payment in the
first place, which is the case. The customer's bank never sent the money to your bank.

BUT, if your bank actually transfers funds for all checks into your account
-- then draws back out an amount equal to any NSF reports you do need to
use something more similar to "refund" to keep your records straight and
show that the money was deposited to your business account -- then taken
back out.

It all depends on how your bank reports the money from batched checks. Do
they report all funds as transferred to you then any NSF checks drawn back
out later -- or do they deduct any NSF amounts before actually showing the
batch deposit on your balance sheet?

In either case, you may need to add some sort of logic such that when a
CHECK payment is voided it adds another order for the NSF fee.

Gerald

On Thu, 3 Mar 2005 21:27:43 -0500 Gilbert Rebeiro <gilbert at dido.ca> wrote:

> Hi again,
> 
> I am using batch-card to send "pre-authorized-payments" to my bank for
> processing. (they provide me with a void check specimen)
> I use realtime for credit-card transactions.
> 
> When I run freeside-daily it populates the cust_pay_batch table (I've
> enlarged the cardnum field to accommodate the account number and aba routing
> information, and removed some of the verification logic for credit cards).
> 
> I then run a simple script that reads through the cust_pay_batch table and
> creates a text file that conforms to the banks' specification and upload the
> file.
> 
> They process the file and accept it with no errors, this doesn't mean that
> nobody will NSF, it just means that my bank will forward me the total
> amount.
> 
> I then create a file from the original table that conforms to the "CSV
> results from TD Canada TrustMerchant PC Batch" format and process all the
> payments in the batch.
> 
> All the clients in the batch get a receipt via email.
> 
> Sometimes a few days (5 in some circumstances) the NSF information arrives.
> 
> I don't mind doing the development, but, how should an NSF be handled so
> that it can be included in the next batch card run?
> 
> I am not sure that a refund is what I am looking for.
> 
> I hope this is clear.
> 
> Thanks in advance,
> Gilbert.
> 
> -----Original Message-----
> From: ivan [mailto:ivan at 420.am] 
> Sent: Thursday, March 03, 2005 7:40 PM
> To: ivan-freeside at sisd.com
> Subject: Re: [freeside] Void payment problem with batch-card invoice event
> 
> "voiding" a payment removes it from your records.  It doesn't send anything
> to a processor.
> 
> "refunding" a payment sends a reversal for the payment to your processor (it
> cancels the transaction if it hasn't been settled yet, or issues a credit if
> it has).  This functionaltiy requires support for "credit"
> (and optionally, "void") actions from the specific underlying
> Business::OnlinePayment::Processor module. 
> 
> This functionality is only available when using a real-time processor.  
> Batch processing only batches payments (IIRC credit card only, not ACH).  
> 
> I've barely worked on the batch processing in years.  All of my current
> installs except one use real-time processing. 
> 
> --
> _ivan
> 
> 
> On Thu, Mar 03, 2005 at 07:58:10AM -0500, Gilbert Rebeiro wrote:
> > Hi,
> >   I am using freeside 1.5.0pre6
> >   after I void a payment for a customer with payment type of  Electronic
> > check (automatic) 
> >   the payment doesn't get into the cust_pay_batch table after running
> > freeside-daily on the next billing run.
> > 
> >   Am I missing a step?
> > Thanks,
> > Gilbert.
> >   
> > 




-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.6.0 - Release Date: 3/2/2005