Home

⌘K
  2. Home
  4. Docs
  6. Home
  8. Client Profile
  10. Visma Horizon

Visma Horizon

Purpose

Use the Visma Horizon page to configure the client’s Horizon integration in Resico ERP. This page controls whether Horizon is enabled, stores the API connection values, defines customer and product mappings, and links Resico POS and locations to Horizon EKA and order parameter values.

Roles involved

  • System administrator
  • Finance manager
  • Integration / support team

Preconditions

  • You need permission to edit Client profile.
  • The Horizon API URL, username and password must already be available.
  • Resico POS terminals, locations and any deposit or gift card products used in accounting should already exist.
  • If Horizon customer, EKA, cash register or location mapping is required, those values must already be available from Horizon.

Navigation path

Client profile → Visma Horizon

Step-by-step procedure

  1. Open Client profile → Visma Horizon.
  2. Enable the integration using Enable Horizon.
  3. In the API settings section, enter:
    • Horizon API URL
    • Horizon username
    • Horizon password
  4. In the Mapping settings section, select the main Horizon EKA code if Horizon customer values are available.
  5. Select the product used as Deposit if deposit transactions must be posted through Horizon.
  6. Review the gift card product mapping section. The page supports up to five gift card product links:
    • Giftcard (1)
    • Giftcard (2)
    • Giftcard (3)
    • Giftcard (4)
    • Giftcard (5)
  7. In the Resico POS → Horizon EKA mapping section, map each active Resico POS terminal to the corresponding Horizon EKA / cash register value.
  8. In the Resico location → Horizon order params section, review every active Resico location and complete:
    • The Horizon order parameter text field
    • The Horizon location code selection
  9. Click Save to apply the configuration.
  10. Use Cancel to leave the page without saving.
  11. If needed, use See request log to review integration-related changes or request history.

Required fields

  • Horizon API URL
  • Horizon username
  • Horizon password

Additional required mappings when used in the client’s Horizon process:

  • Horizon EKA code
  • Deposit product
  • Required Giftcard product links
  • POS to Horizon EKA mapping for each active POS
  • Location order parameter and Horizon location code mapping for each active location

Validation rules

  • Horizon API URL, username and password must match the target Horizon environment.
  • The Deposit and Giftcard selectors use product search fields and should point to valid Resico products.
  • Each active POS should be mapped to the correct Horizon EKA value when POS export is used.
  • Each active location should have the correct Horizon order parameter text and Horizon location code when location-specific export is used.
  • All dropdown mappings must use values available from the loaded Horizon lists.

Exceptions

  • Some mapping sections appear only when related Horizon data is available, such as Horizon customers, Horizon cash registers or Horizon locations.
  • The client may use fewer than five gift card product mappings.
  • The page stores mapping values only; the actual export behavior depends on the broader Horizon integration flow outside this page.

Common errors

  • Incorrect API URL, username or password prevents the Horizon integration from connecting.
  • The wrong deposit or gift card product is selected, causing incorrect accounting or export mapping.
  • A POS terminal is mapped to the wrong Horizon EKA value.
  • A location is mapped to the wrong Horizon code or order parameter, causing exported data to be routed incorrectly.
  • Users save the connection values but forget to complete the POS or location mapping sections.

Troubleshooting

  • If Horizon integration does not work, first verify the Horizon API URL, username and password.
  • If only POS-based exports fail, review the Resico POS → Horizon EKA mapping section.
  • If location-based exports fail, review the Resico location → Horizon order params section.
  • If gift card or deposit-related exports behave incorrectly, verify the selected product mappings.
  • Use See request log when available to review integration activity and troubleshooting history.

Questions / Gaps

  • The page clearly stores API values and mappings, but the exact export scenarios that use each mapping should be confirmed in the live tenant.
  • It should be confirmed whether all five gift card mapping slots are actively used in the client’s production process or only reserved for optional setups.
  • The exact structure and use of the free-text Horizon order parameter field should be validated with a real Horizon export example.