A receiving clerk reports a physical discrepancy to the operations team

Guide

Supplier invoices from phones: get usable documents at the first attempt

Give suppliers a short capture instruction and a specific reason when a resend is needed. Check the document before extracting its invoice data.

Read the guide

Published

Order, delivery, acceptance and invoice records with one discrepancy

To receive a usable invoice from a phone, first request the original file if the sender has it. Otherwise, give a short instruction to photograph every page without cutting off references or amounts. Check the received document before data entry and give a specific reason when another submission is needed.

The aim is a document that is legible, complete and linked to the right record. Image quality does not certify legal or tax compliance. Confirm the requirements for your activity with the responsible professionals.

Ask for the PDF when a digital invoice already exists

A supplier creating invoices in a mobile app may be able to share the original PDF. Request it before a screenshot or photograph of the screen. Still check the file: a PDF does not guarantee all pages are present or the information is correct.

If only a paper invoice is available, a photograph may be an acceptable input for your process. The channel must be authorised and accessible to the responsible team. Avoid leaving the only copy in a personal conversation that colleagues cannot retrieve during an absence.

Start by testing a common instruction and the existing channel. Measure the resubmissions required before imposing a new tool on every supplier.

Give the sender an instruction they can follow

A useful instruction explains what to send, how to make it legible and which reference to add to the message. It avoids a list of technical terms.

Example to adapt: “Please send the original invoice PDF if available. Otherwise, photograph each page flat, with all four edges visible and no reflection over the text. Check that the invoice number, date, line items and amounts are legible. Include our purchase order reference in your message without changing the invoice.”

For multiple pages, request a clear order and a complete submission. Avoid mixing two invoices in one series of images without separation. If a page is missing, request it by page number or the expected section.

Check the image, content and record separately

The first check concerns readability: blur, glare, cropped pages or text that is too small. Google Document AI documentation identifies image quality defects on scans and photographs and explains limits to automatic detection. Source: OCR image quality.

The second concerns completeness: pages, lines, totals and other information your process requires. A clear photograph of half an invoice remains incomplete.

The third concerns the record: supplier, purchase order or service context. A document can be perfectly legible and belong to another operation. Keep a reference provided in the message as contextual information; do not present it as a reference printed on the invoice.

Request a specific correction without rewriting the document

“Non-compliant document” is too vague when the actual problem is a cropped corner. Explain what is missing and what will allow processing to resume.

Fictional example: a contractor sends a photograph with the right edge cut off. The amounts for two lines are missing. The record moves to replacement document awaited. The request says: “Please resend the whole page; the amounts on the last two lines are not visible.”

Retain the first submission and connect the new document to the same record. If the new image changes an amount or reference, check whether it is a better capture or a corrected invoice. Do not automatically replace the earlier source.

If information only the issuer can provide is missing, request a corrected document. The system should not invent it or reconstruct an invoice on the issuer's behalf.

Preserve the record without creating unnecessary copies

Store the useful document, its provenance, receipt date and associated record. Apply the access and retention rules for that workflow. If an external service processes images, check its processing terms before sharing confidential documents.

A resend may be a new photograph of the same invoice. Link it to the existing record and check the import status before creating another entry. Better image quality should not cause duplicate entry.

For receipts requiring a construction site or project code, see the construction receipt guide. That business context adds a separate control.

Measure resubmissions and improve the instruction

Track documents usable on the first attempt, requested resubmissions and their reasons: image quality, missing page, unknown reference or supplier correction. Also measure the time needed to obtain the missing document.

Test the instruction with people who actually send invoices. If the same defect recurs, show an authorised example of an acceptable capture and clarify that point. A short, understood instruction may help more than another image filter.

Kaliits can scope document intake and entry into your systems, including an exception queue before import. Prepare authorised examples and the usual reasons for requesting resubmission. Discuss your phone invoice workflow.

All articles

Related reading