Product descriptions

zapAnalytics

Effective from January 28, 2025

zapAnalytics is a web application for analyzing ERP data. The software can be operated within a company’s internal intranet without internet access, ensuring that data remains at the site where the software is running. The business logic and analyses are provided by zapliance as a content bundle (.zip) and uploaded into the software (Analytics as a Service).

The core functions of zapAnalytics are:

1. Data extraction from ERP systems (“Download Plan”),
2. Data processing using predefined analyses (“Processing Plan”),
3. Preparation of results for the evaluation of the data and integration into third-party software (“Result Plan”).

Both one-time analyses and periodically automatically recurring processing runs (Continuous Control Monitoring) of data extraction, processing, and forwarding can be performed.

zapAnalytics Features:

• Web application
  
  • A central installation that can be hosted either on-premises or in the cloud.
  • Deployment as a Docker container is possible
  • Multilingual support: German and English
• Management of:
  
  • Projects:
    
    • Projects organize and control data extraction, processing, and preparation.
    • Projects are managed within an organization and provided through a “Content Bundle” (see Content Bundle).
  • Databases:
    
    • The zapAnalytics database stores data on data extraction, processing, and forwarding.
    • For the creation of a project, existing zapAnalytics databases or a new database can be selected.
    • Users can store the connection data for this database in zapAnalytics.
    • Databases can be password-protected.
    • Database connections can be encrypted.
    • Supported databases: PostgreSQL
  • Connection data to ERP systems:
    
    • For data extraction, saved connection data can be selected, or new connection data can be created.
    • An SAP data extraction occurs either via the SAP message server or application server using RFC (Remote Function Call).
  • Download Plans:
    
    • Download plans define the data scope to be extracted from ERP systems. 
    • The scope definition is done in consultation with zapliance. Download plans are created by zapliance and provided specifically for the customer in a Content Bundle.
  • Processing Plans:
    
    • Processing plans determine the automated processing of extracted data in zapAnalytics according to the agreed product.
    • Processing plans are created by zapliance and provided specifically for the customer in a Content Bundle.
  • Result Plans:
    
    • Result plans define the output format of the project results. 
    • Typical output formats include CSV, Excel, database files, REST API, pbix, pbit, or interfaces to external tools like Microsoft SharePoint.
    • Result plans are created by zapliance and provided specifically for the customer in a Content Bundle.
    • The results of result plans are made available via zapAnalytics, for example, through web download, database access, or interface.
• Content Bundles:
  
  • • A content bundle consists of a set of Download, Processing, and Result Plans, as well as a project template, an organization template, and all necessary licenses.
    • A content bundle (typically a .zip file) is provided by zapliance and can be uploaded by the customer into zapAnalytics. The project features become available to the customer, subject to project activation.
• Security:
  
  • A role/permissions concept is integrated into the application, allowing for controlled access.
  • Password-protected installation
  • Encrypted system database
  • Project database with password encryption

License Conditions for zapAnalytics Solutions:

The customer acquires a Response Key voucher for the creation and use of a customized project or Continuous Service in zapAnalytics, with the following license components:

• Project Type: The project type determines whether a project in zapAnalytics is a one-off project or a continuous service.
  
  • One-off projects enable the customer to extract data once, process data once, and generate a result once.
  • Continuous Services enable the customer to extract, process, and generate results multiple times.
• Service Start or End Date: The service period regulates when projects can be processed. If the offer includes a restriction on the service date, this restriction applies to the specified period.
• Service Period: In Continuous Service mode, the service period defines the subscription and billing period during which continuous services can be processed. The service period automatically extends for another term unless terminated in writing.
• Minimum Duration: If a minimum duration is defined in the offer, termination is only possible at the end of this period. The service period is effective from the service start date.
• Content Bundles: Content bundles include contractually agreed licensing conditions and define the Download Plan, Processing Plan, and Result Plan. If the customer-specific offer does not include specific plans, the details of the specified content bundle apply.
  
  • Download Plan: If the offer restricts download plans, the data scope applies to the agreed-upon download plans of our offer (e.g. company codes, fiscal years).
  • Processing Plan: If the offer restricts processing plans, the scope applies to the agreed-upon processing plans of our offer.
  • Result Plan: If the offer restricts result plans, the scope applies to the agreed-upon result plans of our offer.
