ImaCash integration

Ficheros Alcornoque

Configure Ficheros Alcornoque with ImaCash: a dedicated exchange folder, permissions, cash request capture and verification of results.

ImaCash branding identifying the Ficheros Alcornoque profile
Other

Configure Ficheros Alcornoque with ImaCash

This profile exchanges files with the POS. Before use, the provider must confirm that the installation produces and collects the format expected by Ficheros Alcornoque. Configure the cash device separately; this page does not validate every edition or model.

1. Prepare a dedicated folder

Agree a folder dedicated to this installation with the provider. ImaCash reads and deletes requests and creates response files there: the Windows user running the application needs those permissions. Do not select the drive root, personal documents, backups or a folder containing unrelated files. For a shared folder, verify access and permissions under that same user.

2. Select the profile

Open Configuration > Integration, choose the ImaCash category and select exactly Ficheros Alcornoque. Do not replace it with ficherosTXT, CashDro Ficheros or another file profile: their formats and responses are not assumed to be equivalent.

3. Set Sales

Under Sales, use the folder picker to enter the confirmed full exchange path. Select a directory, not a sales file. This profile does not request an SQL server, database, port or connection account. Do not publish the private path or the credentials for a network share.

4. Save when closing

Close Configuration and confirm saving when prompted; follow the proposed restart if applicable. Reopen it to check the path. A nonempty path or connected indicator does not prove that the folder exists, has permissions or receives valid files; saving does not prove a payment either.

5. Understand capture

Available TXT files in that folder are read without recovering history from the synchronization date. Requests are deleted during capture, before payment confirmation: preserve traceability from the POS with support and do not share the folder between readers. The timestamp comes from file creation and does not prove the original fiscal date. The provider must validate reference, salesperson, amount, sign, currency and decimal separator.

6. Check scope and filters

Requests are classified as cash; this profile does not split mixed payments or authorize or settle card payments. It provides no store, terminal or salesperson catalogs: check local filters with included and excluded cases, without assuming separation by company or till. Item, shift and bank total retrieval is not validated.

7. Verify the result at the source

Confirmation attempts to create an .OK or .KO response linked to the reference in the same folder. Local confirmation or the presence of a file does not prove that the POS has read it and closed the operation; a cancellation response does not prove a cash refund either. Check the outcome in the POS, ImaCash and the device before considering the operation complete.

8. Validate before commercial use

Agree a supervised test using complete requests in the format prepared by the provider and verify each outcome end to end. Do not assume automatic recovery or freedom from duplicates. If the outcome is uncertain, review the systems and actual cash with support before resending files, repeating, resynchronizing or restarting. This documentation review does not replace physical validation.

Integration ready to move forward

If this integration matches your software, the next step is moving into real operation

We can help you validate the scope, confirm compatible hardware and prepare the next implementation step.