When a vendor record looks different, start with the vendor’s Activity tab to review who changed what and when. Use UnitConnect’s Audit Log when you need a broader view or want to narrow the history by date, person, record type or action. Open the relevant entry to inspect field changes where available, then share the filtered view with the colleague who can explain the change.
This is a record-history investigation, not a reason to edit the vendor immediately. A logged update tells you what the software recorded; it does not, by itself, explain why the person made the change or whether the team approved it.
Start with the vendor, not every event in the account
If you know which vendor is involved, open Vendors in the sidebar and find it in the list. The list’s search matches a vendor’s name, type or code. Select the intended record and open Activity.
The current vendor activity guide distinguishes two useful tabs. Activity lists changes to the vendor record. Transactions lists expenses recorded against the vendor. Use Activity for “Who updated this vendor?” rather than treating a list of bills as a history of edits.
Confirm the record before following a suspicious-looking entry. Similar names can make it easy to investigate the wrong vendor, particularly when several team members work across properties. Keep the vendor’s identifying information with your notes so a colleague can reproduce the review.
Widen the search only when the question needs it
Open Audit Log under System in the sidebar. Alternatively, View all on Home’s Recent activity card opens the log. Access requires permission to view activity. If the option is missing, ask your UnitConnect administrator rather than assuming there is no history.
The log includes account activity such as invoices emailed, charges added, payments recorded and vendors deactivated. To keep a vendor investigation focused, use the controls documented in the Audit Log guide:
- Date range provides presets such as Last 30 days and All time, plus custom dates.
- Search summary, type, action… looks for words in the summary, record type or action.
- More filters, shown as a funnel, narrows results by Actor, Entity and Action. Entity means the record type, such as Vendor or Invoice.
Begin with the period in which the discrepancy was noticed and the relevant entity. If you do not know who made the change, leave Actor open until an entry gives you a reason to narrow it. Filtering to the person you suspect first can exclude the event you are trying to find.
If a search is unexpectedly empty, inspect the active filters and date range before concluding that nothing happened. Clear removes all filters, so use it when you want to restart the search rather than preserve part of the current view.
Read the event before interpreting it
Each Audit Log row shows When, Actor, Action, Resource and Module. Actor identifies the user associated with the change, or System for an automatic change. Resource summarizes the event and identifies the affected record; Module identifies the area of UnitConnect it came from.
Read those columns together. A user name alone does not tell you which record changed. Likewise, a broad Updated action does not tell you which value is different. Click a column heading to sort, and use the page controls at the bottom when matching results span several pages. The filter bar shows the total number of matching records.
Open the relevant row. Its detail panel shows the actor, time, module and audit record number. It also shows the related property when there is one. The record chip at the top opens the affected record, providing a way to compare the event with the current vendor information.
Use field details where they exist
Under Field changes, a recorded old value appears crossed out beside the new value. That is the place to check the specific difference instead of guessing from a row’s summary.
Some actions display No field-level detail for this action. When that happens, report the limitation as part of the finding. Do not reconstruct an old value from memory and present it as something the log proves. You can still use the event’s actor, time, action and resource to ask a focused follow-up question.
The log is also not a documented one-click undo control. Treat finding an event and deciding how to correct the current record as separate tasks. If the present value is wrong, confirm the intended replacement with the responsible colleague before an authorized user edits it.
Example: a description changed during a team handoff
Imagine that a portfolio coordinator notices that the description for a hypothetical vendor, Meridian Supply, is more specific than it was earlier in the week. They want to know whether a colleague clarified the description or whether somebody changed the wrong record.
The coordinator opens Meridian Supply’s Activity tab first. If more context is needed, they open Audit Log, set the relevant date range and choose Vendor as the entity. They do not initially filter to a particular actor because they have not yet established who made the update.
Suppose an entry identifies an update by Jordan. If its field details show Description changing from “Regional supplier” to “Regional electrical supplier,” the coordinator can report that exact difference and the displayed time. These names and values are illustrative; the available detail must be checked in the actual account.
If the entry has no field-level detail, the finding is narrower: an update was recorded for this vendor at that time, but the panel does not establish the old and new description. The coordinator asks Jordan about the change rather than filling in the missing history.
After that conversation, the team can decide whether the current description is appropriate. The vendor details guide documents Description as an editable vendor field and requires permission to edit vendors. A history review does not grant that permission or replace the decision about the correct value.
Share the view and the question together
Audit Log filters are stored in the page address. Copy the browser address to share the same filtered view with a colleague. Send it with the vendor identifier, audit record number and the question you need answered. A link without context can leave the recipient unsure which row matters.
For example: “Please review the Meridian Supply update at the displayed time. Is the current description intentional? The field-change panel shows the previous and new wording.” If the panel lacks detail, say that instead.
Use your team’s appropriate internal channel and a colleague with the necessary account access. Sharing a filtered address is a way to preserve the search context, not an instruction to make account history public or bypass access controls.
Want to see how vendor Activity and Audit Log work together in your team’s workflow? Schedule a UnitConnect demo and walk through a focused record-history review before your next staff handoff.