• Content Bundle Update: The number of content bundle updates determines the maximum number of content bundles configured specifically for the customer within a service period and delivered to the customer.
• SAP Clients: If the offer provides a restriction on clients, this restriction applies to the specified clients within an SAP system. The content bundle can either:
  
  • contain no restrictions for an SAP client.
  • contain a predefined response key for a customer-specified SAP client. Changing the SAP client within the project is not possible.
  • include a Response Key voucher. By specifying the SAP client in the zapAnalytics project, an activation-required Challenge Key is generated.
• SAP Company Codes: If the offer provides a restriction on company codes, this restriction applies to the specified company codes within an SAP client. The content bundle can either:
  
  • contain no restrictions for SAP company codes.
  • contain a predefined response key for customer-specific SAP company codes. Changing SAP company codes within the project is not possible.
  • include a Response Key voucher. By specifying SAP company codes in the zapAnalytics project, an activation-required Challenge Key is generated.
• Fiscal Years: If the offer provides a restriction on fiscal years, this restriction applies to the specified fiscal years within an SAP client. The content bundle can either:
  
  • contain no restrictions for SAP fiscal years.
  • contain a predefined response key for customer-specific SAP fiscal years. Changing SAP fiscal years within the project is not possible.
  • include a Response Key voucher. By specifying SAP fiscal years in the zapAnalytics project, an activation-required Challenge Key is generated.
• Frequency: In Continuous Service mode, the frequency regulates the intervals at which downloads, data processing, and result generation may be automatically executed via batch run. If the offer provides a frequency restriction, the listed frequency is considered the minimum.
• Continuous Control Monitoring Services: If the offer includes a restriction on continuous control monitoring services, a control subscription may be used for a maximum of the specified number of Continuous Control Monitoring Services.

If the content bundle contains Response Key vouchers, projects must be activated by the customer. During project processing, the customer receives a Challenge Key in the form of a weblink or QR code. The customer can redeem the acquired Response Key voucher either by visiting the weblink on the zapliance website or by contacting zapliance support. The generated response key unlocks full functionality by inputting it into the zapAnalytics project.

Cooperation Obligations:

General prerequisites for using zapAnalytics:

• Provision of a server or virtual machine (VM) with the specified hardware requirements.
• Administrator rights for installing zapAnalytics on a virtual machine or server.
• Installation, licensing, and granting user access to the necessary Microsoft Services to utilize the zapliance outputs.
• Use of a PostgreSQL database.
• The hardware used requires a network connection to the ERP system for the duration of data and document extraction.
• For licensing download plans, the following information must be made available to zapliance before data download: SAP client, SAP company codes, and fiscal years to be analyzed.
• The customer is responsible for security requirements and measures for operating the system. Security requirements for the server and system environment should meet the SAP data security standard.
• The principal ensures the logical and physical security of the IT infrastructure on which the digital products, the data generated by digital products, and/or zapAnalytics operates or where the digital products and data are transported or transferred. The principal is guided by their already applied measures concerning the SAP productive system.
• Additionally, the principal ensures the interface security between the SAP systems, zapAnalytics, and the web browser used for access. zapliance GmbH is not liable, subject to the provisions in section 7 of the General Terms and Conditions, for damages due to lack of access protection, lack of security measures, insufficient archiving, and lack of encryption of the customer’s data.
• Activation of Response Key vouchers requires an internet-enabled device.
• The principal ensures that (network) access to the customer’s SAP systems – or direct use of zapAnalytics on the customer’s systems – and possibly on an SAP test system (with up-to-date original data) is enabled for zapAnalytics. The principal is responsible and may take appropriate measures to prevent damage (e.g., virus infestation, system crash) due to access or software use on the customer’s systems.
• The principal is responsible for complying with all legal (especially data protection and labor law) regulations during software use, including the data protection officer and works council if necessary.

Hardware requirements for using zapAnalytics:

• Windows 64-bit operating system (e.g., Windows Server 2022)
• Modern multi-core processor (at least 8 cores)
• Scalable RAM with 64GB or more
• Scalable hard drive capacity from 1 TB with a read/write speed of at least 100 MB/s
• Uninterrupted availability during the processing of projects, including data , processing, and preparation

Additional requirements for the SAP data extraction:

• Availability and accessibility of the following SAP function modules:
  
  • RFC_READ_TABLE, BBP_RFC_READ_TABLE
