# Document activity

See who corrected a document, what changed, and the outcome of publishing or sending it.

Source: https://ziffa.io/user-guide/document-activity

Open a document and select **Activity**. Its history shows recorded events, newest first, with the person responsible and the time. Events made by the system are attributed to **Ziffa**.

## What is recorded?

| Event | What you can check |
| --- | --- |
| Saved corrections to extracted fields in **Review** | The person who saved, the time, and the before-and-after values. This includes supported nested values such as invoice line items. |
| Status changes | The previous and new status, such as Completed → Reviewed, and the person responsible or Ziffa. |
| Document-type changes | The previous and new document type and who made the change. |
| Publishing or sending through a Document Action | The attempt and its confirmed success or failure. Details can include the destination, external reference, or failure reason. |

A successful save produces one field-edit event containing the changed values. Saving unchanged values or submitting an invalid form adds no field-edit event. When an extraction model and run are known, the correction details include them; older documents may have no such information.

## Inspect a correction

Select **View details** on the edit event to compare **Before** and **After**. Changes inside a line item show its row and field. **Not set** means the value was absent; `null` means it was explicitly empty.

The history loads 25 events at a time. Use **Older** and **Newer** to move between pages. A large edit shows 50 individual changes at a time, with separate controls for more details. If loading fails, use the displayed retry control.

## Check a publish or send outcome

A started attempt records that the action began. A separate outcome confirms whether it succeeded or failed. Complete success also marks the document **Reviewed**, records that status change, and prevents further field/type editing in the interface.

For **Publish to Xero**, open **View details** for the destination organisation and created reference. If Xero created the document but its attachment failed, the reference is retained and the Ziffa document remains unreviewed. Check that existing Xero document before retrying, to avoid creating a duplicate.

An **unconfirmed** attempt has no recorded final outcome. It does not prove that the other software received nothing. Check the destination before retrying an interrupted action.

## Limits of the history

Access follows your Role's **Entities** permission: **View** or **Manage** for the relevant Entity, within the Role's **Which clients** scope. There is no separate Activity permission. See [Roles: Entities](https://ziffa.io/user-guide/settings/roles#entities) and [Which clients](https://ziffa.io/user-guide/settings/roles#which-clients) for how access is controlled.

**Export to CSV** and other download actions do not create publish/send events or mark a document Reviewed. Opening or viewing a document does not create an access entry either.

Activity describes the events above; it is not a log of every possible click, file operation or metadata change. It does not add field-edit events retrospectively for corrections made before that recording was available. The history is read-only and does not offer an undo or restore control. It remains available while the document exists.

See [Document Actions](https://ziffa.io/user-guide/document-actions) for available integrations and custom integration enquiries, or follow [Review processed documents](https://ziffa.io/user-guide/review-processed-documents).