Audit Logs (Finance, Plan & Budget)

Short Description Hive9 maintains three audit logs — Finance Log, Plan Log, and Budget Audit Log. This article covers what each captures and how to investigate changes.

What this article answers

• The three audit logs and what each tracks.
• How to filter and search them.
• How to investigate a specific change.

The three audit logs

All three require role permissions to view. Most admin roles see them by default.

Finance Log

Access: Menu → Settings → Audit Logs → Finance Log.

Filter Column options

• Year
• Budget
• User
• Type of Edit (Budget Event Type, Budget Item Event Type)

Multi-select within filters. Click the action button at the bottom of the Filter Column to apply.

Grid columns

• Date — when the edit was made.
• User — who made the edit.
• Budget — name of the budget edited.
• Budget Item ID — unique system identifier.
• Budget Item — name of the row edited.
• Action — the edit type.
• Value Prior — pre-edit dollar value (if amount edit).
• Value After — post-edit dollar value (if amount edit).
• Difference — net change.

Controls

• Row count selector.
• Go To Finance Budget — jump directly to the Finance Budget section.

Plan Log

Access: Menu → Settings → Audit Logs → Plan Log.

Filter Column options

• Date Range
• User (who made the edit)
• Owner (who owns the edited item)
• Tactic Type

Per-column inline filtering also supported — type a column value and the grid narrows to matching rows.

Grid columns

• Date — date of edit.
• User — editor.
• Object Type — Plan, Campaign, Program, Tactic, Line Item, PR, PR Line.
• ID — unique system ID.
• Object Name.
• Year — Plan Year of the object.
• Action Type — Create or Edit.
• Attribute — the attribute that was edited.

Controls

• Row count selector.
• Go To Plan Grid — jump to Plan Grid for further investigation.

Budget Audit Log

The Budget Audit Log captures every budget change in detail. Fields:

• When the change happened.
• Who made it.
• Which budget and which budget item (ID).
• Action.
• Prior value.
• After value.
• Difference.

Filter by date / budget name / user / action. Can include deleted budgets in the filter — useful when investigating where removed budget activity went.

Per-line audit log available via an icon on a budget line — clicking filters to that line only.

[SCREENSHOT NEEDED — Budget Audit Log with filtered entries showing prior/after values]

How to investigate a change

1. Identify the suspected change — what was the value, when did it look wrong?
2. Open the right audit log — Plan Log for tactic/line item changes, Finance Log for finance budget changes, Budget Audit Log for detailed budget line changes.
3. Filter to the affected object and a date range that brackets when you suspect the change.
4. Scan in reverse chronological order — earliest entries show prior state; later entries show the edit.
5. Identify the user — visible in the User column.
6. Reach out to that user — they may have context. If not, the prior value is captured for restoration.

Common questions

Why don't I see the audit log option? Permission is role-controlled. Ask your admin or check your role's settings — Plan and Measure tabs have audit log permissions.

How far back do audit logs go? Retention varies by configuration. Default retention is generally long, but if you need to confirm, ask your CSM.

Can I export audit log entries? Yes — most audit logs support CSV export. Look for the export icon on the grid.

Are changes from integrations logged? Yes — integration-driven changes are recorded with the system identity, distinguishable from manual user edits.

What if I see a change but I don't know what it's for? The audit log shows what changed, not always why. Ask the user who made the change for context.
 

Related articles

• Finance Budget — snapshots and audit log
• Plan Log details
• Creating, editing, and deleting users
• Workflow lifecycle (activate, deactivate, delete)