• SAP user with access rights to the function modules
  
  • RFC_READ_TABLE
  • BBP_RFC_READ_TABLE
  • DDIF_FIELDINFO_GET
  • RFCPING
  • RFC_GET_FUNCTION_INTERFACE
  • SO_DOCUMENT_READ_API1
  • ALINK_RFC_TABLE_GET
  • STFC_CONNECTION
• SAP Library SAP-JCO 64bit (requires SUSER in the SAP Store)
• Network connection and shares to the SAP system
• Connection data to the SAP “Application Server” or “Message Server”
  
  • Message server (MSHOST)
    
    • Message server port
    • SAP system name (R3NAME)
    • Group of application servers
    • SAP Router String
    • Client
  • SAP Application Server
    
    • SAP System Number
    • SAP System Name (R3NAME)
    • Client
    • SAP Router String

Customer Success

1. Service period

The service period defines the timeframe during which services of Continuous Customer Success can be utilized. If the offer includes a restriction on the service period, this restriction applies to the specified timeframe. The service period mandatorily includes the onboarding period as well as the project period.

• 1.1 Onboarding Period: The onboarding period is defined as the timeframe between the service start date and the beginning of the first productive data extraction or data processing. If the onboarding period is intended to start before contract signing, the service start date will be adjusted at contract signing to the actual service start date. The actual pre-contractual service start date begins as soon as at least one of the following services is utilized: stakeholder onboarding, technical setup support, or confidentiality and DPA. These services must go beyond self-service. The project period remains constant, so the service end date will also be adjusted (Adjusted End Date).

• 1.2 Project Period: The project period is defined as the timeframe between the beginning of the first productive data extraction and project completion.

• 1.3 Project Completion: Project completion is the last day of the month in which the closing meeting with zapliance and at least the customer’s central project contact person takes place.

• 1.4 Closing Meeting: The closing meeting is the final meeting of the customer project. In addition to a retrospective and a preview, all outstanding liabilities are clarified finally in the closing meeting at the latest, so that any necessary final invoice can still be issued within the service period.

• 1.5 The service end date corresponds at least to the project completion, i.e., the project completion occurs temporally before the service end date. A postponement of the project completion extends the agreed service period by a chargeable (Additional Period) timeframe until project completion.

• 1.6 Remuneration for an Additional Period: The remuneration for an additional period describes the fixed cost rate per started month for the extension of Customer Success services between the earlier contractually agreed end date or an adjusted end date and the actual date of project completion.

2. Service Hours

The service hours regulate the daily period in which the customer can use Customer Success services. If the acquired Customer Success Plan or the offer includes a limitation on service hours, this restriction applies for the specified time. Saturdays, Sundays, and public holidays at the company’s headquarters are excluded from service hours.

If the customer wishes to utilize Customer Success Services outside of service hours, these will be billed separately according to the conditions of the additional Customer Success services.

3. Language

If the acquired Customer Success Plan or offer includes a language limitation, this restriction applies to all Customer Success Services. Should the customer wish to use additional languages, these will be billed separately according to the conditions of the additional Customer Success services.

4. Response Time

The response time refers to the period between reporting an issue or request by the customer and the first feedback from Customer Success to begin addressing the concern. The response time only applies to the agreed communication channels and is only valid within the defined service hours and period. If the acquired Customer Success Plan or the offer includes a response time restriction, this constraint serves as a guideline for all Customer Success services.

5. Personal Customer Success Specialist

If the acquired Customer Success Plan or the offer includes a personal Customer Success Specialist, you will receive your dedicated Customer Success staff member, available during the agreed service period and within service hours as a central contact person. We strive to have the same Customer Success Specialist available to you throughout the entire service period. We reserve the right to replace the Customer Success Specialist at our discretion.

6. Communication Channels

The communication channels define the optional Customer Success contact options for the customer. If the acquired Customer Success Plan or offer includes one of the following communication channel restrictions, this limitation applies to all Customer Success services:

• Email: Includes communication over the mailbox: support@zapliance.com and opening support requests in our Knowledge Base. Excluded from this restriction are explicitly offered or agreed meetings or workshops.
• Online-Meeting: Includes Email and also:
  
  • Individual Email of the Customer Success Specialist.
  • Arrangement of online meetings, e.g., via Microsoft Teams. The agreed response time applies as the minimum lead time for arranging online meetings.
  • Reachability by phone
  • Calendar link of the Customer Success Specialist for booking appointments,
  • Individual Microsoft Teams chat with the Customer Success Specialist.

