Security Invoice Discrepancy Request Checklist

A useful invoice question identifies a specific difference and gives the other party enough information to resolve it. “These hours are wrong” does neither. It may trigger a long exchange while the original issue becomes harder to trace.

For NYC hotel and property managers, a discrepancy packet should connect an invoice line to the relevant assignment and evidence without accusing anyone of misconduct or changing the underlying record. This is one step in the security-service invoice review workflow, not guidance about withholding payment or resolving legal disputes.

Define the difference before requesting an answer

Choose a category that describes what you can actually observe. An invoice can differ from a schedule because the schedule was never updated, because additional coverage was provided, or because the invoice needs correction. The initial comparison alone does not establish which explanation is correct.

Useful categories include:

Period: a date or overnight boundary needs clarification.
Quantity: the billed hours differ from the available delivery evidence.
Scope: the described post or service differs from the authorization.
Pricing reference: the invoice uses a different agreed rate reference.
Duplication: a line appears on another invoice or adjustment.
Documentation: the record needed to review the line is missing.

Use “needs clarification” until the relevant facts are established. Do not label a documentation gap as an uncovered shift solely because the supporting record has not arrived.

Illustrative property manager and security supervisor comparing paper service records at an office desk. — AI-generated editorial illustration. People, location and documents are illustrative, not an actual client or billing record.

Preserve originals and build a comparison copy

Keep the vendor's invoice exactly as received. Put annotations in a separate review sheet or clearly identified working copy. Preserve the original schedule and later changes rather than overwriting one with the other.

A compact discrepancy entry contains:

Invoice number, date and line identifier.
Property and assignment reference.
What the invoice states.
What the available evidence states, with document links.
The precise explanation or correction requested.
A named property reviewer and an agreed or requested response date.
Current status and the next action owner.

Store the comparison where the authorized reviewer can access it. Do not put employee personal details or unrelated incident narratives into a wide email chain merely to demonstrate that records exist.

Illustrative building team comparing a floor plan and operational documents to clarify the scope of a service assignment. — AI-generated editorial illustration. People, location and documents are illustrative, not an actual client or billing record.

Share relevant evidence, not the whole operational file

A coverage discrepancy may need an arrival entry, a relief record or an approved extension. It rarely needs every guest name in the day's log. Share only the portion needed for the question, through the organization's approved channel, while retaining the complete original appropriately.

Illustrative blank sequence cards beside a clock and ruler representing a chronological review of service intervals. — AI-generated editorial illustration. People, location and documents are illustrative, not an actual client or billing record.

A hypothetical request

“Invoice ABC, line 4, lists the additional lobby assignment as ending at 23:00. Our approval reference records 22:00, and the extension field is blank. Please provide the extension authorization and service end-time record, or advise whether this line needs revision.”

That wording does not assert that the officer left at 22:00. It identifies a gap between the documents and offers two useful paths to resolution. For change records, see the extra-coverage approval guide.

Keep factual explanations separate from decisions

A vendor may supply a missing record, explain an overnight allocation or propose a credit. Each is a different response. Record the evidence received first, then the authorized property review decision.

Evidence received: the supporting document arrived.
Explanation reviewed: the reviewer assessed what it establishes.
Correction agreed: the parties have documented a change.
Accounting action pending: an adjustment still needs to be issued or recorded.
Closed: the defined resolution has been checked in the appropriate records.

Do not mark an issue resolved merely because someone replied. A reply saying “we will look into it” is acknowledgement, not a correction. For time boundaries, consult the overnight and relief-hours guide.

Illustrative security officer recording an arrival at a reception desk, one source of context rather than proof of a complete assignment. — AI-generated editorial illustration. People, location and documents are illustrative, not an actual client or billing record.

Escalate the unresolved question without escalating the tone

If the requested evidence does not answer the question, identify the remaining gap and send it to the designated operational or commercial decision-maker. Follow the contract and internal approval process for payment decisions. This article does not establish a right to deduct charges, delay payment or change service obligations.

The IRS recordkeeping guidance describes supporting documents for business transactions. Linking the invoice, explanation and adjustment helps preserve that record trail; retention and tax treatment should be reviewed with the appropriate advisers.

When a correction is agreed, use the credit and reissued-invoice closeout guide. For an operational discussion about property coverage and supervision, see Guardian Consulting's security services.