Set up Garpesoft with ImaCash
This guide covers the ImaCash Garpesoft profile that queries SQL Server. The supplier must confirm the edition and prepare its exchange view; the name does not validate similarly named applications or every cash device model.
1. Prepare SQL access
Ask the administrator for the server and instance, active database and a private SQL account with read permission on the sales view prepared by Garpesoft. A shared administrator account or an empty replacement database is not required. The supplier must confirm network, structure and installation scope.
2. Select Garpesoft
Open Configuration > Integration, choose POS and select Garpesoft. Set up the cash device separately. This profile uses neither an exchange folder nor a DSN.
3. Complete the four fields
Server IP takes the confirmed SQL destination and its instance where applicable. Database name takes the active database; User and Password take the administrator-provided private SQL account. There are no separate port or Windows authentication fields. Keep these details out of public pages, screenshots and documents.
4. Save when closing
Close Configuration and confirm saving when prompted; follow the suggested restart if applicable. The initial connection opens and closes SQL: it does not by itself check the view, all permissions, filters or a payment.
5. Understand capture
The query reads from the synchronisation instant, inclusive, retrieving ticket reference, amount, date and payment type from the view. Check business date, currency, amounts and signs. Availability depends on what the supplier retains and exposes; do not assume complete history or duplicate-free resynchronisation.
6. Check payment types and filters
Workstation and operator come from the view: compare their identifiers with ImaCash filters without guessing. Payment type also comes from the source; the supplier confirms its encoding. There is no payment-type, workstation or operator list to discover them. Recording a card does not prove bank payment; the fixed company reference does not prove isolation between companies.
7. Confirm scope
Confirming or rejecting in ImaCash does not write a closure or cancellation in Garpesoft. The local result does not prove the final POS state. Items, shifts and bank total are not provided. Check both systems for any state change or refund supported by the installation.
8. Verify before live use
With the supplier, validate capture, references, filters and the actual result in ImaCash, POS and device. A connection or this guide does not replace supervised physical testing. If the result is uncertain, check the operation and actual cash before repeating, resynchronising or restarting.