Check a Vendor Invoice Against the Approved Furnishing Scope

A vendor invoice is easier to review when every billed line can be traced to an approved scope, a documented change and a delivery or service record. Start with that comparison before deciding what the document means. A difference may be a transcription error, an approved addition that has not reached the reviewer, a different billing unit or an unresolved request. The comparison identifies questions; it does not establish contract rights, tax treatment or permission to withhold payment.

This guide walks through a fictional furnishing invoice for a short-term rental. The practical output is a short explanation of which lines match, which need supporting records and who can answer each question. It is intended for owners and coordinators who need a clearer handoff to the person authorized to approve invoices. It does not certify vendors listed in this directory or describe a real property's transaction.

Collect the documents that describe the same job

Find the approved quotation or order, the version that was actually accepted, any later written changes, the invoice being reviewed and available delivery or completion records. A draft quotation with a lower total may be useful history, but it is not automatically the correct comparison. Record the document dates and identifiers so another person can reconstruct which version you used. If the accepted version cannot be found, make that absence explicit instead of quietly choosing the most convenient file.

Keep the property and project reference visible. A vendor may have supplied similar chairs to two properties during the same month. Matching the item name without matching the delivery address or project identifier can produce a convincing but wrong comparison. Use only the minimum property information needed in the working sheet. There is no need to copy door codes, guest details or private account credentials into an invoice explanation.

Identify the reviewing roles before forwarding the packet. The coordinator may confirm what arrived, the project owner may confirm what was authorized and the accounting contact may determine how to record the transaction. Those are different questions. A delivery photograph cannot prove that someone approved a price change. An approval email cannot prove that the final installation was completed. A useful handoff names the question each record can actually answer.

Choose a comparison unit before calculating a difference

An invoice line might bill one package while the approved quotation lists individual pieces. Four chairs at seventy-five dollars each and one four-chair package at three hundred dollars may describe the same merchandise amount. Write down the unit conversion before labeling the invoice inconsistent. If the package includes assembly or freight, the conversion is incomplete until those inclusions are understood. Do not assume every similarly named line has the same scope.

Keep currency and rounding visible. A dollar sign alone does not identify a currency, and a converted bank transaction is not necessarily the amount printed on a supplier invoice. For the fictional example below, every merchandise amount is in US dollars with two decimal places. That choice makes the arithmetic easy to inspect; it is not a recommendation about accounting systems, exchange rates or how a real business should round a particular transaction.

Separate an arithmetic question from an authorization question. If five chairs multiplied by seventy-five dollars equals three hundred seventy-five dollars, the multiplication can be correct even when the approved order contains only four chairs. Calling the invoice a mathematical error would send the vendor toward the wrong answer. The question is whether there is a supporting change for the fifth chair, not whether multiplication works.

Work through the fictional merchandise example

The approved fictional order contains four dining chairs at seventy-five dollars each, two bedside lamps at forty dollars each and one rug at one hundred eighty dollars. The merchandise subtotal is five hundred sixty dollars: three hundred for chairs, eighty for lamps and one hundred eighty for the rug. Delivery is separately listed at sixty dollars. The approved comparison total before any unresolved tax treatment is therefore six hundred twenty dollars.

The fictional invoice contains five chairs at the same unit price, two lamps at forty dollars each and the same rug at one hundred eighty dollars. Its merchandise subtotal is six hundred thirty-five dollars. Delivery is sixty dollars, producing a comparison total of six hundred ninety-five dollars. The difference from the approved comparison total is seventy-five dollars. It can be located entirely in the additional chair quantity; no difference appears in the listed unit prices or delivery amount.

The correct initial note is specific: the invoice bills five chairs while the located approved order lists four; the reviewer has not yet located authorization for the additional chair. It would be premature to write that the vendor overcharged, that the fifth chair was never delivered or that the additional amount is not payable. Each of those statements needs information the worksheet does not contain. Preserve the difference while leaving the conclusion open.

Suppose the project owner then supplies a dated approval for an additional chair at the same unit price. Attach or reference that record and update the review state to supported change. Do not alter the original approved-order column to make the difference disappear. Keeping the original scope and the later addition in separate fields explains why the final invoice exceeds the first order. It also prevents a future reviewer from believing five chairs were included from the beginning.

Distinguish delivered quantity from billed quantity

A packing slip, a receiving note and an invoice can describe different stages of the job. A delivery record might show four chairs received on Monday while the fifth is scheduled separately. That does not by itself settle how the vendor is permitted to bill. Record the observed delivery state and ask the authorized reviewer to compare it with the actual agreement. Avoid converting an incomplete delivery observation into a universal payment rule.

Use the receiving record's own terminology where possible. Delivered to the building, placed in the room, assembled and accepted are not interchangeable labels. A box photographed in a hallway provides different evidence from a signed completion record. When a coordinator says the room is finished, ask what was checked and by whom. The invoice packet should make those limits visible rather than turning a casual message into a stronger certification.

