Transactions and titles
Banking transactions, payables and receivables, manual entries, transfers, instalment purchases and recurrences.
Banking Transactions
Account Management → Banking Transactions lists everything that came into and went out of the accounts and cards. The columns follow the order the questions get asked in:
- Transaction - what the bank wrote, exactly as it is on the statement;
- Description - the name of the title the transaction settled (blank until it is reconciled);
- Partner - who it was with. A transfer shows a dash: it is between two of the company's own accounts, so there is nobody on the other end;
- Category - the classification from the chart of accounts.
The search box looks at the first three at once: typing "rent" finds the transaction whose title is called Rent, even if the bank wrote "TED 4406.49020". The filters - period, account, category, partner, reconciliation status, inflow or outflow, amount - run on the server, over every transaction, not just the ones on the page. The partner filter has a Not identified option: the pile of transactions that do not yet say who they were with. In Amount, type the figure without a sign (150 or 150.00): it finds the inflow and the outflow of that amount, unless Entry type says which one.
Columns your way
Right-click any column heading (on a phone, touch and hold) to hide it or bring it back. Drag the heading to change the order, or its right edge to change the width. The preference is saved in your browser.
Clicking a transaction opens it: that is where you classify it, pick the partner and reconcile it. On an imported transaction, date, amount and description do not change - they are the bank's quotation. The classification sits at the bottom of the window, after the reconciliation: when raising a title, picking the partner fills it in with their default category. A payment that settled more than one thing can be split across several titles, and unclassified transactions can be classified with AI - after the classification rules.
A transaction with no partner or no classification can be completed in the list itself: each of those empty fields is a search on the row. Picking a partner with a default category on an unclassified transaction classifies it too. Once filled in, they are changed on the transaction. When reconciling with a title already on file (Find title), the title's partner appears right above the classification and can be chosen there - their default fills in the classification. The classification starts as the title's, and whatever is in the field when you reconcile is what counts: choosing another one there writes it on the title and on the transaction.
Classification rules
A rule says "this is always so": the same description, on the same account, always under the same classification. Entries that arrive unclassified - from statements, from the ERP or typed with no classification - go through them before anything else.
PhinApp learns rules by itself. When you classify a description, on one account and with the money going one way, a rule is born - the first time, or after as many alike classifications as you ask for under Settings → Organization details → Entries to learn a rule (1 to 20; 1 to begin with). Dates, times, document numbers and amounts do not count: "RESERVA PROGRAMADA 12/08" and "Reserva programada" are the same description, and the amount is never part of a learned rule. One different classification among those entries and nothing is learned - and a rule that already existed becomes Conflicting until they agree again. An ERP title teaches by the partner's ERP code and the description - or, with no description, the partner's name.
Three things teach nothing:
- what the AI classified. Only a person teaches: if the AI classified two alike entries and you correct one of them, your correction stands - the rule is born and the other entry is reclassified. A rule with nothing but the AI's answers behind it is retired, and what it classified counts as the AI's classification again;
- what only repeats the partner's default. An entry classified with its own partner's default is already explained by the default, and a rule saying the same thing would only stand in front of it. A learned rule that came to say only what the default says is retired;
- split transactions, transfers and whatever another rule classified.
A rule for any partner is only learned from entries with no partner identified, or from at least two different partners: one partner's entries teach only that partner's rule.
A new rule applies to what is open too. When it is born - learned or written by you -, or when a partner is given a default category, the open transactions and titles with that description (or of that partner) are reclassified at once: the unclassified ones, those classified by the AI, and those classified by a rule further down the order. A rule you save (or apply from the ⋯ menu) also reaches what a person classified, and puts its result's partner on the open entries; only a rule earlier in the order keeps what it classified. Otherwise what a person classified never changes by itself, and nothing already reconciled ever does.
A rule knows who it was with. When the entry has already identified the partner - by the tax ID on the statement, by the ERP code or by the boleto's payer - the rule can be that partner's and applies only to their entries. An any partner rule gives the classification and leaves each entry with the partner it identified - or none: two boletos of the same amount, on the same day, from two customers, each keep their own customer. Only a manual rule with a partner in its Result changes the partner - see below.
The order is always the same: transfers and card bill payments first; then your manual rules, by priority; then the learned ones - the partner's before the any-partner one; then the partner's default category on the side the money moved; and only then the AI.
What a rule classified shows a list icon next to the classification: hover to see which rule, click to open it. If somebody changes the classification - or the partner the rule filled in - of such an entry, the rule is suspended, with the date and the entry that suspended it. It does not come back by itself, not even when the classifications agree again: only if somebody reactivates it.
Where to see and write rules
Settings → Rules lists them all in the order they are tried - the Priority column gives each one's place (and, on a manual one, the priority you gave it) -, with their conditions, result, origin (learned or manual), status, how many times each was used and when. The search looks in the conditions and the result: a partner's name, a description, a classification. There you can write your own - equal description or one that contains a text, account, partner, tax ID, ERP code (not in a family), document number, amount range -, edit, suspend, reactivate, delete and apply to open entries, which shows how many will be classified before classifying them. Changing what a learned rule says makes it manual. The form keeps the Conditions (what the entry has to have: list, direction, account, description, the partner the line identified and the rest) apart from the Result (what the rule writes: the partner and the classification). A manual rule can fill in the partner - for example, description and account as the condition, partner and classification as the result. The result's partner is written on every entry the rule classifies, in place of whoever the import identified (a wallet payment whose description the import read as a partner's name, for example); a partner you choose when creating an entry is not replaced. When the partner is a condition, the result shows that same partner. Duplicate, in each rule's ⋯ menu, opens a new rule filled in with everything the other one says.
On an entry or title, Create a rule from this entry opens the form filled in with its description, account, partner and classification - with no classification yet, you choose it in the form. On an entry a rule classified, the button is Edit rule and opens that rule. Saving makes the rule classify the open entries it reaches there and then - this one included, and it may reconcile it - so the entry's window closes and the page says how many were classified.
Below the rules are the partners' default categories, for reference: they are changed on the partner itself.
Manual entries
New manual entry records a movement on a manual account - petty cash, for example. Statement-fed accounts do not accept manual entries (see why), and no entry may be dated in the future: a bank transaction is money that has already moved.
The form has three shapes:
- A plain movement - in or out, date, amount and description.
- Transfer between accounts - choose the destination account, and PhinApp records both legs, already linked to each other and classified as a transfer. Transfers stay out of cash generation: the money only changed accounts.
- A classified movement - once the partner and the classification are filled in, the matching title (payable or receivable) is created and reconciled together with the entry. The classification comes right after the partner, and picking a partner with a default category fills it in - it can still be changed.
When the organization has a single manual account, it comes already selected.
The entry is in the account's currency, which the form shows beside the account chosen - an entry's currency is not chosen, and the amount box already carries its symbol.
A partner who is not in the register yet can be registered right there, on this form and on every form that asks for a partner: type the name and choose Register "…". PhinApp also asks for their tax ID - a CNPJ or CPF for a Brazilian organization, checked on the spot; the tax identification number anywhere else - so it does not have to be filled in later in the register.
Transfers between currencies
A transfer between accounts in different currencies - from a real account to a dollar one, say - asks for two amounts: the amount sent, in the source account's currency, and the amount received, in the destination account's currency, as it arrived. PhinApp converts nothing: each leg keeps its own amount.
Any transfer can also record taxes and fees - IOF, a bank fee, a spread charged separately - choosing which of the two accounts they were charged to (usually the source). They come in as an entry of their own, an expense: the transfer only moves money between accounts, while the fee leaves the cash. It can be classified right there - also saying who was paid - or later, like any entry.
Instalment purchases
On a manual card, tick Instalment purchase and give the total amount - the whole purchase, not one instalment - and the number of instalments. Instalments already past become card transactions; the ones still to come become open payables, one per month.
An instalment purchase is a series: Edit the purchase, on any instalment's entry, changes the classification and the partner of all of them at once - reconciled ones included.
Each instalment shows its number (3/12) in the list, on the reconciliation cards and in the transaction and title windows, so the card's instalment is reconciled with the title of the same instalment. An instalment's title also shows the Statement due date - the day the card bill carrying that instalment falls due - in a column of its own in Payments and in the title's window.
Payables and Receivables
Payables and Receivables are the same page on the two sides. Each title has a partner, a due date, an amount, a classification and - when it comes from the ERP - the document code and the instalment. It may also carry the numbers the document and the bank know it by - Document no. and Bank number (the number the bank gave the boleto) -, which reconciliation compares with each transaction's document number. They are the list's last columns, with the ERP code and, on a receivable, Paid by the customer on.
- The page opens on what is open only, oldest first: it is the work list. The reconciled tab keeps the history, newest first, with the payment date and the bank transaction that settled it.
- Each title's status is On time, Overdue or Paid.
- Titles arrive through the ERP import, New payable / New receivable, recurrences, or from a bank transaction.
- A title with no partner can be given one in the list itself, like the classification: the empty field is a search. Picking a partner with a default category on an unclassified title classifies it too - and, in the title's window, picking the partner also fills in the classification with their default.
- Clicking a title opens it. To settle it, Record payment (or Record receipt) - see Reconciliation.
A title that is still open can be deleted from its own form (Delete, at the bottom) or with the trash icon on its row. A reconciled title cannot be deleted - it is the document of a payment that happened. To fix a mistake, unreconcile it first.
Bank and payment
In New payable and New receivable, the optional Bank and payment section (Bank and receipt, on a receivable) takes the Document no., the Bank number and the day the money moved - Paid on, on a payable. A receivable has two days: Paid by the customer on, the day the customer paid, and Received on (credited on), the day the money reached the account - the same day for a PIX, a business day or two later for a boleto. The second follows the first until you change it, and cannot be before it.
Filling in the day the money moved marks the title Paid, and reconciliation looks for its transaction around that day. Neither day can be in the future - and "today" is the company's day, in its time zone: the same for every member, even one travelling with a phone set to another zone.
A title's currency
A title is owed in one currency: the main one, unless the organization holds accounts in other currencies and you choose one of them under New payable or New receivable - only the currencies an account is held in are offered, because a title in a currency no account holds could never be paid. A title's currency never changes afterwards, and it is settled only by an entry in the same currency: Record payment offers only accounts in it. A recurrence follows the same rule, and all its entries are in the series' currency.
Recurrences
What repeats - rent, payroll, the accountant, subscriptions - does not need to be entered every month. New recurrence creates a series: partner, classification, expected amount, frequency (daily, weekly, monthly or yearly), start and, if there is one, end.
- The series' entries are created at once and appear in the Forecast like any other title. Each one can be edited, reconciled or deleted on its own.
- With No end date, the series is generated up to 31 December of the following year and automatically extended by another year every 1 January. In a family it runs to 31 December three years from now - created in 2026, to December 2029 - and also gains another year every 1 January.
- The amount is a template: the water bill repeats, its amount does not. Each entry can have its own, and when the ERP issues the real document, it fills in the expected entry instead of creating another.
- Edit series changes the entries not yet reconciled and with no ERP document; the paid ones stay as they are. Delete series takes the open entries with it and keeps the reconciled ones.
- Right-clicking a title, Start a recurrence from this begins a series already filled in with its details.