View Recurring Cost Logs

Modified on Mon, 5 Jan at 6:01 AM

Linarc provides a centralized log for all recurring cost payment history. This log serves as an audit trail, helping finance teams track recurring expenses over time and ensure alignment with the original cost configurations.

To view recurring cost logs

  • Ensure you are on the 'Logs' screen within the 'Recurring Cost' module of the project. If not:
    • Click the app launcher icon in the top-right and select 'Finance'
    • Click 'Recurring cost' at the top and 'History' on the left

The list view shows the approved recurring cost logs.

  • Cost code - The unique task code associated with the category/task. 
  • Name -The label of the task
  • Amount - The estimated cost value for each recurring instance.
  • Cost Relates To - The category the cost applies to. The permitted values are Material, Other, and Overhead
  • Vendor - The name of the vendor or supplier associated with the recurring cost.
  • Approved by - The designated individual responsible for reviewing and approving cost requests associated with this entry. 
  • Approved on - The date on which the recurring cost entry was approved.
  • Updated On - The system-generated date on which the recurring cost entry was updated.
  • Created By - The name of the user who edited the recurring cost configuration.
  • Status - The current state of the recurring cost entry.

Search and filter options

Sortting options

Hover over a column header and click theicon next to it to access sorting options.

  • Select 'Ascending' to sort the rows based on the values in that column, arranged alphanumerically from lowest to highest
  • Select 'Descending' to sort  the rows based on the values in that column, arranged alphanumerically from highest to lowest
  • Click 'Clear' to return to the default view

Download List in Excel Format

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article