ImaCash integration

FactuSol

Set up the ImaCash FactuSol profile using the active Access file: ACE requirements, Sales field, password limitations and cash payment checks.

TeamSystem Factusol logo
Other

Set up FactuSol with ImaCash

TeamSystem Factusol is the current brand. FactuSol and FactuSol 2020 name two distinct ImaCash profiles; the year in the selector does not validate every later edition or cloud service. Ask the provider to confirm your installation’s edition and format. Configure the cash machine separately.

1. Prepare the Access file

The administrator must identify the active Access file for the correct company and financial year, accessible under the actual ImaCash Windows user. You need the Microsoft.ACE.OLEDB.12.0 provider with an architecture compatible with the installed application. The provider prepares access and sharing permissions, including any lock files Access may require. Do not use an old copy or assume that read-only file permission is sufficient.

2. Select the profile and complete Sales

Open Configuration > Integration and choose POS. In Sales, use the file picker to enter the full private path of the active database confirmed by the administrator. This is not an exchange folder, a DSN or a SQL connection using server, port and user.

Select FactuSol. If your installation requires FactuSol 2020, use its dedicated guide: the readers differ.

Access to protected files

Both profiles show Password, but their current connection does not use this field to open Access. Filling it in does not prove that a protected database can be opened. If the file requires a password, first confirm a supported method with support and the provider; retain protection and do not create unprotected copies to bypass it.

3. Save when closing

Close Configuration and confirm saving when prompted; follow any proposed restart when applicable. The check opens and closes Access, but does not validate the whole structure, complete reading or a payment. An empty list does not prove that no payments are pending.

4. Which payments are read

This profile reads payment records with a nonzero amount of the intended cash type, from the start of the selected day. The exact time does not limit the query. It has no payment method selector and does not validate cards. Confirm classification, signs and currency with the provider.

5. Limit the terminals

Local filters run after reading, but this profile supplies generic terminal, company and seller identifiers. Do not use them as validated separation of real terminals or sites; a terminal or seller list does not prove that each payment retains those details.

Confirmations and limits

Confirming or rejecting in ImaCash does not write a payment closure or cancellation in Factusol. Items, shifts and bank totals have no validated scope. Do not assume mixed payments, bank authorization, complete historical recovery or absence of duplicates.

6. Verify before commercial use

Arrange a supervised test with the provider comparing document reference and date, amount, sign, currency, terminal and outcome in Factusol, ImaCash and the machine. For FactuSol 2020, check both allowed and excluded terminals. If the outcome is uncertain, review both systems and actual cash with support before repeating, resynchronizing or restarting; do not change references or dates to repeat payments. This documentation review does not validate physical operation.

Historical ImaCash screenshot with empty access fields
Historical Spanish interface: FactuSol, Others category and Save button. Fields are empty; the current form uses POS and saves when closing.

View the other profile: FactuSol 2020

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.