• Phone and Chat: Includes Online-Meeting and additionally: 
  
  • Accessibility via phone.
  • Booking appointments through the Customer Success Specialist’s calendar link.
  • Individual Microsoft Teams chat with the Customer Success Specialist.

7. AI-Support

AI support means that online meetings and workshops are automatically transcribed and summarized by our AI assistant. The data is processed by a service provider on servers in Europe. If the acquired Customer Success Plan or offer includes one of the following AI support restrictions, this limitation applies to all Customer Success services:

• Inclusive: Subject to the data security interests of the customer or the individual interests of the participants of the customer, the customer agrees to AI support. If at least one participant of the customer does not wish for AI support in a meeting, the AI support will be stopped by us. For each commenced meeting hour, we will charge the additional effort incurred at a Customer Success hourly rate.

8. Updates

Our software is continuously developed. During the service period, all product updates and upgrades are provided. The installation of updates is not included. If the customer requires support for installing updates, this support will be invoiced separately at the Customer Success hourly rate.

9. Self-Service

Self-service means that Customer Success support is provided exclusively in electronic form, e.g., through Knowledge Base articles or via pdf or email. Customer-specific elaboration and responses are not part of self-service.

10. Technical Setup Support

Technical setup support means that Customer Success assists with the initial installation and updates of zapAnalytics. If the acquired Customer Success Plan or offer includes one of the following restrictions, the following applies:

• Self-Service: See self-service.
• Standard Setup: The standard setup is described in our Knowledge Base for each of our zapAnalytics solutions. Customer Success supports and guides all necessary steps to achieve the standard setup. If the customer requires further support, e.g., for individual cloud integrations, these are to be billed separately at the Customer Success hourly rate.
• Individual: Customer Success supports and guides all necessary steps to achieve the zapAnalytics setup tailored to the customer, supported by zapliance.

11. Stakeholder Onboarding

Stakeholder Onboarding assists with onboarding the necessary stakeholders. This includes SAP administrators, network administrators, IT infrastructure administrators, IT security, ESG, or compliance staff, data protection officers, or works councils. If the acquired Customer Success Plan or offer includes one of the following restrictions, the following applies:

• Self-Service: See self-service.
• X-20-min Meetings: Customer Success supports a maximum in the number of online meetings defined by x during stakeholder onboarding. Additional support in extra online meetings, or the requirement to fill out customer-specific questionnaires (or forms on web platforms) will be billed separately at the Customer Success hourly rate.
• Individual: Customer Success supports necessary stakeholder onboarding online meetings as well as the required customer-specific questionnaires.

12. Confidentiality and Data Processing Agreement

Depending on the customer-specific service, the necessity of a confidentiality agreement (NDA) or a data processing agreement (DPA) may arise. If the acquired Customer Success Plan or offer includes one of the following restrictions, the following applies:

• zapliance Standard: Based on zapliance standard documents, customer-specific adjustments that do not exceed one zapliance working hour including coordination and adjustment are part of the contractual agreements. Should the customer need further adjustments, these are to be charged separately at the zapliance Partner hourly rate.
• Individual: NDA and DA are agreed upon individually with no additional cost.

13. zapliance Access to Customer Systems

Depending on the customer-specific service, it may be necessary that zapliance team members gain access to customer systems. If the acquired Customer Success Plan or offer includes one of the following restrictions, the following applies:

• Additional: The setup, support of access, as well as the access by zapliance team members will be billed at the zapliance Professional hourly rate.
• Individual: The setup, support of accesses, as well as the access by zapliance team members, are part of the agreement.

14. Fast-Track Onboarding

Depending on the customer-specific service, it may be necessary to carry out the onboarding under time constraints. If the acquired Customer Success Plan or offer includes a time constraint, this constraint applies as the minimum onboarding period within the service period. Should the customer have the requirement to complete the onboarding in a shorter time with the help of Customer Success, zapliance charges 4 zapliance Customer Success hourly rates for each planned week by which the minimum onboarding period is accelerated.

15. Kick-Off Meeting

The kickoff meeting takes place after the conclusion of the contract and at the beginning of the onboarding period. The aim of the kick-off meeting is to coordinate the project process including status meetings, the project details including the analysis scope, as well as roles and responsibilities in the project. Customer Success prepares a summary and provides this summary to all participants. If the acquired Customer Success Plan or the offer includes a restriction for the number or duration of the kick-off meeting, this restriction applies. Additional kick-off meetings are billed at double the Customer Success hourly rate per meeting.

16. Status Meeting

