Farmatic configuration
Open Configuration > Integration, choose POS and select Farmatic. The Farmatic administrator must confirm the edition, active database structure and private query details for this installation. Configure the cash machine separately; this guide does not validate every edition or model.
- Server (IP): private SQL Server host reachable from the ImaCash computer. If the installation uses an instance, the provider must state how it forms part of the destination. This profile has no separate TCP port field; do not copy addresses from another installation.
- Database (DB): exact operational database name confirmed by the provider; it is neither the instance name nor a file folder.
- User: private SQL account authorized for the required queries, prepared by the administrator. Preserve any other permissions required by the installation; do not use example accounts.
- Password: Private information provided by the administrator. Enter it only in ImaCash.
Special sales
Capture special sales: this checkbox includes special sales without an associated cash movement. Enable it only if the provider confirms that your installation uses this sale type and how it must be handled.
- Selected: includes special sales in addition to normal capture.
- Cleared: keeps normal capture without special sales.
The saved selection must remain when Configuration is reopened. Do not enable special sales to try to recover any missing reading.
In older versions, Use Special Sales=0/1 uses 1 to include special sales and 0 to keep normal capture only.
Close Configuration and confirm saving when prompted; follow any proposed restart when applicable. The connection check proves basic SQL access only, rather than every table, filter or sale. Saving, a ping or a connected indicator also do not validate a payment. Then check that the checkbox retains the chosen value.
Cash, cards and mixed payments
Accept cards allows movements identified as card payments at the source to be included; it does not authorize or settle the bank payment. For mixed payments, check each cash and card portion separately, including amount and sign, without confusing them with the full sale amount. The connector may recheck recent mixed movements preceding the synchronization point; do not assume complete history or absence of duplicates when changing the date.
Installation filters
Review Configuration > Filters with support: terminal, company, salesperson and till must match actual Farmatic identifiers. Do not confuse a till with a cash machine. A movement without an assigned terminal is distinct from one with a terminal; do not assume it belongs to a till. An available list does not prove isolation: verify what is included and excluded, including mixed payments and special sales.
E-commerce
If the ECommerce? question appears, confirm its use with the Farmatic administrator before answering or changing an existing configuration. Exclusion values are interpreted as comma-separated document prefixes, rather than payment method identifiers. Their scope differs between movement types: check normal sales, special sales and payments. Identifying e-commerce operations may remove operations from the local view; this does not validate a cancellation in Farmatic or the return of cash.
Confirmations and limits
Confirming or rejecting in ImaCash does not write a closure or cancellation in Farmatic. Reading a shift, when available, does not prove fiscal closure or full reconciliation. Do not assume a bank total from card capture. Farmatic Ortogest has a different configuration and must be reviewed separately.
Supervised check
Arrange a test with the provider comparing reference, date and time, amount, sign, currency, terminal, company, salesperson, till and outcome across Farmatic, ImaCash and the machine. Include the modes confirmed for the installation. If the outcome is uncertain, review both systems and actual cash with support before repeating, resynchronizing or restarting. This documentation review does not replace physical validation.