ERPax: Unified Business Management Platform - Comprehensive Overview

ERPax represents a fundamentally reimagined approach to enterprise resource planning, built as a modern SaaS platform specifically designed for contemporary business needs. Rather than fragmenting business operations across multiple disconnected systems, ERPax consolidates invoicing, accounting, and workflows into a single, unified document model that automatically handles business documents while generating compliant accounting entries in real-time.

Core Philosophy: The Unified Document Model

The foundation of ERPax's approach differs radically from traditional ERP systems. Instead of maintaining separate data models for quotations, invoices, purchase orders, and credit notes, ERPax uses one powerful, extensible Invoice model that serves all document types seamlessly. This architectural decision eliminates substantial complexity and creates a coherent system where all business documents operate under the same logic and rules. This unified approach delivers several critical advantages. Users learn one system, master one workflow, and leverage one interface regardless of document type. Documents flow automatically through their lifecycle—a quotation becomes an invoice, which generates accounting entries, which tracks payments—without manual intervention or data re-entry. This automatic transition system ensures consistency across all business processes while reducing human error and administrative overhead. The unified model also means one API for developers, infinite integration possibilities for businesses. Rather than building separate integrations for each document type, developers can integrate once against a single, consistent data structure. This dramatically reduces integration costs and accelerates the time to value for connected systems.

How the Unified Model Works

The Invoice model adapts based on the invoice_type field, using a modular architecture to provide type-specific behavior while maintaining a unified foundation. API Usage:

# Create quotation
POST /admin/invoices.json
{ "invoice": { "invoice_type": "quotation", ... } }
# Create invoice
POST /admin/invoices.json
{ "invoice": { "invoice_type": "invoice", ... } }
# Create purchase order
POST /admin/invoices.json
{ "invoice": { "invoice_type": "purchase_order", ... } }

This means:

• One API - Same endpoints for all document types
• One Workflow - Consistent lifecycle management
• One Data Model - Unified database schema
• One Codebase - Shared logic, shared improvements Learn more about the unified document model philosophy and technical implementation.

Automatic Accounting Integration

One of ERPax's most powerful differentiators is its built-in double-entry accounting system that generates ledger entries automatically when documents are confirmed. The system doesn't require accountants to manually journal transactions; instead, when an invoice is confirmed, ERPax automatically generates the complete accounting equation from both seller and buyer perspectives.

Key Components

This automatic accounting integration includes several critical components:

• Chart of Accounts Management - Comprehensive account structure with hierarchical organization
• Automatic Equation Generation - Complete accounting equations with seller and buyer perspectives
• Complete Audit Trail - All changes tracked via PaperTrail for regulatory compliance
• Real-Time Financial Reporting - Financial reports always current, no lag between operations and visibility
• EU-Compliant Accounting Practices - Built-in compliance from day one

How It Works

When you confirm an invoice:

1. Seller Equation Created - Debit entry for seller's account
2. Buyer Equation Created - Credit entry for buyer's account
3. Line Item Entries - Entries for each invoice line's accounts
4. Tax Entries - Separate entries for tax accounts No manual journal entries. No accounting errors. No reconciliation needed. The real-time nature of this integration means financial reports are always current. As soon as a document is confirmed and accounting entries are generated, they're immediately reflected in financial statements and reporting dashboards. This eliminates the lag between operational events and financial visibility that plagues traditional ERP systems. See Accounting Documentation for detailed API reference.

Multi-Tenant Architecture: Enterprise-Grade from Ground Up

ERPax was designed as multi-tenant from its initial architecture, rather than adding multi-tenancy as an afterthought. This foundational design decision has profound implications for scalability, customization, and cost efficiency.

Data Isolation

Data isolation is achieved through host-based separation, ensuring complete data segregation between different tenants. The API automatically scopes all requests to the current tenant:

• All API requests are automatically scoped to the current tenant
• No cross-tenant data leaks possible
• Foreign key constraints enforce isolation
• Tenant context is managed automatically via API authentication

Hierarchical Domain Structures

The system supports enterprises with multiple subsidiaries, allowing parent companies to manage multiple business entities within a single system while maintaining appropriate separation and control:

• Enterprises can host subsidiaries
• Domains can host sub-domains
• Shared resources at host level
• Granular permissions per level

Per-Tenant Customization

Each organization can configure independently:

• Locale Settings - Language preferences per tenant
• Timezone Preferences - Timezone handling per organization
• Currency Handling - Multi-currency support with tenant-specific defaults
• Business Rules - Customizable workflows and processes
• Branding - Logos, addresses, and visual identity This architecture enables ERPax to scale from startup to enterprise smoothly. A small company can use the system affordably, and as it grows or adds subsidiaries, the platform scales without requiring migration or major reconfiguration. The hierarchical domain structure is particularly valuable for holding companies and corporate structures with multiple operating entities. Learn more about multi-tenancy architecture.

EU-First Compliance and Regulatory Ready

ERPax was built specifically with European businesses in mind, incorporating comprehensive compliance features as core functionality rather than optional add-ons. This EU-first approach is increasingly critical as regulatory requirements become more stringent across Europe.

VAT Compliance

The VAT system is particularly sophisticated, understanding the different VAT treatment requirements for different transaction types:

• B2B Transactions - Reverse charge mechanisms
• B2C Transactions - Standard VAT application
• Intra-EU Trade - Special handling for cross-border EU transactions
• Imports/Exports - Customs and import VAT handling
• VAT Directive 2006/112/EC - Full compliance with EU regulations

Multi-Currency Support

Multi-currency support extends beyond simple conversion:

• Real exchange rate management via EU Central Bank integration
• Proper accounting treatment of currency fluctuations
• Multi-currency payments with automatic conversion
• Currency-specific payment methods per address

Tax and Reporting

Built-in tax calculation and reporting systems:

• Tax calculations and reporting
• Invoice compliance workflows that ensure all documents meet regulatory requirements
• Comprehensive international trade support including Incoterms compliance, HS codes and customs documentation
• Complete audit trail for regulatory compliance Rather than requiring businesses to customize or add additional systems for compliance, these features are embedded in the core platform. This means compliant from day one, no plugins, no extra costs, no compliance headaches. See Features for complete compliance capabilities.

Workflow Automation: Documents Flow, Not Stack

Workflow automation is fundamental to ERPax's design, not an afterthought or premium feature. The system automates entire business processes, transforming manual document handling into flowing, intelligent workflows.

Automatic Document Transitions

The automation framework handles:

• Automatic Document Type Transitions - Quotation → sales order → invoice → payment
• Automatic Number Generation - Unique numbers for each seller and buyer combination ensuring proper document tracking
• Automatic Account Assignment - Based on business relationship types
• Automatic Payment Tracking - Overdue calculations that flag past-due amounts
• Automatic Email Notifications - To relevant parties at each workflow stage
• Automatic PDF Generation - For distribution and archival

Workflow Examples

Quotation to Invoice Flow:

1. Create quotation → System assigns quotation number
2. Confirm quotation → Automatically transitions to proforma invoice
3. Confirm proforma → Automatically becomes final invoice
4. Invoice confirmed → Accounting entries generated automatically
5. Payment received → Status updated automatically Purchase Order Flow:
6. Create purchase request → System tracks request
7. Approve request → Automatically creates purchase order
8. Receive goods → Protocol created automatically
9. Confirm protocol → Bill created automatically
10. Bill confirmed → Accounting entries generated This comprehensive automation dramatically reduces administrative work. Accounting staff don't manually create journal entries; sales teams don't manually number documents; finance doesn't manually track payment status. Instead, the system orchestrates these activities based on business rules and document state transitions.

Key Features Overview

Document Management Across Business Processes