Status meetings serve regular coordination during the project course. They provide an overview of the current progress, clarify open points, and identify potential challenges. Furthermore, the next steps are defined to ensure a smooth process. If the acquired Customer Success Plan or offer includes a restriction for the number or duration of status meetings, this restriction applies as the maximum frequency or length of the meeting. Additional status meetings are billed at the simple Customer Success hourly rate per meeting.

17. zapAnalytics Training

The zapAnalytics training empowers zapAnalytics users to independently use the features required for the acquired use case with zapAnalytics and PowerBI Desktop. If the acquired Customer Success Plan or offer includes one of the following restrictions, the following applies:

• Self-Service: See self-service.
• Standard Setup: The standard setup is described in our Knowledge Base for each of our zapAnalytics solutions. Customer Success supports and trains a key-user for all necessary steps to achieve the standard setup. Should the customer require further training, e.g., for individual cloud integrations, or own databases, these are to be billed separately at the Customer Success hourly rate.
• Individual: Customer Success trains all necessary steps to achieve the zapAnalytics setup tailored to the customer, supported by zapliance.

Current Customer Service Hourly Rates

The following hourly rates apply per commenced hour:

Customer Success: €150,-.

zapliance Professional: €250,-.

zapliance Manager: €350,-.

zapliance Partner: €500,-.

Continuous Customer Success (Subscription)

Workshops

Effective from March 10, 2025

zapliance conducts workshops in collaboration with the customer to convey the professional foundations and methods of the solutions based on the customer-specific data analysis results.

The prerequisites for conducting a workshop are:

• The purchase of a paid digital product,
• Reaching the project timeline,
• Providing access to the necessary data analysis results, e.g., transmitting PowerBI files (.pbix) to zapliance or setting up a Remote Desktop Protocol (RDP) for accessing the result files.

zapliance is entitled to subcontract the service after prior notification to the customer.

The delivery of the workshop service is specified based on the following parameters in the offer:

1. Scope of Service

The scope of service defines the number and duration of the sessions. zapliance reserves the right to change the date or time of the workshop at any time before the start of the workshop. If the purchased Customer Success Plan or the offer contains limitations on the number or duration of the workshop sessions, these limitations apply. Additional workshop sessions will be billed at double the zapliance partner hourly rate per session.

2. SAP Company Codes

If the offer provides a limitation on the company codes, this limitation applies to the specified number of company codes.

3. Number of Fiscal Years

If the offer provides a limitation on fiscal years, this limitation applies to the specified fiscal years in SAP.

4. Service Start or End Date (Service Period)

The service period regulates the timeframe during which workshop services can be utilized. If the offer includes a limitation on the service period, this limitation applies to the specified period. The service period of the workshops is an integral part of the service period of the Customer Success.

zapAudit

valid as of May 23, 2022

The zapAudit web application uses more than 150 audit indicators to analyze SAP data for profitability, accounting compliance, access protection, and process standardization. It automates data collection and data processing, taking into account methods of econometrics, statistics, and process mining. The analysis includes the reconstruction and evaluation of all business processes such as purchasing, sales, asset accounting, financial accounting, access authorizations, including separation of duties (SoD)) conflicts, superuser, and much more. All results are available via the interactive front-end in the browser for analysis by any number of users (zapAudit report) or can be exported as Excel (exports zapAudit report data). It is possible to evaluate and acknowledge the results directly in the software (Professional Judgement).

zapAudit Features

• Web application
  • • One central installation
    • Usable with any number of users
• User administration
  • • A role/authorization concept is integrated into the application so that access can be controlled.
• Project management

A zapAudit project analyzes exactly one company code for one fiscal year. It includes the FI data for exactly one fiscal year from one SAP company code on one SAP client. Change documents, asset data, master data, and other data from 1.5 to 2 years in the past are also taken into account for each project for the complete reconstruction of all business processes. A zapAudit project goes through the following phases:
• • Create master data
    • • In the master data, basic settings such as the name or the data source to be used for the project are defined.
  • Define data scope
    • • SAP company code and a fiscal year for the data pull are defined here.
      • The exact zapAudit data scope can be downloaded as Excel during project creation in the software (~120 SAP tables).
      • Review of the pseudonymization of personal data
  • Define SAP server connections
    • • Using the SAP connection data, zapAudit establishes a connection to the SAP server and is able to extract the relevant tables for the audit.
  • Data extraction
    • • During data extraction, zapAudit establishes a connection to the SAP server and performs a data print. This contains the necessary data for the audit.
  • Data Processing
    • • Data Preparation
      • Financial Process Mining (reconstruction of all business processes)
      • Indicators Audit (calculation of ~150 indicators)
      • The currently valid list of indicators can be found at: List of all zapAudit indicators
  • zapAudit Report (requires activation)
    • • Dashboards
      • Indicator Audit
      • Profile audit
      • Document Audit
      • Professional Judgement
      • Process visualization (process mining)
      • Real-Time Filter
      • Excel Export

