Internal invoicing redesign

feature
Automating and unifying internal invoicing processes by introducing a numbering sequence, structuring the invoice template and preparing an electronic format. The goal was to standardise invoices across the products and services offered, while preparing the system for e-invoicing requirements.
problem

Too many invoices were still created manually from scratch

The accounting team was still creating many invoices manually. Invoices were structured and generated differently for each product or service being billed. There was no shared system or consistent numbering across invoice types. The goal was therefore to automate invoice generation within a single system.
approach

Understanding the accounting process before improving it

I spoke with the accounting team and the people affected by the planned improvements to better understand their work and the difficulties they faced. This helped me identify what took the most time, where errors were more likely to occur and what the new system could offer them. In parallel, I studied the invoicing requirements relevant to the project, including numbering rules, mandatory details and structured electronic formats. I used this functional and regulatory analysis to break down the development work into epics and user stories, which we then refined and validated with the CTO and developers.
solution

Unified numbering, a new template and structured XML data

I introduced a common numbering scheme across all invoices, replacing the different rules used until then. I also designed a new PDF invoice template that included the missing mandatory details and created the corresponding XML structure for generating Factur-X invoices, which combine a PDF/A-3 document with embedded XML. This work was intended to prepare the invoices for transmission through our approved platform.
impact

A more consistent, structured invoicing foundation

This work replaced service-specific invoicing rules with a common numbering scheme and template across the platform. It also addressed the points identified during the analysis: numbering rules, mandatory details and structured electronic data. This gave the team a shared foundation for developing the invoicing system and preparing the next steps towards e-invoicing.
BACK TO PROJECTS
let's connect

Let's build something great together!

Whether it's a project, an idea, or just a chat, I'd love to connect.
contact
AIJA