ERPax handles the complete spectrum of business documents through its unified system: Sales Documents:

• Invoices - Final sales invoices with automatic numbering
• Quotations - Price quotes with automatic conversion to invoices
• Proforma Invoices - Preliminary invoices before final invoicing
• Credit Notes - Refunds and adjustments for returns
• Debit Notes - Additional charges and adjustments Purchase Documents:
• Purchase Orders - Supplier orders with tracking
• Purchase Requests - Requests with approval workflows
• Receiving Protocols - Goods receipt confirmations
• Bills - Supplier invoice management Recurring Documents:
• Subscriptions - Recurring service agreements with automatic renewals
• Lease Agreements - Equipment or property leases with billing period management Lead Documents:
• Shopping Carts - For e-commerce with automatic conversion to quotations and orders
• Requests - Customer purchase requests with automatic processing

Payment Processing and Financial Management

ERPax provides comprehensive payment management that extends far beyond basic transaction recording:

• Payment Tracking - Track payments against specific invoices
• Overdue Calculations - Automatic calculation of overdue amounts and interest charges
• Multiple Payment Methods - Bank transfer, card, cash, checks
• Multi-Currency Payments - Proper exchange rate treatment
• Credit Line Management - Credit lines for business customers with usage tracking The payment tracking creates a complete audit trail showing which documents have been paid, when, and through which methods. Overdue calculations automatically flag invoices past their payment terms, enabling better cash flow management.

Product and Inventory Management

Complete product catalog management with variant support enables businesses to manage complex product hierarchies:

• Multi-Domain Product Visibility - Different subsidiaries or business units can have appropriate access to products
• Pricing Rules and Profit Margin Management - Sophisticated pricing strategies
• Real-Time Inventory Tracking - Stock levels across locations
• External Integrations - Notably Shopify connects e-commerce platforms to the core ERP system

Business Relationship Management

ERPax uses a unified Address model that represents customers, suppliers, sellers, buyers, and agents as flexible business relationships:

• Sales Agreements - Document credit terms with specific customers
• Payment Methods - Configured per address ensuring the system knows how each business partner prefers to conduct transactions
• Accounting Accounts - Assigned per address allowing customer/vendor-specific accounting treatment
• Hierarchical Relationships - Support complex business structures (parent companies, branches, departments) See Features for complete feature documentation.

Data Model & Relationships

ERPax uses a unified data model where all resources relate through clear relationships: Core Entities:

• Domain - Multi-tenant root (has Address, Users, Invoices)
• Address - Unified business partner model (customers, suppliers, sellers, buyers)
• Invoice - Unified document model (all document types)
• Item - Products and inventory
• Payment - Payment tracking
• Accounting - Double-entry accounting system Key Relationships:
• Domain → Address (domain.address - business entity)
• Invoice → Address (seller, buyer, supplier)
• Invoice → InvoiceLine[] → Item
• Invoice → Payment[] → Address
• Invoice → AccountingEquation[] → AccountingEntry[] → AccountingAccountSee route documentation for detailed relationships:
• Invoices - Invoice relationships section
• Addresses - Address relationships section
• Domains - Domain relationships section
• Items - Item relationships section
• Payments - Payment relationships section
• Accounting - Accounting relationships section

Target Market and Use Cases

European Businesses and Compliance-First Organizations

The EU-first compliance approach makes ERPax ideal for European companies and multinational businesses operating in Europe. Rather than retrofitting compliance, it's inherent to the platform. Industries: Retail, Services, Manufacturing, Distribution

Multi-Subsidiary Enterprises

Organizations with multiple business units, subsidiaries, or holding company structures benefit from the hierarchical domain architecture. Each subsidiary can operate with appropriate autonomy while the parent company maintains consolidated visibility. Industries: Corporate groups, Franchises, Agencies

B2B Companies with Complex Sales

