Use entry history for individual records
Lexoh entry history is the detailed view for locating and reviewing recorded entries and their available associations. Use it to investigate a session or reconcile a known record. Use entry statistics for aggregated arrival patterns and the relevant occupancy report for recorded presence.
An entry record is not automatically proof of a completed physical passage or a payment. Establish what creates the record in your installation and distinguish credential validation, an equipment command, detected movement and any manually entered information.
The visible list depends on your permissions, filters, data received and retained history. It should not be described as a complete log of every physical arrival without checking that coverage.
Check your scope before using the controls
Open the entry-history view available to your role and identify the search field, filters, refresh control and result count. The arrangement may differ by screen size and software version. On a compact view, open a record’s details to see information omitted from its summary.
Viewing records, filtering, exporting and changing records can require different permissions. If an expected control is unavailable, ask the administrator to verify your intended role and site scope. A visible or hidden button alone does not establish how access is enforced.
Wait for loading to finish before interpreting an empty list. A failed request, restricted scope and a successful search with no matches are different outcomes. Keep the error message and the time of the request if loading fails.
Locate a known entry before narrowing the search
- Start with a stable entry reference when available, or a known time and entrance. Keep the site and time zone with the reference.
- Use fields that the current search actually supports. If searching a name, plate or device gives no match, try the corresponding available filter rather than assuming every displayed field is searchable.
- For an autocomplete filter, wait for results and select the intended record. Typed text is not necessarily an applied selection. Distinguish people or devices with the same name by their references or other known details.
- Apply the search as required, wait for completion and verify the active selections and result count. Check the displayed page after changing the search.
- Open a matching record and compare its reference, device and time with your evidence. Clear or adjust one condition at a time if the known record is missing.
Verify how combined filters select records
Use available customer, operator, company, device, tag and zone filters to define the population needed for the review. Check whether a device filter refers to the entry device, exit device or either; the label alone may not resolve that distinction.
Confirm how multiple selections combine. Selecting devices A and B might mean either device, while selecting a customer and a device may require both conditions. Verify the behavior against known records before relying on a combined result.
Company, zone and tag associations can change. Determine whether the filter uses the association recorded at entry time or the current association. A company name or zone label does not establish the physical entrance or the access rights that applied.
Review the selected values before applying. When resetting, check which selections and dates actually clear; saved defaults may still affect the list. Do not interpret missing suggestions as proof that a customer or device does not exist.
Define dates and record types explicitly
Record the exact start, end and time zone. Verify which timestamp is filtered: entry, exit, creation or another field. A session that starts before the range and ends within it may be included or excluded depending on that choice.
Check boundary behavior with known records near the start and end. A date-only end value does not, by itself, establish whether the whole final day is included. Available date choices do not prove that records exist or have been retained throughout that range.
Customer, user and guest categories describe recorded associations. A customer does not necessarily have a paid subscription; a guest is not necessarily anonymous; an associated operator is not necessarily the visitor. Keep entity type separate from an entry-event type or payment status.
Investigate payment labels through linked transactions
Use amount and payment filters to identify records for review, then open the linked transaction or billing information. An entry-level label alone does not establish an amount due, a payment’s settlement or the financial result of a visit.
Confirm the amount field, currency, tax treatment and handling of multiple related transactions. Check whether a range includes its endpoints and whether zero differs from an unset amount. Do not assume that minimum zero and maximum zero selects every complimentary or permit-based visit.
Paid
Check what produces this label and review the actual transaction, amount and any later reversal or refund. Do not treat the entry label as proof of deposited funds.
Unpaid
Determine whether payment is required, still pending, failed, absent or represented elsewhere. Verify the applicable charge and billing record before using this result for a customer reminder. The entry date is not automatically a payment due date.
Payment not required or no amount
A permit, staff rule or another arrangement may change how a visit is charged. Confirm the actual rule and linked records. A blank or zero amount alone does not establish a complimentary visit.
Read the record and its related evidence
Available fields vary by installation and permission. Use this checklist to interpret the information shown in the list or detail view; it does not promise that every field or linked view is available.
| Information | Interpretation and check |
|---|---|
| Record reference | Use the stable reference to compare the list, details and export. Similar names or times do not establish a duplicate. |
| Customer, operator, credential and vehicle | Confirm the role of each association. A credential or vehicle link is not proof of the holder’s identity. |
| Entry/exit device, zone and tags | Check device direction and historical versus current labels. A zone association is not evidence that a particular barrier moved. |
| Entry/exit timestamps and duration | Confirm time zone, event meaning and how the session is matched. A blank exit can reflect an open, missing, unmatched or delayed record; it does not prove current physical presence. |
| Amount and payment status | Follow the linked transaction and applicable rule. Displayed duration may differ from billable duration, and a status may not reflect later adjustments. |
| Camera or event associations | Confirm the time, device and relationship to the session. A thumbnail is not proof that a playable recording exists or that it covers the entire visit. |
Adding or correcting a record
If your version and role allow changes, follow the site’s correction procedure. Record the reason and original values, verify the intended fields, save, reopen and check related reports. A manual entry is not automatically a command to open an entrance. Changing a displayed amount or status is not evidence that a payment was taken or refunded; use the appropriate transaction workflow.
Verify the exported population and values
- Confirm permission and define the records needed. Record the search, selections, exact period, time zone and displayed result count.
- Check the available export format and scope: selected rows, the visible page or all matching records. Use the supported export action and wait for completion.
- Open the result and verify the file is readable. Compare the row count and a few known record references with the intended population; account for header rows and repeated transaction or detail rows.
- Check available timestamps, time zones, identifiers, amount fields and currency. Preserve leading zeros in identifiers when opening or transforming a file.
- Keep the original file with the report settings and generation time. If splitting a large period, document the boundaries and reconcile overlaps or gaps.
- Share only the necessary fields through the approved channel. Follow the site’s retention process. An entry export alone is not a tested system backup or proof of complete audit coverage.
Distinguish page size from the result total
Use the available page-size and navigation controls to inspect the matching set. The number of rows shown on one page is different from the total number matching the filters and from the number selected for export.
Illustrative example: 63 matching records at 25 records per page require 3 pages. Page 1 shows positions 1–25, page 2 shows 26–50, and page 3 shows 51–63, or 13 records. These positions are not the entry IDs.
After changing search, filters or page size, verify the current page and count. New or updated records can change the order while you browse. Use a stable sort where supported and preserve the export time when a reproducible snapshot is needed; do not assume that a saved page preference or default ID sort applies.
Resolve discrepancies before drawing conclusions
An expected record is missing
Check the site, permissions, exact date field, time zone, search and applied filters. Confirm that loading succeeded and that the device’s record reached the system. A blank list alone does not prove there was no activity.
Two records look alike
Compare references, event times, credentials and directions. Distinguish repeated attempts, legitimate re-entry and delayed records before proposing a correction. Preserve the source records.
The export and screen disagree
Compare scope, filters, generation time, row granularity and later updates. Check a known record in both sources. Report the actual difference instead of assuming that the export or screen is complete.
Counts do not explain occupancy
An entry list records activity; presence also depends on starting occupancy, exits, matching and corrections. Use the relevant occupancy report and verify its data coverage.
Hand off a reproducible case
Provide the record references, site/device, exact period and time zone, selected filters, expected result and observed result. Include only the personal or credential details needed for the investigation.