UnionTax ERP — Running cases from acquisition to completion

Bitbrew built UnionTax’s industry-specific ERP as the operational system behind its day-to-day casework. Instead of starting with a generic customer record, the data model connects clients with their families and with the individual tax and child-benefit cases created around them. Documents, deadlines, fees and case completion are part of the same workflow.

That becomes important when several organisational layers work on the same mandate. The tax office and agency have distinct roles and responsibilities, while the business spans Germany, Austria and Switzerland and serves clients who may speak Romanian, Hungarian or Polish. The system therefore has to keep ownership, case status and context unambiguous across countries, languages and case types.

This is what separates the application from a general CRM or off-the-shelf ERP. A case is not simply an activity attached to a customer. It has its own family context, documents, deadlines, financial status and completion criteria. The software follows that real operating model from acquisition through active processing to the finalised mandate.

The UnionTax ERP is not a DATEV plug-in, nor is it presented as a container for every adjacent integration. ELSTER, VaSt and EBICS are separate authority and banking components with their own requirements. The underlying ERP pattern is reusable wherever businesses manage long-running, document-heavy cases involving multiple roles, deadlines and financial states.