**|** {{:icons:menu.png?16|}} Documents **|**
{{:icons:apps.png?16|}} [[brix:en:accounting]]
====== Bank Statements ======

Bank statements have the document type code //75 IZV//.

===== Data tabs =====

  * **//[[brix:en:bank_statements:basic]]//**
  * **//[[brix:en:accounting:items|~ ITEMS ~]]//**
  * **//[[brix:en:tab_dms]]//**\\ Adding, viewing and updating documents attached to the statement. The tab is shown to companies subscribed to the [[brix:en:dms]] module.

<note>
  * [[brix:en:accounting:general#document_sequence_numbers|Document sequence numbers]]
  * When a posted item is deleted from a closed statement or [[brix:en:journal_entries|journal entry]], Brix will:
    * delete only the selected item; the other items remain in the statement,
    * delete all postings of the statement from the general ledger sheets, balance sheet and so on,
    * reopen all clearings in which the statement items took part.
  * After new items are added, the statement is posted again with the **POST** button.
</note>

===== Direct statement import =====

Statements can be imported directly into Brix as a draft statement. Brix then tries to "recognise" each transaction, assign an account and analytics to the item and link it to the matching open item.

Statements can be imported:

  * [[brix:en:bank_statements:manual]]
  * [[brix:en:bank_statements:auto]]

The original SEPA file of the statement is stored in the **//[[brix:en:tab_dms]]//** tab of the statement form.

==== SEPA file data in the item description ====

When a statement is imported, Brix fills the //**{Description}**// field of each item with data from the SEPA file. Each value is preceded by a label identifying the data:

  * IBAN of the payer or payee,
  * payment reference number,
  * additional payment details.

==== Partner recognition ====

By analysing the data in a statement item, Brix tries to recognise the account, the partner and, for accounts with open-item clearing, the item to be cleared.

  * The partner is recognised by the IBAN in the statement item and entered into the partner analytics.
  * The recognised partner is shown in the form even when account //99999999// is selected in the item.
  * When an account is selected and the item is saved, if the selected account has no partner analytics, the previously entered partner analytics is removed from the item.

In addition to the IBAN, Brix analyses the data following the **//<Nm>//** tag and can identify the partner according to predefined rules. If you find a rule that always links a specific partner to the data following the **//<Nm>//** tag in the XML, partner "detection" can be improved further. Send us, via [[brix:en:tickets]], the company, the bank, the statement date and the rule you have found, and we will build that rule in.

Example of such data in a SEPA XML file:
<code>
...
<RltdPties>
   <Cdtr>
      <Nm>Google GSUITE_pilana-vrat</Nm>  <<<< This is the <Nm> tag followed by the data that may define a rule.
...
</code>

===== Automatic IBAN updates =====

When a statement is imported, Brix remembers the IBANs from items that are not yet in the IBAN codebook. When the statement is closed, such an IBAN is automatically entered into the **//[[brix:en:partners:iban]]//** tab of the analytics entered in the item.

The IBAN is entered only if all of the following conditions are met:

  * the IBAN begins with the country code //HR//,
  * a partner, employee or member is entered in the item analytics,
  * the bank of that IBAN has a //**{Bank leading number}**// entered.

<note>
The bank leading number corresponds to characters 5 to 11 of the IBAN and is entered in the **//[[brix:en:partners:basic]]//** tab of the partner marked as a //**{Bank}**//.
</note>

<note important>
If the bank has no leading number entered, the message **Bank leading number not entered** is displayed for each such item together with the IBAN it refers to. That IBAN is not added to the codebook, but closing the statement is not prevented.
</note>

<note tip>
An automatically added IBAN is entered without the //**{Name}**// and //**{#}**// data. For partners with several accounts it is recommended to add these afterwards.
</note>

===== Advance payment invoice =====

When a statement is closed, a list of items with unlinked customer payments is displayed. Marking such items automatically creates draft advance payment invoices. If at least one such payment is marked, after confirming the selected payments the program opens the //**[ [[brix:en:invoices:rapp]] ]**// form directly, with the data of the last marked payment.

===== Reports =====

The {{:brix:hr:kartica.png?40|}} icon gives direct access to the [[brix:en:journal:general_ledger_sheet]] report.