Money S4/S5¶
Bring your customers and received orders from the Money S4/S5 ERP into the Daktela CRM, so agents know who is calling and what they ordered β without opening Money.
What it does and when to use it¶
The Money S4/S5 integration regularly imports data from your Money installation into a Daktela CRM database:
- Companies (Firmy) become Daktela CRM accounts.
- Persons (Osoby) become Daktela CRM contacts, each linked to its company.
- Received orders (PΕijatΓ© objednΓ‘vky) become Daktela CRM records of a record type you choose (Order pairing).
Data flows one way, from Money to Daktela. Money stays your master record; Daktela keeps an up-to-date copy that agents work with.
Typical use cases
- Recognise customers. An incoming call, e-mail or chat is matched to the synced contact, so the agent sees the customer's name and company right away.
- Answer order questions. When a customer asks about an order, the agent finds it among the customer's CRM records in Daktela, without asking the back office.
- Give agents context. Agents see the company and order details you choose β company ID, address, order number β in Daktela's CRM.
- Keep one source of truth. Your team keeps working in Money; changes reach the contact centre automatically within half an hour.
Tip
Daktela offers similar integrations for other accounting and ERP systems, for example Pohoda and Helios Green. See CRM Synchronisation Integrations for the full list.
Prerequisites and setup¶
Prerequisites¶
- In Money: the Money S5 API set up for your installation and reachable from the internet over HTTPS, and an API client (Client ID and Client secret) whose role can read companies, persons and received orders. The first API setup is done by your Money implementer β if Daktela is your first API integration, ask them to set it up.
- In Daktela: an administrator account with access to Settings β Integrations, and a CRM database to import the data into.
- Optional: a CRM record type in Daktela, if you want to import received orders.
Step 1: Get the Money API details¶
Ask your Money implementer or administrator for:
- the base URL of your Money S5 API β you'll enter it as Instance URI;
- a Client ID and Client secret for Daktela (in Money S5 these are generated in the API settings, under API keys).
Make sure the API is reachable from the internet, not only from your internal network β Daktela connects to it from the cloud.
Step 2: Connect Money in Daktela¶
- In Daktela, go to Settings β Integrations and click Configure under MoneyS4/S5.
-
Fill in the connection form:
Field What to enter CRM Database The Daktela CRM database the Money data is imported into. CRM Record type Optional. The record type used for received orders imported through Order pairing. Instance URI The base URL of your Money S5 API, starting with https://(orhttp://).Client ID The Client ID from Step 1. Client secret The Client secret from Step 1. -
Click Authorize. Daktela checks that Money issues an access token for these credentials.
Step 3: Pair the fields¶
-
A list of your Daktela CRM fields opens. Under Contact pairing, choose the Money field that fills each Daktela contact field (from persons) and each account field (from companies). Under Order pairing, do the same for CRM record fields (from received orders).

-
Click Activate.
The first synchronisation runs within 30 minutes.
Technical details¶
| Topic | Behaviour |
|---|---|
| Direction | One-way, Money β Daktela. Nothing is written back to Money. |
| Connection | Daktela passes the credentials to the Daktela integration service, which calls the Money S5 API on its behalf. The API must be reachable from the internet; the service waits up to 10 seconds to connect and 60 seconds for each answer. |
| Authentication | OAuth 2.0 client credentials: the service gets an access token from <Instance URI>/connect/token (scope S5Api), stores it and requests a new one when Money rejects it as expired. |
| API | The GraphQL endpoint <Instance URI>/graphql. The available queries and fields are read from <Instance URI>/graphql/schema. Your Money version must offer paginated queries for persons (Person), companies (Company) and received orders (ReceivedOrder); if it doesn't, loading the field pairing or the sync fails with an error saying so. |
| Schedule | Every 30 minutes. |
| Incremental sync | Each run asks only for records whose modification date (Modify_Date) is later than the previous run; for persons, the creation date (Create_Date) is checked as well. The time is sent in UTC (from version 33.8.0). The first run imports all records. |
| Batch size | Records are fetched in pages of 100, ordered by Money ID. |
| Order of entities | Companies (accounts) first, then persons (contacts), then received orders β so a contact can always link to its company. |
| Not supported | Other Money documents (invoices, issued orders, β¦). Records deleted in Money are not deleted in Daktela. |
| Multiple configurations | You can connect more than one Money installation, or import into more than one CRM database. Each configuration has its own tile, titled with its Instance URI. |
How records are matched¶
- Every imported contact, account and record gets the Daktela unique name
<configuration ID>_<Money ID>. Daktela remembers this pairing, so later changes in Money update the same Daktela record instead of creating a duplicate. - The Money
IDis always paired automatically to the unique name, andNazevto the title of contacts and accounts; received orders always get their document number (CisloDokladu) as the title. All other fields follow your pairing from Step 3. - Contact β company: a person is linked to the company in its
Parent_IDfield. - Received orders are always imported with the Daktela stage
OPEN. Pair the order's customer to the record's Contact field (and its company to Account) to link them. If an order ends up without a contact and has a phone number, Daktela looks for an existing contact with the same phone number or e-mail and links the order to it. If the order has no phone number or no contact matches, Daktela creates a new contact from the order's data. - Field list: the pairing list offers every field of the Money object, including fields of linked objects up to three levels deep, flattened with an underscore (
<object>_<field>). - If you delete an imported record in Daktela, the next run does not recreate it; it reports it as an error instead.
Test run and complete sync¶
- Test run (from version 30.0.0): once the integration is active, open its configuration and click Test Run. Daktela imports the first five records of each paired entity right away, so you can check the pairing without waiting for the scheduled run.
- Complete sync: when you edit an active configuration, the option Complete sync makes the next run re-import every record, not just the changes β useful after you change the field pairing.
Sync errors¶
If a run fails β Money can't be reached, it rejects the credentials, or some records can't be saved β the Money tile in Settings β Integrations shows a warning. Open it to download an error file (CSV) listing each failed record with its title, unique name, entity type and the reason. When the connection fails, administrators also get an e-mail notification β once, until a later run connects again.

Common messages from the integration service:
| Message | What to check |
|---|---|
| Money ERP connection failed / timed out | The API isn't reachable from the internet at Instance URI, or it answers too slowly. |
| Money ERP authentication failed | The Client ID or Client secret is wrong, or the API client was removed. |
| Money ERP returned an API error; check the query, mapped fields and API user permissions | The API client's role can't read one of the paired objects or fields. |
| Money ERP mapped field is absent from the GraphQL schema | A field you paired no longer exists in your Money version β pair a different field. |
| Money ERP GraphQL schema does not expose a paginated β¦ query | Your Money version doesn't offer the query Daktela needs β ask your Money implementer about an update. |