Integration modes
Choose the mode that matches your installation. Confirm the connector and its requirements with the provider before changing the setup.
Configure BDP through a database
BDP mode uses SQL Server to read documents and payments. The person responsible for BDP must confirm the compatible schema and prepare a dedicated payment method for payments handled by ImaCash.
You need access to the SQL service from the ImaCash computer and a private account with permission to query the necessary data. This mode uses SQL authentication without an ODBC DSN. A successful connection alone does not validate the complete workflow or a compatible cash machine model.
Prepare the connection
- Open Settings > Integration, choose POS, select the BDP group and then BDP mode. BDP V2 and BDP V3 are previous names for this mode, not certified commercial versions.
- In Server IP, enter the private destination supplied by the administrator. Database name refers to the BDP SQL database. Obtain distinct server, instance and database details; do not use defaults from an old guide.
- Two fields may be labelled Database name: the one in the Instance position is used as the instance in the connection. Do not duplicate the database in both or repeat an instance already included in the server address. If a legacy configuration makes them unclear, confirm the assignment with the administrator or support.
- Fill in User and Password with the private SQL account supplied by the administrator. This connection has no separate port field or cash drawer identifier.
- Close Settings with changes pending and choose Save. After connection validation, review the filters offered and the Cash and Card dialogs when applicable. Review the final result; select Restart only if offered, when appropriate and with no operations in progress.
Scope and verification
Capture uses the amount of each supported payment line, preserving its sign. A sale with several payment methods may produce separate entries; the entire invoice is not automatically treated as cash. For cards, also review Accept cards: selecting a code does not demonstrate a bank card charge.
This SQL mode does not mark documents as paid or cancelled in BDP. Physical confirmation belongs to the cash machine controller. Confirm the selected workflow with the provider and check its outcome before treating the installation as validated.
BDP_Ficheros uses an exchange folder with read and write permissions. BDP Hotel uses its own SQL schema. Their requirements and confirmations differ; do not automatically apply this guide’s scope to them. BDPCash is a hidden historical mode, not a current option for a new setup.
Database payment methods
The person responsible for BDP must prepare a dedicated ImaCash payment method, separate from its Cash and Card methods. Use it in the POS for those payments: native BDP Cash may record the sale as paid without passing through ImaCash. The connector does not create this method automatically.
In the ImaCash Cash dialog, select the method prepared for ImaCash; if applicable, choose a different card method. Options come from FormasDePago: the description is displayed and the selected code is saved for capture.
If the list or an option is missing, review the configured database, FormasDePago catalogue and query permissions with the administrator. A missing dialog does not establish a correct selection. Saving without changes does not guarantee reopening the list; contact support if it does not reappear.
Cash inflows and outflows
Cash entries such as purchases must belong to supported concepts, use the selected cash method and have an employee assigned. They must pass the terminal and cashier filters. Inflows retain a positive sign and outflows a negative sign; a purchase label alone is insufficient, and another sale must not be created to repeat the movement.
Capture filters
In Settings > Filters, enable and save the terminal and cashier criteria required by this installation. Terminals and waiters are selected from their catalogues; no actual shop catalogue is discovered. Filters restrict the local pending view and do not guarantee exclusive SQL reading.
Configure BDP file exchange
BDP_Ficheros exchanges requests and responses through a folder prepared by the person responsible for BDP. This mode is separate from BDP SQL and BDP Hotel.
The provider must enable a compatible exchange. The accounts running BDP and ImaCash need access to the same folder and permission to read, create, write and manage exchange files. Use a dedicated folder, not documents, backups or unrelated data.
Prepare the connection
- Open Configuration > Integration, choose POS, select the BDP group and then BDP_Ficheros.
- In Sales, use the folder picker to select the exchange path confirmed by the BDP administrator. This field takes a folder, not an individual file. An existing or empty folder does not prove that BDP is sending requests.
- Check the “BDP version equal to or higher than 35.1.” option with the provider. Set it for the installed exchange: it changes how the response is published. The label does not establish a universal minimum version or commercial compatibility.
- Close Configuration with pending changes and choose Save. Review the result; use Restart only if offered, when appropriate and with no operations in progress. Saving does not replace permission checks or verification of the full exchange.
- Before live use, agree on a supervised test: check the received request, reference and amount including cents, physical outcome and response acknowledged by BDP. If any part is missing, the installation remains unvalidated.
Requests, responses and filters
The link uses the reference, amount, date, terminal and employee from the message. It treats a standard request as cash. It does not offer the SQL payment-method catalogue or independently validate card or mixed payments.
The response reports the outcome by reference, including cancellation and paid-in and returned amounts where applicable. Check that BDP receives and interprets it. A request or cancellation file does not prove that the machine has stopped or returned cash. If the outcome is pending or uncertain, review both systems and the actual cash before repeating, restarting or charging again.
Under Settings > Filters, check local installation criteria against the terminal and employee identifiers received. This mode does not discover SQL catalogues of terminals, employees or shops.
Do not configure a SQL server, username, password or DSN for this mode. The exchange does not import products or shifts. Files being present or a successful connection status do not validate the physical operation or correct completion in BDP.
Do not apply payment methods, cash movements or acknowledgements from BDP SQL, Hotel or other workflows to this guide. The provider must confirm the mode, installed version and specific workflow.
The following image is a historical screenshot in Spanish with an empty Sales field. It shows the former Hospitality label and Save button; the current path is POS > BDP > BDP_Ficheros and saving is confirmed when Configuration closes.
Configure BDP Hotel
BDP Hotel uses its own SQL Server schema. The BDP administrator must confirm the installed mode, compatible structure and payment methods before preparing the ImaCash link.
The computer and account running ImaCash need access to the SQL service and a private SQL account with permission to read invoices, payment methods, cash registers and employees. This mode does not use an exchange folder or an ODBC DSN.
Prepare the connection
- Open Configuration > Integration, choose POS, select the BDP group and then BDP Hotel.
- In Server IP, enter the private destination supplied by the administrator, separately from the instance name. This mode builds the destination from both fields; do not repeat the instance within the server value.
- In Database name, enter the Hotel catalogue confirmed by the administrator. In Instance name, enter the corresponding SQL instance. Do not reuse standard BDP settings because the brand is the same or assume default values.
- Enter the authorised private SQL account in Username and Password. This mode has no separate port field or Windows authentication selector.
- Close Configuration with pending changes and choose Save. After validating the connection, review filters and the Cash and Card dialogues when offered. Check the final result; use Restart only if offered, when appropriate and with no operations in progress.
Payments, invoices and limits
The Hotel payment catalogue is Formas_DePago, distinct from standard BDP FormasDePago. The dialogue displays the description and stores the selected code. Choose the actual cash method and, where applicable, a separate card method; also check Accept cards. Selecting a code does not prove a bank charge.
If the list or a method is missing, check the Hotel catalogue and read permissions with the administrator. An absent dialogue does not validate an earlier selection. Saving without changes does not guarantee that the options will be read again; contact support if they do not reappear.
The reader processes up to five positive payment positions on an invoice and stops at the first position without a positive amount. It uses each payment’s cash register and the invoice employee. It retains the invoice date, not the original payment time. Check invoices with several methods: arbitrary mixed-payment layouts and unconfigured methods are not guaranteed.
Under Settings > Filters, check the payment cash registers and employees received against active local criteria. Confirm name-to-code mappings with the BDP administrator. This mode does not discover a real shop catalogue, and enabling filters does not guarantee an exclusive SQL read.
Do not assume that Hotel supports standard BDP cash movements, purchases or negative refunds. The connector does not import products or shifts, or mark invoices as paid or cancelled in BDP. A local acknowledgement or successful connection proves neither those outcomes nor the machine’s physical operation.
Before live use, agree on a supervised test of reference, payment code, amount including cents, cash register, employee and filters; include cards and several methods where applicable. If an outcome is uncertain, check both systems and the actual cash before repeating or restarting. The provider must confirm the installed workflow.
BDP SQL and BDP_Ficheros are separate modes with their own requirements and acknowledgements. This Hotel guide does not certify compatible models, firmware or commercial versions.
BDPCash: reference for legacy installations
BDPCash is a historical mode that is not offered in the current ImaCash selector for new configurations. This page preserves the reference for earlier installations.
It is not another name for BDP over SQL Server, BDP Hotel or BDP_Ficheros. The old Cash/Lean names do not identify a current mode or establish compatibility with a supplier version.
If you already use BDPCash
- Check with the BDP administrator and ImaCash support which mode your installation uses and which configuration must be preserved.
- Do not replace BDPCash with BDP, BDP Hotel or BDP_Ficheros merely because their names are similar, or copy settings from an old guide.
- Before making a change, agree on requirements, payment methods and filters, and validate the complete workflow in a supervised test. A connection does not establish a payment or physical compatibility.
Server, database, instance and account details, where applicable, are private and supplied by the administrator.
Guides to the current modes
These guides describe different modes. Confirm with the supplier which one applies to your installation; they do not automatically convert a BDPCash installation.