If an item was substituted, link the substitution decision instead of relying on a similar appearance. A replacement lamp can have a different model number, quantity or approved price. The reviewer needs the relationship between the originally specified item, the proposed replacement and the accepted change. Keep the separate furnishing-substitution workflow as the owner of that decision; the invoice comparison should reference its result rather than approve the substitution again.

Read additional charges as separate scope questions

Delivery, assembly, disposal and storage charges should each have a clear comparison point. If the order includes delivery but the invoice adds assembly, ask whether assembly was separately requested and authorized. Do not silently absorb the charge into the furniture subtotal, because that makes the merchandise prices appear different. A separate line preserves the real question and makes it easier to request the missing supporting document.

Some quotations contain allowances or estimates rather than final amounts. Copy that qualification into the comparison. A sixty-dollar delivery estimate and a confirmed sixty-dollar delivery charge are not equivalent commitments, even when the numbers happen to match. If the final charge differs, the reviewer needs the relevant terms and any later notice, not just a percentage variance. The worksheet can flag the difference but cannot interpret the legal effect of an allowance.

Treat taxes, credits and deposits carefully. This fictional example does not determine sales tax, use tax, taxable delivery treatment or the accounting treatment of deposits. On a real invoice, preserve the printed components and refer tax or recording questions to the appropriate professional. Do not force the merchandise comparison to equal a bank debit by deleting a tax line or subtracting a deposit whose application has not been documented.

Keep invoice totals and prior payments in different views

An invoice may describe the full project value while a statement describes the balance after payments or credits. Compare the invoice to the scope first, then reconcile the relevant payment records in a separate view. Otherwise, an advance payment can make a valid project total look too high or a missing credit can be hidden by comparing only the final bank transaction. Label every total by the question it answers.

For a second fictional calculation, suppose the supported invoice total is six hundred ninety-five dollars and a recorded deposit is two hundred dollars. Subtracting that deposit produces a mathematical remainder of four hundred ninety-five dollars. That is only a reconciliation illustration. It is not confirmation that the deposit applies to this invoice, that no other charges exist or that this is the amount a real business should pay. Those conclusions require the actual records and authorized review.

Ask for a revised invoice or clarification through the vendor's normal process when appropriate. Keep the original document and the revision linked, including which version supersedes which. Do not overwrite the original file and leave two different totals under the same unexplained filename. A clear version history helps the next reviewer understand whether the difference was resolved by a correction, additional evidence or a change to the underlying scope.

Write a clarification that another person can answer

A useful request contains the invoice reference, the disputed or unexplained line, the located approved quantity and the precise record being requested. For the fictional chair example, ask for the approval reference for the fifth chair or confirmation that the invoice quantity should be revised. That gives the recipient two concrete paths to resolve the issue. A message saying the total looks wrong requires them to repeat the entire review.

Use neutral language while the evidence is incomplete. State that a document has not been located, rather than saying no approval exists anywhere. State that the receiving sheet shows four chairs, rather than claiming the vendor delivered only four unless the reviewer has reliable evidence for that conclusion. The difference matters because the recipient may hold a later approval or delivery record that was never included in the packet.

Give each open question one owner and a next review point. The owner might be the project approver for an authorization question or the receiving coordinator for a delivery question. A deadline in the working sheet is an internal follow-up reminder, not an amendment to the vendor's terms. If contractual timing is important, the authorized person should review the actual agreement. The worksheet should not create a new payment policy by accident.

Recognize suspicious invoices without mislabeling ordinary differences

The Federal Trade Commission's small-business invoice warning explains that scammers can send bills for goods or services a business did not order and that invoice messages can also be phishing attempts. Its practical emphasis includes clear approval procedures and checking invoices carefully. That warning is relevant to unfamiliar documents, but it does not mean every mismatched quantity is fraud. Keep the ordinary reconciliation question separate from a suspected impersonation or unknown supplier.

When the sender, business relationship or payment instructions are unfamiliar, follow the organization's established verification process using known contact information. Do not treat a reply to the same unexpected message as independent verification. This guide does not ask readers to send sensitive account details, open a particular attachment or change payment instructions. An invoice comparison is a document-review task, not authority to move money or update a vendor's banking profile.

Record what is known without spreading the suspicious document unnecessarily. A concise escalation can identify the claimed supplier, invoice reference and reason for concern while keeping sensitive records within the appropriate process. If a legitimate vendor simply used an unfamiliar trading name, the verification may explain it. If the document remains suspicious, the relevant business procedure and official reporting guidance can determine the next action. The worksheet does not make that determination for the reader.

Make the record usable after the project closes

