Symptoms
A long receipt is cut into two images even though it was scanned once.
Keep the original configuration intact for the first comparison. A long receipt is cut into two images even though it was scanned once. A one-variable test is easier to undo and produces a more reliable conclusion.
- The failing path: A long receipt is cut into two images even though it was scanned once.
- Control test: Scan a short page and a long receipt with auto-edge detection enabled, then compare.
- A successful outcome: One saved scan contains the entire receipt and readable totals.
Why It Happens
Retail output has at least three stages: application data, printer formatting and the physical scan or receipt. Verify the last stage with a disposable item.
There are three genuinely different layers worth checking; use the observation in the table to decide which one is implicated. None of these is proven merely by the symptoms.
- Auto edge detection sees fold. This explanation predicts a different result in the comparison test or the more advanced inspection.
- Receipt exceeds scan area. This explanation predicts a different result in the comparison test or the more advanced inspection.
- Multi-page capture enabled. This explanation predicts a different result in the comparison test or the more advanced inspection.
Before Making Changes
Keep the original paper receipt until the final digital copy is verified.
Save the current configuration or capture screenshots of the exact option values; where a file or recording is involved, work on a disposable duplicate. If this is shared equipment, ask the owner or administrator before changing it. Prefer a safe test item over real customers, medical decisions, paid transactions or irreplaceable data.
Write down the device model, platform, observed time of failure, and which action still works. These details will distinguish an unsupported feature from a malfunction and will be useful if escalation is required.
Problem-Specific Diagnosis
Use the following route rather than guessing based on a product name. The expected differences are designed for this particular failure.
| Action or observation | Meaning of the result | Decision |
|---|---|---|
| Scan a short page and a long receipt with auto-edge detection enabled, then compare. | Does the failure follow the affected file, profile, connection or location? | Keep this result as the baseline; do not alter two systems at once. |
| Use document/receipt mode or manual border capture without auto-splitting. | Does the low-impact correction restore the exact failure without altering the control case? | Re-test; reverse the change if the original symptom is unchanged. |
| Check page boundary detection, contrast against background and multi-page auto-capture behavior. | Does this separate receipt exceeds scan area from multi-page capture enabled? | Use documented diagnostic views rather than blind replacement. |
| One saved scan contains the entire receipt and readable totals. | Is the same original symptom gone after a normal repeat? | Record the pass condition and preserve the working settings. |
If the control case fails as well, the fault may be broader than this guide. Stop at that point and check the shared power, account, access or media path before applying the narrow fix.
Beginner and Advanced Paths
Start with the reversible Beginner path. The Advanced path examines a different layer when the first route fails; it is not a repetition of the same restart or setting.
Step-by-Step Troubleshooting
Choose the simple reversible checks first, then investigate the deeper system layer only if necessary.
Record the exact failure
Confirm the behavior without guessing: A long receipt is cut into two images even though it was scanned once. Note the affected account, file, connection or physical control and record the current settings. Keep the original paper receipt until the final digital copy is verified.
Run the passing comparison
Scan a short page and a long receipt with auto-edge detection enabled, then compare. Keep the working and failing cases separate. If both fail, stop and investigate the common path instead of forcing a narrow repair.
Apply the least disruptive correction
Use document/receipt mode or manual border capture without auto-splitting. Change only this setting or route; do not reset unrelated profiles, storage or pairing records. Save the previous value so it can be restored.
Retest and keep the result
One saved scan contains the entire receipt and readable totals. Repeat after a normal reopening or reconnect. If the control case gets worse, undo the last change and write down the difference.
Separate the three underlying layers
Test the hypotheses independently: auto edge detection sees fold; receipt exceeds scan area; multi-page capture enabled. A green status indicator does not distinguish them. Use the recorded control case as evidence.
Inspect the deeper component
Check page boundary detection, contrast against background and multi-page auto-capture behavior. Use only read-only diagnostics or documented configuration screens first. Capture logs and timestamps rather than removing the component or reinstalling software blindly.
Cross-check with an independent path
Where possible, repeat “Scan a short page and a long receipt with auto-edge detection enabled, then compare.” using a second supported account, safe sample file, physical input, known-good cable or alternate compatible application. Change only one variable and note which outcome follows it.
Choose a reversible targeted escalation
If the deeper check isolates a fault, use a vendor-supported fix or authorized service for that layer; otherwise restore original values. Finish only when: One saved scan contains the entire receipt and readable totals. Keep the original paper receipt until the final digital copy is verified.
Solution Checklist
Solution Checklist
Common Mistakes to Avoid
- Treating auto edge detection sees fold as certain just because the behavior looks familiar.
- Changing several independent settings together, which makes the result impossible to interpret.
- Skipping the safety boundary: Keep the original paper receipt until the final digital copy is verified.
- Calling the issue fixed after one status indicator changes but before repeating the original operation.
- Discarding the working configuration or the only original file before a replacement has been verified.
How to Verify the Fix
One saved scan contains the entire receipt and readable totals.
Use the same baseline case: Scan a short page and a long receipt with auto-edge detection enabled, then compare. Then repeat the previously failing operation after a normal close-and-open, reconnect or next scheduled cycle, whichever matches the scenario. Confirm the part of the system that was already working is still unaffected.
Where a result can be measured, retain the test timestamp, file name, screenshot or device state. A temporary success that cannot be repeated is not yet a confirmed repair.
If the Problem Continues
Escalate from the surface symptom to the narrower mechanism: Check page boundary detection, contrast against background and multi-page auto-capture behavior. If this identifies a hardware, account-policy or service limitation, use the manufacturer’s authorized support route rather than bypassing controls.
When opening a support case, supply the model, software/firmware version actually installed, the failing operation, the successful comparison, the three possible explanations checked, and the final observed result. Redact account identifiers, access codes, serial-number photos and personal information from public posts.
Prevent Recurrence
Keep a short note of the confirmed working configuration, particularly the setting implicated by auto edge detection sees fold. Repeat the disposable comparison after an app update, device replacement, major account change or new connection only when that change plausibly affects this issue.
Retain a recovery path: spare test material, a saved profile, a restore point, a backup copy or official service information, as appropriate for the device. Do not schedule risky resets as routine maintenance.
FAQ
Is auto edge detection sees fold definitely the reason this happens?
No. The same symptom can come from receipt exceeds scan area or multi-page capture enabled. First compare the affected and unaffected paths: Scan a short page and a long receipt with auto-edge detection enabled, then compare. Do not assume any cause without a different outcome.
How can I safely rule out receipt exceeds scan area?
Try the reversible correction only after documenting the control: Use document/receipt mode or manual border capture without auto-splitting. If the behavior does not change, restore the old value and use the deeper observation: Check page boundary detection, contrast against background and multi-page auto-capture behavior.
What if multi-page capture enabled turns out to be responsible?
Do not force an unsupported setting or a factory reset. Keep the evidence and ask the manufacturer or responsible administrator to investigate the isolated layer. The measurable pass condition remains: One saved scan contains the entire receipt and readable totals.