Symptoms
Automatic page detection omits the bottom line of long receipts. This guide addresses that particular contrast, not every fault that can occur with the product or service.
- Observable failure: Automatic page detection omits the bottom line of long receipts.
- Control test: Compare manual corner adjustment with auto-crop for the same receipt.
- A confirmed correction must meet this outcome: All lines including subtotal and tax remain legible in output.
A working state in another app or device is a useful control only when the account, source material and operating conditions are comparable. If they differ, that comparison may produce a misleading conclusion.
Why It Happens
A PDF can contain page images, a searchable text layer, annotations and form fields that behave independently. Visual correctness in one viewer never guarantees that hidden text, signatures or export layers are correct.
The symptom alone cannot distinguish edge detector loses low-contrast border from camera perspective. Evidence related to receipt longer than supported capture area changes the next action, so record the comparison before applying a fix.
Three competing explanations
- Edge detector loses low-contrast border.
- Camera perspective.
- Receipt longer than supported capture area.
These are hypotheses. Do not infer a hardware defect, account restriction or network outage from one status indicator alone. A result that supports edge detector loses low-contrast border does not automatically exclude camera perspective; the comparison needs to separate them.
Before Making Changes
Work on a duplicate PDF and retain the unmodified original, especially when text recognition, signatures or redaction are involved. Retain the original image until extraction is checked.
Preserve the current state: note the affected product or account, current mode and time of the failed attempt. If settings will be changed, photograph or write down their original values. Keep copies of any unique files or evidence before overwriting anything.
Use a non-sensitive sample whenever possible. If the issue involves a shared device, building system, workplace account or regulated equipment, obtain the appropriate owner or administrator permission first. Stop if the test would compromise security, electrical protection, access or an animal's welfare.
Problem-Specific Diagnosis
Run this discriminating test before restarting or resetting the entire system: Compare manual corner adjustment with auto-crop for the same receipt. Compare the observed result against the three paths below.
| Observation or suspected layer | Interpretation | Next controlled check |
|---|---|---|
| Edge detector loses low-contrast border | If the failing state changes under the comparison, edge detector loses low-contrast border is plausible. This is not yet proof. | Repeat with that one factor changed, then return to baseline. |
| Camera perspective | If the first change has no effect but a supported configuration differs, camera perspective moves higher on the list. | Inspect the relevant option or documented behavior without clearing unrelated settings. |
| Receipt longer than supported capture area | If both earlier paths are contradicted, investigate whether receipt longer than supported capture area accounts for the timing or device-specific result. | Collect an event timestamp or status report for qualified support. |
Now apply the least-disruptive change that corresponds to the evidence: Use manual corner controls and include a visible margin around the entire receipt. Avoid treating all three hypotheses at once; simultaneous changes erase the diagnostic value of the test.
Step-by-Step Troubleshooting
Begin with reversible comparisons. Use Advanced only if the evidence points to a deeper problem.
Verify the affected workflow
Automatic page detection omits the bottom line of long receipts. Write down where it happens, its most recent time and the state displayed by the product. Do not treat a nearby working feature as proof the whole path is healthy.
Run the safe comparison
Compare manual corner adjustment with auto-crop for the same receipt. Use the same device, account and operating conditions where practical. Note what remains unchanged so the comparison is meaningful.
Try the smallest safe intervention
Use manual corner controls and include a visible margin around the entire receipt. Make one adjustment at a time and preserve the previous value so it can be restored if the result becomes worse.
Confirm the real outcome
All lines including subtotal and tax remain legible in output. Repeat the complete user-facing operation and then make sure unrelated protections and functions still work. If the result is inconsistent, restore the previous setting and continue diagnosis.
Separate the three suspected layers
Assess evidence for edge detector loses low-contrast border, camera perspective and receipt longer than supported capture area separately. A positive result for one path is not evidence for every path. Preserve before-and-after observations, including timestamps.
Check the responsible subsystem
Test a multi-shot or longer-document scanning mode when supported, verifying stitched text. Gather only logs and supported diagnostic views that apply to this exact scenario; do not change service-wide policy or hardware wiring.
Validate the unaffected path
Revisit the comparison: Compare manual corner adjustment with auto-crop for the same receipt. If the first suspected cause is not supported, compare the behavior predicted by camera perspective with the behavior predicted by receipt longer than supported capture area. Keep the first correction reversible.
Commit or escalate with evidence
Confirm: All lines including subtotal and tax remain legible in output. If that cannot be reproduced, restore the original safe configuration and send sanitized observations to the document originator or PDF software vendor. Safety boundary: Retain the original image until extraction is checked.
Solution Checklist
Solution Checklist
Common Mistakes to Avoid
- Assuming edge detector loses low-contrast border is proven simply because the visible symptom matches this page.
- Changing multiple accounts, rules, connections or device settings before running the control: Compare manual corner adjustment with auto-crop for the same receipt.
- Skipping this safety boundary: Retain the original image until extraction is checked.
- Resetting, formatting, deleting credentials or replacing hardware without a confirmed backup, a supported recovery path and evidence that the step is necessary.
A setting that makes one symptom disappear is not always the correct permanent configuration. If it disables another essential function, revert it and investigate the underlying dependency rather than leaving an unsafe workaround in place.
How to Verify the Fix
The primary pass condition is specific: All lines including subtotal and tax remain legible in output. Repeat the original workflow, not a loosely related shortcut, and confirm both the previously failing behavior and an unaffected comparison still work.
- Record the before-and-after state in the same location, account and operating mode.
- Repeat the original comparison: Compare manual corner adjustment with auto-crop for the same receipt.
- Check the stated pass result: All lines including subtotal and tax remain legible in output.
- Confirm that normal security, notification, storage or physical safety protections remain enabled.
If the result works only once or disappears after reopening the app, reconnecting the accessory or waiting for the next scheduled event, treat the issue as intermittent instead of fixed. Keep the event time and what changed between attempts.
If the Problem Continues
If the safe correction does not work, move to a focused deeper investigation: Test a multi-shot or longer-document scanning mode when supported, verifying stitched text. This is a different path from the first settings check; use it only if the device or service supports the required diagnostics.
When escalating to the document originator or PDF software vendor, provide the exact symptom, result of the control test, changes already tried, time of occurrence and any non-sensitive error or status data. Explain whether edge detector loses low-contrast border, camera perspective and receipt longer than supported capture area were supported or contradicted by evidence.
Do not share account recovery codes, private documents, live access tokens, sensitive location histories or full recordings merely to prove the problem. Redact or summarize identifiers before opening a public support request.
Prevent Recurrence
Keep a short reference note with the working configuration and the successful check: All lines including subtotal and tax remain legible in output. After an app update, firmware change, network migration or scheduled clock change, run the same short test before depending on the function again.
Watch for the condition that originally made the failure visible: Automatic page detection omits the bottom line of long receipts. Where practical, retain an alternative approved way to perform the essential task so that one device, cloud service or interface does not become a single point of failure.
FAQ
How can I tell whether edge detector loses low-contrast border is responsible?
Run the controlled comparison: Compare manual corner adjustment with auto-crop for the same receipt. A change that specifically affects the failing layer supports this hypothesis, but repeat it before changing permanent settings.
What if the real cause is camera perspective rather than edge detector loses low-contrast border?
Do not repeat the initial correction blindly. Check the supported diagnostic path: Test a multi-shot or longer-document scanning mode when supported, verifying stitched text. Keep the earlier working configuration recorded so you can reverse the test.
When is this particular issue resolved?
The decisive result is: All lines including subtotal and tax remain legible in output. If it fails after the normal workflow is repeated, document whether receipt longer than supported capture area still explains the remaining behavior and escalate with non-sensitive observations.