License conditions

The Response Key to be purchased are specified in the offer according to the following parameters:

Performance Period: the performance period for the use of the software starts with your acceptance of the offer (the purchase of the digital product) and ends after the term formulated in the offer. During this period, zapAudit Response Keys can be used to activate zapAudit projects.

SAP clients: If the quotation specifies a limitation of clients, this limitation applies to the specified number of clients within an SAP system.

SAP company codes: If the offer includes a limitation of company codes, this limitation applies to the specified number of company codes within an SAP client.

Fiscal years: If the offer provides for a limitation of fiscal years, this limitation applies to the named fiscal years in SAP.

Number of users: unlimited.

Number of zapAudit projects: unlimited.

Data protection

For the analysis, all required data is copied from SAP and stored locally in the installation path. The SAP data does not leave the company.
zapliance GmbH has no access to the zapAudit installation or the data of the zapAudit projects.

Requirements for the use of zapAudit

General requirements for the use of  zapAudit

• Administrator rights to install zapAudit on a notebook or server
• An update of the SAP system / import of ABAP is not necessary
• No installation of a database is necessary
• All data is stored in a file database exclusively locally and remains in the company
• Data retrieval and processing can take several days, depending on the size of the data set
• The hardware used only requires a network connection to the SAP system for the duration of the data retrieval process

Additional requirements for the data migration phase

• Availability and accessibility of the following SAP function modules:
  • • RFC_READ_TABLE,
    • BBP_RFC_READ_TABLE
• SAP user with access rights to the function modules:
  • • RFC_READ_TABLE,
    • BBP_RFC_READ_TABLE
    • DDIF_FIELDINFO_GET
    • RFCPING
    • RFC_GET_FUNCTION_INTERFACE
• SAP library SAP-JCO 64bit (requires SUSER in SAP Store)
• Network connection and network shares to the SAP system
• Connection data to the SAP “Application Server” or “Message Server”
  • Message Server (MSHOST)
    • Message server port
    • SAP system name (R3NAME)
    • Application server group
    • SAP Router String
    • Client
  • SAP Application Server
    • SAP system number
    • SAP system name (R3NAME)
    • Client
    • SAP Router String
  • Hardware requirements for the computer:
    • Windows 64bit operating system (e.g. Windows 7, 8, 8.1, 10, 11)
    • Recommended main memory (RAM)
    • At least 32 GB for company codes/fiscal year up to 1 million BSEG entries
    • At least 64 GB for company codes/fiscal year up to 6 million BSEG entries
    • At least 128 GB for company codes/fiscal year with more than 6 million BSEG entries
    • Modern multi-core processor (i7 or comparable)
    • 1TB hard disk with at least 100 MB/s read and write speed performance
    • Optional: USB 3.0 or newer (when using an external SSD hard drive)

Prerequisites for the data processing phase

• • The hardware requirements differ depending on the amount of data. A high-performance system with the above hardware requirements is recommended for data extraction and processing.
  • The Customer shall ensure that (network) access to the Customer’s SAP systems – or the direct use of zap Audit on the Customer’s systems – and, if applicable, on an SAP test system (with updated original data stock) is enabled for zapAudit. The customer is responsible for and will, if necessary, take appropriate measures to ensure that no damage (virus attack, system crash, etc.) occurs as a result of accessing or using the software in the customer’s systems. Within the scope of the use of the software, the Customer shall be responsible for compliance with all statutory provisions (in particular data protection and labor law provisions) as well as for the involvement of the data protection officer and the works council, if required.
  • The data scope of the data print as well as the definition of which columns might contain personal data is predefined in zapAudit. The client is responsible for checking the data scope, including the columns marked for pseudonymization, and for verifying it in the software prior to the data extraction. zapAudit automatically fully pseudonymizes all columns that are defined as personal data in the preparation based on the “public key” of the asymmetric key pair that can be generated by the client. The “private key” generated by the client is not known to zapliance GmbH and is the sole responsibility of the client. De-pseudonymization of the data is not technically possible in zapAudit.

