Artur K.

🚀 Excited to launch my latest project 👉 Zenix! After months of building bit by bit (and refactoring way too many times 😅), it’s finally ready with that extra layer of polish. Zenix is an end-to-end platform that simplifies Indian tax prep 👉 no more spreadsheet chaos, no more juggling PDFs. With this, I might just replace a few CAs (kidding… or am I? 😂). 🎥 Check out the full demo: edited entirely by yours truly. 🧩 Tech Stack Breakdown Frontend: React 18 + TypeScript SPA powered by Vite, styled with Chakra UI, Tailwind, and Material UI. Routing and state flow via React Router, context-based auth guards, toast notifications, Axios, Framer Motion for animations, Lucide/React Icons, and Recharts for analytics visualizations. Backend: Built with FastAPI (async routes) handling document ingestion, uploads, tax logic, and analytics. Uses Pydantic for configuration, centralized logging, and async SQLAlchemy for data access. Document intelligence routes PDFs/CSVs/XLS/images to processors (Form 16, payslips, or bank statements). There’s also a Node/Express sidecar with Multer + pdf-parse for auxiliary pipelines. AI Power: Landing AI drives extraction. OpenAI is used for insight generation, it composes regime-specific tax summaries, deductions, and spending recommendations from structured prompts. Database: PostgreSQL with async + sync engines, JSON fields, and models covering everything from assessment rollups to categorized transactions. Auth: bcrypt via Passlib, JWT-based tokens with strict verification, and multi-level route protection. (Still expanding on security because in finance, it’s everything.) 💡 Still a lot more to do, but I’m proud of how far it’s come. Would love to hear your thoughts, suggestions, or even your “CA panic” reactions 😄 #Zenix #TaxAutomation #FastAPI #React #OpenAI #LandingAI #FinTech #IndieDev #Python #TypeScript #Vite #AI #ProjectLaunch #DeveloperJourney #StartupLife

33

4 Comments

Below we present a few pieces of advice for those of you who are freelance developers, analysts, etc and are entering cooperation with a client based out of your own country e.g. Poland. It is in most cases a good deal but things don't look so great when the client 'forgets' to pay. This post is inspired by a true story.. and if you have experienced delayed (or no) payment situation and would like to share it in the comments - feel free to do so. You may help and warn others... 💸 The Payment Risk Trio You Must Mitigate: Late Payment: Many international clients operate on longer payment terms (e.g., 60 or 90 days), or may delay payments due to internal processes. This impacts your cash flow and financial stability in Poland. Non-Payment/Disputes: If a client refuses to pay, recovering the debt internationally can be slow, complex, and expensive, especially if the governing law is not Polish. Currency Fluctuations: If you are paid in EUR or USD, the exchange rate may drop significantly between invoicing and payment, reducing your income in PLN. ✅ Actionable Safeguards: Payment Terms: Negotiate strict, short payment terms (e.g., 7 or 14 days) and include a clear, high penalty interest for late payments. Upfront Payment/Milestones: For new clients, require a deposit or structure payments around small, easily defined milestones. Escrow/Insurance: Consider using an escrow service or securing credit insurance for large contracts to protect against non-payment. Crucial Step: Always have a Polish legal professional specializing in B2B and international contracts review the payment clauses before signing and - as they say on the planes- locate your nearest emergency exit...:-) In other words: don't wait too long to step out and if in need use a reliable international debt collection company.. #ITContractors #PolishIT #InternationalBusiness #PaymentRisk #B2B #Freelance #debtcollection

7

Poland Launches KSeF 2.0 API Pre-Production (Demo) Environment  On October 15, 2025, Poland’s Ministry of Finance released the KSeF 2.0 API pre-production (Demo) environment, enabling financial and accounting system providers to test their software in production-like conditions. Key Highlights:  Integration Opportunity: Test how financial and accounting systems interact with the KSeF 2.0 system before mandatory rollout.  Realistic Environment: Uses actual authentication data (e.g., Tax Identification Numbers) and ownership permissions, similar to production conditions.  Safe Testing: Issuing invoices in the pre-production environment has no legal consequences.  Technical Support: Available on business days, 7:00 a.m. – 7:00 p.m., via the Ministry of Finance form: https://lnkd.in/dx_6hgvq  Access Demo Environment: https://lnkd.in/eeu2-M4B  Mandatory Compliance Dates: All financial systems must comply with KSeF 2.0 from January 1, 2026.  This environment ensures compatibility, security, and readiness of financial systems for Poland’s mandatory e-invoicing requirements. Source / More Info: Ministry of Finance Announcement Visit our website: https://lnkd.in/eKbjCcmh #KSeF #PreProduction #Demo #Poland #MinistryofFinance #Eaglessoft #Ecompliance #Einvoice #API #FinanceTech #AccountingSoftware #Digitalization #Compliance #FinTech   

10

Is your automation framework smart enough to adapt when the unexpected happens? Modern QA is no longer about scripts and steps - it’s about intelligence and autonomy. According to Gartner, by 2026, over 45% of testing activities will involve AI or agentic assistance. That’s where Agentic E2E Test Frameworks come in. They redefine automation by enabling systems that can: - Identify issues in real-time - Self-heal test failures - Optimize coverage dynamically Join Doug Bowen and Alessandro De La Garza from Slalom at our 5th Houston Meetup to explore how these frameworks are changing enterprise testing forever. Learn what’s possible when AI becomes your testing co-pilot. 🗓 20th November | 📍 Improving Office RSVP 👉 https://luma.com/krw9o6v1 Thanks to Srijaya Suresh, Todd Deering, and Nhan N for driving this incredible session forward! #automation #aitesting #endtoendtesting #testingcommunity #thetesttribe

