Audit history in BE Custody helps organisations review custody-related activity and support operational oversight, investigation, reconciliation, and control processes.
The information available in audit history may depend on your organisation’s BE Custody configuration, user permissions, enabled services, and the activity being reviewed.
Why audit history matters
Audit history helps organisations understand what actions took place, when they occurred, and which users or workflows were involved.
It can support:
- Internal control reviews
- Operational investigations
- Reconciliation processes
- User access reviews
- Governance oversight
- Transaction review
- Incident analysis
- Audit and compliance processes
Audit history should be used alongside your organisation’s internal records, approvals, tickets, and control evidence.
What type of activity may appear in audit history?
Depending on your organisation’s setup, audit history may include activity relating to:
- User actions
- Transaction creation
- Transaction approval or rejection
- Governance changes
- Wallet or address activity
- Role or permission changes
- Operational events
- Report exports
- Other custody-related workflows
The exact information shown may vary by configuration and permissions.
Who can access audit history?
Access to audit history depends on the roles and permissions assigned to each user.
Organisations should restrict access to audit history to users who require it for an approved operational, compliance, audit, reconciliation, or governance purpose.
Access should be reviewed regularly as part of the organisation’s user access review process.
How should audit history be used?
Audit history can help organisations verify activity, but it should not be treated as the only source of operational evidence.
Where relevant, organisations should compare audit history with:
- Internal tickets or approvals
- Transaction records
- Wallet or address records
- Compliance records
- Reconciliation outputs
- Support communications
- Internal incident or control logs
How should exported audit history be handled?
Exported audit history may contain sensitive operational information.
Users should store and share exports only through approved systems and with authorised recipients. Avoid downloading exports to unmanaged personal devices or sharing them through informal channels.
Do not include passwords, PINs, private keys, seed phrases, API keys, API secrets, access tokens, or other sensitive authentication information in exported files, screenshots, or support requests.
What should I do if audit history looks incorrect?
If audit history does not match your organisation’s expected records, follow your internal escalation process.
If support is required, contact Bitpanda Enterprise Custody Support through the approved support channel and include relevant non-sensitive details such as the user, wallet, transaction, date, time, and activity type.