Set up Cashlogy Tickets
This guide covers the POS file link named Cashlogy Tickets. It is separate from the Cashlogy machine connector and Cashlogy Connector. Confirm that the source program uses this exchange with the provider; the brand does not validate every model, version or module.
Both folders must exist and be accessible from the ImaCash computer under its actual Windows user. This selector does not configure an IP address, port, SQL, DSN or device account.
Setup steps
- Agree two dedicated exchange folders with the provider and establish who places and collects each file. The ImaCash user needs permission to read and remove its own requests and to create or replace responses. Do not select documents, backups or unrelated data.
- Open Configuration > Integration > POS and select Cashlogy Tickets. The Machine tab configures the cash device separately and does not replace these folders.
- Under Sales, select the folder where the POS places collection and refund requests. Under Response, select the folder where ImaCash writes results for the POS to collect. These are folders, not a sales file or database. Confirm directions and permissions with the provider.
- Close the changed configuration and choose to save. Review the result and confirm a proposed restart only when appropriate. The initial check verifies that both folders exist; it does not test all permissions, responses or actual cash.
- With the provider, separately validate supervised collection, refund and cancellation: unambiguous reference, cents, sign, source till and user, an actually received response and actual cash. Check each refund’s link to its original ticket. Do not repeat an operation with an uncertain result.
Scope and checks
Reads collection and refund requests in the file format agreed with the provider without searching subfolders. Uses reading date and time rather than the original ticket date; changing the synchronization date does not recover a full history. An input file disappearing does not by itself prove a recorded or paid operation.
Uses the till and user identifiers received without discovering lists of terminals, sellers, shops or payment methods. Review the exact general capture and pending transaction filter values with the provider; local till and shop values may not distinguish terminals. Treats requests as cash without card or mixed payment breakdowns.
After local processing it attempts to write a collection or refund response, including cancellation. A local return does not prove that the response was saved or read by the POS, that a sale was cancelled or that cash was returned. If the result is uncertain, check both programs and actual cash before repeating, resynchronizing or restarting.
The link consumes input requests: do not delete, rename or restore them to retry. Does not import products or shifts or provide a bank card total. Saving, a response or this guide does not validate physical operation or other devices.
The historical screenshot shows empty Sales and Response fields, the Others category and the Save button from an older interface. The current selection is POS > Cashlogy Tickets, with saving on closing. The shield in the screenshot is ImaCash’s own brand rather than the Cashlogy logo.
