Hi Paul, > There is no built-in way to put old data into the database at this > time. You could put things directly into the billing_details, > billing_history, and payment_history tables, that would require > reading the code to figure out what needs to go where or printing new > invoices and then editing the dates and payments in those tables so > they match your previous bills. If you know those customers are paid > until a certain date you could make their next billing date, from > date, and payment due date correct so it sends their next bill at > least. > > When you use the e-invoice feature it generates another invoice with > additional charges, just like a printed invoice does. The invoice > maintenance function is used to see old invoices that you've already > charged, printed, or emailed. An email function could be added to > the invoice maintenance function if you want to resend individual invoices > by email. > > Paul
Would you consider setting up a feature where invoices could be auto-emailed out (through cron for example) in either html or pdf formats? Michael. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Citrusdb-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/citrusdb-users
