fax
By L'équipe MondialFax

Fax delivery receipt: proving your fax actually arrived

A fax marked "sent" isn't necessarily a fax that was "received". We explain how to read a transmission report, which result codes to watch for, and how to archive your receipts so they hold up with a counterparty — or a judge.

Short answer: a fax is only considered transmitted if you keep the technical record of its delivery, i.e. a transmission report showing the date, time, number dialled, page count and a positive result (OK, Success, code 0). That record, generated by the fax machine or by your online fax service, is the only thing that distinguishes "I sent it" from "the recipient received it". Without it, your transmission has no evidential value whatsoever, however perfect the document may have been.

It's one of the questions that comes up most often through our contact form: "How do I prove my fax actually went through?" The answer deserves more than a single line, because behind the slightly grand phrase "delivery receipt" there are in fact three very different things, which differ in both reliability and usefulness.

Three concepts not to be confused

The transmission report

This is the document produced by the sending device or service at the end of the call. It summarises what the machine observed: number dialled, timestamp, call duration, number of pages transmitted, negotiated speed, result. On a physical fax machine, it's the small sheet that prints automatically (or on demand) after the send. With fax-to-email, it's the confirmation email you receive, often including a thumbnail of the first page.

It's by far the most useful piece of evidence in day-to-day practice.

Delivery confirmation on the recipient's side

In traditional faxing, the T.30 protocol provides for a tight dialogue between the two machines: each page received is acknowledged by an MCF (Message Confirmation) message sent by the receiver. In other words, when your report says "4 pages OK", it isn't your machine congratulating itself: it genuinely received four acknowledgements from the machine at the other end. This particularity is what long gave the fax its reputation compared with plain email, where nothing guarantees that the remote server accepted the message.

One caveat, though: the acknowledgement covers the electronic reception of the pages, not their printing, nor their reading, nor the fact that the right person ever had them in hand.

The read receipt request

It doesn't exist in the fax world. No standard allows you to require the recipient to confirm they have read anything. If you need that level of assurance, you have to switch to another channel: registered electronic mail, a secure exchange platform or, more simply, a confirmation phone call noted in your file. We cover this in more depth in our comparison of fax versus secure messaging.

Two rotary landline telephones sitting on an empty desk, with a chair and a metal filing cabinet

Reading a transmission report line by line

The labels vary between manufacturers and operators, but the fields are always the same. Here's how to interpret them.

FieldWhat it meansWhy it matters
Date / TimeTimestamp of the start or end of the callEstablishes that a deadline was met
Number dialledThe number actually dialled, country code includedProves you targeted the right recipient
Remote ID (CSID)String announced by the receiving machineCorroborates the recipient's identity
DurationLength of the callAn abnormally short duration betrays a truncated send
PagesNumber of pages acknowledgedTo be compared with the document's page count
Resolution / SpeedStandard, fine, superfine; 14,400 bit/s, 9,600 bit/s…A downward renegotiation signals a degraded line
ResultOK, NG, Error, numeric codeThe verdict

The most overlooked field is the remote ID. Many businesses leave the fax machine's factory default in place, but when it is properly configured it provides a valuable clue: it shows that the machine that picked up did indeed identify itself under the name of the firm or public body you were targeting. If you manage your own devices, take five minutes to set this identifier to your company name and number: it's free and it strengthens every report you produce from then on.

The second poorly read field is the page count. An OK result on 3 pages when your file ran to 7 is not a success: it's a partial failure. The recipient did receive something, but an incomplete document, which is sometimes worse than nothing. Always check that the figures match.

Result codes that should set off alarm bells

Fax error messages are inherited from the T.30 protocol and fall into a handful of families.

  • No answer : the line never picked up. A common cause in 2026: a number still printed on letterhead when the analogue line was cancelled as the copper network was switched off.
  • Busy : the line is engaged. Online services generally retry several times automatically; a poorly configured fax machine may give up after two attempts.
  • No fax tone : someone or something picked up, but there was no fax modem at the other end. Typical of a number that has become a voice extension or a switchboard.
  • Communication error mid-page : the connection was cut. On VoIP, it's almost always a signal transport issue, a subject we cover in detail in our article on T.38 failures.
  • Compatibility error / Incompatible : the two machines failed to find a common mode. Rare, but possible with very old equipment or overly chatty gateways.

Our practical advice: never retry the exact same send three times in a row when it fails with the same code. A repeated failure with the same cause signals a structural problem, not bad luck. Call the recipient, check the number, test with a single page.

Online fax: a richer receipt than paper

The move to fax-to-email has quietly improved the quality of the evidence, for three reasons.

The receipt is natively digital. A confirmation email timestamped by a mail server and kept in a work mailbox is far easier to find two years later than a yellowed thermal slip at the bottom of a binder. Thermal paper rolls have a limited lifespan anyway: the print fades with light and heat, and many businesses have discovered too late that their old reports had become illegible.

It carries a copy of the document. Most platforms attach the PDF that was actually transmitted, or at least an image of the first page. That way you prove not only that a call took place, but what you sent — which is often the real point of dispute.

