PhinAppbeta

Reconciliation

How PhinApp links each title to the bank transaction that settled it - by itself or with your confirmation.

Reconciling is saying that a title and a bank transaction are the same money: the electricity bill due on the 10th and the debit that left the account on the 9th. It is what lets the forecast be compared with the actuals - and what takes the title off the list of things still to pay.

Automatic reconciliation

After every import, from a statement or from the ERP, PhinApp looks for pairs: open titles and unreconciled transactions with the same amount, nearby dates and, where both say, the same partner. For a title the ERP already reports as paid, the date looked around is the payment date rather than the due date. For a boleto from Bradesco's collection report, it is the day the money was credited, and only the credited account's transactions count. A transaction whose document number is one of the title's numbers - the bank number, the document's, the ERP code - is that title's pair.

A suggestion nobody has answered is a guess made with what was on file at the time, and it gives way to a better pair: if a title carrying the transaction's number arrives later - another boleto of the same payer and amount, say - the old suggestion goes and the new pair takes its place, as a suggestion or reconciled on its own, by the rules below. The title that lost the pair goes back to the open list. Only a better pair replaces a suggestion: at the same score, the one already there stays.

What happens to each pair depends on an organization setting, Reconcile automatically, under Settings → Organization details:

  • On (the default for a new organization): a pair is reconciled on its own when PhinApp is sure of it and the partner has a default category on the side the money moved - the purchases one for a payment, the sales one for a receipt. If the title has no classification yet, it takes the partner's default; if it has one, the title's stands. Every other pair stays a suggestion.
  • Off: every pair becomes a suggestion, waiting for someone on the Reconciliation page.

Only for partners with a default category

A default category is somebody saying "this is how this partner is booked" - and that is what makes reconciling without anybody looking safe. Partners without one stay as suggestions, even with the setting on - unless a classification rule that may reconcile by itself classified the entry. See how to set one under Partners.

Reconciliation also runs the moment a partner gets a default category - through the Always classify this way? question, on the partner's record or by merging two records. With the setting on, whatever that partner has to reconcile is reconciled right there, without waiting for the next import.

A classification rule counts too. A rule with May reconcile by itself ticked - the default for rules learned from classifications people made - plays the part of the default category: with the setting on, what it classified is reconciled by itself, and in a company without an ERP the title is raised as it would be for a default category. Only when the entry identified the partner: an any-partner rule, on an entry with no partner identified, only classifies, and the pair stays a suggestion.

With or without an ERP

  • Without an ERP - the organization has never imported a payables or receivables report and allows raising titles from entries: when a statement is imported, every transaction with an identified partner and a default category is reconciled with its matching title, where there is one; where there is none, PhinApp creates the payable or receivable and reconciles it. If an open title of the same partner and the same amount is due within a month of the transaction, nothing is created: the transaction is left for you to reconcile, so that one payment never becomes two titles.
  • With an ERP - both when statements are imported and when the paid and received reports are, every pair found is reconciled when the partner has a default category. No title is created from a statement: the ERP's next report brings that title, and creating it first would duplicate the payment. The transaction waits for the report - and is reconciled when it arrives.

PhinApp knows the company uses an ERP from the first report imported, or from Allow raising titles from entries being off. Since a new organization has automatic reconciliation on from the start, a company that will import from its ERP should import a report - or turn that option off - before its first statements: otherwise they may raise titles the ERP would later bring again.

What is never reconciled on its own

  • A transaction dated in the future: a settlement is money that has already moved.
  • A pair somebody undid, or a suggestion somebody discarded: PhinApp remembers the answer and does not propose that pair again.
  • A title with nobody on it - like a card instalment, which the statement does not say whose it is.

Transfers between two of the company's accounts do not depend on the setting: they have no partner, and when both transactions are already marked as a transfer they are linked on their own, as always.

The Automatic tag

Everything PhinApp reconciled on its own carries the Automatic tag - in the Reconciled column of Banking Transactions and in the Status column of Payables and Receivables. To see only those:

  • on Banking Transactions, filter Reconciled → Yes, automatically;
  • on Payables and Receivables, on the Reconciled tab, filter Reconciliation → Automatic (or Manual, for what a person reconciled).

A suggestion somebody confirmed is a manual reconciliation: a person decided it.

The Auto-reconcile button

On the Reconciliation page, the Auto-reconcile button applies the same rules right away, whether the setting is on or not - including to the suggestions already waiting and, without an ERP, to raising the titles that are missing. Afterwards it says how many transactions were reconciled, how many titles were raised and how many new suggestions appeared.

The Reconciliation page

Account Management → Reconciliation gathers the work still to do:

  • Automatic suggestions - the surest first, by the percentage each one shows. Each suggestion is a pair of cards: the title on the left (partner, document, due date, status) and the bank transaction on the right (account, date, source). Check them, adjust what needs adjusting, and Confirm reconciliation - or Discard suggestion, which is not proposed again.
  • Payables and receivables without a matching payment - titles waiting for the payment to show up on a statement.
  • Transactions without a matching entry - bank movements nobody has explained yet.

The card is a place to work: the title's description, the classification and - where it is missing - the partner can be filled in right there, without leaving the suggestion.

The partner counts on both sides. On reconciling, a bank transaction with no partner takes the title's, and a partner chosen at that moment - on the card or in Find title - is saved on the title and on the transaction. A transaction that already has a partner of its own changes it only when you choose another.

