# PolyAccounts for iPhone and iPad

PolyAccounts has a native SwiftUI iOS app. TestFlight access requires an invitation from the PolyAccounts team. The app requires iOS 17 or later and uses the same company login as the website.

## Install and open your books

1. Install Apple's TestFlight app, open your tester invitation, and install PolyAccounts.
2. Sign in with your existing email and password. An approved accounting user, administrator or owner can open their company. Restricted portal and entity-only accounts continue to use their appropriate website workspace.
3. Open Overview for net income, revenue, expenses, assets and liabilities. Change the reporting period, then tap a figure to inspect the matching ledger entries.
4. Reports includes profit and loss, balance sheet, bills and customer invoices. Ledger supports account filters, period filters, loaded-entry search, pagination and source documents.

Explore sample books on the sign-in screen without connecting an account. They are illustrative and cannot change real books.

## Code new transactions

Open Inbox and choose Code bank transactions. Review the amount and accounts, save the coding, then confirm posting. Changing a saved account requires saving and reviewing again. Possible duplicates require an explicit decision. Pending bank transactions cannot post. Match invoice and bill payments on the website so subledgers remain consistent.

Use New transaction in Ledger for a simple balanced entry. Amounts use exact decimals with up to four decimal places. Both accounts, the date and description require your review. Draft creation and posting are separate actions. Closed periods, account status, revisions and approval controls still apply. The mobile app does not execute bank payments.

## Capture receipts and emailed invoices

Use Capture in Overview or Inbox to scan with the camera, select a photo, or import a file. In Mail, open an invoice attachment, tap Share, choose PolyAccounts, then Save to Inbox. Open PolyAccounts and explicitly assign the unassigned document to your current company. You can also open supported files with PolyAccounts from Files.

Supported originals are PDF, JPEG, PNG, HEIC, plain text and EML, up to 10 MB each. Text recognition runs on the device and reads up to ten PDF pages. The complete original is retained. Text, totals and merchant names are suggestions, never automatic accounting instructions. Check the original, currency, tax treatment and duplicates before saving a draft or posting.

Saving uploads the original with its journal association and checksum. Posting changes the shared books. A receipt is not proof that a supplier payment was executed. Use the website for split entries, advanced tax and invoice workflows, payment matching and corrections.

The app receives attachments you choose to share. It does not read your mailbox automatically or create a forwarding email address.

## Privacy and interrupted saves

Sign-in tokens are stored in iOS Keychain, restricted to this device. Local receipts, pending operations and drafts use file protection and are excluded from device backups. Drafts are separated by company and user. Shared attachments remain unassigned until you choose a company. An optional device-unlock setting protects reopening, and sensitive views are covered when the app is inactive.

Save drafts before removing the app or replacing your device. Unsynced local documents will not be restored from an iCloud backup. Signing out clears the session and visible books but retains protected drafts for that same account to recover later.

If a response is interrupted, use Check saved operation. The app preserves operation keys to avoid duplicate submissions. A confirmed rejection can be corrected. An uncertain server result may require your administrator to reconcile the existing journal or receipt before proceeding. Never create a replacement posting just because the network timed out.

Uploaded documents and accounting records are stored with your company on the existing PolyAccounts service. No advertising identifier, third-party analytics or external OCR service is used by the native app. See [the privacy policy](https://polyaccounts.com/privacy).

## Developer documentation

Native sources and reproducible build instructions are in `ios/README.md` in the PolyAccounts repository. The shared Swift package is `packages/AccountingCore`. The scoped human API and recovery contract are documented in `docs/mobile-api.md`. The CLI and MCP remain available for developer and AI-agent workflows through [the CLI guide](https://polyaccounts.com/cli.md).