Mertens · Reference

    KYC that keeps up with every order.

    A business application between ERP and CRM for customer verification and explosives precursor records. People and agents share validated facts, with fresh checks when the order or applicable rules require them.

    See the rulesExplore the workflow
    Mertens

    One shared record between customer relationships and execution

    1. CRM

      Customer, contact and agreements

    2. APPSS

      Validated record, rules and permissions

    3. ERP

      Product, concentration and order

    The single version of the truth: source, verification time, validity and rule version accompany each relevant fact.

    Regulatory and business rules before release

    When selling explosives precursors, the product determines which statutory checks apply. Mertens connects those checks to the customer record and the order.

    Regulatory requirements

    Regulation (EU) 2019/1148 and the Dutch Explosives Precursors Act and its implementing rules. The Dutch Human Environment and Transport Inspectorate (ILT) supervises sales.

    Verification on sale · Article 8
    Where the sale of a restricted precursor triggers verification, check the representative’s identity and authority, the business details and whether the proposed use fits the business activity.
    Re-verification and records · Article 8
    Reuse a business verification only within one year and when the transaction does not differ significantly. Keep the required information for 18 months from the transaction. The NCTV explains Dutch record-keeping and re-verification.
    Suspicious transactions · Article 9
    Report a suspicious transaction or attempt within 24 hours of identifying it as suspicious.
    Customs checks on import
    Where applicable, imports are also subject to the checks in the Dutch Customs Handbook.

    Business rules in the order workflow

    The order from the ERP system and the customer record from the CRM determine which checks the workflow needs.

    Identify the checks for this order
    Check the product, concentration, customer type and intended use. Request the specific information needed when evidence expires or circumstances change.
    Hold the order until approval
    Release the order once all mandatory checks for that order are current and approved. An authorised member of staff reviews exceptions.
    Keep the decision traceable
    Record each check’s source, outcome, date and rule version against the order.

    Workflow model

    From ERP order to controlled release

    This workflow brings the order, the customer record and the business rules together.

    1. Retrieve the order and record

      The ERP supplies order and product data. The CRM supplies the customer details and existing verification.

    2. Apply the rules

      APPSS determines which checks apply. The record keeps the source, validity and rule version for each check.

    3. Release or hold the order

      The order can proceed once checks pass. Missing evidence puts it on hold for additional information or review.

    Workflow model for the case. DataInbox has separate inbox configurations for verification, transaction records and reporting.

    Ongoing customer verification

    An approved customer is no blank cheque for the next order.

    For explosives precursors, the checks depend on the product, concentration, customer type and intended use. The application brings that context together with the order and customer record. Existing information is reused only when the applicable rules and its validity permit it.

    1. At initial onboarding

      Establish the business, identity and authority to represent it where required. Record the intended use and supporting evidence. Distinguish registry facts, customer statements and the reviewer’s assessment.

    2. With a new order

      Check the order against the current record and applicable rules. Does the intended use fit the business activity? Have the product, quantity or contact changed? The outcome determines which additional verification or review is required.

    3. When fresh verification is due

      Agents can monitor deadlines and request updates when evidence expires or details change. NCTV guidance calls for annual checks and earlier verification after significant changes. Ask again only for the information that is needed.

    4. When rules or guidance change

      Agents can flag changes in official sources and identify affected records. An authorised colleague reviews the impact and approves a new rule version. Earlier decisions retain their sources, versions and verification times.

    The release requirement

    100% validated before release.

    For the order concerned, every applicable mandatory fact and check must be complete, current and supported by evidence. Release stays blocked while information or review is outstanding. The status applies to that order, time and rule version; the next order may require fresh checks.

    • Information required
    • Review required
    • Released

    This is the process requirement in this reference, rather than certification or a guarantee that every source is always accurate. Specific integrations and production configuration are established for each project.

    Agents prepare. People retain control.

    Shared facts for sales, operations and compliance.

    Agents help gather information, flag differences and prepare a message with specific questions. Colleagues see what is missing, who acts next and what supports a review. Approved rules govern release; an authorised person decides where required.

    Which record connects your systems?

    Start with one order and the checks your people carry out today. Turn that knowledge into the agreements for your own business application.

    Explore your applicationAll references