Preventing self-dealing: employee and related-party comps
A comp is cash by another name. The person who can issue it is the person most tempted to point it at themselves — and rank is the easiest lever to pull.
Most comp fraud is not exotic. It is a member of staff directing value to the one patron they care most about: themselves. A comp is discretionary and cash-equivalent, so whoever holds the pen faces a standing temptation to write it in their own favour — to a personal account, to a friend at the tables, or to a colleague who will return the favour next shift. Seniority makes it worse, because rank reads as informal leverage: "I outrank you, approve it." This guide sets out the self-dealing risk and how a delegation-of-authority model removes it by construction rather than by trust.
The problem: discretion pointed inward
Comps exist to reinvest in players, and that discretion is the point. But discretion without a boundary is an invitation. When the same person can both decide a comp is warranted and issue it, nothing structural stands between the decision and self-interest. The value can be steered to the issuer, to a friend, or to a fellow member of staff, and on paper it looks like ordinary generosity. Add a reporting line and the pressure compounds: a senior employee can lean on a junior to push a comp through, and the junior, outranked, complies. The corner cut is invisible precisely because everyone involved was "allowed" to be in the room.
Segregation of duties, by construction
AEGIS resolves authority per identity. Every comp is checked against a delegation-of-authority (DOA) matrix — role, comp type, dollar limit, and what happens on exceed — resolved at runtime against a live org chart. The consequence is simple and structural: no one simply authorises their own comp. A request that touches the requester, or that exceeds the requester's limit, cannot be self-approved. It escalates automatically up the reporting line until it reaches someone whose authority actually covers it. Segregation of duties stops being a policy people are asked to remember and becomes a property of the model — the self-approval path does not exist to walk down.
Related parties and house accounts
Self-dealing rarely announces itself. It routes value to a connected party — a spouse, a friend, a house account the issuer quietly controls. AEGIS tracks related-party and house-account relationships, so a comp directed to a connected party can be flagged rather than absorbed into routine issuance. Favours to friends and family surface for review instead of hiding in the volume. The point is not suspicion of every comp; it is that the connections which make a comp questionable are recorded, not left to whoever happens to notice.
Seniority is not authority
The most corrosive assumption on any floor is that rank equals reach. It does not — not here. A senior title confers no higher limit. Only the matrix decides who can approve which comp type up to which amount, so a senior employee cannot use position as informal authority to push a comp past a junior. The junior never held the limit, so there is nothing for rank to borrow. "I outrank you" stops working the moment authority is a fact the system resolves rather than a social pressure a person absorbs.
| Ungoverned comps | Under AEGIS | |
|---|---|---|
| Self-approval | Possible — same hand decides and issues | Impossible — escalates off the requester |
| Rank as leverage | Seniority pressures a junior to approve | No effect — only the matrix sets limits |
| Comps to connected parties | Blend into routine issuance | Flagged — related parties tracked |
| Authority basis | Informal, per person, per moment | Per identity, per amount, at runtime |
| Denied attempts | Leave no trace | Sealed to the ledger, visible to audit |
Every attempt is on the record
A control is only as good as the evidence it leaves. In AEGIS every decision — approved, escalated, or denied — is sealed to an immutable audit trail: hash-chained and anchored into a ledger the platform itself cannot alter, each record carrying its ledger anchor and the matrix version in force at the time. That last detail matters for self-dealing. A single denied attempt tells you little; a pattern of an employee reaching for their own limit, testing house accounts, or repeatedly routing value toward the same connected party is exactly what audit needs to see. Because denials are recorded, not just approvals, the shape of self-directed value stays visible even when no single attempt succeeded.
The result is a floor where the tempting shortcut is closed at the source, the leverage of rank is neutralised, and the attempts that do happen are written down where investigators can find them. For the adjacent controls, see how a delegation-of-authority matrix works and investigating comp abuse and structuring.
Frequently asked questions
Can an employee approve their own comp?
No. Authority is resolved per identity. A request that touches the requester — or exceeds their limit — cannot be self-approved; it escalates automatically up the reporting line to someone whose authority covers it. Segregation of duties is a property of the model, not a policy someone has to remember.
Does a senior manager get a higher comp limit automatically?
No. Rank does not confer authority. Only the delegation-of-authority matrix decides who can approve which comp type up to which limit. A senior employee cannot lean on a junior to push a comp through, because the junior never held the limit in the first place.
How does AEGIS catch comps directed to friends, family, or house accounts?
Related-party and house-account relationships are tracked, so a comp steered to a connected party can be flagged rather than blend in. Favours to friends and family surface for review instead of hiding inside routine issuance.
Is there a record when a self-dealing attempt is denied?
Yes. Every decision — approved, escalated, or denied — is sealed to an immutable audit trail carrying its ledger anchor and matrix version. Patterns of self-directed value are visible to audit even when no single attempt succeeded.
See AEGIS close the self-approval path
Watch a comp that touches its own requester escalate off them, and a rank-based override refuse to resolve — sealed either way.
Book a demo →