Work already held on this device
The native app reads its local planning store. Existing supported local records and calculations do not become new bank information merely because you can view them without a connection. Keep the date of any confirmed balance visible.
Access still follows the app's existing subscription and sign-in rules. Being offline does not create a new free plan or guarantee a first-time subscription verification can complete. Reconnect when the app needs to verify access or obtain remote information.
Changes that have not synced yet
A change can be saved locally before the account receives it. Check the Sync section's actual status and any remaining-change explanation. Do not assume a successful local edit has already appeared on another device.
When the connection returns, the app handles its supported sync process. If it explicitly asks you to sign in again, use that route. There is no need to invent another copy of the same expense simply because the second device has not received it yet.
Information that needs a connection
Bank updates, remote price lookups, account verification and connected services require their own available connection and permissions. A saved value can be older than the current market or bank record. Offline access does not make an old figure current.
Keep missing or stale rates visible rather than inventing a conversion. A locally saved quote is still a quote with a date, not proof of a new transaction or a guaranteed future price.
Before moving to another device
Reconnect and check the reported sync state. Keep your original device and records available until you have confirmed the expected information on the other device. Do not erase, reinstall or sign out as a routine way to fix an unresolved sync difference.
See using a second device, confirmed balances and Payday versus Transactions for the separate jobs of stored data, current money and the plan.