CertPas

SAP Concur · Troubleshooting

Why SAP Concur Receipt Timestamps Become Ineligible: Image Requirements and Next Steps

A practical guide to checking receipt-image requirements, separating ineligible from invalid, and choosing the next step.

From receipt image to the next stepAn original learning diagram for checking the image, reviewing its details and timestamp status, narrowing down the cause, and choosing the next step.CERTPAS · TIMESTAMP CHECKCheck the receipt status step by step1Receipt imageOriginal file2Image detailsDPI · pixels3Timestamp statusIneligible · invalid4Find the causeRequirements5Next stepRecord · consultFrom receipt image to the next stepA vertical learning diagram for checking the image, status, cause, and next step.TIMESTAMP CHECKCheck the receipt status1Receipt imageOriginal file2Image detailsDPI · pixels3Timestamp statusIneligible · invalid4Find the causeRequirements5Next stepRecord · consultRecord the status and choose the next step
An original diagram for checking the image and choosing the next response.
Updated 2026-08-148 min readBeginner to intermediate
On this page
  1. If Concur says ineligible, start with the image
  2. Ineligible and invalid are not the same result
  3. The image-creation method changes the numbers to check
  4. Check the original record before taking a new picture
  5. When the result does not change, bring the evidence to your administrator

If Concur says ineligible, start with the image

When SAP Concur shows an Ineligible timestamp status, it is easy to suspect a workflow or configuration problem. The first useful check is usually the receipt image itself.

For Japan e-Bunsho timestamp processing, SAP Help lists an image below 3.88 megapixels as one possible reason for an ineligible result. A receipt can look clear on screen and still fail a technical requirement, so visual readability is not enough to close the investigation.

Ineligible and invalid are not the same result

Ineligible means the image does not meet the conditions for timestamp processing. Invalid means the image failed a validation check.

That distinction changes where to look next. For an ineligible result, start with image dimensions, resolution, and color mode. For an invalid result, examine how the image was handled and what the validation process reported. The status is a clue, not a reason to change settings at random.

What to check for ineligible and invalid statusesAn original comparison diagram: check image requirements for ineligible and record status for invalid.CERTPAS · CHECKPOINTSCheck ineligible and invalid separately!IneligibleCheck image requirements200 dpi3.88 MPRGB 24-bit×InvalidCheck the record statusMissing recordStatus mismatchRecord the resultSeparate image requirements from record statusWhat to check for ineligible and invalid statusesA vertical comparison diagram for image requirements and record status.CHECKPOINTSCheck ineligible andinvalid separately!IneligibleCheck image requirements200 dpi3.88 MPRGB 24-bit×InvalidCheck the record statusMissing recordStatus mismatchRecord the resultSeparate image requirements from record status
Ineligible and invalid require different checks.

The image-creation method changes the numbers to check

For a scanned image, check whether the resolution is above 200 dpi. For an image captured with a smartphone or digital camera, check whether it exceeds 3.88 megapixels. RGB color at 24 bits or higher is another requirement to verify.

Do not rely on zooming in on the screen. Open the original file properties and compare the resolution, pixel count, and color mode with the relevant requirements.

Check the original record before taking a new picture

Keep the original image according to your company process, then record how it was created, whether it was compressed or converted to black and white, and what status Concur shows. Create a new image only after you have evidence that the current file does not meet the requirement.

A Pending or Requested status does not by itself prove that the image failed. Record the status and time before replacing a file that may still be processing.

When the result does not change, bring the evidence to your administrator

If the image appears to meet the numerical requirements but remains ineligible, check whether a smaller copy was registered after passing through email or another application. Comparing the original file properties with the file stored in Concur can narrow the cause.

If the reason is still unclear, give your Concur administrator the status, creation method, resolution, color mode, and occurrence time. Contract details and organization-specific settings can change the operational response.

Back to all articles