I'm looking for advice/direction/ideas from the list's collective experience in emailing invoices to customers.

I've set up a client to email their invoices to certain selected customers of theirs. I'm using the PRINT command with EMAIL ON in a WHILE loop - the PRINT command is below. I don't think guts of the WHILE loop are important cuz the variables are correctly defined and invoices are getting emailed as an attached PDF. The PDF file name is ('.\ARInvoices\Invoice'+ (CTXT(.vInvoice#)) + '.PDF') - e.g. Invoice12345.PDF in the ARInvoices subfolder. The email address to which they are being sent, ,vInvEmailAddress, is a specific address to the customer's payables dept for invoices. The custom subject, .vSubject, for each email is  ('Invoice for PO#' & .vPONum & 'from ClientName') The custom body of each email is ('Attached please find ClientName's invoice number' & (CTXT(.vInvoice#)) & 'for your Purchase Order' &.vPONum +'.')

The results: Some customers are getting their emailed invoices (good) and paying them (better). The problem is that a significant number of emailed invoices are not getting through to the customer's Payables dept (worst) for several possible reasons that we can think of: * The email is treated as junk mail - we had customers white list [email protected].

* In some cases, it seems that customer's ISP may be intercepting the emails because customer claims they never received them.  I'm not sure how likely that is - ISPs shouldn't be filtering (mine sure doesn't).  I suspect customers received but can't find the emails. Could ISPs be filtering based on client's old/unrecognized (but working) ISP, optonline.net ?

* The email was rejected because it had an attachment, though we don't know where it went - junk folder, automatically deleted...? The solution is to code the invoice info into the body of the email to eliminate the attachment but could be more cost than its worth.

* Could anti-virus software be intercepting the emails (and not paying them :)?

* Use RMail to request a return receipt?  If we can get this to work using the PRINT command, RMAIL won't be needed.

I'm proposing this checklist for emailing invoices:
* Personally contact each customer before starting to email invoices.
* Confirm email address for customer's AR Invoices
* White list Client's email address on customer's email software and anti-virus & spam filters. * Email one invoice to customer and confirm it was properly received and processed.

Any other ideas, suggestions or advice?

TIA,
Doug

  PRINT InvoiceEM +
   WHERE INVOICE# = .vInvoice# +
    OPTION PDF|FILENAME .vPDFName +
    |EMAIL ON +
    |EMAIL_TO_LIST .vInvEmailAddress +
    |EMAIL_SUBJECT .vSubject +
    |EMAIL_BODY .vBody +
    |EMAIL_FROM_NAME ClientName +
    |EMAIL_SHOW_DIALOG OFF +
    |EMAIL_FROM_ADDRESS [email protected]

R:Base ver X.5E

--
This email has been checked for viruses by Avast antivirus software.
www.avast.com

--
For group guidelines, visit 
http://www.rbase.com/support/usersgroup_guidelines.php
--- You received this message because you are subscribed to the Google Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/rbase-l/c8e3f582-2c51-4e8c-96c2-cd991fd7c42b%40wi.rr.com.

Reply via email to