Businesses managing complex sales agreements, credit terms, multiple payment methods per customer, and sophisticated business relationships find ERPax's relationship management particularly valuable compared to systems built for simpler commerce. Industries: Wholesale, Distribution, Manufacturing, Services

E-Commerce and Recurring Billing Models

Shopify integration, cart management, customer self-service portals, and subscription/lease automation make ERPax suitable for both pure e-commerce companies and traditional businesses adopting recurring revenue models. Industries: E-commerce, Online retail, Marketplaces, SaaS, Software, Leasing

International Traders

Multi-currency support, exchange rate management, HS codes for product classification, Incoterms compliance, and international trade compliance features address the specific needs of businesses trading across borders. Key features for international trade:

• Incoterms support - Standardized trade terms (FOB, CIF, EXW, DDP, DAP, etc.) to clearly define shipping responsibilities, costs, and risk transfer points
• HS codes - Harmonized System codes for customs classification
• Multi-currency - Real exchange rate management with proper accounting treatment
• Customs documentation - Support for international shipping and trade compliance Industries: Import/Export, International Distribution, Global Manufacturing See Why ERPax? for more detailed use cases and For Business for business-focused resources.

Technology Stack and Developer Experience

ERPax is built as a modern SaaS platform designed for developers:

• Comprehensive API - 337+ documented endpoints for building integrations
• Unified Data Model - One API structure that handles all document types
• Extensive Documentation - API integration basics, code examples, quick reference guides
• Architectural Overview - Materials designed to accelerate development
• Strong Security Practices - Built-in authentication, authorization, and data isolation
• Excellent API Capabilities - Advanced features for complex queries and data integrity

Frontend Development

The Stimulus framework integration enables building reusable, maintainable frontend code without requiring a heavyweight SPA framework. This approach balances modern interactivity with simplicity and performance. See For Developers for technical documentation and API Reference for complete API documentation.

Key Differentiators from Traditional ERP

The comparison between ERPax and traditional ERP systems reveals fundamental architectural differences:

Aspect	Traditional ERP	ERPax
Document Models	Separate data models for different document types	Unified Invoice model for all types
Accounting	Manual journal entry creation required	Automatic generation from business documents
Multi-Tenancy	Added years after initial development	Built-in from ground up
EU Compliance	Add-on or completely missing	Comprehensive compliance as core functionality
Workflows	Manual or complex, fragile customization	Automatic through document transitions
Complexity	High - multiple systems to learn	Low - one system, one workflow
Integration	Difficult - separate APIs per document type	Automatic - one API, one data model
Setup Time	Weeks to months	Days
Maintenance	Changes in multiple places	Single codebase, shared improvements
This fundamental architectural redesign means businesses using ERPax have:

• Fewer Systems to Manage - One system instead of many
• Fewer Manual Processes - Automation reduces administrative overhead
• Faster Time to Financial Reporting - Real-time accounting integration
• Better Compliance Assurance - Built-in compliance, not bolted-on
• Lower Total Cost of Ownership - Less complexity, less maintenance, less training See Why ERPax? for detailed comparisons and Philosophy for the design principles behind these decisions.

Getting Started

See the Getting Started Guide for detailed setup instructions, prerequisites, and first steps.

Common First Tasks

• Create First Invoice - Understand the basic workflow through Creating First Invoice tutorial
• Set Up Multi-Tenant - Configure multi-tenant structure via Multi-Tenant Setup guide
• Process Payments - Learn the complete transaction lifecycle with Processing Payments tutorial
• API Integration - Connect external systems using API Integration Basics The platform's unified approach means mastering one system, understanding one data model, and gaining the ability to handle virtually all business document types and workflows. Rather than fragmented complexity, ERPax offers coherent simplicity at enterprise scale.

---

Ready to transform your business management?

• Get Started - Begin your ERPax journey
• Explore Features - See detailed capabilities
• Read Philosophy - Understand the unified approach
• For Business - Business-focused resources
• For Developers - Technical documentation