Choosing a classification on the card saves it on the title at once. If the partner has no default category on that side yet, PhinApp then offers to make it their default - which also classifies the partner's other open entries. With the default set, Auto-reconcile reconciles all of that partner's suggestions in one go, instead of one card at a time.

When the two sides disagree

  • Different classifications: the title's wins; the bank transaction's is replaced. If the title has none yet, it takes the one chosen.
  • Different partners: the title's is the one the settlement is filed under, and the transaction keeps the name that came from the statement. Nothing is discarded, but it is worth checking that the pair is right - and, if they are the same company under two records, the warning itself offers Merge the two records.
  • Different numbers: when the title has a bank number and the transaction carries a document no. that is none of the title's numbers, both are highlighted. Confirming changes neither, but check the pair: two boletos of one payer and amount differ only by their number.
  • A date different from the due date: nothing is wrong - the title now counts on the day it was paid, and the note only records the difference.

From a title

Under Payables or Receivables, open the title and use Record payment (or Record receipt). The window opens on Find the bank transaction: a list of unreconciled transactions of exactly the same amount. Most of the time it is already there, because the statement was imported first - just point at it.

If the payment is on no statement (a cash payment, for example), the New bank transaction tab records the movement on a manual account and reconciles it with the title straight away.

From a bank transaction

Under Banking Transactions, open the transaction:

  • Find a title - the open titles of exactly the same amount. Point at the one this transaction settled.
  • Raise a title - for companies without an ERP: creates the payable or receivable the transaction stands for, already reconciled. It needs a classification and a partner, and can have a description of its own (the statement's stays the same). This option appears when the organization allows raising titles from entries, under Settings → Organization details.

Splitting a transaction across several titles

Sometimes one payment settles more than one thing: the rent and the building fee in one bill, three of a customer's invoices in one PIX, a card line that was two expenses. Open the transaction in Bank transactions and use Split across several titles:

  • each part is an open existing title - settled at its own amount - or a new title, with a partner, a classification, a description and an amount;
  • the parts have to add up to exactly the transaction: the dialog shows how much is left (or over) and splits only when the difference is zero;
  • every part is reconciled with the transaction at once.

A transaction already reconciled with a title can be split too: that title becomes the first part, and a title you take out of the split goes back to open. New titles are offered only where the organization allows raising titles from transactions.

In Bank transactions, the classification column reads Split - the classification is on each part. In Payments and Receipts, each title shows its own classification and the Split tag, saying it shares the bank transaction with other titles. A part's classification is changed on the title itself. Undo the split - on the transaction or on any of its parts - undoes the whole split, because the parts left would no longer add up to the transaction.

In the cash flow, each part counts under its own classification, at its own amount, on the transaction's date.

Only within one currency

A title is reconciled only with an entry in the same currency: automatic reconciliation never proposes a pair in two currencies, the Find the bank transaction and Find a title lists show only entries in the same one, and the database refuses the pair if anybody tries. The two legs of a transfer, too, are only found by their amount within one currency. To join two accounts in different currencies, mark the entry as a transfer and give the amount in the other account - that is what the other leg is looked for by or, on a manual account, written with.

Transfers between accounts

A transfer between two of the company's accounts has no title - it has two legs: the outflow on one account and the inflow on the other. When you mark a transaction as a transfer, PhinApp asks for the account, not the transaction:

  • if the other leg is already there (opposite amount, up to 3 days apart), the two are linked - the usual case, because a transfer between two banks arrives as two imported transactions;
  • if it is not and the other account is manual, the other leg is created;
  • if it is not and the other account is statement-fed, it is refused: that account's statement will bring the transaction, and creating it now would duplicate it. Import the statement and try again.

Both legs are classified under the reserved transfer classification and stay out of cash generation.

Paying a credit card bill

It is the most common transfer, and it is recognized on its own. On the bill, the payment line - PAGAMENTO RECEBIDO - OBRIGADO, Pagamento da fatura, Pagamento em 15 SET, PAGAMENTO PIX and the like - is recorded as a transfer, with no partner, and linked to the checking account's debit of the same day and the same amount, whichever of the two was imported first. If the debit is up to 3 days away (a boleto that takes a business day to reach the issuer, for example), the link appears as a suggestion for you to confirm. Bill payments imported before this rule are corrected on the next import or by pressing Auto-reconcile.

Unreconciling

A reconciled title or transaction shows Unreconcile where an open one would show Delete. Unreconciling:

  • removes only the link - the title and the transaction keep the classification, partner and description they already have;
  • puts the title back on the open list, and the Forecast counts it on its due date again;
  • and teaches automatic reconciliation: that pair will not be suggested or confirmed on its own again, even with the same amount and dates. Linking the two by hand is still possible;
  • and, if the pair had been reconciled by itself and a classification rule had classified one of its sides, that rule stops reconciling by itself - it keeps classifying, until somebody changes the classification.

Changing the classification of something reconciled

The classification is the one field that stays editable on a reconciled title or transaction - and changing it on one side changes the other. The Forecast reads the title's classification, and so do the Actuals: a reconciled transaction counts under the classification of the title it settled - or, for a split transaction, of each part. Changing both sides together keeps the transaction and the title saying the same thing.

On this page