The Customer shall ensure the logical and physical security of the IT infrastructure on which the Digital Products, the data generated by the Digital Products and/or zapAudit are operated, or to which the Digital Products, the data generated by the Digital Products and/or zapAudit are transported or transferred. In addition, the client guarantees the interface security between the SAP systems, zapAudit as well as the web browser that is accessed. Subject to the provision in section 7 of the GTC, zapliance GmbH is not liable for damages due to lack of access protection, lack of security, lack of archiving, and lack of encryption of the client’s data

zapCash

valid as of November 20, 2022

The web application zapCash detects multiple recorded liabilities within an SAP client by artificial intelligence (hereafter “AI”). In this way, double payments within a group can be analyzed, found and reclaimed even across company boundaries. With the help of zapCash, the user checks whether a double-entry liability exists and evaluates the results of the check directly in the software (hereinafter “Professional Judgement”). The AI patterns and Professional Judgements are then transmitted to zapliance without the SAP data. The AI algorithms then estimate the likelihood of two liabilities being double-entered liabilities. This result is sent to the user for import and therefore continuously ensures optimal prioritization of potential duplicate payments.

zapCash Features

• Web application
  • • flexible installation variants local or server-based (cloud-ready)
• User administration
  • • A role/authorization concept is integrated in the application so that accesses can be controlled.
• Project management
  A zapCash project examines selected company codes within a specified SAP client and identifies potentially double-entered liabilities for selected fiscal years. A zapCash project goes through the following phases:

• Master data
  • • In the master data, basic settings such as the name, or the data source to be used for the project are defined.
• Data scope
  • • SAP company codes and the fiscal years to be evaluated are defined for the data deduction here.
    • The exact zapCash data scope can be downloaded as Excel during project creation in the software (~58 SAP tables).
    • Review of the pseudonymization of personal data
• SAP server connections
  • • Using the SAP connection data, zapCash connects to the SAP server and is able to extract the relevant tables for review.
• Data extraction
  • • During the data extraction process, zapCash connects to the SAP server and performs a data print. This contains the necessary data for the audit.
• Data Processing
  • • Data Preparation
    • Financial Processing & AI
    • Reporting
• zapCash Report (requires activation)
  • • Candidate List
      • The candidate list contains all potential double-entered liabilities
      • Filter function for individual prioritization
      • Overview of all ratings
      • Exporting the candidate list to Excel
    • Detailed analysis
      • Detailed information on a potential double-entered liability
      • Comment function (Professional Judgement)
    • Import/export (manual interface to zapliance GmbH)

License conditions

The Response Key vouchers to be purchased are specified in the offer according to the following parameters:

Performance Period: The performance period for using the software starts with your acceptance of the offer (the purchase of the digital product) and ends after the term formulated in the offer. During this period, zapCash projects can be activated.

SAP clients: If the offer specifies a limitation of clients, this limitation applies to the specified number of clients within an SAP system.

SAP company codes: If the offer includes a limitation of company codes, this limitation is valid for the mentioned number of company codes within one SAP client.

Fiscal years: If the offer provides for a limitation of fiscal years, this limitation applies to the named fiscal years in SAP.

Number of users: unlimited.

Number of zapCash projects: unlimited.

Cooperation obligations of the customer

• The AI is to learn the company-specific patterns. For this reason, the customer evaluates at least 100 potential hits for each activated zapCash project or the complete analysis result if it shows less than 100 hits. The documentation of the Professional Judgement should be done during the review in zapCash in order to fulfill the transmission obligation of the completed project in a timely manner.
• To use the AI, the customer submits the AI export to zapliance. The export essentially contains:
  • • the unique document numbers of the double entry, as well as the document type
    • the assessment made, including comments
    • the amount
    • various lists of criteria used by the AI.
    • statistical evaluations about the project
