Guide: Understanding e-invoice
Sage 50 2017, Payment Center
|Software is installed||This includes Sage Exchange Desktop and Sage 50 2017|
|SEHOST32||After the plugin is enabled and access is allowed to Sage 50 “SEHOST32” becomes a background process in Windows. This application is what synchronizes the invoices between Sage 50 and Payment Center. It must be running to work. It will also close if SED is closed or if the plugin is disabled or set to off.
In some cases it may wait until the sync is done before it closes and as a result it may linger for some time.
|APIAccess.dat||When “Always Allow” is select this creates a permission that allows our plugin to talk to Sage 50. The file that it uses is called APIAccess.dat. In some cases this may need to be deleted if Sage 50 and SEHost32.exe stop communication.
It can be found in the company folder. This can be found by going to System in Sage 50 and looking for datapath.
|Configure Sage 50||
|Payment Center||Payment Center uses the MID and Mkey stored in Sage 50 to identify the Payment Center account. If left blank the merchant will see a “Merchant Application” screen.
If the MID/MKEY is for some reason not linked to their SED account it can prevent them from logging in.
You can always use www.sagepaymentcenter.com to test their login.
|Invoice Syncing||At this point the setup is complete. SEHOST32 will now start to collect invoices going one day at a time starting with the current day and working back today-365. Invoices should start appearing within a few minutes.
After the initial sync is done SEHOST32 will begin to check for updated invoices based on a “Last Saved Date”. This will check continuously throughout the day.
|404 Error In Tracelog||Description: When viewing the tracelog if you see an error response 404 this normally means that the data set is too large to sync with Payment Center. This typically occurs when a large number of receipts are created for an invoice.|
<add key="404ALL" value = "true" />
|Invoices stopped Syncing||Description: This may be caused by the 404 error or if Sage Exchange Desktop and SEHOST32 is no longer running.|
|Resolution: Restart SED. Under plugins make sure it is on.|