Integration modes
Choose the mode that matches your installation. Confirm the connector and its requirements with the provider before changing the setup.
Set up a3ERP TPV with ImaCash
This guide covers the A3ERPTPV selector in ImaCash. It reads sales, terminals and salespeople from the a3ERP TPV installation prepared by the provider.
Before you start
Ask the provider to confirm the installed mode and prepare read access to SQL Server for the Windows account running ImaCash. Obtain the private server, database, instance and authentication details. Do not copy default values from old manuals.
Choose the integration
- Open Settings > Integration in ImaCash.
- Select the POS category, then A3ERPTPV. Do not choose Link, Táctil, Facturación or V2/V3 variants based on a similar name; they require the mode confirmed by the provider.
- Complete the connection fields with your installation details:
- Server IP: private server name or address supplied by the administrator for SQL Server.
- DB Name: exact name of the company database that ImaCash should read.
- Instance Name: SQL Server instance confirmed by the administrator, if used. Do not add the instance twice to the server.
- User: private SQL account with the required read permissions. With Windows authentication, access depends on the actual Windows user running ImaCash.
Password: Private information provided by the administrator. Enter it only in ImaCash.
Payment methods and mode
Cash payment method ID and Card payment method ID must match the actual POS codes. Configuring them also enables reading receivables movements in this selector: confirm that mode before saving. Do not reuse another company’s codes or assume every document is cash.
Company series does not replace the database and does not by itself filter terminals or sales. Confirm its use with the provider and review ImaCash filters separately.
Save the configuration
Enter the private password only in ImaCash, review authentication and save. Resolve any connection warnings with the administrator before continuing. Saving does not prove that the correct sales are being read.
Check the scope
Review terminals and salespeople, apply the appropriate filters and compare authorised transactions with the POS: date, amount and payment method. Validate the full workflow with the provider before commercial use.
An SQL connection does not prove compatibility with every version or physical machine validation. This connector does not write confirmations or rejections to the POS and does not import a product catalogue.
Review the a3ERP TPV V2 connection
This page covers the legacy A3ERPTPV_V2 connection mode in ImaCash. It reads POS documents and adds receivables from configured series. V2 identifies this connection mode; it does not establish a current commercial release or equivalence with Link, Táctil or V3.
Installation requirements
Confirm the mode, compatible SQL Server structure and a private account with read access with the provider. Preserve the connection and authentication settings already used by the installation; do not reuse accounts or passwords from old screenshots.
Preserve the existing mode
- Request technical assistance before opening the configuration to change or save it again. A3ERPTPV_V2 is hidden in the current selector; preserve the working connection.
- Confirm the exact mode with support. Do not choose another a3ERP version because its name looks similar or fill fields to try to activate it: this page does not offer a complete graphical setup process for new installations.
- Review the private settings of the prepared configuration with the technician:
- Server IP: private server name or address supplied by the administrator for SQL Server.
- DB Name: exact name of the company database that ImaCash should read.
- User: private SQL account with the required read permissions. With Windows authentication, access depends on the actual Windows user running ImaCash.
Password: Private information provided by the administrator. Enter it only in ImaCash.
This mode has no dedicated editable Port or Instance Name fields. The provider must confirm how the existing connection identifies the server; do not transfer instructions from other modes.
Identify every payment method
ID forma pago efectivo and ID forma pago tarjeta take actual POS payment identifiers, not user or terminal files. Confirm the lists with the provider and keep the same identifier out of both lists. Do not copy codes from another installation.
In V2, an unrecognised payment method may be treated as cash. Check cards, credit and other payment methods in both POS documents and receivables. Do not assume cards are separated by enabling a checkbox or leaving a list empty; request a review before operational use if a method is not represented correctly. Disabling card acceptance does not replace this check either. If correct classification cannot be ensured, do not treat the configuration as validated or use it for automatic cash collection.
Serie empresa: series to read from receivables; separate multiple series with commas. It does not restrict POS sales. An empty field skips receivables reading. It does not by itself select a shop or terminal.
Private settings and saving
Enter private settings only in ImaCash with technical assistance. Preserve the valid configuration and the confirmed series and payment methods. Opening and saving another selection may replace the legacy mode.
Check the results
Compare previously recorded documents for every payment method with the provider: amount, date, type, vendor and terminal where applicable. Also check mixed payments and refunds without assuming automatic splitting. Validate filters against known operations: receivables do not necessarily retain the original POS terminal.
The connection reads data; it does not import products or write confirmations or rejections to the POS. A successful SQL connection does not validate payment classification, all sales or a physical cash machine. Each installation requires technical review for continued use.
Review the a3ERP TPV V3 connection
This page covers the legacy A3ERPTPV_V3 mode in ImaCash. It reads cash and card amounts prepared by the POS connection. V3 identifies this connection mode; it does not establish a commercial software version or mean V2, Link or Touch mode.
Installation requirements
Ask the provider to confirm that the POS connection prepares compatible data and that a private SQL Server account with read access is available. Preserve the existing connection and authentication; do not copy access details from old screenshots.
Preserve the existing mode
- Request technical assistance before editing or saving the configuration again. A3ERPTPV_V3 is hidden in the current selector; preserve the working connection.
- Confirm the exact mode with support. Do not select a similar a3ERP option or change fields to try to activate it. This page does not provide a complete graphical setup for new installations.
- With the technician, review the private details of the prepared connection:
- Server IP: private server name or address supplied by the administrator for SQL Server.
- DB Name: exact name of the company database that ImaCash should read.
- User: private SQL account with the required read permissions. With Windows authentication, access depends on the actual Windows user running ImaCash.
Password: Private information provided by the administrator. Enter it only in ImaCash.
Instance: the SQL Server instance supplied by the administrator, where used by the installation. It is not a company series or file path. Confirm the server and instance as one destination; this mode has no separate editable Port field.
Cash, cards and mixed payments
The connection reads the cash and card amounts received from the POS separately. A document containing both amounts produces two distinct movements; a zero amount produces no movement for that part.
With card acceptance disabled, ImaCash skips the part classified as card. Enabling it allows that part to be handled in ImaCash, but does not process or authorise a bank payment. The split depends on the data prepared by the provider: these two amounts do not establish credit, vouchers or other methods, or that a document is closed or paid. This mode does not use payment code lists like V2.
The workstations and salespeople supplied by this connection are generic. They do not identify the physical till or the person who made the sale. A filter can exclude all reads if these values do not match; do not use it to separate shops or staff without specific validation.
Private details and saving
Enter private details only in ImaCash with technical assistance. Preserve the valid configuration; opening and saving another selection may replace the legacy mode. Authentication must work under the Windows account running ImaCash.
Check the results
With the provider, compare existing cash, card, mixed-payment and refund documents: amounts, date and possible duplicate movements. Also check filters and installation scope. Do not perform real payments or refunds to test the configuration.
The connection reads data; it does not import products or write confirmations or rejections to the POS. A successful connection does not validate all sales, separation by workstation or salesperson, or a physical cash machine. Each installation requires technical review.
Review the legacy a3ERP TPV Táctil connection
This page documents the A3ERPTPVTactil mode used by existing installations. It uses Firebird and is distinct from A3ERPTPV base, Link, V2 and V3. A published page does not establish availability for a new installation.
Installation requirements
Confirm the POS version, its Firebird service and authorised read access with the provider. The administrator supplies the private server, port, database path, role and account. Do not reuse screenshot values or default accounts.
Preserve the existing mode
- Request technical assistance before opening the configuration to change or save it again, and preserve the working connection. This legacy mode is hidden in the current selector.
- Confirm the exact A3ERPTPVTactil mode with support. Do not select another a3ERP mode because its name looks similar; this guide does not provide a complete graphical setup process for new installations.
- Review the fields of the prepared configuration with the technician:
- Server IP: private name or address of the server running Firebird, supplied by the administrator.
- Ventas: Firebird database path as seen by the service server. This is not an exported sales file or a path to guess from the ImaCash PC.
- Server Port: actual Firebird service port confirmed by the administrator; no universal port is assumed.
- DB Name / Nombre de la BBDD: this mode uses the field as the Firebird role. It does not replace the Ventas path; the provider confirms whether a role applies and which one.
- User: private account with the read permissions required by the POS exchange.
Password: Private information provided by the administrator. Enter it only in ImaCash.
Private settings and saving
Enter private settings only in ImaCash with technical assistance. Preserve the valid configuration; opening and saving another selection may replace the legacy mode. Do not test combinations of database, role or account, or change server permissions using this page.
Check reading
Compare previously recorded operations with the provider: date, cash amount and terminal. The connector reads only movements for the payment method expected by its exchange; these fields do not select an arbitrary payment code. Confirm terminals and vendors and validate filters against known data before using them.
Reading does not include card amounts, import products or write confirmations or rejections to the POS. A successful connection does not establish that all sales are read or physically validate a cash machine. The provider must review continuity for each installation.
Prepare TPV Link with ImaCash
This page covers the Link mode in the a3ERP environment. ImaCash reads the cash amounts provided by the exchange prepared by Link, together with terminals and salespeople. It is not equivalent to the other a3ERP modes.
Installation requirements
The provider must prepare the cash exchange compatible with ImaCash and read access to SQL Server. Installing TPV Link does not prove that this exchange is ready. Obtain the private server, database, instance and authorised account details.
Confirm the mode
- For a new installation, ask the provider or support to prepare the Link mode before changing ImaCash configuration. On configured systems, retain the existing connection.
- Confirm A3ERPTPVLink mode and the available exchange with the provider. Do not replace it with base A3ERPTPV, V2 or V3 based on a similar name. Preparation requires technical assistance; this page alone does not provide a complete Link setup workflow.
- In the Link configuration prepared for your installation, review these fields with the administrator:
- Server IP: private SQL Server name or address supplied by the administrator.
- DB Name: exact name of the company database prepared by the provider for the Link exchange.
- Instance Name: actual SQL Server instance, where used. Do not add the instance twice to the server or use it instead of the database name.
- User: private SQL account with the required read permissions for the cash exchange, terminals and salespeople.
Password: Private information provided by the administrator. Enter it only in ImaCash.
Private details and configuration changes
Enter private details only in ImaCash as part of the confirmed technical preparation. Keep an existing installation’s working configuration and request assistance before opening it to change or save it again. Do not empty the database field or save another mode to try to enable Link.
Check the readings
With the provider, check terminals and salespeople and apply appropriate filters. Compare already recorded transactions with the POS: date, cash amount and terminal. Check cash refunds reported by Link, retaining their sign. A successful SQL connection alone does not prove that the expected sales are being read.
This mode reads cash; it does not include card amounts through this exchange, import products or write confirmations or rejections to the POS. Preparation and full validation depend on each installation; universal compatibility and physical machine validation are not claimed.