Transfers

Move inventory between FBO accounts with approval workflows

Transfers move inventory items between FBO accounts. They support batch operations, approval workflows, and full audit trails to ensure every asset movement is tracked and authorized.

How transfers work

Transfers operate in batches. A transfer batch groups one or more individual item transfers from one FBO account to another into a single operation.

Transfer Batch
├── From: FBO Account A
├── To: FBO Account B
├── Items:
│   ├── Transfer 1: Item X
│   ├── Transfer 2: Item Y
│   └── Transfer 3: Item Z
└── Status: pending → approved → completed

Transfer reasons

Each transfer has a reason that categorizes why the movement is happening:

Reason	Description
Request	The account holder requested the transfer
Trade	Items are being exchanged as part of a trade
Rebalance	Internal portfolio rebalancing between accounts

Approval workflow

Transfers follow a structured approval workflow:

Status	Description
Pending	Transfer has been requested and awaits approval
Approved	Transfer has been approved by vault staff
Denied	Transfer has been rejected
Completed	All items have been successfully moved
Partially Completed	Some items in the batch were transferred

Only Beach Depositories staff can approve or deny transfers. Transfer requests can be initiated by organization admins.

Cross-organization transfers

Transfers can occur:

• Within an organization — between FBO accounts under the same organization (initiated by org admins)
• Across organizations — between FBO accounts in different organizations (initiated by vault staff only)

Audit trail

Every transfer action is recorded:

• Transfer creation (who requested, reason, notes)
• Status changes (approval, denial, completion)
• The specific staff member who approved or denied
• Timestamps for each state transition

Transfer events are also recorded in the inventory event log, creating a complete chain of custody for every item.