Import a statement
Map a bank CSV or read a PDF, then approve rows once.
Importing reads a file you already have. It does not sign in to a bank, and the App Store release has no bank connection to offer instead. The file stays on this device until you choose to attach a piece of it to an entry.
Bring the file in
Any of these opens the same review:
- Upload a file inside FIA
- New Entry → Documents, the inbox of PDFs already handed over
- Shared with Chicken Bank, for a picture, PDF, CSV, or text another app shared
- File → New Entry from File… on a Mac, or a file dropped on Transactions
A PDF is read on the device, a few pages at a time. The inbox says Reading, or stopped when the app closed. If it stopped, it says Stopped. Open it to go on. When it knows the pages, that line still says to open it to go on, and names how many pages were read. If there is not enough space, it says Stopped: not enough space. Open it to go on. A locked file says Locked. Open it to enter the password. Rows waiting say 1 entry to review. An approved file says Done. A failed read says FIA couldn't read this one. Archive only moves it between lists. Delete removes the original and its drafts on this device. Entries you already approved stay.
A locked PDF asks for the password and does not store it. Balance rows, subtotals, carried-forward totals, and a card charge the bank has not finished are not entries. A row that is not finished cannot be saved into the book. When the bank later finishes that charge, that finished row is the one entry.
Map a CSV
Before any row is read as money, you confirm the columns: date, a signed amount or money out and money in, currency, payee, memo, a balance column if there is one, and the bank's own reference. You also confirm whether the first row is a header, which date order the file uses, which mark is the decimal, and which sign is money out.
The first rows are shown as those choices read them. Continue stays off while a date or a decimal mark is still ambiguous, and while the decimal mark you chose would misread an amount. The mapping is remembered for the next file with the same header. A file of another shape asks again.
The same file chosen again, under any name, resumes the job. It does not post the rows a second time.
Approve
Review is the same Save as a receipt. One save posts the selection or nothing.
- Two identical coffees in one file stay two entries.
- A row that matches an entry you already have, in the same wallet, direction, and amount, within a few days, waits as possibly already in the book. Keep as new posts it. Already in my book does not.
- A later correction from the bank is Changed at the bank. Update entry adds a new change only where the entry still holds what you saved from the file, and it keeps edits you made after that. Keep mine declines the bank's change. The answer is remembered.
- A credit that reads as a refund is proposed against the latest earlier purchase at that payee, from that wallet, that can still take it. You can refuse the link.
- A row that pays a bill, a debt, or an open invoice can be proposed as that payment. Not a bill payment, or None of these, leaves it as an ordinary entry. Approving it as the payment posts once, not as spending and as the payment.
A balance column is a check. It is not an entry, and it does not overwrite the wallet. If the book's figure and the statement's figure differ, reconcile.
Attach a piece of the original
On an entry that was read from a picture or a PDF, Attach Part of the Original… starts from the pages that entry came from. The preview is a new image of those pages: no hidden text, no links, no camera data, no location. Attach stays off until that preview is ready. People in a shared book, on a build that shares, see only that file. Remove takes it off the entry. A copy someone already saved outside the app is not recalled.
Last updated on