You’re offline. This is a read only version of the page.
20
*This post is locked for comments
I have the same question (0)
Hi Tracey, Can't answer your Cogsdale question, however I have a fair bit of experience interfacing GP and other systems. There is a product for GP called eConnect. In short this lets you create very stable interfaces to GP from other systems, and the error reporting is pretty good. You can run it as a service in the background with no user intervention, except when a document fails to integrate. We have a customer who interfaces sales invoices from their maufacturing system (bespoke software) and the FC runs a smartlist daily that lists any invoices that have failed, and why they have failed. He can then correct the source data, and the next time the integration runs, the invoices come in. Failures are usually eithre incomplete data coming from the source system, or exchange rates or items or smething not being set up in GP. There are other options such as integration manager, or writing bespoke interfaces, but if you're bringing in a volume of transactions, eConnect is definately the best way. There is obviously a cost up front in purchasing eConnect and having the interfaces set up but this is more than compensated for by the reduced management time in managing the interfaces. Like any other product, GP can interface with really any software and the eConnect functionality ensures no 'Bad' data can be pushed into a GP table. Issues only ever arise due to badly thought out interfaces!
Not sure what you mean by your last question. Expenses are recognised based on receipt of an invoice, not on the payment of the invoice. Maybe you could expand?
Share
Report
All responses (
Answers (
