Hello,
I am wondering what the proper way is to attach a Customer's previous amount owing/invoice to a new invoice with additional items so I am only sending one new invoice with the total amount owing?
Thanks,
Wade
Hello,
I am wondering what the proper way is to attach a Customer's previous amount owing/invoice to a new invoice with additional items so I am only sending one new invoice with the total amount owing?
Thanks,
Wade
Roger
Wade's requirements were to do it on one page. So while cutting the invoice and collating it with the customer statement after printing does work, it was not what he was looking for based on his original post. I took it to mean something like the invoice/statement sample here, which shows the previous total billed, the two invoices and payments posted since the last statement was cut and the aging at the bottom.
This sample was designed for a municipality that bills for water and is based on the concepts of a utilities invoice showing previous amounts owing. However this kind of reporting has to be done outside the Sage 50 program. It might be an option for him to just include the total amount owing information in the description column manually.
Hi. Anyone has answer for this? I believe Sage has not added this feature to the program yet.
No, that has not been added to the program.
One option would be to turn your email offline, then email the invoice and go back and email the statement. Then open the two emails from your outbox and copy the one attachment to the other email and create an appropriate message.
Delete the first email and send the one with two attachments. Turn your email back online so it will go out.
Hope this helps
Thanks Richard. However, it is very complicated to create the invoice as such since I have to invoice customers in volume and would want the previous owing balance show in the new invoice so customers can pay for the invoice at once. Quickbooks has this feature quite long ago thou.
Then the only real option would be to go to some custom reporting similar to the example I provided in my response to Roger above.
BTW, it doesn't matter what QB has or doesn't have. You are comparing apples and pineapples. At the end, they are the same and get a journal entry done, but the way they get there is different. That argument has never gone over well with the people in Atlanta who control the major feature set changes.
*Community Hub is the new name for Sage City