A security invoice is easier to review when the property can connect each billed line to an agreed service and a dated record of delivery. The invoice alone is not that record. Neither is a schedule that shows what was supposed to happen.
For NYC hotel and property managers, a useful review separates three questions: what was authorized, what the operational records support, and what the contract says is billable. Keeping those questions distinct makes a discrepancy easier to resolve without turning an administrative query into an allegation about an officer or vendor.
This guide describes a property-side review process. It does not determine employee pay, tax treatment, contractual liability or the right to withhold payment. Refer those questions to the responsible payroll, accounting or legal adviser.
Build a small evidence packet before review
Start with a stable property identifier and the exact service period, not only the building's marketing name. A portfolio may have several entrances, billing entities or post names that sound alike. Attach the relevant service agreement or purchase authorization, its effective rate schedule, the vendor invoice and the operational evidence covering that period.
Use a dated index rather than a large unsorted email chain:
- Contract or purchase reference and effective version.
- Property, post and service category, such as security guard coverage or an agreed Fire & Life Safety Director assignment.
- Approved coverage schedule and separately authorized changes.
- Available attendance or supervisor-confirmation records.
- Prior credit, replacement invoice or unresolved query references.
The IRS overview of supporting business records explains why invoices and other transaction evidence belong together. This operational packet is not a substitute for the organization's tax or retention policy.
Match each line to coverage evidence
Give every invoice line a review result: matched, awaiting evidence, awaiting contract interpretation, or corrected. Avoid a single “approved” mark on the whole document when one line remains unresolved.
A schedule is evidence of an assignment. A sign-in, supervisor confirmation or reliable attendance record may support that the assignment was performed. A daily activity report may add context but is not automatically a complete time record. Use the coverage-evidence worksheet to record what each source actually establishes.
For an overnight assignment, preserve both calendar dates. Where records cross a billing period, use the allocation rule agreed with the vendor and accounting team. Do not silently divide a shift because a spreadsheet happens to group rows by start date. The overnight and relief-hours guide explains how to preserve the sequence before applying billing rules.
A hypothetical review example
An invoice contains a regular lobby post and an additional event post for the same evening. The same building and date do not make the second line a duplicate. First identify whether two separate posts were approved and supported. Conversely, different invoice numbers do not prove two different services if one document replaced the other.
Separate exceptions from ordinary coverage
Extra hours, an added post or an extension of a temporary assignment should be tied to a documented request and a decision by someone with the appropriate authority. A message saying “please stay while we confirm” may establish an operational request without resolving the commercial terms.
Use the additional-coverage approval record to distinguish the service request, approval status and agreed billing treatment. Do not use an invoice review to remove necessary current coverage, resolve a live safety issue or instruct staff to leave a post. Those decisions belong to the authorized operational process.
Send a narrow, answerable discrepancy request
A good query identifies the line, the conflicting evidence and the exact clarification needed. “Please explain this invoice” makes the vendor reconstruct the problem. “Line 4 shows this post on these dates; our approved schedule uses a different post name. Please confirm which assignment was billed” gives the reviewer a useful starting point.
Follow the discrepancy-request packet. Preserve the original documents and record the response separately. Route decisions about due dates, disputed sums or payment arrangements to the authorized accounting and contract owners rather than inventing a policy at the security desk.
The FTC's business invoice guidance also recommends clear approval procedures and careful invoice checks. An unfamiliar sender or changed payment instruction deserves separate verification through established vendor contacts, not a reply using only the new instructions.
Close the loop with evidence, not an email promise
A vendor's agreement to issue a credit is a useful intermediate result, not proof the credit reached the account. Track the issued document, its original-invoice reference and the accounting team's application of it. Keep a replacement invoice from becoming a second payable item. Use the credit and replacement-invoice closeout guide for that final handoff.
Before marking the period reviewed
- All included posts and dates match the intended property and service period.
- Each exception has a documented resolution or a named owner and review date.
- Original records remain available alongside corrections.
- The authorized accounting reviewer has the accepted documents and unresolved items.
- Operational lessons are assigned without disclosing unnecessary employee information.
Guardian Consulting's security services can be discussed around a defined property scope and clear reporting expectations. An evidence-led review supports that conversation without promising savings or treating every discrepancy as wrongdoing.