Why Audit Chen exists

Built on curiosity.
Not on a business plan.

A story about late nights, Warsaw in winter, plenty of failures – and a spare-time project meant to make auditors’ work easier.

  • Student, WU Vienna
  • previously at PwC
  • Exchange semester, SGH Warsaw
  • Spare-time project
↓

I study at WU Vienna and was at PwC before that – first as an intern working with family businesses, then as a permanent employee working on investment funds. That time shaped me a lot: it gave me solid foundations and room to stay curious. Ever since, one thought has stuck with me – how much of an audit is still done by hand, twice, or the long way round, and how much room there is for something better.

⏱Hundredsof hours of development
☾2–3 a.m.calling it a day – ready again at 8
€4 figuresin API costs (euros), paid myself
↻Countlessfailures – and each one taught me something
The journey

From Warsaw to today.

  1. 2025

    The question

    First research into how AI can improve audit processes. The idea sticks.

  2. January 2026

    The decision

    Exchange semester at SGH Warsaw: an exciting market, courses in audit and international law, excellent professors.

  3. February 2026

    −20 °C

    Arriving in Warsaw in the middle of winter. Straight into an internship in foreign trade the next day, university alongside — and a great deal learned about AI in audit.

  4. March

    The first line of code

    The first program, built with Python and pandas. Small, bumpy — but it calculates.

    import pandas as pd
  5. April

    Prototypes

    Lots of prototypes. Some discarded after hours, some after days.

  6. May

    Focus

    Even more prototypes — but more targeted. Less trial, more understanding.

  7. June

    The breakthrough

    A good algorithm for journal entry testing. Developed in conversations with people from IT, mathematics, business and law – every perspective made it better.

  8. Autumn

    From tool to audit

    Around JET came AI agents, the FinCrime graph, a client portal, adjustments, group audits, ESG and the Academy – so the path from data to report stays in one program.

  9. Today

    Still building

    Audit Chen keeps growing — module by module, night by night.

Progress is not a straight line

Every red dot is a failure. There were many. It was still a lot of fun.

Line by line

65,000 lines of code

Rounded up to the nearest thousand: about 51,000 lines in the app and 15,000 in this website. The curve shows the app since it moved into its current repository – the starting value includes everything built before.

What it became

One tool became a network

It all started with journal entry testing. Tap a module to see what it does and what it connects to.

“No team, no budget, no shortcut – just a good dose of curiosity and the joy of learning.”

Audit Chen exists because I thought about this a lot – not because I mainly wanted to make money from it. In early 2027 Audit Chen will be the basis of my bachelor’s thesis – after that I’ll decide how to make the platform available to as many auditors as possible. Until then it is what it has been from the start: a carefully considered passion project whose costs I currently cover entirely myself.

I hope that in the end it helps someone – people who wish for better tools for their work.

Let’s connect

Do you work in audit, find the topic interesting or want to try Audit Chen? I’m happy to hear from you.