Protect the existing data first
Do not uninstall, reset, or delete periods as a first troubleshooting step. Keep original paystubs and export a complete backup when the app can read its records. If a recovery screen offers export of unreadable data, preserve that file before replacing local data.
Never change real work facts just to make a comparison green. An error or incomplete result is preferable to a convincing but unsupported answer.
Work and setup problems
| Problem | Check next |
|---|---|
| The rate or a number is rejected | Follow the field’s decimal-point instructions. Remove currency words or ambiguous separators. Hours and money have different precision limits. |
| Save work is unavailable | Verify End is after Start, the dates are inside the open period, and no existing entry overlaps. Use View conflicting entry. |
| An overnight shift has the wrong duration | Set the correct next-day End date. Review payroll timezone, unpaid breaks, and any daylight-saving transition. |
| A different work draft opens | A saved unfinished entry takes precedence. Finish it, keep it, or explicitly discard it before beginning another. |
| Work or a draft was not saved | Keep the form open, note the error, check storage, and retry. Do not assume a preview or typed value is a committed record. |
Expected pay or an audit looks wrong
Review in this order: correct period → complete work → unpaid breaks → base rate and applied rule version → supported premium combination → paystub current-period values → gross basis → earnings layout.
Not ready to compare usually requires confirming complete work or what gross includes. Needs review can reflect missing coverage, conflicting lines, uncertain mapping, or work changed after the audit. Read the specific reasons before re-entering anything.
If gross matches but a component differs, check full-rate versus premium-only reporting and guarantee placement. If the paystub is higher than expected, check missing work and pay types as carefully as you would a shortfall.
A calculation problem around a dated change or callout guarantee should not be replaced with zero. Keep the work and establish the unsupported or ambiguous rule. Supported limits explain common boundaries.
Scanning and imports
If the scanner is absent, use a supported photo/file route or Enter manually. If camera permission is denied, use Open iOS Settings or an alternative input method.
For unreadable text, review the saved original and confirm fields manually. For a failed cloud-file import, make sure the file is downloaded and available through Files. Check storage and use a readable PDF or image without destroying the source.
If another period owns a review draft, resume it from the correct period or explicitly discard the unfinished review. Do not attach the wrong paycheck simply to continue.
Backup or restore trouble
A saved-to-location message does not prove that iCloud upload has completed. Verify the file in Files. A JSON data export or audit PDF is not the complete restorable backup.
If restoration rejects a file, preserve it unchanged, confirm it is a LinePaycheck backup, check available storage and app-version compatibility, and retry. Restoration replaces records rather than merging; always preserve the destination records you need first.
If original-file cleanup remains pending, use Privacy and local data → Retry original cleanup after resolving the cause.
Pro does not appear active
Check the Apple account and subscription state. Use Restore Purchases to refresh access. Pending approval, expiration, billing retry, or revoked access are not the same as an active verified subscription. An App Store product-loading failure should not make existing local records disappear.
For unresolved problems, send a focused support request with the app version, iOS version, affected action, and a redacted example. Do not include passwords or unredacted wage documents.
Still unsure? Keep your original records and get help before changing facts to make a total match.