Skip to content
AktwinsTrust. Transparency. Technology

Case study

Turning annual-report checks into a Beta platform Swedish firms can use

A proof of concept had already shown that Swedish K2 annual reports can be parsed and checked with deterministic rules. We were engaged to take that into a Beta SaaS: upload, validate, comment, revise — with secure access for accounting firms.

ClientA Sweden-based team building software for accounting firms that review K2 annual reports.

Gen AI & Product EngineeringAccounting

Gen AISaaSCompliance

Tech stack

  • AWS
  • Python
  • FastAPI
  • React
  • MySQL
  • LlamaParse
  • OpenAI
  • Stripe
All case studies

Swedish Annual Report QA views

Annual report validation workspace for Swedish K2 filings

The problem

The POC proved the checks. Firms still needed a product.

The proof of concept could extract figures from PDF annual reports, run rules such as equity ratio, tax allocation, personnel notes, revenue variance and rounding, and compare the current year with the previous one.

What it was not: a platform accounting staff could log into, collaborate on, version, and run as a service. Phase 1 is that Beta — K2 reports generated in Fortnox, readable or scanned PDFs, Swedish language, with English and Swedish in the product.

What we are building

A Beta SaaS around a deterministic validation engine

We are designing and building Phase 1 from the ground up, using what the POC already proved. UI and workflows first, then parsing, rules and integrations. The path is upload, classify, fetch last year, parse, validate, then review and approve.

  • 01

    Upload and classify the annual report

    • Fortnox-generated K2 PDFs in Phase 1, including scanned files through OCR
    • Tell the user when the file is K3, not Fortnox, or otherwise out of scope

  • 02

    Parse, then run deterministic rules

    • Twenty validation rules: financial, structural, compliance, notes, cross-year and page-level traceability
    • Prior-year figures from Bolagsverket open data where they exist, or a manual upload if they do not

  • 03

    Review, comment and revise together

    • Comparison of current and previous year, notes per finding, resolve and reopen, report-level status
    • Re-uploads as versions of the same report, with comments and history kept across revisions

  • 04

    A product firms can actually run

    • Company accounts, roles, a basic dashboard and notifications
    • AWS, React, Python/FastAPI, MySQL, with AI-assisted parsing and a Stripe-ready subscription foundation

What Phase 1 is for

A Beta that accounting firms can log into, not a lab demo.

  • From POC to a platform

    • The checks that already worked sit inside upload, review and approval workflows
    • Dev, UAT and production on AWS, with audit trails on validations and user actions

  • K2 in Fortnox, on purpose

    • Phase 1 stays on Swedish K2 annual reports from Fortnox so the first release can be trusted
    • Architecture left open for more accounting systems later, without pretending they are in this release

  • GDPR-aware handling of filings

    • Uploaded reports are financial documents. Access, encryption and logging are part of the build
    • Browser-based. No local install for the accounting team

What this unlocks

Swedish accounting firms get a Beta they can use on real K2 filings: parse the PDF, run the rules, argue the findings, and come back to a revised version. The POC stays the proof. Phase 1 is the product around it.

Have a proof of concept that needs to become a product?

Tell us what already works, and who has to use it next. We'll help you decide what belongs in a first Beta.

All case studies