Set up gsBase with ImaCash
gsBase is a platform for developing business applications. This guide describes the ImaCash file exchange profile; the supplier must confirm that the installed application produces and receives this format. It does not establish compatibility with every ERP, version or the gsBase API.
1. Prepare a dedicated folder
Agree an exchange folder with the supplier for one workstation and one consumer. The actual Windows account running ImaCash needs to list files, open inputs exclusively for reading and writing, delete them and create the RESPUESTA subfolder and its files. Do not select a drive root, documents, backups or folders belonging to other programs.
2. Select the current profile
Open Settings > Integration and select POS > GsBase. In Sales, use the folder icon to choose the agreed directory. This profile does not request a server, port, SQL account, password or DSN. The administrator supplies private installation details.
3. Agree records and references
The reader takes top-level .txt files. Prepare one compact record per file, UTF-8 without BOM and smaller than 1 KiB, with four semicolon-separated fields: shop; sales reference; seller; amount. It accepts a fifth field but does not use it. The reference comes from the second field, not the filename; it must be unique and valid for the response filename. Do not include paths or directory separators.
4. Confirm the amount unit
The fourth field has two interpretations: if recognised as an integer, it is divided by one hundred; otherwise it is converted as a decimal using the Windows regional settings. The supplier must check the unit, decimal separator, sign, currency and resulting amount before use. Do not assume an integer represents whole currency units or that the same decimal text works on every computer.
5. Save and check access
Save and close under the Windows account running ImaCash, using the full, non-empty path. On startup the profile attempts to prepare RESPUESTA; a connected indicator does not establish POS reading, correct format or cash. Check the folder, permissions, amount and response receipt with the supplier before commercial use.
6. Understand reading and identifiers
Inputs are deleted after reading, before the result is confirmed, even when no valid sale is obtained. There is no processed-file archive or historical recovery by date. Shop and seller come from the record; the terminal is assigned internally and the timestamp is the reading time, not an imported sale date. Shop, till and seller catalogues are not queried, and filters do not establish workstation isolation. Keep traceability at source and do not restore files to repeat operations.
7. Check RESPUESTA
Confirmation attempts to write to RESPUESTA using the sales reference and .OK extension, with amount, tendered amount and change separated by |; check the change sign with the supplier. A transaction marked cancelled attempts .KO with the amount and two zeroes. Refusal alone writes no response. An existing file does not prove that the POS has read it, closed the sale or completed cancellation.
8. Validate the flow and its limits
This profile records inputs as cash and provides no Accept cards selector, independent bank-card breakdown, products, stock or shifts. The fifth field does not establish a payment method. Under supervision, validate references, amounts and signs, responses in both programs and actual cash. If the result is uncertain, review them before repeating, restoring files, resynchronising or restarting. A guide or connection does not establish physical validation.
We retain the gsBase logo from the catalogue; the guide explains the current POS selector and replaces old configuration screenshots.