Shariah-Compliant Access for Conventional Client Books

Introduction

An intermediary that allocates on behalf of many clients, a private bank, an external asset manager, a multi-family office, faces a recurring question when it looks at the Gulf. A meaningful share of the most attractive regional product, and an even larger share of the regional client base that wants to own it, is Shariah-compliant. The intermediary's book, by contrast, was built on conventional rails. Its mandates, its product-approval committees, its custody and its reporting were designed for conventional instruments. The instinct, when compliant demand appears, is to treat it as a separate business: a separate desk, a separate platform, perhaps a separate licence. That instinct is expensive, and it is usually wrong.

This paper sets out the case that compliant access is better understood as a thin layer added to an existing conventional book than as a parallel platform built beside it. The compliant Gulf product set is now deep and institutional. What stands between a conventional intermediary and that product set is not supply but a set of access and governance mechanics: how a product is screened for compliance, how the intermediary documents and discloses that compliance to its clients, how the residual non-compliant income is dealt with, and through which wrapper the exposure is actually delivered into a conventional mandate. None of these requires the intermediary to rebuild its book. Each can be added as a layer.

The paper supplies the framework for that layer. It treats the problem as a four-layer architecture, running from the conventional client book at the top, through the intermediary's own screening and governance function, through the access wrapper, down to the underlying compliant product. It then works through the two screens that define compliance and the supporting mechanics that a conventional book must adopt, compares the wrappers by which access is delivered, and sets out a twelve-month path to standing the capability up.

It is worth stating plainly why this matters in commercial terms before turning to the mechanics. An intermediary's franchise is, at bottom, a distribution franchise. Its value lies in the trust of its clients and in the breadth of product it can credibly place into their mandates. A conventional book that cannot serve compliant demand is, in a Gulf context, leaving a structural part of its addressable market unserved, and is doing so not because the product is unavailable but because the intermediary has not built the access layer. Conversely, the intermediary that does build it widens its addressable market without diluting its existing one, because the same platform now serves both a conventional client who is indifferent to compliance and a client for whom compliance is the deciding factor. The economics of distribution, low marginal cost on an established channel, mean that the return on building the access layer is high precisely because the channel already exists. This is the practical case the paper makes concrete.

The Architecture And The Access Routes

This section develops the framework in the order of the propositions. It first sets out the four layers of the architecture (Proposition 1), then the two screens (Proposition 2), then the supporting mechanics a conventional book must add (Proposition 3), then the comparison of access routes (Proposition 4), and closes on the distribution argument for 2026 (Proposition 5).

The Four Layers

The architecture of Figure 1 runs from the conventional client book at the top to the compliant product at the bottom, and it is read in two directions. Capital flows downward: a client's mandate, sitting in the conventional book, is the source of the allocation, which passes through the access wrapper into the underlying compliant product. Compliance assurance flows upward: the underlying product's Shariah board certifies the product, the intermediary's governance function relies on and documents that certification, and the client receives a clear, evidenced statement that its allocation is compliant. The two layers in the middle, the intermediary's screening and governance, and the access wrapper, are the only parts a conventional book must add. The top and bottom layers it either already has (the book) or can source from the market (the product).

Reading the architecture this way dissolves the false choice between a conventional and a compliant platform. The intermediary does not need two books. It needs one book and two added layers, and the second of those, the wrapper, is frequently shared with conventional product the intermediary already distributes. The marginal build is the screening and governance layer and the configuration of an appropriate wrapper, not a parallel business.

The overlap between the conventional and compliant product universes, shown illustratively in Figure 2, reinforces the point. A large part of the Gulf product set is accessible to both kinds of book once the wrapper exists; what differs is not the asset but the screening and documentation applied to it. The intermediary that builds the middle layers turns the overlap into addressable demand.

