ImaCash integration

FarmaBrain

Set up FarmaBrain with ImaCash: private PostgreSQL access, field meanings, cash movement reading, filters and checks before use.

Historical Centro Farmacéutico logo associated with FarmaBrain
Pharmacy

Set up FarmaBrain with ImaCash

The ImaCash profile is named FarmaBrain and queries PostgreSQL. Ask the provider to confirm the edition and exchange structure supported for your installation. Configure the cash machine separately; this guide does not validate every version or physical operation.

1. Prepare PostgreSQL access

The provider must prepare the destination, port and active database, with a dedicated query account for ImaCash and access to the required structure. Check communication under the actual ImaCash Windows user. Access details are private: the administrator supplies them and they are entered only in the application.

2. Select the profile

Open Configuration > Integration, choose POS and select FarmaBrain. The Pharmacy category and Save button in old screenshots belong to an earlier interface.

3. Complete the five connection details

Server IP takes the confirmed private host of the PostgreSQL server; Port takes its connection port, with no universal value. Database name takes the installation’s active database. User and Password take the private account authorized to query it. Do not copy another pharmacy’s details or values from an old configuration.

The four legacy fields

Sales, Companies, Auxiliaries and Counters also appear in the form. The current reader does not use their values as file paths: it queries the intended PostgreSQL structure. Do not prepare exchange files or folders to complete this connection or change these entries to try to alter its scope; check any different configuration with support and the provider.

4. Save when closing

Close Configuration and confirm saving when prompted; follow any proposed restart when applicable. Saving attempts to start the connection. Saving, a ping or a connected indicator do not validate authentication, permissions, complete reading or a payment. An empty list does not prove that no movements are pending.

5. Which movements are read

Movements with a nonzero amount of the intended cash type are queried from the selected synchronization date and time, inclusive. The amount is interpreted in hundredths and retains its sign; confirm currency and meaning with the provider. There is no payment method selector or validated capture of cards or mixed payments.

6. Check the filters

Open Configuration > Filters and select the terminals authorized for that cash register. Check operator and company filters with support and confirm their mapping to received identifiers. A list of names does not prove that those names match movement identifiers. Before considering a site isolated, verify what is included and excluded; do not assume isolation without confirmed filters.

Confirmations and scope

Confirming or rejecting in ImaCash does not write a closure or cancellation in FarmaBrain. Items, shifts and bank totals have no validated scope. Do not assume complete historical recovery or absence of duplicates from changing the synchronization date.

7. Verify before commercial use

Arrange a supervised test with the provider comparing reference, date and time, amount, sign, currency, terminal, operator, company and outcome across FarmaBrain, ImaCash and the machine. If the outcome is uncertain or readings are missing, review both systems and actual cash with support before repeating, resynchronizing or restarting. This documentation review does not replace physical validation.

Historical FarmaBrain configuration in ImaCash with empty access fields
Historical Spanish screenshot with empty data and the Centro Farmacéutico brand. It shows Pharmacy, Guardar and legacy fields; the current form uses POS and saves when closing. Visible file fields do not validate file-based exchange.

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.