HomeFeaturesIndustriesPricingPartnersContact Book a Discovery
Case Study

Real Estate & Fund Operations

How a leading Australian property and fund management group replaced fragmented financial operations with a single governed platform: zero custom code.

7
Financial domains governed
End-to-End
Approval workflows live
Thousands
Of reference data records
0
Lines of custom code

Complex Approvals, No Single System of Record

A large property and fund management group with diversified holdings across multiple property sectors needed to modernise financial operations spanning fund management, payments, expenditure, entity setup, banking, and distributions.

Fragmented legacy forms

Financial operations spread across disconnected forms: each with its own layout, approval chain, and data model. No shared reference data, no consistent user experience.

Complex, manual routing

Multi-stage approval chains with conditional routing based on amounts, asset types, and departments. Some workflows required dozens of routing rules driven by data attributes.

Repeated data entry

The same core master data re-entered across most forms. Thousands of reference data records with no shared lookup mechanism.

No audit trail

Limited visibility into who approved what, when, and why. Regulatory and internal compliance requirements demanded a full, tamper-evident audit trail.

Configuration, Not Code

The entire solution was built using BPA's declarative platform: entities, forms, workflows, and routing rules defined as configuration. No developers. No deployment pipeline. No custom code.

1

Consolidate

Related processes share a single entity with conditional field visibility based on request type, reducing duplication and giving teams one place to manage each domain.

2

Centralise

Shared reference datasets extracted and loaded as platform lookups, eliminating duplicate data entry across all forms.

3

Automate

End-to-end approval workflows with conditional routing, amount-based stage skipping, parallel fan-out reviews, and dynamic assignees: all configured, not coded.

What's Running on BPA

Domain What It Handles Workflow Pattern
Fund Management Multi-stage approval and reconciliation workflows Linear approval with signatures
Payments Payment request workflows File uploads, lookup integrations
Expenditure Capital and operating expense approvals Amount-based routing, conditional approvals
Entity & Trust Entity setup and trust administration Branch routing by request type
Banking Account and banking workflows Multi-stage linear approval chains
Distributions Distribution approval workflows Conditional routing by attribute
Transactions Acquisition and divestment processes Parallel multi-team review

Three Workflow Patterns, Every Domain Covered

Every approval chain uses dynamic assignees: the correct approver is pulled from the form data, not hardcoded. This means the same workflow adapts to any fund, sector, or department.

Linear Approval

Most common pattern

Sequential stages with dynamic assignees. Approvals flow through multiple roles in order, with each approver pulled dynamically from the form data rather than hardcoded.

Conditional Routing

Used in expenditure & distributions

Decision nodes skip or add stages based on business rules. For example, low-value requests can bypass senior approval, and downstream routing can adapt based on attributes captured on the form.

Parallel Fan-Out

Used in transactions

Approvals fan out to parallel reviews across multiple internal teams before converging to a final sign-off chain.

"Every financial domain governed by structured approval workflows, conditional routing, and shared reference data. All delivered as platform configuration. No code was written. No developers were needed."

- BPA Implementation Team

What Was Delivered

Consolidated data model

Structured entities across every financial domain with shared reference datasets, eliminating duplicate data entry and giving every team a single source of truth.

Governed approval workflows

Multi-stage approval workflows across every financial domain, including amount-based routing, attribute-driven conditional rules, and parallel cross-team reviews. Every approval captured in a tamper-evident audit trail.

Full audit and compliance

Every submission, approval, rejection, and field change logged with timestamp, user, and context. Stage-based section visibility ensures reviewers see only what's relevant to their role.

Zero custom code

The entire solution, entities, forms, workflows, routing rules, reference data, and conditional logic, was delivered as declarative configuration on BPA. No developers. No deployment pipeline.

What Made This Possible

Declarative Entities

Field schemas, validation rules, and relationships defined as configuration. Type-discriminators let one entity serve multiple form variants without duplication.

Flow Designer

Visual approval workflows with conditional edges, amount-based stage skipping, parallel fan-out, and dynamic assignees pulled from form data.

Reference Data

Shared lookup entities loaded once and referenced across all forms. Thousands of records centralised with search and filtering.

Conditional Visibility

Hundreds of field and section visibility rules ensure each user sees only what's relevant to their role and the current stage, reducing errors and training time.

Multi-Tenant Isolation

All data scoped to the organisation. Full tenant isolation at every layer: database, API, and UI. Infrastructure delivered by Norbrik, an ISO 27001 certified company.

AI-Assisted Build

BPA's AI tools accelerated the build, generating entity schemas, form layouts, and workflow definitions from requirements. Human review at every step.

Similar Challenges?

If your organisation manages complex approval workflows across legacy forms, we'd like to show you what BPA can do, configured to your use case, in a live demo.

Book a Discovery Call →

Ready to automate smarter?

Start free. No credit card required.