It is worth being precise about what flows in each direction, because the two flows are governed by different parties and this division is the key to keeping the build small. The downward flow, of capital, is owned end to end by the intermediary and its client: the client commits, the intermediary directs the commitment through the wrapper, and the wrapper subscribes to the product. The upward flow, of assurance, is owned mostly by others: the product's Shariah board certifies, the manager maintains compliance, and the intermediary's role is to rely on that assurance correctly and to translate it into a statement the client can trust. The intermediary, in other words, owns the capital pipe and the client relationship but rents the certification. Recognising which parts are owned and which are rented is what prevents an intermediary from over-building, from trying to recreate a Shariah board it should instead rely upon.

Figure 2. The Compliant and Conventional Product Universes

Illustrative. A substantial overlap of Gulf product is accessible to both a conventional and a compliant book once an access wrapper exists; the screening and documentation, not the asset, is what differs.

The Two Screens

Compliance, at the operational level that matters to an intermediary, is defined by two screens applied in sequence. The first is the activity screen, a qualitative test of what the underlying business does. Businesses whose core activity is prohibited, conventional interest-based lending, alcohol, gambling, pork, tobacco, adult entertainment and certain others, are excluded outright. The activity screen is binary and is applied first because it removes whole categories before any number is computed. For most Gulf private-market product, real assets, infrastructure, compliant operating companies, the activity screen is passed comfortably, which is part of why the region's product set lends itself to compliant distribution.

Two features of the activity screen matter for an intermediary. The first is that it is applied to the core activity of the business, not to incidental or de minimis exposures; a business is not failed because a trivial fraction of its activity touches a prohibited area, which is what the second, quantitative screen and the purification mechanic exist to handle. The second is that the activity screen is where most of the intellectual work has already been done by the product's Shariah board before the intermediary ever sees the product. The intermediary's task at this stage is verification and reliance, confirming that the screen has been applied and certified, not reapplication from first principles.

The second is the financial-ratio screen, a quantitative test of how the business is financed and what it earns. It typically examines three ratios: interest-bearing debt as a share of assets; cash and interest-bearing securities as a share of assets; and income from non-compliant sources as a share of total revenue. A business that passes the activity screen but is financed largely with conventional debt, or earns a material share of its revenue from interest, fails the ratio screen. The illustrative thresholds in Figure 5 convey the order of magnitude, commonly cited cut-offs sit in the region of one third of assets for the leverage and liquidity ratios and a low single-digit percentage for impermissible income, but the exact figures differ across standard-setters and must be taken from the applicable standard.

Illustrative. A Gulf product pipeline narrows through the activity screen, the financial-ratio screen and the structuring and documentation step to a compliant allocation.

Implementation: A Twelve-Month Roadmap

This section sequences the build into a stylised twelve-month roadmap, shown in Figure 8. The phases overlap, and the durations are illustrative; the purpose is to show the order of dependencies, not to assert a fixed timetable.

Illustrative and overlapping phases. The sequence shows dependencies, not a fixed timetable; durations vary by intermediary, jurisdiction and platform.

Months 0 to 3: Mandate and Policy Framework

The build begins with policy, not product. The intermediary defines its compliance policy: which standard it will rely on, how strict its house overlay will be, what it will and will not represent to clients, and how it will document reliance on a product's Shariah board. This is the cheapest phase and the one that prevents the most expensive mistakes, because it fixes the standard against which everything later is judged.

Months 1 to 4: Shariah Governance Set-Up

In parallel the intermediary stands up its governance arrangement: who in the organisation owns compliance reliance, whether it appoints or retains a Shariah adviser for its house overlay, and how it will monitor that product certifications remain current. The output is the responsibility matrix of Figure 6, populated with named owners.

Months 2 to 6: Wrapper and Share-Class Build

The intermediary then configures the access route or routes it will offer, the compliant share class where one exists, the feeder where it must aggregate, the note where the platform requires it, and works with administrators and custodians so that the chosen wrapper settles and reports through existing plumbing. This is the most platform-dependent phase and the one where timelines vary most.

Months 3 to 8: Product Due Diligence

With the policy, governance and wrapper in place, the intermediary runs its diligence on the actual product it intends to distribute: confirming the activity and ratio screens, reviewing the product's Shariah certification, and checking that purification is handled by the manager or administrator. The output is an approved-product list the intermediary can place with confidence.