The IRS recordkeeping page describes transaction summaries and their supporting documents, including electronic records. That supports the general value of an understandable record trail; it does not validate this worksheet as a complete accounting system or determine whether an expense is deductible. Keep the invoice packet connected to the business's actual records and retention process. A tidy comparison sheet cannot replace missing source documents or professional accounting decisions.

Use descriptive filenames or document references that remain understandable outside the original email thread. Include the project reference, document type and version where your organization's process allows. Avoid storing the only explanation in a private chat that the accounting reviewer cannot access. The goal is for someone with an appropriate role to follow the approved scope, subsequent change, invoice and resolution without needing the original coordinator to narrate every step.

Close an issue with evidence rather than a check mark alone. Supported change, revised invoice received and delivery question referred are different outcomes. Record the actual result and its source. If an issue remains open when the project coordinator hands over the job, preserve that open state and name the next owner. An unresolved question is more useful than an inaccurately completed task that makes the missing evidence harder to find later.

Use the downloadable example without importing its conclusions

The accompanying fictional CSV contains the three merchandise lines, the delivery line and their approved and invoiced quantities and unit prices. It is deliberately small enough to recalculate manually. Its purpose is to show where the seventy-five-dollar difference comes from and why an authorization reference is needed. It contains no real vendor, actual invoice number, property address, bank information or determination about a real payment.

When adapting the structure, preserve the difference between a blank field and a confirmed zero. A missing delivery charge does not necessarily mean delivery was free; an empty approval-reference field means the reference has not been entered. Add a note for missing information instead of supplying a plausible value. Review the resulting totals only after checking units, currency and scope. Accurate arithmetic applied to mismatched records still produces an unreliable comparison.

Handle partial credits without losing the original comparison

A credit can resolve one line while leaving another question open. Suppose the fictional vendor issues a seventy-five-dollar credit for the additional chair. The invoice comparison total of six hundred ninety-five dollars less that credit returns to six hundred twenty dollars. That arithmetic matches the original comparison total, but the reviewer should still identify the credit document and verify which invoice it references. A credit mentioned in an email is not the same record as a credit that has been issued and applied in the business's system.

Do not delete the fifth-chair line from the review history. Show the original billed quantity, the credit reference and the revised reconciliation state. This makes the resolution visible and avoids making a corrected transaction look as though it never required clarification. If the credit applies to a later purchase instead, the current invoice and the later account statement may need different explanations. Ask the authorized accounting contact how the actual documents should be connected.

When several properties share one vendor account, keep credits tied to their source projects until the appropriate reviewer confirms any allocation. A credit for a damaged lamp at one house should not be casually used to explain an extra chair at another. The numbers may offset while the underlying records remain unrelated. A short project-reference column can prevent that confusion without adding guest details or unnecessary personal information to the packet.

Frequently asked questions

Does an invoice above the quotation prove an overcharge?

No. It establishes a difference between the records being compared. A later approved addition, a different package unit, an allowance or a missing credit may explain it. Locate the accepted scope and subsequent changes, identify the exact line causing the difference and request the supporting record. Whether a particular amount is owed depends on the actual agreement and authorized review, not the presence of a variance alone.

Can a delivery photograph approve a billed change?

A photograph may help describe what was observed, but it does not automatically establish purchasing authority or approved price. Keep delivery evidence and authorization evidence in separate fields. In the fictional example, a picture of five chairs might help with the receiving question while leaving the approval question unresolved. Refer each question to the person who can answer it using the relevant source record.

Should I compare the bank debit directly with the merchandise subtotal?

Usually those figures answer different questions. The debit may reflect a deposit, taxes, a credit, multiple invoices or another recorded adjustment. First compare the invoiced scope with the approved scope, then examine the payment records separately. Preserve the components rather than modifying them until the totals appear equal. This guide illustrates reconciliation structure and does not determine a real business's accounting entries.

What if the vendor uses a different item description?

Look for a model reference, package definition or accepted substitution record that connects the descriptions. Similar wording or appearance is not enough to prove identical scope. Record the relationship you can support and ask for clarification where it remains uncertain. If a substitution decision already exists, link that decision instead of using the invoice review to make a second, undocumented approval.

Is an unfamiliar invoice necessarily a scam?

No. An unfamiliar document deserves verification, especially when the business relationship or payment instructions are unexpected, but uncertainty is not proof of fraud. The FTC describes fake-invoice and phishing risks for small businesses. Follow established procedures using known contact details, keep the authorization process clear and distinguish a suspicious sender from an ordinary line-item discrepancy. Do not change payment instructions based on this worksheet.

What should the final handoff contain?

Provide the approved scope reference, later changes, invoice version, relevant delivery records, the line-by-line comparison and the evidence supporting each resolution. Name the owner of every remaining question. Include separate payment or tax questions only as clearly labeled referrals to the appropriate reviewer. The final packet should explain what was checked and what remains uncertain without implying vendor certification, legal conclusions or permission to pay.