Set up the Hostelco profile in ImaCash
The Hostelco profile reads operations from MySQL and uses an auxiliary Access file to look up users. The provider must confirm the application, edition and both data sources for your installation. This guide does not establish compatibility with every edition or physical validation with a cash device.
1. Prepare both sources with your provider
Ask the provider or administrator for the correct MySQL database, a private read account and the auxiliary file for that installation. Also confirm the currency and scope of operations. Do not use another company’s data, universal accounts or values from old examples.
2. Select the integration
Open Configuration > Integration, select the POS category and then Hostelco. The business category on this website does not replace the selection in the application.
3. Set up private MySQL access
Fill in “Server IP”, “DB Name”, “User” and “Password” using only private details confirmed by the administrator. The database name is not a folder or DSN. This profile has no port field: the provider must check that the service is compatible with the expected connection.
4. Select the file under “Auxiliaries”
Enter the full path to the auxiliary Access file prepared by the provider, accessible to the Windows user running ImaCash. The connector uses the 32-bit Microsoft.Jet.OLEDB.4.0 provider and requires a compatible process. Installing another ACE provider does not automatically replace it. Do not select a TXT, CSV or arbitrary database, or convert the file as a test.
5. Save and check both reads
Save the settings and check auxiliary access and MySQL operation retrieval with support. A connection indicator or saving without a warning does not prove that both sources can be read correctly, that the data is complete or that a payment worked.
6. Compare the received operations
The profile collects specific payment operations, not every POS document. Compare the amount, currency, sign, date and reference with the source. The selected date is used in the query: check the interval and returned records before resynchronizing. Do not assume a complete history or references that are always unique.
7. Review the profile limits
There is no card selector: accepted operations follow the cash workflow and do not prove bank authorization or settlement. Auxiliary lists do not establish filtering by seller, shop, till or company. Products, stock, shifts and an independent bank total are not included. Confirm the scope before mixing payment methods or several workstations.
8. Verify the result before repeating
Confirming or refusing in this connector does not write completion or cancellation to the POS. Before commercial use, validate the workflow and selected device with support. If the result is uncertain, compare both programs and the actual cash before repeating, resynchronizing or restarting. Do not alter source data to unblock an operation.