Configure Hosteltáctil in ImaCash
ImaCash's HostelTactil profile queries an Access file that the supplier must identify for your installation. Confirm the edition, structure and intended operations before configuring it. This guide describes that query connector; it does not establish compatibility with every Hosteltáctil edition or physical validation with a cash device.
1. Prepare the file and data provider
Ask the supplier for the active Access file, its password if protected, and access under the Windows account running ImaCash. The connector uses 32-bit Microsoft.Jet.OLEDB.4.0 and opens the connection in read mode: the process and file must be compatible. Do not replace Jet with ACE or change permissions yourself; the supplier must confirm the requirements.
2. Select the correct profile
Open Configuration > Integration, select the POS category and HostelTactil, exactly as shown in ImaCash's selector. The commercial brand is Hosteltáctil. This selection provides Password and Transactions; it does not require a SQL server, database account or DSN in other fields.
3. Complete Password and Transactions
In Transactions, select the Access file confirmed for this installation, rather than an exchange folder, exported receipt or old copy. In Password, enter the private value supplied by the administrator; leave it empty only if the administrator confirms that the file is unprotected. There is no universal file name, path or password.
4. Review cash and card payment methods
When saving, ImaCash queries the file's payment methods and asks you to map them. Confirm the cash method and a different card method where applicable; their identifiers depend on the installation. Review the saved settings even if you cancel a selector, and do not assume its initial selection is correct. Check with the supplier which methods actually fall within the intended scope.
5. Check saving and reading
Save when closing configuration and review any message. Opening the file or displaying connected does not establish that all data can be read, that the edition is compatible, or that a payment has completed. Seeing the payment method list checks only that query. If it fails, the supplier must review the file, protection, process and Windows access before the integration is used.
6. Reconcile payments and cash movements
The profile queries recorded receipt payments and cash movements from the synchronization time, including that instant. One payment need not equal the receipt total: check partial or mixed payments, amount, sign, currency, date and reference. Refunds depend on how the source identifies them. Do not assume complete history, unique references or duplicate-free synchronization.
7. Validate terminals, operators and scope
Compare terminals and operators with Hosteltáctil's lists and check their filters for both payments and cash movements. The terminal identifier comes from the POS till, not the cash device. The profile provides no independent shop or company filter, items, stock, shifts or independent bank total. A list alone does not establish data isolation.
8. Confirm the result before repeating
Confirming or refusing in ImaCash does not write a closure or cancellation to Hosteltáctil. Classifying a record as card also does not establish bank authorization. If the result is uncertain, reconcile the source, ImaCash and actual cash before repeating, resynchronizing or restarting. The supplier must supervise testing of the specific edition and equipment before commercial use.