• The AI data transmitted to zapliance does not contain any personal data or data that allows third parties to draw conclusions about the customer’s identity. Before sending the KI export, the customer has the possibility to take a look at the data to be transmitted. An actual AI export of an actual customer is available at the following link as an example: Example Export zapCash
• The AI learns based on the ratings. To make the quality of the ratings verifiable by an independent reviewer or zapliance, the client documents the derivation of its ratings of the selected potential matches in detail according to the minimum requirements conveyed. An example of proper documentation is available at the following link: zapCash Documentation standards
• Information on quality assurance is provided by the customer. zapliance receives a right of inspection regarding the provided documents and AI exports.
• zapliance reviews the AI export with the aim of optimizing the AI and ensuring the quality of the evaluations. zapliance is entitled to request an appropriate sample as part of the quality review. For the selected sample, the customer provides zapliance with his documentation including copies of the original documents justifying the booking. The way of accessing the documentation will be determined during the training or in the joint kick-off. If the original documents contain personal data, the customer is responsible for compliance with data protection requirements.
• In order to optimize the AI, it is necessary in rare cases for zapliance to understand the customer’s individual accounting logic and to be able to reproduce it on the basis of concrete entries. The customer agrees to support zapliance in this process, e.g. within the scope of web conferences.

Data protection

zapliance has no access to the zapCash installation or the data of the zapCash projects.
In order to obtain better results and fewer so-called false positives, the AI also analyzes text fields and business partner details, among other things. The analysis, which is run locally on the customer’s computer, is performed without pseudonymization of data fields that could contain personal data. zapliance has no access to the customer’s computer.

Requirements for the use of  zapCash

General requirements for the use of zapCash

• Administrator rights to install zapCash on a notebook or server.
• An update of the SAP system / import of ABAP is not necessary
• No installation of a database necessary
• All data is stored in a file database exclusively locally and remains in the company
• Data retrieval and processing can take several days, depending on the size of the data set.
• The hardware used only requires a network connection to the SAP system for the duration of the data retrieval process.

Additional requirements for the data migration phase

• Availability and accessibility of the following SAP function modules:
  • • RFC_READ_TABLE,
    • BBP_RFC_READ_TABLE
• SAP user with access rights to the function modules
  • • RFC_READ_TABLE,
    • BBP_RFC_READ_TABLE
    • DDIF_FIELDINFO_GET
    • RFCPING
    • RFC_GET_FUNCTION_INTERFACE
• SAP library SAP-JCO 64bit (requires SUSER in SAP Store)
• Network connection and network shares to the SAP system
• Connection data to the SAP “Application Server” or “Message Server”
  • • Message server (MSHOST)
      • Message server port
      • SAP system name (R3NAME)
      • Application server group
      • SAP Router String
      • Client
• SAP application server
  • • SAP system number
    • SAP system name (R3NAME)
    • Client
    • SAP Router String
• Hardware requirements for the computer:
  • • Windows 64bit operating system (e.g. Windows 7, 8, 8.1, 10, 11)
    • At least 64GB RAM
    • Modern multi-core processor (i7 or comparable)
    • 1TB hard disk with at least 100 MB/s read and write speed performance
    • Optional: USB 3.0 or newer (if using an external SSD hard drive)

Prerequisites for the data processing phase

• • hardware requirements differ depending on the data volume. A high-performance system with the above-mentioned requirements is recommended for data extraction and processing.
  • The customer shall ensure that (network) access to the customer’s SAP systems – or direct use of zapCash on the customer’s systems – and, if necessary, on an SAP test system (with updated original data stock) is made possible for zapCash. The customer is responsible for and will, if necessary, take appropriate measures to ensure that no damage (virus attack, system crash, etc.) occurs as a result of accessing or using the software in the customer’s systems. Within the scope of the use of the software, the Customer shall be responsible for compliance with all statutory provisions (in particular data protection and labor law provisions) as well as for the involvement of the data protection officer
    • and the works council, if required.
    • The data scope of the data print as well as the definition of which columns could contain personal data is predefined in zapCash. The client is responsible for checking the data scope including the columns marked for pseudonymization and for verifying it in the software prior to the data extraction. zapCash automatically fully pseudonymizes all columns that are defined as personal data in the preparation on the basis of the “public key” of the asymmetric key pair that can be generated by the client. The “private key” generated by the client is not known to zapliance GmbH and is the sole responsibility of the client.

The client ensures the logical and physical security of the IT infrastructure on which the digital products, the data generated by the digital products and/or zapCash are operated, or to which the digital products, the data generated by the digital products and/or zapCash are transported or transferred. In addition, the client guarantees the interface security between the SAP systems, zapCash as well as the web browser that is accessed. Subject to the provision in section 7 of the GTC, zapliance GmbH is not liable for damages due to lack of access protection, lack of security, lack of archiving, and lack of encryption of the client’s data.

• • 1TB hard disk with at least 100 MB/s read and write speed performance