Configure Futura with ImaCash
This guide covers the Futura profile that queries SQL Server. The supplier must confirm the installed edition and database structure; the name does not validate every edition or equivalence with the FireSoft file connector.
1. Prepare SQL Server
Ask the administrator for the server and instance, active database and a private SQL read account with the minimum required permissions. There are no universal credentials. The supplier must confirm network, structure and access under the actual ImaCash Windows user; do not create an empty replacement database.
2. Select Futura
Open Settings > Integration, choose POS and select Futura. Configure the cash device separately. The old screenshot showed Others and an earlier Save button; these are not the current steps.
3. Complete the fields
Server IP takes the confirmed SQL destination and its instance where applicable. Database name takes the active database; User and Password take the private SQL account. These are not a DSN, folder or sales file. There is no separate port or Windows authentication field. Keep values out of public pages, screenshots and documents.
4. Save when closing
Close Settings and confirm saving when prompted; follow the proposed restart if applicable. The initial check opens and closes SQL and may read payment methods. It does not validate all queries, filters, payment or physical communication with the device.
5. Choose payment methods
Select the actual cash payment method from the database list. If a card method is requested, choose a different method and confirm its mapping with the supplier. Do not guess identifiers or use the same method for both. Cards are classified for capture: this query does not authorize or settle a bank payment.
6. Check captured data
The query starts at the selected date and time, inclusive, grouping amounts by order and supported payment method. Check business date, amount, sign and refunds. Before allowing split payments, verify each portion and reference in both systems, without assuming complete historical recovery or freedom from duplicates.
7. Review filters and scope
Compare the received seller identifier with local filters. Terminal and company use fixed internal values: they do not establish multiple tills or companies, or isolation between them. Terminal, shop and seller catalogues are not provided. Items, shifts and bank totals are not validated, even if a general interface option exists.
8. Verify the outcome
Confirming or rejecting in ImaCash does not write a closure or cancellation to Futura. With the supplier, verify payment selection, capture and the result in ImaCash, the device and the source, including supported refunds. If the result is uncertain, check both systems and actual cash before repeating, resynchronizing or restarting. This documentation review does not replace a supervised physical test.