RevoraSphere Architecture: Built for Public-Sector Scale in Canada

Architecture as a Competitive Advantage

In enterprise software, architecture is destiny. A platform built with the right architectural principles can evolve, scale and integrate. A platform built as a collection of point solutions stitched together will always be constrained by the gaps between its parts.

RevoraSphere was designed by practitioners who spent years implementing municipal finance systems — and who understood the architectural debt that fragmented legacy platforms accumulate over time. Every decision in the RevoraSphere architecture reflects a specific lesson learned from the limitations of what came before.

This article describes the core architectural layers of the RevoraSphere platform, the design principles behind them, and how they translate to practical operational advantages for Canadian municipalities.

At a glance:

• Azure infrastructure — backed by Microsoft's published Azure service-level agreements
• AES-256 — encryption standard for data at rest and in transit
• Canadian data residency — hosted in Microsoft Azure Canadian data centres

The Five Architectural Layers

RevoraSphere is organized as five distinct but tightly coupled architectural layers. Each layer has a clear responsibility and communicates with adjacent layers through well-defined interfaces. No layer is optional — they are designed to work together.

Layer 1: Assessment Data Layer

Municipal property taxation begins with assessment data. In Ontario, this is MPAC. In British Columbia, BC Assessment. In Alberta, the provincial assessment system. Each authority provides assessment data in different formats, on different schedules, with different update rules for supplementary assessments.

RevoraSphere's assessment data layer is designed to handle these provincial formats without manual data transformation. Scheduled feeds are ingested automatically, supplementary assessments are matched to the correct tax account, and assessment appeals are tracked within the same system that manages the underlying tax roll.

This removes what is, in most legacy environments, a time-consuming manual process: the periodic import and reconciliation of assessment authority data files.

Layer 2: Core Revenue Engine

The core revenue engine is the heart of RevoraSphere. It implements the business logic for property tax calculation, utility billing, accounts receivable and cashiering within a single shared data model.

The key architectural decision here is the unified account ledger. Rather than maintaining separate ledger systems for property tax and utilities — the legacy approach and the source of most reconciliation complexity — RevoraSphere maintains a single AR subledger where every revenue type is represented as a ledger entry with a revenue type code.

This single decision eliminates:

• Cross-module reconciliation
• Duplicate account records
• Conflicting balance displays between modules
• Year-end reconciliation as a distinct work stream

The revenue engine also implements rate structure logic: tiered utility rates, seasonal adjustments, penalty and interest calculations, instalment billing schedules and tax rate changes. Rate structures are configured in the platform's administration layer, not hardcoded — so new rate structures can be deployed without software updates.

Layer 3: Integration & API Layer

RevoraSphere does not exist in isolation. Municipal technology environments include GL systems, document management, GIS, building permit software and other platforms the revenue system needs to connect with.

The integration layer provides a REST API for platform functions, connectors for financial integration with Dynamics 365 Finance or Business Central, and a configurable event-driven notification system that can trigger workflows in external systems when specific events occur in RevoraSphere.

Payment processing is designed around Canadian payment rails, with PAD (pre-authorized debit) and EFT processing built into the payment layer, including CPA 005 file generation. Stripe is the planned initial online payment provider.

Layer 4: Citizen & Staff Portal

The portal layer serves two distinct audiences through a single platform: citizens who need self-service access to their accounts, and municipal staff who manage accounts, process payments and handle service requests.

The citizen portal is designed with WCAG 2.2 AA principles in mind, with formal accessibility validation performed during implementation and release readiness — supporting the accessibility obligations Canadian public-sector organizations carry under legislation such as Ontario's Accessibility for Ontarians with Disabilities Act (AODA) and equivalent provincial legislation. It is mobile-responsive, designed for bilingual delivery (English today, with French planned), and works on any device without a native app installation.

Citizen-facing features include:

• A unified account view showing outstanding balances across property tax, utilities and other revenue types
• Online payment and PAD enrolment
• Payment history and statement download
• Exemption application submission with document upload
• Service request tracking
• Usage history and consumption charts for utility accounts

Staff-facing features use the same underlying data layer but present a different interface optimized for high-volume transaction processing, account research and exception handling.

Layer 5: Analytics & Reporting

Municipal finance leadership needs two categories of reporting: operational reports for day-to-day management and strategic reports for council presentation and annual reporting. RevoraSphere's analytics layer provides both.

Operational dashboards include AR aging by revenue type, daily collections summary, delinquency tracking by ward or rate class, utility consumption anomalies and payment channel performance (counter vs online vs PAD).

Strategic reporting includes levy realization analysis, multi-year revenue trend analysis, rate scenario modelling for budget planning and council-ready PDF exports with the municipality's branding.

Power BI integration allows municipalities already invested in the Microsoft analytics ecosystem to extend RevoraSphere data into their existing Power BI environment. The platform exposes a read-only analytics data feed that Power BI can connect to directly.

Cloud Infrastructure and Security

RevoraSphere runs on Microsoft Azure with Canadian data residency. All data — property assessment records, financial transactions, citizen account information — is stored in Azure regions within Canada. This supports the data-residency expectations of Canadian municipalities and their privacy frameworks, and simplifies privacy documentation for municipalities subject to provincial privacy legislation.

The security architecture follows zero-trust principles:

• All API calls require authentication and authorization — there are no implicit trust relationships between services
• Role-based access control (RBAC) governs staff access, with segregation of duties enforced at the data layer
• Microsoft Entra ID (formerly Azure AD) integration supports single sign-on for staff using their existing municipal Microsoft 365 credentials
• Data in transit is encrypted using TLS 1.3; data at rest uses AES-256 encryption
• An immutable audit trail records every data change with user identity, timestamp and previous value
• Documented security controls — encryption, role-based access, audit trails and segregation of duties — support municipal security and audit reviews

Dedicated Environments and Isolation

RevoraSphere is deployed in a dedicated, municipality-specific environment. There is no shared database and no multi-tenant data layer — one municipality's data never sits alongside another's. Each subscription includes production, UAT and test environments, with Econix managing updates, patches, monitoring, backups, performance and capacity according to the selected service plan.

Update and Maintenance Model

One of the most significant operational advantages of a cloud-native platform over legacy on-premises software is the update model.

In legacy municipal software, even minor updates require testing cycles, change management and often consultant involvement. Major version upgrades can take months and cost significant amounts in consulting fees. As a result, many municipalities run substantially outdated versions of their revenue software — which means missed security patches, regulatory updates and feature improvements.

RevoraSphere uses a continuous delivery model. Platform updates are prepared by Econix, tested in staging before release, and applied to each municipality's dedicated environment on a managed schedule. Municipalities run the current version without upgrade projects or version-compatibility issues.

Regulatory changes — new rate calculation rules, provincial assessment format updates, payment standard changes — are implemented by Econix and rolled out to each municipality's environment on the same managed schedule.

Conclusion

The RevoraSphere architecture reflects a deliberate set of decisions: unified data over federated integration, cloud-native deployment over hosted legacy, municipal-specific business logic over generic platform customization.

These decisions translate into a platform designed to be faster to implement, easier to maintain and more capable than the legacy alternatives it replaces — with a straightforward subscription model in place of licence-plus-maintenance-plus-upgrade economics.

For municipalities considering platform modernization, the architecture conversation is not a technical detail. It is the foundation of every operational outcome the platform will deliver.