Configure Ibiza in ImaCash
ImaCash's Ibiza profile reads files from a main folder and, if configured, an auxiliary folder. Both inputs are treated as cash. The source system's administrator must confirm the specific exporter, format, currency and installation. This guide describes that profile; it does not establish compatibility with other applications sharing the name or physical validation with a cash machine.
1. Prepare dedicated folders
Agree the main exchange folder with the supplier and, only if its export uses one, a separate auxiliary input folder. Keep them dedicated to this installation, without unrelated documents, copies or unfinished files: the reader processes every file at the top level, without filtering by extension.
2. Select POS > Ibiza
Open Configuration > Integration and select POS > Ibiza. Transactions takes the main folder; Auxiliaries takes the second input folder. Leave it empty only if the supplier confirms it is unused. Do not select the same folder in both fields, a database, a DSN or an individual file.
3. Check the actual permissions
ImaCash's Windows account must be able to list the folders, open their files for exclusive read/write access and delete them. The exporter must be able to deliver complete files. Confirm the location and access under both programs' actual accounts; access available to another user does not establish these permissions. This profile has no server, port, SQL user or password fields.
4. Confirm the format and currency
The supplier must deliver one complete, compact message per file, in UTF-8 without BOM and smaller than 1 KiB. The first field holds the numeric amount in cents and is divided by one hundred; any further fields are separated by a backslash. Confirm the sign, regional settings and two-decimal currency with ImaCash and the machine. Do not infer references or payment methods from other fields or change amounts by hand.
5. Save and test under supervision
Close configuration to save. Startup only checks that Transactions is not empty; a connected status does not validate existence, permissions, format or cash. Receiving an input can start the configured payment flow: carry out initial checks in a supervised test environment, using an authorised file without customer data.
6. Check file consumption and the result
Files are deleted during reading, before a payment result has been established; an invalid input can also be consumed. There is no processed-files folder or date-based recovery archive. Check the source document, the amount incorporated into ImaCash and actual cash. A file disappearing does not mean that it has been paid.
7. Understand the data scope
The reference and date are generated on reading rather than retrieved from the source receipt. Terminal, shop and salesperson data do not by themselves identify their real counterparts; local filters do not establish separation between companies or tills. There is no catalogue of terminals, salespeople or payment methods, products, stock, shifts, separate bank total or card selector. The auxiliary folder does not establish card or mixed payments either.
8. Check before repeating or resynchronising
Confirming or rejecting in ImaCash does not write a closure, cancellation or response file to the source system. Cancelling or resynchronising does not recover consumed inputs or establish a physical refund. If the result is uncertain, compare both programs and actual cash before restoring files, resending, repeating or restarting; the supplier must supervise validation of the specific installation and equipment.
The image identifies ImaCash, like the symbol in the historical entry. It does not identify an external supplier or establish compatibility with other products sharing the name.