Months 5 to 9: Client Disclosure and Onboarding

The intermediary prepares the client-facing layer: the disclosure documents, the suitability process for compliant allocations, and the onboarding of clients into the chosen wrapper. This phase touches the client relationship directly and is where the intermediary's existing strengths, knowing its clients and communicating clearly, do most of the work.

Months 7 to 10: First Compliant Allocations

The first allocations are made, deliberately at modest size, to test the full chain end to end: screening relied upon, wrapper settling, disclosure delivered, purification reported. The aim is to surface any operational gap on a small allocation before scaling.

Months 8 to 12: Reporting and Purification Cycle

Finally the intermediary establishes the steady-state cycle: periodic confirmation that certifications remain current, the regular purification calculation and reporting, and the inclusion of compliant allocations in standard client reporting. At this point compliant access has become a routine part of the book rather than a project.

Common Pitfalls and How the Roadmap Avoids Them

Three pitfalls recur. The first is building product before policy, which leads to inconsistent representations and rework; the roadmap puts policy first. The second is treating compliance as a marketing label rather than a governed function, which risks the intermediary's credibility; the roadmap makes governance an explicit, owned layer. The third is choosing the most elaborate wrapper by default, usually a bespoke managed account or a structured note, when a compliant share class would have reused existing plumbing at a fraction of the friction; the roadmap forces the access-route decision to be made deliberately against Figure 4 and Appendix C.

Two further pitfalls deserve a mention because they appear late and are therefore costly. The first is failing to assign a named owner to the monitoring of certifications, with the result that a lapsed certification is discovered only when a client or a regulator asks. The roadmap's governance phase exists precisely to put a name against this task before any allocation is made. The second is scaling before the first end-to-end allocation has been tested, so that an operational gap, a wrapper that does not settle cleanly, a purification calculation that does not flow into reporting, is discovered at size rather than at a deliberately small first ticket. The roadmap's sequencing, a modest first allocation before the steady-state cycle, is designed to surface such gaps cheaply.

Conclusion

A conventional client book and a Shariah-compliant product universe are usually presented as two businesses. This paper has argued that, for an intermediary, they are better understood as one book and a thin layer of access architecture. The architecture has four layers, the client book, the screening and governance function, the access wrapper, and the underlying compliant product, and only the two middle layers must be added. Compliance itself reduces to two screens, an activity screen and a financial-ratio screen, that the intermediary can rely on rather than originate, supported by three additive mechanics, governance, disclosure and purification, that sit on top of an existing platform. The exposure is delivered through one of five wrappers that differ in friction, with the compliant share class usually the lowest-friction route where it exists.

The framework is deliberately general. It does not depend on any one jurisdiction's rules, any one standard-setter's exact thresholds, or any one platform's plumbing, because those are the variables an intermediary substitutes for itself. What the framework supplies is the invariant structure: the four layers, the two screens, the three mechanics and the five routes. That structure holds whether the intermediary is a Gulf private bank serving a regional book, a European EAM serving cross-border clients, or a multi-family office assembling a bespoke compliant sleeve. The reusability of the structure across these settings is itself part of the contribution, because it means an intermediary need not re-derive the problem each time the jurisdiction or the client changes.

The argument matters most because of timing. In 2026 Gulf conditions the supply of institutional compliant product is no longer the binding constraint; clean distribution is. The intermediary that can take compliant product onto a conventional platform, screen and document it properly, and place it into a client mandate without friction, captures a channel advantage that its competitors lack. It does so, the central claim of this paper, without re-platforming its book.

Three implications follow for the intermediary that accepts the argument. The first is sequencing: build policy and governance before product, because the standard against which everything is judged must exist before anything is judged against it. The second is restraint in the choice of wrapper: prefer the route that reuses the most existing plumbing, usually a compliant share class, and escalate to more elaborate vehicles only as the size or bespoke nature of the allocation demands. The third is discipline in reliance: rent the certification, do not rebuild it, but assign a named owner to monitor that the rented certification remains current. Each implication points the same way, towards a thin, well-governed overlay on an unchanged conventional spine.