Yeah we use Artsyl, or docAlpha. It’s one area I keep meaning to double back and check on - my users won’t put their hand up and say that they are having to teach it the same invoice multiple times, they would just plod along. I want to check that the learning part of it is working as intended. You say a year, but in reality if you purchase from most of your suppliers monthly or quarterly, then it will be much less. Also, the standard one does a good job of picking up the required fields. The ones I have personally had to teach it, are the invoices where I sit and wonder what’s going on for a while because it’s in multiple currencies, and the VAT is shown in GBP but the rest of the invoice is in EUR - stupid things like that, sit there cussing the supplier!
The docAlpha bit if it’s working well is just looking to capture: InvoiceNum, InvoiceDate, SupplierName, SupplierID, SubTotal, Tax, Total. We supplemented this with Description, so that for Non-PO invoices the AP guys can put a description in at the docAlpha stage and it goes straight through to the relevant budget holder inside docStar for coding to the correct GL.
That reminds me, that was another custom field on the Vendor - to hold the username of the person within E10 that it should be routed to. DocStar does a lookup from VendorID, to find that username, and then look that up for a docStar user to route to.