Bank accounts and cards
Statement-fed accounts, manual accounts, credit cards and how PhinApp works out each day's balance.
Accounts live under Banking Transactions → Bank accounts. There are two ways of keeping an account up to date, and each account uses exactly one:
| Connected account (statement) | Manual account | |
|---|---|---|
| How it is created | By itself, on the first import of the bank's statement | By hand, with the previous day's balance |
| Where transactions come from | Imported statements | What somebody types |
| Accepts manual entries | No | Yes |
| Meant for | Checking, savings, investment accounts, cards | Petty cash and accounts with no statement |
Connected account
Create a connected account asks for nothing: just import the bank's statement. Bank, branch and account number come from the file itself, and the bank is recognized by its bank code - the name written in the file changes from one export to the next, the code does not. From then on, every new statement for the same bank and number lands in the same account - in the same format as the first (OFX, PDF, CSV, QIF or Excel), shown beside the account in the list. See One format per account.
A connected account does not accept manual entries. It is whatever its statements say it is: an entry typed by hand would only last until the next import contradicted it, and until then it would skew every balance worked out from it. If a transaction is missing, a statement is missing - import the period that is not there.
Manual account
Create a manual account asks for the type (Checking, Savings, Credit card, Cash or Investment), the bank, the account number and the previous day balance. For petty cash, instead of a bank and a number, a name is enough - it is the only thing that tells two of them apart.
The opening balance is an anchor
The balance given at creation is what the account held at the close of yesterday, as on the bank statement. It becomes an anchor: each following day's balance is the anchor plus everything entered since.
- The anchor cannot be edited afterwards. If it is wrong, the fix is to enter whatever is missing, not to change the number.
- Entries dated before the anchor can be recorded too - and then it is the past that moves: the anchor is a fact, so money we did not know about means the earlier balances were different.
Currencies
Every account has its own currency, and every amount in it is in that currency: a dollar account at a Brazilian bank is a dollar account.
- For a manual account, the currency is chosen at creation, and starts as the organization's main currency.
- For a connected account, the currency comes from the statement: an OFX declares it, and PDF, CSV and Excel files print it -
R$on the amounts or in a heading such as Valor (R$). Only when a file shows no currency at all (Inter's and Nubank's CSV exports, for instance) does PhinApp ask, on the import that creates the account, with the main currency already chosen. See The account's currency. - An account's currency never changes afterwards: it is the currency of everything already recorded in it. Changing the organization's main currency changes no account.
PhinApp never converts amounts between currencies: figures in different currencies are shown side by side and never added together. On the Overview, each card shows the main currency large and the other currencies right below it; the cash flow has one cash flow per currency; and a transfer between currencies records how much left one account and how much arrived in the other.
Credit cards
A card's balance is what is owed on it, which is why it is negative.
- Closing and due days. Every card has a statement closing day and a due day (1 to 30). A card's PDF bill states both, and the card is set up from it; the first time a card's OFX is imported, PhinApp asks for the card's name and those two days - card OFX files do not include them. For a manual card they are asked at creation, together with the open statement up to yesterday, which comes with the minus sign already in place.
- Each purchase counts on the day it posts to the card, like any other transaction. In Banking Transactions, the Card Due date column shows which bill it will be paid on, and the Due date filter gathers the purchases of one bill.
- Paying the bill is a transfer from the checking account to the card: not an expense, because the purchases it pays for were already counted when they happened. The payment printed on the bill is recognized and linked on its own to the checking account's debit of the same day and amount.
- Instalment purchases. Parts the issuer has already posted become card transactions; parts still to come become open payables, one per month, and are reconciled by themselves when the statement brings them. A part the statement brings that nothing reconciles yet - usually this month's, on the first bill the purchase appears on - gets a payable of its own, with its number (3/12), already linked to it as a suggestion in Reconciliation: the series is complete, and this month's part is not mistaken for the following months'.
The system account
A card's first statement usually carries the payment of the previous bill - which PhinApp knows nothing about. So that this credit does not read as income, PhinApp writes the other leg of the transfer on a system account, which appears in no balance and no filter, and leaves the link as a suggestion under Reconciliation. If the debit that paid that bill is already in the checking account, nothing is written: the two are linked (see how). That entry can be deleted; it disappears by itself if the previous month's statement, or the debit that paid the bill, is imported later.
Each day's balance
On connected accounts the balance comes from the statements themselves: every import uses the balance stated in the file to settle the days it covers that have already ended. When two balances stated by the bank do not add up with the transactions between them, something is missing - and PhinApp says so instead of hiding it:
- the import result shows a Balance discrepancy, with the account, the period and the difference;
- the Actuals show a Missing entries row in that period, kept out of cash generation, because nobody knows what that money was.
The warning goes away by itself once the missing statement is imported.
Deleting an account
Only manual accounts can be deleted, and only while none of their transactions has been reconciled - a reconciled transaction is the payment of a title, and the title, the audit trail and the balances all point at it. The confirmation says how many unreconciled transactions go with it. A statement-fed account is whatever its imports say it is; the way to set one aside is to stop importing into it.