Set up GPASoft with ImaCash
This profile exchanges files with the POS. The supplier must confirm the installed edition, format and response flow; the GPASoft name does not establish compatibility with every program in its range.
1. Prepare a dedicated folder
Agree an exchange folder with the supplier for one workstation and one consumer. The Windows account running ImaCash needs to list files, open inputs exclusively for reading and writing, delete them and create responses. 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 and GPASoft. 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 any private installation details.
3. Agree the sales file format
The exchange uses .txt files in the top-level folder. Prepare one compact record per file with the supplier, UTF-8 without BOM, smaller than 1 KiB, with six semicolon-separated fields: amount; terminal; supplier field; seller; date and time; payment type. Amount and date must match the Windows regional settings. The reference is the filename without .txt, not the third field: it must be unique and kept until the result has been checked.
4. Save and check access
Save and close settings under the actual Windows account used by ImaCash. A non-empty path is enough for this profile to appear connected: it does not check existence, permissions, format, POS receipt or cash. Review those points with the supplier before commercial use.
5. Understand input consumption
ImaCash reads top-level .txt files and deletes inputs during reading, before the result is confirmed, even when they are not accepted. It provides neither a processed-file archive nor historical recovery by date. Keep traceability at the source and do not copy an input back to repeat an operation.
6. Check identifiers and scope
The terminal and seller come from the file; company, till and seller catalogues are not queried. Saved filters do not establish workstation isolation in this reader: prepare a dedicated folder and verify the received records. This profile does not import products, stock, shifts or an independent bank-card total.
7. Review Accept cards
When Accept cards is off, inputs whose sixth field is 0 are excluded. Enabling it allows those inputs, but does not prove a card payment, split payment or bank settlement: the profile records operations as cash. Before combining payment methods, the supplier must check that each response retains the correct file reference. Do not enable the option to conceal missing sales.
8. Check the response and cash
Confirmation attempts to create an empty file with the same reference and .OK extension; a transaction marked cancelled uses .KO. Refusal alone generates no response. These files do not prove that the POS has read them or closed the sale, or that cancellation has finished. Under supervision, validate the reference, amount, response in both programs and actual cash. If the result is uncertain, review them before repeating, restoring files, resynchronising or restarting. This guide does not establish physical validation.
The logo identifies the supplier; the guide describes current ImaCash fields without reusing old configuration screenshots.