Full Audit Trail for DD Financial Actions — What's New in v1.0.50
Full Audit Trail for DD Financial Actions
Released in v1.0.50
The audit log now captures every significant financial event in the Direct Debit lifecycle — giving admins and compliance teams a complete, tamper-evident record of what happened, when, and why.
Why This Matters
Direct Debit operations involve money moving across multiple accounts and services (Modulr, Griffin, and agent client accounts). Before this release, state changes and fund movements were processed without a centralised audit trail. This made incident investigation, compliance reporting, and dispute resolution harder than it needed to be.
With v1.0.50, every financial action leaves a structured log entry. Nothing happens in the dark.
What Gets Logged
Mandate State Changes
Every time a mandate transitions between states, the audit log records:
| Field | Description |
|---|---|
actor | The user or system process that triggered the change |
from_state | The previous mandate state (e.g. pending, active, suspended) |
to_state | The new mandate state (e.g. active, cancelled, reactivated) |
timestamp | When the transition occurred |
This covers all state transitions — including those initiated by admins (via the API or admin UI), automated processes (e.g. AUDDIS responses), and system events (e.g. failed collections triggering a suspension).
Collection Submissions
When a BACS collection request is submitted to Modulr, the following is recorded:
| Field | Description |
|---|---|
amount | Collection amount in GBP |
due_date | The scheduled BACS collection date |
modulr_reference | The reference returned by Modulr for this submission |
Fund Sweeps
When collected funds are swept from the Modulr collection account into the Griffin DD holding account:
| Field | Description |
|---|---|
amount | Amount swept in GBP |
source_account | Modulr collection account identifier |
destination_account | Griffin DD holding account identifier |
swept_at | Timestamp of the sweep |
Forward Payments
When the hold period elapses and funds are forwarded to the agent's client account:
| Field | Description |
|---|---|
amount | Amount forwarded in GBP |
destination_account | The agent's Griffin client account |
reserve_at_time | Clawback reserve balance at the moment of forwarding |
The reserve_at_time snapshot is particularly valuable — it provides an exact record of the reserve state that satisfied the forwarding conditions.
Clawback Events
All clawback activity (where a tenant's bank reverses a collected Direct Debit) is now captured in full, supporting dispute resolution and reserve reconciliation.
Accessing the Audit Log
Admin Activity Page
Admins can view the full audit history for their customer account from the Activity page in the admin UI. Entries are scoped strictly per customer — no cross-tenant data is ever visible.
API
Audit log entries are available via the audit/activity API endpoints. This allows consuming applications (such as agentOS) to surface audit history in their own interfaces or export it for compliance purposes.
Use Cases
- Incident investigation — Trace exactly what happened to a mandate or collection when something goes wrong.
- Compliance reporting — Provide regulators or auditors with a timestamped record of all financial operations.
- Dispute resolution — When a tenant or bank raises a clawback, the full event history is available.
- Operational transparency — Agents and admins can see which system actions triggered fund movements, removing ambiguity.