7

🚀 From #Warsaw Streets to Global Fintech Powerhouse: BLIK's Microservices Magic & Historic #IPO 🌍💳 In the heart of Warsaw, Poland, BLIK emerged in 2015 as a game-changer in mobile payments—think instant bank transfers via a simple 6-digit code in apps like PKO Bank Polski or Allegro. Backed by Poland's top 6 banks (PKO Bank Polski, mBank, Santander, etc.), it exploded to 18M+ users and 2B+ transactions by 2024, capturing 45% of Poland's e-commerce payments. No cards, no wallets—just seamless #P2P, #POS, and online magic. 🇵🇱✨ The #Tech Backbone: Microservices Mastery 🛠️ BLIK's secret sauce? A resilient microservices architecture on Kubernetes-orchestrated clouds (Microsoft Azure/Amazon Web Services (AWS) hybrid). Key innovations: - Real-time Processing: Kafka streams handle 10K+ TPS with <100ms latency, powered by Spring Boot APIs and OAuth 2.0/JWT security. - AI Fraud Shield: ML models (TensorFlow) detect anomalies in real-time, slashing fraud by 70%. - Scalable APIs: gRPC for inter-bank comms, enabling cross-border pilots in Czechia & Slovakia. This distributed design turned BLIK from a local hero into a €1.5B-valued beast—processing €50B+ annually. IPO Triumph: Nasdaq Exchange ,Warsaw Stock Exchange (GPW) Leap 📈💥 In Dec 2024, BLIK's parents @Polski Standard Płatności (PSP) IPO'd on Nasdaq Warsaw, raising PLN 300M+ at a 40x valuation surge. It wasn't luck—microservices enabled 99.99% uptime during Black Friday peaks, proving enterprise-grade scalability. Now eyeing EU expansion via PSD3 compliance. Global Traction Playbook 🌐 BLIK's model screams "export-ready": Imagine it in India’s UPI ecosystem or SEA's GrabPay. Lessons for #fintech builders: Prioritize #API-first design + bank consortia for hypergrowth. Who's integrating next? 🚀 What’s your take on BLIK's rise? Scaling microservices in #payments? Drop thoughts below! 👇 #Fintech #BLIK #IPO #Microservices #PaymentsInnovation #WarsawTech #Kafka #SpringBoot #FintechGlobal #SystemDesign

6

Recently, I was informed that Dom Development S.A., a major residential developer in Poland, suffered a cyberattack resulting in the unauthorized extraction of data from its IT systems. According to the official notification, my personal data may have been affected. What is particularly concerning is the breadth and sensitivity of the data categories involved. Based on the communication sent to impacted individuals, the potentially exposed data appears to include not only standard identification and contact details, but also PESEL, identity document data, bank account numbers, transaction history, financial information related to crediting, civil status, and health-related data. This represents a combination of high-risk personal data and special categories under GDPR. While the company states that it has complied with its obligations under Articles 33 and 34 of the GDPR, the timeline between the incident and direct communication to affected individuals highlights how critical incident detection, escalation, and transparent communication are as part of mature data governance. Timeliness in this context is not a formality, it is a core risk-mitigation control. An additional concern is the sequence of communication. In my case, I became aware of the incident through media reports and public social media discussions before receiving a direct notification from the company. From a data protection and incident response perspective, learning about a potential breach affecting one’s own data via third-party channels undermines trust and reinforces the need for prompt, direct, and prioritized communication with affected data subjects. From a risk management perspective, the response also raises questions about whether the remedial measures offered are proportionate to the potential impact of the breach. Beyond formal notifications and general guidance, there appears to be limited evidence of enhanced support, concrete remediation, or accountability measures that would meaningfully reduce downstream risk for data subjects. In incidents involving identifiers with long-term consequences, compliance alone may not be sufficient to restore trust. I am sharing this not to sensationalize a single incident, but to underline a broader point: organizations that process large volumes of sensitive personal and financial data must treat cybersecurity and data protection as core operational risks, not auxiliary IT concerns. Incident response maturity, realistic threat modeling, and timely communication are essential components of that responsibility. We should continue to expect high standards of accountability and transparency when it comes to the protection of personal data. Repeated exposure to such incidents erodes trust, even when formal compliance requirements are met. It is my understanding this case has already been notified to Urząd Ochrony Danych Osobowych and the DPA as always will keep up their good work of oversight and control Mirosław Wróblewski

10

Poland continues to stand out as a strategic location for financial services tech teams. Developer skill levels are high, costs are competitive, and global firms are scaling into major cities fast. According to HackerRank (https://bit.ly/44a88ET) Poland ranks third worldwide for developer capability. Hiring costs are up to 30% lower than in the US, and teams are delivering strong results across trading, risk, and analytics. What I’m hearing and seeing points to sustained growth and strategic value in Polish tech hubs. We published a report (see comments) that backs this up, looking at the tech ecosystem in Poland, investment trends, and what this means for engineering teams in finance.

8

1 Comment