> For the complete documentation index, see [llms.txt](https://docs.mastersindia.co/accounts-payable/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mastersindia.co/accounts-payable/invoice/audit-trail.md).

# Audit Trail

Audit Trail is a feature that enables the users to keep a track record of the progress of invoice stages and see who approved or rejected the invoice and what is their comment for the same.

For viewing Audit Trail of an invoice follow these steps -

1. Go to the invoice module and find the required invoice in the listing.
2. Go to the right most side and find the “Audit Trail” button.
3. The audit trail will display Accepted steps in Green and the Rejected step in Red. Users can add their Comment before accepting / rejecting the invoice. The comment made by the user will be displayed below the step.
4. The audit trail will also display the date of action made by the user.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mastersindia.co/accounts-payable/invoice/audit-trail.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.