How to document a billing discrepancy

Most billing files fail because they are a pile. Emails, PDFs, and screenshots sit in different inboxes. A reviewer who cannot reconstruct the timeline will not reconstruct it for you.

Build one folder per discrepancy. Name it with the counterparty, the invoice or claim number, and the date. Put a cover note on top. Number the exhibits. That is the file. Everything else is noise.

This guide is educational. Telvon does not guarantee a correction. A complete file is what makes pursuit possible.

Name the discrepancy in one sentence

A discrepancy file starts with one sentence: what was authorized, what was billed, and where they differ.

Start with these:

• A dated cover note that states the discrepancy in one page.
• The invoice, claim, or statement you are disputing.
• The agreement, purchase order, or policy that sets the correct amount.
• Receiving, delivery, or service records for those lines.
• Correspondence that shows you raised the gap before the window closed.
• A catch-all code that still needs a documented reply.

If the documents disagree, say so plainly and attach both. Guessing the story is how files get dismissed.

Keep the authorization next to the bill

The window is short. Missing it is treated as an uncontested dispute, not a delay you can explain later.

Put these on a calendar the day the notice arrives:

• The date the discrepancy first appeared on the invoice or statement.
• The date you requested statements, receipts, and delivery proof.
• The date the processor last asked for more documents.
• Who on your team is authorized to speak for the business.
• Where the finished PDF packet will live, with a file name the processor can open.

Do not wait for a perfect packet. File a complete one before the deadline, then add supplements only if the processor asks.

Date every document

Processors read documents. They do not sit on hold with you. A clean packet beats a long explanation.

Collect, in this order:

• The original receipt or invoice, with the same amount as the charge.
• Proof of delivery, pickup, or service completion.
• The signed ticket, terms, or booking confirmation.
• The authorization: purchase order, agreement, rate sheet, or signed estimate.
• AVS, CVV, and 3-D Secure results if the sale was card-not-present.

If a document is missing, say so. Do not fabricate a delivery screenshot or a signature.

Mark the gap in the invoice itself

One page of facts, then exhibits. Lead with the invoice number and the date of the bill.

The cover note should answer:

• What was sold, and on which date.
• How the billed amount was calculated on the invoice.
• Whether goods or services were delivered.
• Whether a refund was already issued.
• Which exhibit proves each point.
• What you are asking the other party to do: correct the billed amount.
• How to reach the person who assembled the file.

Number the exhibits. A reviewer who cannot find the receipt in thirty seconds will not hunt for it.

Store correspondence in one thread

Send only records that belong to this sale. Extra screenshots of unrelated tickets slow the review.

• Merchant copy of the receipt or invoice.
• The original purchase order, rate sheet, or signed estimate.
• Shipping label, pickup log, or signed work order.
• Contract or policy language that defines the authorized rate.
• Prior refund or replacement if one already happened.

Do not attach marketing pages, unrelated reviews, or a letter that only says the customer is wrong.

Record who you spoke with

One authorized person. Mixed stories from the kitchen, the bookkeeper, and the owner look like confusion, not proof.

Give that person:

• A written note of who at the vendor you already contacted, and when.
• The merchant ID and the case number on the notice.
• A single packet, not a chain of forwarded emails.
• A record of every call: date, name, and what was requested.
• A rule: no one else calls the bank about this case.

If you hire Telvon, that file is the work. You do not rebuild the packet while the shop is open.

What a reviewer can use

Submission is not the end. Processors ask follow-up questions, and silence is often read as abandonment.

Keep a log of:

• The date the packet was uploaded or mailed.
• Confirmation numbers from the portal.
• Any request for more documents, with the due date.
• The decision letter, even if it is a denial.
• Whether the vendor still accepts a written dispute for this invoice.

Store the log with the packet. If you later hire an advocate, that log is the first thing they need.

What a reviewer will ignore

A denial is not always the last word. It is also not a cue to invent a new story.

• Read the invoice line, not the summary total.
• Check whether the contract still has an open dispute window.
• Send only the missing exhibit, not a rewritten argument.
• If the window is closed, stop calling. The file is done.
• Keep the packet. Patterns across cases matter more than one loss.

Telvon will not tell you every discrepancy is recoverable. Some billed amounts match the agreement once you read it closely.

Spreadsheets are not the file

Reviewers look for a dated, specific packet. Vague explanations rarely move a file.

Keep:

• The invoice number, period, and line items that do not match the authorization.
• The invoice number and the exact wording of the questioned line.
• The date the charge posted and the date the notice arrived.
• The amount in dispute, the vendor name, and the invoice or claim number.
• The deadline printed on the notice, in writing, on a calendar.

Treat the file as a calendar problem first. Deadlines expire whether you feel ready or not.

Do not inflate the gap

A complete file usually includes:

• The original invoice or receipt.
• Proof of delivery, service, or attendance.
• The authorization and the invoice for the same period.
• Your refund or cancellation policy as it stood at the time.
• Correspondence that shows they knew the charge.
• A short cover note that states the request.

None of this guarantees a correction. It puts the other party in a position to review documented facts.

A discrepancy file checklist

A complete file is not a long file. It is a dated timeline, the agreement that sets the amount, the bill that departed from it, and the correspondence that shows you raised the gap in time. Extra screenshots of unrelated matters hide the exhibits that matter.

After you submit, document:

1. The date and channel you used to submit.
2. The exhibit list you attached.
3. Any items you could not produce in time.
4. A copy of the full PDF stored off the processor portal.
5. The confirmation number or reference the processor gave you.
6. The next date you are expected to hear back.
7. Who on your team owns follow-up if the file is silent.

Do not store the only copy inside a vendor portal. Export the PDF. Keep the cover note with the exhibits. If you later authorize Telvon, that packet is the handoff, not a tour of your inbox.

After the packet is together

Keep a log of:

• Dates: every notice, call, and upload.
• Names: who you spoke with and what they asked for.
• Status: open, submitted, or closed.
• Owner: the person authorized to speak for the business.
• Next date: the next deadline or expected reply.
• Ask: what you want corrected.

What Telvon will not do

• Hold, manage, or transfer funds.
• Process payments or serve as a financial institution.
• Provide legal advice or appear as counsel.
• Promise a recovery amount, outcome, or timeline.
• Replace your bank, processor, or insurer.
• Send promotional text messages.

Telvon is an advocate. You remain the merchant of record.

When to hand the file over

If you are missing the calendar, the evidence, or the time to speak for the business, that is the point to authorize an advocate.

Telvon investigates, assembles documentation, and communicates with the bank or processor on your behalf. You stay the merchant of record. Telvon does not hold the money.

Start a case when the dispute is large enough that sitting on hold is costing more than the work of handing it over.

‍