It is tied to a searchable log. Your account's send log reconstructs the full history: attempts, retries, intermediate codes. An isolated report can be challenged; a coherent log, with its failures and its successes, is far more credible precisely because it clearly wasn't manufactured for the occasion.

If you nonetheless need to produce a paper file, print your receipts on a laser printer rather than on thermal paper, and file them in clear punched pockets together with the corresponding document. It's rudimentary, but a well-kept file always makes a better impression than a stapled bundle.

Hands handling a tangle of colourful electrical cables laid out on a workbench

Build a body of evidence, not a single proof

Under French law, faxes fall under the principle of free proof in dealings between professionals: the judge has full discretion to assess their evidential weight. In practice, nobody will ask you for a magic document — what will be examined is the overall consistency. The right reflex is therefore to stack several elements that corroborate one another.

A solid body of evidence includes:

  1. The document sent in its exact version, with its dated cover page.
  2. The corresponding transmission report, with a positive result and matching page count.
  3. A log entry showing the sequence of attempts.
  4. A contextual record: a note in the file, an internal email reading "fax sent at 2:12 p.m.", a note of a confirmation phone call.
  5. Where applicable, a duplicate via another channel (email, post) with its own record.

That last point is underrated. Backing up a sensitive fax with a courtesy email ("further to our fax of today's date…") takes two minutes and creates a second, independent line of evidence, with the advantage of bringing a real person's name into play rather than a machine's.

A small self-inking date stamp kept next to the scanner also helps keep the team disciplined: every incoming or outgoing item carries its date of arrival, which makes reconstructing a timeline six months later considerably easier.

The five mistakes we see most often

Not enabling automatic report printing. On many fax machines, the factory setting only prints the report in case of error. The result: you only have a record of your failures. Switch the setting to "always".

Confusing the cover page with the receipt. The cover page is part of what you send; it proves nothing about reception. It remains essential for identifying the sender and the expected page count — our template is set out in the article on the fax cover page.

Trusting an interface's "Sent" label. Some services display a "sent" status as soon as the job is queued. The only status that counts is the final one: delivered, failed, or abandoned after retries. Wait for it before closing the file.

Not checking the dialling code. An international send that goes out with a missing 00 or a retained national leading zero will fail or, worse, end up with a complete stranger. Our supported countries page sets out the expected format for each destination.

Leaving receipts in a personal mailbox. If confirmations land in an individual employee's named address, they disappear along with them. Route them to a shared mailbox such as fax@, with a clear archiving folder.

For firms handling high volumes, a duplex desktop scanner combined with monthly PDF filing prevents paper from piling up while keeping everything instantly accessible. And if you hold sensitive archives, a lockable filing cabinet remains the simplest way to reconcile accessibility with confidentiality.

How long should you keep your receipts?

The common-sense rule: as long as the document they accompany. A receipt only has value when paired with its document. So align its retention with that of the file: the duration of the commercial relationship plus the applicable limitation period for a contract, or the sector-specific statutory period for accounting, employment or medical records. In practice, we recommend never purging a receipt on its own, and treating the document + report pair as an indivisible unit in your filing plan.

On the confidentiality side, don't forget that these confirmations contain personal data: numbers, names, sometimes a legible image of the first page. They therefore fall under the same protection regime as the fax itself, with the data minimisation and security obligations that entails.

Frequently asked questions

Does an "OK" report mean the recipient has read my fax?

No. It means the remote machine acknowledged reception of the pages. It may then run out of paper, be out of service, or drop the document into a tray nobody ever checks. For critical sends, a confirmation call remains irreplaceable.

Can I request a receipt from my provider several months later?

That depends on its log retention policy, often somewhere between a few months and a few years. Don't count on it: download and archive your receipts as you go — that's your responsibility, not the provider's.

The report says "OK" but the recipient claims they received nothing. What should I do?

First check the number and the remote ID on the report: the most common error is a transposed digit that sent the fax to a third party. If the number is correct, resend while explicitly telling the recipient the time of the first transmission, and keep both reports.

Does online fax produce a receipt as solid as paper?

It produces a more usable one: digital, timestamped, accompanied by the transmitted document and backed by a log. Legal weight doesn't come from the medium but from the consistency of the record, a subject we develop in our article on the legal value of faxes.

Should failure reports be kept?

Yes, counter-intuitive as it may seem. A failure report proves you attempted the step within the deadline, which may be enough to demonstrate your diligence. It also justifies falling back on an alternative channel.

Key takeaways

  • A fax delivery receipt is the transmission report: date, number, pages, result.
  • The T.30 protocol has each page acknowledged by the receiving machine: that's what makes a fax more probative than a plain email.
  • Always check that the page count matches: a partial OK is not a success.
  • No receipt proves reading: back up critical sends with a call or an email.
  • Set your devices to print the report every time, not just on error.
  • Centralise confirmations in a shared mailbox, never in a named individual address.
  • Archive the document + report pair together, for the same retention period.
  • A body of consistent records is worth more than a single item.

You can test how receipts behave right now by sending a document from our send form: the report will reach you by email, with a breakdown of the pages transmitted. And if you're wondering about reception, our receive a fax page explains how to pick up incoming faxes directly in your inbox.

Tagsfaxsecurityplatformpaperless

Back to the news

Read next