Set up ICG Retail in ImaCash
The ICGRetail profile reads SQL Server cash records without writing to the source. ICG presents FrontRetail as its retail software; the provider must confirm the specific edition, structure and installation. This profile cannot be replaced by ICG, ICGV2, ICGV3 or ICGMarket and does not establish compatibility with the whole range.
1. Confirm the database and private access
Ask the administrator for the SQL Server destination, transactional database and a private read-only account. It must be able to query FACTURASVENTA and TESORERIA and inspect their structure; VENDEDORES is needed for the seller catalogue and filters. Write or administrator permissions are not required. Do not copy another installation's settings.
2. Select POS > ICGRetail
Open Configuration > Integration and select POS > ICGRetail. Fill in Server IP, DB Name, User and Password with the confirmed private settings. The destination can be the SQL name or instance supplied by the administrator. This profile does not show separate port or instance fields or a Windows authentication selector: do not look for those options or change permissions to compensate.
3. Enter cash codes in Terminals
In this profile, Terminals takes the exact cash payment method codes, despite its label. Separate multiple codes with a comma or semicolon; do not assume a universal value or enter till numbers. At least one code is required. The provider confirms which codes mean cash; this field does not select cards, and an incorrect mapping misclassifies amounts.
4. Check the captured amount
Records for the configured payment methods are summed by document; mixed payments contribute only that cash component, not the full receipt total. Negative amounts keep their sign, and a zero net amount creates no transaction. The time boundary uses the treasury date, which may differ from the issue date; a date-only field can cause the whole day to be read again. A record alone does not prove the entire document is settled or that a device dispensed cash.
5. Review terminal and seller filters
Terminal and seller filters are checked against the available database columns and catalogue. Review the codes and saved selection with the provider; an empty list does not prove there are no sales. If the data needed for a filter is missing, do not replace it with unrestricted capture without review. This profile has no independent shop or company filter.
6. Save and review the selected database
Close the configuration to save. Startup checks the connection and structure. If the core tables are missing and only one accessible compatible database exists, the reader may use it for that connection; if several exist, the correct one must be selected. Always confirm the transactional database with the administrator. A valid connection does not prove complete capture, correct payment mapping or a physical payment test.
7. Stop if the transaction cannot be uniquely identified
The reader checks the identity of the document and its payments. An ambiguous result or interrupted read may stop the batch; this does not mean there are duplicate receipts. Have the mapping and history reviewed before resynchronising or repeating. Do not delete ImaCash records, change dates or alter documents to force their capture.
8. Reconcile the result before repeating
Confirming or rejecting in ImaCash does not write a closure, cancellation or refund to ICG. Compare the document, the amount received by ImaCash and the actual cash before repeating, cancelling or restarting. This profile does not import items, stock or shifts, or validate an independent banking total. Initial tests require a supervised environment and fictitious data.
The logo identifies ICG Software; it does not imply certification, a commercial partnership or physical validation of an edition or device. ICG Software