ERP reports (SAP) and bank collection
How to import payables and receivables from SAP - both open and settled - and the boletos paid from Bradesco's collection report.
Supported reports
Today PhinApp imports SAP's four title reports:
| SAP report | What it carries | Where to import it |
|---|---|---|
| Contas a Receber | Open receivables | Receivables |
| Contas Recebidas | The same titles once received, with the date they were received | Receivables |
| Contas a Pagar | Open payables | Payables |
| Contas Pagas | The same titles once paid, with the payment date and method | Payables |
The file is the spreadsheet SAP exports (.xls or .xlsx), unedited.
Using another ERP?
Talk to us and send a sample payables or receivables report from your ERP - a report PhinApp cannot read yet is refused with a message giving the address. Meanwhile, titles can be entered by hand, set up as recurrences, or raised from the bank transactions themselves.
Discord community
discord.gg/XRFVcuM5JFHow to import
Export the report from SAP
Export the payables or receivables report - open or settled - to Excel.
Open the page for the same side
Payable and paid reports go under Account Management → Payables; receivable and received ones under Account Management → Receivables. Click Import ERP file and drop the spreadsheet.
Check the result
PhinApp shows how many rows it found, how many were imported, how many already existed (duplicates), how many were settled, how many new partners were registered and how many titles were reconciled automatically.
PhinApp tells from the header which of the four reports a file is, and refuses a report imported on the wrong page: receivables imported as payables would turn every customer into a supplier and every receipt into a debt. If you see that warning, open the other page and import it there.
Large files
A report can hold up to 25 MB and 50,000 rows; past that it is refused before a single title is written - export the period in parts. A large report can take a few minutes: the dialog says the import is still running and waits for it.
What happens on every import
No duplicates
Each title is identified by its ERP code and instalment number. Importing the same report again, or a period that overlaps another, duplicates nothing.
Settlements update what is already there
A title imported while open and later found in a Contas Pagas or Contas Recebidas report is not duplicated: it is the same title, now with the answer it was missing. PhinApp records the settlement date and, for payables, the payment method - a title paid by credit card gets the Paid by card tag.
At the end of every import, reconciliation looks in the statements for the bank transactions that settled those titles - around the settlement date, when the report gives one. With automatic reconciliation on, those of partners with a default category are reconciled on their own; the rest stay as suggestions.
Partners
Each title is linked to a partner, looked up in this order: by ERP code, by CPF/CNPJ and by name, including the names it has already appeared under in bank statements. That way, a supplier first met through the bank statement is not registered a second time when it shows up in the SAP report.
- Two records with different CPF/CNPJ, or different ERP codes, are always different partners, however alike the names look.
- When the ERP record has the CNPJ written inside the name (for example, "ACME LTDA 11.222.333/0001-81"), PhinApp takes the two apart - as long as the number is a valid CNPJ.
- Whatever the report carries and the record lacks - the tax ID, the ERP code - is filled in.
First the classification rules classify what they recognise - the learned ones by the partner's ERP code and the title's description (or, with no description, the partner's name); then, if the partner has a default category, the title arrives already classified.
Recurrences and card instalments
- When the ERP finally issues the document for something already expected in a recurrence - same partner, a date at most 7 days apart -, the imported title fills in the expected entry instead of creating another one. The amount may differ: the recurrence's was only a template.
- Likewise, a future card instalment that already exists in the ERP, with the same amount and a nearby due date, is taken over instead of duplicated.
Bradesco's collection report
A company paid by registered boleto at Bradesco can import the report the bank itself produces, the Extrato de Movimentação da Carteira de Cobrança (.xls), in Accounts → Receivables, with the same Import ERP file button. Every paid boleto comes in as a receivable already received, and the title keeps what the report says:
| In the report | In the title |
|---|---|
| Nosso Número | Bank number - the number the bank gave the boleto |
| Seu Número | Document no. |
| Nome do Pagador | The customer, looked up by name - and registered if they are not yet |
| Vencimento and Valor do Título | Due date and amount |
| Valor Cobrado | Amount receivable - with interest or a discount, when it differs from the boleto's amount |
| Data Pagto | Paid by the customer on |
| CRÉDITO EM | Received on (credited on): the day the money reaches the account, a business day or two after the payment. It is the date of the receipt in the cash flow |
Each boleto is recognised by its bank number. Importing the same report again duplicates nothing, and two boletos of the same customer, paid on the same day for the same amount - two instalments, two services -, are two titles, as they should be. The bank number and the document number find the title in the Receivables search.
Reconciliation looks for the credit where it is: on the day it was credited, and only on the account the report names (the branch and the C/Creditada), as soon as that account exists in PhinApp - a PIX from the same customer for the same amount into another account is not that boleto. If the statement carries the boleto's number as the transaction's document number - Bradesco's Docto. - or in its description, that transaction is matched to the boleto with that number: that is what tells apart two boletos of the same customer, day and amount.
- Only paid boletos (code 02 - COBRADO) are imported. Rows with other codes - registered, returned, written off - are listed in the result and left out until we have an example of them.
- A report crediting boletos on more than one day is refused: it shows each day's total, but not which boleto went into which credit.
- If the bank credits several boletos as one transaction on the statement, the sum is not reconciled on its own: each title waits for a transaction of its own amount.
- If the company also imports from its ERP the titles it collects by boleto, every receipt comes in twice - once per report. For those titles, use one of the two. The same goes for a boleto typed in by hand with its bank number: the report does not recognise it, and the boleto comes in again.
Send us an example of what is not read yet:
Discord community
discord.gg/XRFVcuM5JF