Sage 100

Sage v2013 Advanced - Client in process of migrating from 3.71 to v2013. For reasons beyond me, their AP clerk has to complete and Excel template with AP invoice data entry information, print the page and attach it to the actual invoice. To me, it seems like a waste of time, they don't quite see it that way.........yet. So I am wonder if there is a way to script the data from the data entry screen to print on a Crystal form. While they would still be wasting some time, this would eliminate the necessity to double enter the data (Excel and Sage) and WOULD streamline their process. Thoughts?

It could be added to the Invoice Register - like put a subreport at the end to reprint everything one page per invoice.

Interesting. I was wondering if this might be scriptable when you are on the invoice being entered. Perhaps when you click accept, it launches the Crystal for what you just entered.

Probably - I'm just thinking about how long Crystal takes to run these days...

If you're in the AP Invoice Data Entry \ Lines screen, you can just right-click on the primary grid and Export to Excel. The problem with this is you won't get the vendor/invoice number, but that's a little bit of progress...

You could modify the Crystal form MAS90\Reports\AP_InvoiceRegister.rpt that creates the AP Invoice Register. Align the data so it can be previewed and exported in an intelligible fashion.

OT: These are difficult customers. Invariably a new controller or bookkeeper comes along and asks ""why does Sage 100 require all these extra steps and why didn't you tell us the right way to do it"". This usually comes 90 days before the ROR and there's nothing you can do to prevent it.

The difficulty with this new client is that they are doing something manually that no one has been able to explain why they are doing it. What a waste of time to key information into Excel to print a sheet of paper, then turn around and rekey the data into Sage 100. IMHO, she is wasting half her day. So if I can come up with a method to key data once, they can still have the cover page. The bigger issue is that they need to integrate their scanning process with Sage. They have started looking at Altec, but (in their words) it is a pricey solution. So first we need to complete the migration doing exactly what they have been doing, then phase two will be to create efficiencies for them.

I have a banking client doing similar. When I get together with the IT director and the person's supervisor they scratch their heads over why the person does it the way she does. Then when you show the right way they seem to ""get it"" but next time they're back at the old time consuming routine. In some ways I think it's job preservation as well as a safety net of not wanting anything to change.

@JeffSchwenk I think the first thing needed is to get the customer to define the purpose of the spreadsheet. The process you are describing is not unusual. A voucher is created and then routed through the office for approval prior to the invoice being entered into the accounting system. If this is the case, I suggest discussing doclink or some other document management tool that will avoid double entry and improve workflow processing. If they are just doing this because they always have and no one is approving the voucher prior to entry, put a page break by invoice in the invoice register so you get one invoice per page and use that as your voucher. If they are truly wed to their Excel entry process, create a VI job to import the invoices and then write a macro in Excel to take the data in excel, copy it to another worksheet in the workbook in a format necessary for import, and then call the VI job to import the info to save them from re-entering. @Wayne, I don't want to hear any TL/DR comments! ;-)

They aren't wedded to Excel, just the piece of paper............... This will be a phase two project after we get them move up to and using v2013. This is the accounts payable manager telling me this. Scary.....

@JeffSchwenk, Halloween is just around the corner so 'Scary' seems appropriate. Boo!