[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"site:en":3,"case:en:custom-billing-ksef-integration":109,"seo:en:\u002Fen\u002Fcase-studies\u002Fcustom-billing-ksef-integration":29},{"locale":4,"settings":5,"services":30,"hasBlog":38},"en",{"company":6,"contact":20,"social":24,"analytics":27,"seo":28},{"name":7,"legalName":7,"url":8,"nip":9,"krs":10,"address":11,"brand":16,"regon":17,"registryCourt":18,"shareCapital":19},"Softwaresystem sp. z o.o.","https:\u002F\u002Fsoftwaresystem.pl","7532454521","0000807293",{"street":12,"postalCode":13,"city":14,"country":15},"Obrońców Tobruku 5\u002F203A","48-300","Nysa","Polska","SoftwareSystem","","VIII Wydział Gospodarczy Krajowego Rejestru Sądowego w Opolu","5 000 zł (wniesiony w całości)",{"email":21,"phone":22,"meetingUrl":23,"hours":17},"kontakt@softwaresystem.pl","+48 726 456 455","https:\u002F\u002Fapp.simplymeet.me\u002Fsoftwaresystem",{"linkedin":25,"facebook":26,"github":17},"https:\u002F\u002Fpl.linkedin.com\u002Fcompany\u002Fsoftwaresystempl","https:\u002F\u002Fwww.facebook.com\u002Fsoftwaresystempl\u002F",{"gtmId":17},{"ogImage":29},null,[31,39,46,53,60,66,73,78,84,90,97,103],{"key":32,"slug":32,"slugs":33,"title":35,"excerpt":36,"icon":37,"featured":38},"web-apps",{"pl":34,"en":32},"aplikacje-webowe","Web apps","Internal panels, B2B portals and operational tools in the browser, built around your processes.","web",true,{"key":40,"slug":40,"slugs":41,"title":43,"excerpt":44,"icon":45,"featured":38},"custom-software",{"pl":42,"en":40},"dedykowane-oprogramowanie","Custom software","Software written for how your company works when ready-made tools fall short. You own the code.","code",{"key":47,"slug":47,"slugs":48,"title":50,"excerpt":51,"icon":52,"featured":38},"erp-crm-hrm",{"pl":49,"en":47},"systemy-erp-crm-hrm","ERP, CRM and HRM systems","Sales, stock, customers and HR in one system: a ready-made ERP (e.g. WAPRO) or custom modules.","systems",{"key":54,"slug":54,"slugs":55,"title":57,"excerpt":58,"icon":59,"featured":38},"websites",{"pl":56,"en":54},"strony-www","Company websites and web platforms","Fast company websites with a content panel, SEO and contact forms.","globe",{"key":61,"slug":61,"slugs":62,"title":64,"excerpt":65,"icon":61,"featured":38},"cloud",{"pl":63,"en":61},"chmura-i-infrastruktura","Cloud and infrastructure","Servers in the cloud or on premises, with backups, monitoring and predictable costs.",{"key":67,"slug":67,"slugs":68,"title":70,"excerpt":71,"icon":72,"featured":38},"server-admin",{"pl":69,"en":67},"administracja-serwerami","Server administration","Linux and Windows servers: updates, backups, monitoring, security and incident response.","server",{"key":74,"slug":74,"slugs":75,"title":76,"excerpt":77,"icon":74,"featured":38},"devops",{"pl":74,"en":74},"DevOps and CI\u002FCD","Automated builds, tests and deployments, with a quick rollback to the previous version.",{"key":79,"slug":79,"slugs":80,"title":82,"excerpt":83,"icon":79,"featured":38},"ai",{"pl":81,"en":79},"ai-dla-firm","AI for business","Language models for specific tasks: enquiries, documents, reports. With control over your data.",{"key":85,"slug":85,"slugs":86,"title":88,"excerpt":89,"icon":85,"featured":38},"automation",{"pl":87,"en":85},"automatyzacja-procesow","Process automation","Repetitive tasks turned into automatic workflows, usually in n8n.",{"key":91,"slug":91,"slugs":92,"title":94,"excerpt":95,"icon":96,"featured":38},"integrations",{"pl":93,"en":91},"integracje-api","API integrations","We connect ERP (e.g. WAPRO), KSeF, online shops, couriers, payments and CRM so data is not retyped.","api",{"key":98,"slug":98,"slugs":99,"title":101,"excerpt":102,"icon":98,"featured":38},"architecture",{"pl":100,"en":98},"architektura-oprogramowania","Software architecture","A plan for a system before coding, or a clean-up of one that grew without a plan.",{"key":104,"slug":104,"slugs":105,"title":107,"excerpt":108,"icon":104,"featured":38},"maintenance",{"pl":106,"en":104},"utrzymanie-systemow","Maintenance and development","Updates, backups, monitoring, fixes and new features after launch. We also take over other teams' systems.",{"item":110},{"key":111,"slug":112,"slugs":113,"title":115,"excerpt":116,"client":117,"industry":118,"year":29,"tags":119,"metrics":124,"cover":29,"visibility":134,"visibilityType":135,"featured":136,"problem":137,"result":138,"body":139,"seo":185,"related":186},"services-billing-ksef","custom-billing-ksef-integration",{"pl":114,"en":112},"integracja-billing-ksef","Billing integration with KSeF","Dedicated integration of a custom billing system with Poland's National e-Invoice System – submission, statuses, and UPO in one flow.","Client: B2B services company, Poland (anonymous)","B2B services",[120,121,122,123],"KSeF","API integration","Billing","Node.js",[125,128,131],{"label":126,"value":127},"Invoice structure compliant with KSeF","FA(3)",{"label":129,"value":130},"Confirmations in the billing system","UPO",{"label":132,"value":133},"Invoice submission from billing to KSeF","Auto","Anonymous","anonymous",false,"The invoicing system worked well internally but had no layer for exchange with the National e-Invoice System.","The company kept its own invoicing system and added production-grade KSeF integration.",{"title":140,"description":141,"ogTitle":142,"ogDescription":143,"industry":118,"heroTitle":144,"heroLead":145,"clientLabel":117,"visibilityLabel":146,"challenge":147,"solution":158,"results":170,"visibilityType":135,"technologies":184},"Billing and KSeF integration – case study","Dedicated integration of a custom billing system with KSeF: FA(3) generation, submission, UPO receipt, and error handling.","Billing KSeF integration – SoftwareSystem","Case study: custom billing system integrated with KSeF for a B2B services company.","Invoices from billing reach KSeF without manual work","A services company with its own billing system – the KSeF mandate was approaching faster than accounting and IT processes could adapt.","Anonymous project (NDA)",{"badge":148,"title":149,"lead":137,"paragraphs":150,"bullets":154},"Challenge","Custom billing without ready-made KSeF integration",[151,152,153],"Invoices issued in custom billing required manual transfer to an intermediary tool or export to accounting before KSeF submission.","No automatic UPO and status receipt in the source system – accounting had to verify each invoice separately.","Changes to the FA(3) schema and KSeF requirements risked invoicing downtime without a dedicated integration layer.",[155,156,157],"Manual steps between billing and KSeF","No UPO in the source system","Error risk on bulk invoice submission",{"badge":159,"title":160,"lead":161,"paragraphs":162,"bullets":165},"Solution","Dedicated billing-to-KSeF integration layer","Mapping billing data to FA(3), submission via KSeF API, and status sync back to the system.",[163,164],"We designed an integration module mapping invoice entities from custom billing to FA(3) structure with pre-submission validation. Invoices reach KSeF directly from the billing process after approval.","The system receives UPO and statuses from KSeF, stores them on the invoice in billing, and handles retries on API errors. A job queue ensures idempotent submission and a full audit log for accounting.",[166,167,168,169],"Billing → FA(3) mapping with XSD validation","Invoice submission via KSeF API","UPO and status receipt into billing","Queue, retry, and audit log",{"badge":171,"title":172,"lead":138,"paragraphs":173,"bullets":176,"metrics":180},"Outcome","KSeF compliance without replacing billing",[174,175],"Accounting sees KSeF status and UPO on each invoice in billing – without switching between systems.","Invoice submission runs automatically after business approval, with exception handling in one panel.",[177,178,179],"One process from billing to UPO","Ready for FA(3) schema changes","Full submission audit trail",[181,182,183],{"label":126,"value":127},{"label":129,"value":130},{"label":132,"value":133},[120,121,122,123],{"title":140,"description":141,"ogTitle":142,"ogDescription":143,"ogImage":29,"noindex":136},[187,212,236],{"key":188,"slug":188,"slugs":189,"title":191,"excerpt":192,"client":193,"industry":194,"year":29,"tags":195,"metrics":200,"cover":29,"visibility":134,"visibilityType":135,"featured":38,"problem":210,"result":211},"erp-window-joinery",{"pl":190,"en":188},"erp-stolarka-okienna","ERP system for a window manufacturer","B2B portal: orders, contract preview, transport packages, lead-time forecasts, shipping claims, and shipment tracking.","Client: window joinery manufacturer, Poland (anonymous)","Window joinery",[196,197,198,199],"ERP","B2B portal","PostgreSQL","Shipping integrations",[201,204,207],{"label":202,"value":203},"Order, contract, and package view","360°",{"label":205,"value":206},"Shipment status monitoring","Live",{"label":208,"value":209},"Portal for the B2B partner network","1","Sales, production, and logistics used separate systems – end customers had no transparent status view.","One access point instead of calls and emails about order status.",{"key":213,"slug":214,"slugs":215,"title":217,"excerpt":218,"client":219,"industry":220,"year":29,"tags":221,"metrics":225,"cover":29,"visibility":134,"visibilityType":135,"featured":38,"problem":234,"result":235},"transport-routes-docs","transport-routes-shipping-docs",{"pl":216,"en":214},"analiza-tras-dokumenty-spedycyjne","Route analysis and international shipping docs","Route optimization, international shipping document generation, and fleet fuel consumption monitoring.","Client: transport company, Central Europe (anonymous)","Transport and freight",[222,223,198,224],"Route analysis","Shipping documents","Maps",[226,229,231],{"label":227,"value":228},"International shipment handling","Multi-country",{"label":230,"value":209},"Unified shipping document system",{"label":232,"value":233},"Route and fuel analysis access","24\u002F7","Dispatchers and drivers worked on spreadsheets and Word templates – every international shipment was a separate process.","Dispatchers plan routes in the system, documents are generated automatically.",{"key":237,"slug":238,"slugs":239,"title":241,"excerpt":242,"client":243,"industry":244,"year":29,"tags":245,"metrics":250,"cover":29,"visibility":134,"visibilityType":135,"featured":38,"problem":258,"result":259},"energy-telemetry","energy-telemetry-predictive-maintenance",{"pl":240,"en":238},"telemetria-i-predykcja-awarii","Telemetry and network failure prediction","Collection and analysis of district heating line telemetry, operational reports, and early failure detection models.","Client: district heating network operator, Poland (anonymous)","District heating",[246,247,248,249],"Telemetry","IoT","Analytics","Failure prediction",[251,253,256],{"label":252,"value":233},"District heating line data collection",{"label":254,"value":255},"Measurement points in the network","100+",{"label":257,"value":209},"Reports and alerts dashboard","Sensor data landed in separate tools – no unified view of district heating line status.","Operators see anomalies before customers report problems."]