PhinAppbeta

Chart of accounts and partners

The classifications every amount is recorded under, the side of each one, and the register of suppliers and customers.

The chart of accounts

Settings → Chart of accounts is the organization's list of classifications. Each line has four parts:

PartExampleWhat it is for
Category - Level 1ExpensesThe cash-flow group: revenue, costs, expenses, other.
Category - Level 2Fixed expenseA grouping inside the group.
Category - Level 3PayrollA finer grouping.
ClassificationSalariesThe name an entry is actually classified under - what every picker shows.

The cash flow shows exactly this structure: level 1, then "level 2 - level 3" on one row, then the classification.

The chart starts from a template for the organization's country, in its language, and from then on it is yours: you can add lines, rename levels and delete what you do not use.

D/C: debit or credit

Every classification has a side: D (debit) takes money out of the company, C (credit) brings it in. The side decides which lists it appears in - the payables pickers offer debits only, the receivables pickers credits only -, because a payment booked to a revenue classification would show up in the cash flow as money the company never received.

When you create or edit a line, the D/C field follows level 1:

  • under Revenue, every line is a credit; under Costs and Expenses, every one is a debit - the field is disabled and already set to the group's side;
  • only under Other, the group that holds both sides (a capital contribution comes in, a profit distribution goes out), is the side chosen line by line.

PhinApp does not decide this by the group's name, but by the lines it already holds: a renamed group keeps behaving the same way.

The transfer between accounts

One line of the chart is Reserved: the transfer between accounts (side T). It is what marks every transfer, on both legs, which is why it cannot be edited, deleted or chosen to classify a title - a transfer is something a statement shows, never something anybody invoices.

A family's chart of accounts

A family's chart has only three groups: Revenue, Expenses and Other - no Costs. Inside Revenue and Expenses, levels 2 and 3 are the area the money went to or came from: Housing, Food, Transport, Health, Education, Leisure, Work, Benefits, Property and investments...

  • Other holds only the transfer between accounts. No new line can be added under it: in a household, anything that is not a transfer is income or an expense.
  • There is no D/C column. The group already says the side - Revenue brings money in, Expenses take it out - and the field does not even appear when adding a line.
  • Investments have two lines, under Property and investments: Investment, under Expenses, for money put in, and Investment withdrawal, under Revenue, for what comes back - what it earns stays in Investment income. A family created before these lines existed can add them.

Adding and deleting lines

When adding a line, level 1 is always chosen from the groups that already exist. Levels 2 and 3 offer what is already filed under the level chosen above them - and accept a new value if needed. That way "Fixed expense" and "Fixed expenses" do not become two branches of the same chart.

Deleting a classification leaves every transaction and title that used it unclassified - they go back to the Classification pending row of the cash flow.

Partners

Settings → Partners is the single register of who the company buys from and sells to. A company buys from and sells to the same company all the time, so there is one register, and the type says the side: Supplier, Customer or Both.

Each partner can have:

  • a Tax ID - for Brazilian organizations, checked against the CPF/CNPJ check digits - stored without punctuation;
  • an ERP code - what links the partner to the SAP reports;
  • Default category (purchases) and Default category (sales) - which classification payments to them and receipts from them go to;
  • Notes.

In a family, the same register is called Counterparts, and the types are Payee (somebody the family pays), Payer (somebody who pays the family) or Both. There is no ERP code.

Partners are also registered by the imports themselves: Itaú's statement carries the company name and the CPF/CNPJ, and the SAP report carries the code and the name. PhinApp keeps every spelling a partner appears under in bank statements, so renaming the record does not break the next imports. The instalment a card bill prints is not part of the name: "Store X - Parcela 4/12" is Store X.

Default category

When you classify by hand the first transaction of a partner with no default category yet, PhinApp asks: Always classify this way?

  • Set as default - the partner's next transactions arrive already classified, including those imported from statements and from the ERP, and the partner's open, unclassified ones take it too;
  • Not now - asks again some other time;
  • Do not ask again for this partner.

The default category is also what automatic reconciliation relies on: only the transactions of partners that have one are reconciled without anybody looking. With automatic reconciliation on, setting the default category - through this question or on the partner's own record - reconciles straight away whatever that partner has to reconcile.

Merging two records

When the same company shows up under two records - a name spelled two ways, for example -, open one of them and use Merge with another. The whole history of the absorbed record moves to the one that stays, reconciled transactions included, and the statement names of both are added together. For each field that differs, choose which value stays - except the kind: if one record is a supplier and the other a customer, the merged one becomes Both, without asking.

  • Open, unclassified transactions and titles take the default categories of the record that stays and, with automatic reconciliation on, whatever can be reconciled is reconciled right after.
  • Records with different tax IDs cannot be merged: they are different people or companies.
  • A merge cannot be undone; it is recorded in the audit log.

A partner with reconciled transactions cannot be deleted - deleting it would leave that history unattributed. If it is the same as another record, merge them.

Several records at once

Tick the records in the box at the start of each row - the one in the heading ticks every record the filter shows, on every page - and choose what to do with them:

  • Set default category (purchases) or (sales) - the same classification becomes each one's default, and their open entries with no classification yet take it, as when setting it on one record. Those on the other side stay as they are: a purchases default is for whoever you pay, a sales default for whoever pays you - and PhinApp says how many were left out.
  • Delete selected - those with reconciled entries are kept, and PhinApp says how many: for those, use Merge with another.

Changed the filter? Only the ticked records it still shows are acted on.

Classifying with AI

In Bank transactions, Payments and Receipts, the Classify with AI button classifies every entry of the list that has no classification yet. Before asking the AI it applies the classification rules - yours and the ones PhinApp learned - and at the end says how many were classified by rules and how many by AI; the rules work even when the AI cannot be reached. What is left goes to the AI:

  1. it groups the entries with the same description - forty ride-app trips are one question - after taking out of it what does not say what the money was for: the instalment counter, dates, times, document numbers and amounts;
  2. it first uses what the AI already answered for the same description - for any organization on PhinApp - when that answer is a line your chart of accounts also has, in the same words at every level;
  3. it asks the AI (TypeSafe) about the rest in one request, sending only the descriptions and the lines of your chart of accounts with each line's notes - nothing that identifies the company;
  4. it classifies each entry by the answer only when the answer is clear: if the description does not say what it was (a PIX with a person's name, a TED with a number), or the money only moved between your own accounts (a savings box, a reserve, an investment, paying your own card bill), the entry stays unclassified.

An answer that was not clear is kept too: the same description is not asked again while your chart of accounts has the same lines. Those entries are yours to classify - or a partner default's.

Entries classified this way show the AI icon beside their classification. Check them and change what you need - the icon goes as soon as anybody changes the classification.

At the end, PhinApp offers to use those classifications as the default of the partners whose entries the AI classified all the same way. Defaults set this way carry the AI icon in the partner register and in the chart of accounts, and the register's Default set by the AI filter lists them all for you to review.

If the AI cannot be reached, the button uses only what it had already answered and says so.

When importing files

In Settings → Organization details, Classify with AI when importing files does the same for the entries of every imported statement or report that no rule and no partner default classified. It is on for organizations created from now on; in the ones that already existed, switch it on if you want it. With automatic reconciliation on as well, reconciliation runs right after, with those classifications in place.

On this page