Middleware Integration Connector - Storyous REST API to Pohoda mServer (XML)

Project Title: Middleware Integration Connector - Storyous REST API to Pohoda mServer (XML)

Overview:
We require an automated integration bridge (a custom middleware script, cloud function, or Make.com scenario) to synchronize daily sales data from the Storyous POS system into Pohoda SQL accounting software via Pohoda mServer.

Technical Architecture:

Source System: Storyous POS System (REST API). API access is activated, credentials (ClientID, Secret, MerchantID, PlaceID) are available.

Target System: Pohoda SQL running on cloud hosting (iPodnik). Pohoda mServer is configured and exposed via HTTPS with basic authorization.

Goal: Automatically retrieve daily sales, receipts, and Z-reports from Storyous REST API, transform the data into Pohoda-compliant XML format, and send it to Pohoda mServer for accounting entry.

Detailed Functional Requirements:

Data Extraction (Storyous API):

Periodically (e.g., daily cron job or scheduled execution) connect to Storyous REST API.

Fetch closed sales transactions, cash receipts, and Z-reports for specified date ranges.

Maintain execution logs and state tracking to prevent duplicate postings in Pohoda.

Data Transformation & Mapping:

Convert Storyous JSON response data into Pohoda XML schema (creating Prodejky / Cash Receipts or Vydané faktury).

Map VAT rates accurately according to Czech tax legislation (standard 21% and reduced 12% rates).

Map payment methods correctly (e.g., Cash to Pokladna, Credit Card payments to terminal/bank settlement clearing accounts).

Map Cost Center / Outlet (Středisko) in Pohoda dynamically based on Storyous PlaceID / venue location.

Map document numbering series (Číselná řada) and company details (IČO).

Multi-client / Multi-tenant Architecture:

The system must support multiple clients/companies dynamically.

Configuration for each client (API keys, IČO, mServer credentials, VAT rates, accounts, Středisko) must be stored in a config file or database.

Data Ingestion (Pohoda mServer):

Send HTTP/HTTPS POST requests containing generated XML payloads to Pohoda mServer endpoint.

Authenticate using mServer login and password.

Parse mServer XML response to confirm successful import or capture error details.

Error Handling & Monitoring:

Implement error logging (e.g., email alert, log file, or notification) in case mServer is temporarily unreachable or returns validation errors.

Provide an option to manually trigger data re-synchronization for a specific date or date range.

Deliverables:

Complete, documented integration connector (Python, Node.js, PHP, or Make.com scenario).

External configuration structure for multi-client setup.

Brief deployment guide and testing instructions