Pilot structure
A pilot starts with a limited reporting scope.
Typical starting scope:
- one legal entity
- one custody environment or wallet group
- selected spot assets
- one reporting period
- one ERP output target
This keeps the work focused and gives the team a concrete result to review.
What happens in a pilot
1. Scope and ownership mapping
Define the entity, wallet and custody accounts, ownership mappings, and reporting dates.
2. Data ingestion and historical backfill
Collect the wallet, custody, and supporting source data needed for the period under review.
3. Balance and inventory reconstruction
Build a ledger view of the activity and replay balances and inventory through the reporting period.
4. Reconciliation review
Identify:
- transfers between company-controlled accounts
- unresolved or ambiguous items
- missing ownership mappings
- differences against source systems or existing books
5. Output generation
Produce:
- reconciliation reports
- inventory rollforwards
- supporting schedules
- journal-ready outputs where relevant
What success looks like
At the end of a pilot, a team should be able to answer:
- what was held
- where it was held
- which movements were internal transfers
- what still requires classification or follow-up
- what the period-end inventory was
- what should reach the books
Who the pilot is best for
The pilot is usually most useful for teams that already have:
- digital assets on the balance sheet
- some operational complexity
- an existing spreadsheet or internal process
- an ERP for the final books
- a need for clearer support before close or audit review
Why start this way
A limited pilot reduces implementation risk and makes evaluation concrete. Instead of comparing product claims, the team can review one reporting scope and decide whether the output is clearer and more useful than the current process.
Request a pilot
Use the contact form
to request a pilot or share your current workflow.