BOG Bank Integration
Within the system, there is the ability to export payments and import bank statement. The integration is fully implemented for BOG bank. For full integration with BOG, it’s necessary to set up Bank Accounts, Vendor Bank Account, Vendor Card, Bank Account Details in the system, and the process of creating, exporting and importing payments should be done in the Bank Payment Journal.
##Process Beyond System
A company should have an account on: https://bonline.bog.ge and unique credentials for accessing the system. To call the API, you should first register your application on the https://bonline.bog.ge/admin/api webpage. When registering, you should enter the application name in an international language. After registration, Application identifiers which you will have to use on the authentication request will appear on the application details page.
- client id
- client secret
Second step is giving API rights to application user in the online bank.
Required Settings
To create company bank accounts, Select the 
icon, enter Bank Accounts and fill out the mandatory fields for integration with the bank:
Section - General
| Fields | Description |
|---|---|
| No. | Specifies the number of the involved entry or record, according to the specified number series |
| Bank Code | International code of Bank - BAGAGE22 |
| Name | Specifies the name of the bank where you have the bank account |
| Bank Account no. | Specifies the number used by the bank for the bank account |
| Export Format | Options - XML/Individual Bank of Georgia API/Package Bank of Georgia API. Individual - not more than 10 payments are exported, Package - less and more than 10 payments are exported. |
| Import Format | Option - Bank of Georgia API |
| Bank Extract Format | Bank Extract Format |
| Client Bank | Specifies the type of interaction with the client bank system for the bank account, the ability to import/export a bank statement or just import |
| Bank Service | Specifies authentication credentials of the internet bank, card of credentials created for BOG must be selected. |
- Section - Communication
| Fields | Description |
|---|---|
| Country/Region Code | It’s necessary to choose for foreign currencies transactions |
- Section - Posting
| Fields | Description |
|---|---|
| Currency Code | Specifies the relevant currency code for the bank account |
| Bank Acc. Posting Group | Specifies a code for the bank account posting group for the bank account. The selected one should have G/L, Transit and Commissions Accounts filled out. |
- Section - Transfer
| Fields | Description |
|---|---|
| SWIFT Code | Specifies the international bank identifier code (SWIFT) of the bank where you have the account (BAGAGE22). |
| IBAN | Specifies the bank account's international bank account number. |
To specify bank exchange formats, go to Bank Services. Here you can add bank account code and approproate bank service, and from actiones "Setup" opens main integraiton tool page with fields:
| Fields | Description |
|---|---|
| Base API URL | Specifies the URL for connecting via the API if the bank extract format is being configured for online banking:https://api.businessonline.ge/ |
| Authentication API URL | Specifies the value of the Authentication API URL field: https://account.bog.ge/auth/realms/bog/protocol/openid-connect/token |
| Client ID | Specifies the Client ID for connecting via API, alue from BOG internet bank |
| Client Secret | Specifies the client secret for connecting via the API, value from BOG internet bank |
Bank Account Details defines the setting for recognizing specific operactions (such as transfers between own accounts, conversion, commisions...) by transaction codes . Select the icon, enter Bank Account Details and fill out the following mandatory fields:
| Fields | Description |
|---|---|
| Code | Specifies the unique identification code associated with this bank account detail record |
| VAT Registration No. | Specifies the Company's VAT registration No. from the company information |
| Bank Account No. | Specifies the account number of the bank associated with this general ledger account bank operation |
| Account Type | Specifies the type of account that the entry on the journal line will be posted to ( G/L Account/Vendor/Customer) |
| Account No. | Specifies the Account No. to which the entry on the journal line will be posted to |
| Bank BIC | Specifies the SWIFT BIC code of the recipient of the bank operation |
| Document Type | Specifies the document type of the identifyed transaction by transaction code (Payment/Refund) |
| IBAN | Specifies the bank account's international bank account number |
| Transaction Code | Specifies the transaction code to which this bank information applies |
The uniqueness of lines is checked by the following fields: Account Type, Account No., Currency Code, Transaction Code, Document Type, Payment Assignment.
If IBAN, Bank Account No. and Currency Code are empty -> the setup specified in bank account details work for all bank accounts without overlay filters for those fields, if any of the values are filled in -> it takes priority and use the indicated values as filters at the moment of checkup.
If in the Bank Account Details lines Shortcut Dimension 1 and Shortcut Dimension 2 are specified and the transaction in the buffer has been checked up from the setup in the bank account details -> the specified dimensions will be filled in the Bank Buffer accordingly.
Vendor Bank Account card must be configured to export transactions. The following are the required fields for exporting payments in local and foreign currencies:
| Fields | Description |
|---|---|
| Code | Specifies the unique identification code associated with this bank account detail record |
| Bank Code | International code of the Bank |
| Name | Specifies the name of the bank |
| Adress | Specifies the adress of the Beneficiary Bank (for foreign payments) |
| Country/Region Code | Specifies the country of the Beneficiary Bank |
| City | Specifies the City of the Beneficiary Bank (for foreign payments) |
| Currency Code | Specifies the relevant currency code for the bank account |
| Bank Type | Specifies the Beneficiary Bank Type Vendor or Tax Authority (for treasure payments) |
| SWIFT Code | Specifies the SWIFT code (international bank identifier code) of the beneficiary bank account. For treasure payments - TRESGE22 |
| IBAN | Specifies the bank account's international bank account number |
| Intermediary Bank | Specifies the SWIFT code (international bank identifier code) of the intermediary bank |
| SWIFT Intermediary Bank Name | Specifies the name of the intermediary bank |
Functionality
Bank Payment Journal
In order to complete import/export of payments from bank payment journal, General Journal Batches should be set up.
Select the icon, enter Bank Payment Journal, and from the Batch Name field, open General Journal Batches. There can be added batches for different bank accounts that company has. It is necessary to fill out Bal. Account Type, Bal. Account No., No.Series. and mark "Use Document No. from Batch No. Series" in order for Document No.s to always be unique in the bank payment journal.
After setting up the batches, choose one of them and begin the processes of bank payments.
For additional information about Templates and Batches, see the link.
Exporting Payments
BOG export formats:
• Bank of Georgia XML - XML format is downloaded to be manually imported into the internet bank
• Individual Bank of Georgia API - payments are sent straight to internet bank's individual payments
• Package Bank of Georgia API - payments are sent straight to internet bank's package payments
To export Payments from Bank Payment Journal, the following Account types are mostly used: G/L Account, Vendor.
BOG payments can be created in Bank Payment Journal and exported:
- To own BOG accounts, in national and foreign currency,
- To another bank in national currency,
- To another bank in foreign currency.
- Bank Payment with the Vendor Account Type.
In order to export payments from the Bank Payment Journal to the Vendor, the following fields should be filled in:
| Fields | Description |
|---|---|
| Posting Date | Specifies the posting date for the entry |
| Document Type | Specifies the type of document that the entry on the journal line is (Payment) |
| Document No | Specifies a document number for the journal line. Automaticaaly filled in from the No. Series of the batch |
| Account Type | Specifies the type of account that the entry on the journal line will be posted to (Vendor) |
| Account No. | Specifies the account no. that the entry on the journal line will be posted to (Vednor Account No.) |
| Description | Filled in with the name of the selected Account No |
| Currency Code | Specifies the code of the currency for the amounts on the journal line. Filled in automatically from the Bank Account No. of the selected Batch name |
| Amount | Specifies the total amount (including VAT) that should be exported |
| Recipient Bank Account | Specifies the bank account that the amount will be transferred to after it has been exported from the payment journal |
| Payment Assignment | Specifies the purpose of the payment |
| Payment Order Status | If export is required, select For Export from options |
| Expense Type | Specifies who is the payer of the charges and fees associated with the bank payment journal line (BEN/OUR/SHA) |
Note. Refunding to Customer is filled out in the same way and can be exported.
Payment preparation can be done in the following ways:
- Manually
- By Suggest Vendor Payments. In the Payment Journal window, you can use the Suggest Vendor Payments batch job to suggest payment lines based on due date. For further information see the link.
- The Create Payment feature on the Open Documents subform. For further information:see the link
In case of exporting payment to Treasury (when Bank Type=Tax Authoirty), payment assignment value exports in additional description field in internet bank.
- Bank Payment with the G/L Account Account Type.
To export payments in Bank Payment Journal from one company’s account to another, in Lines, use Account Type- G/L Account in Bank Payments Journal lines. The following fields should be filled out for exporting G/L Account payments:
| Fields | Description |
|---|---|
| Posting Date | Specifies the posting date for the entry. |
| Document Type | Specifies the type of document that the entry on the journal line is (Payment, Refund, Invoice, Credit Memo, Finance Charge Memo, Reminder). |
| Document No | Specifies a document number for the journal line. |
| Account Type | Specifies the type of account that the entry on the journal line will be posted to (G/L Account). |
| Account No. | Specifies the account number that the entry on the journal line will be posted to. Only those accounts that are added for Bank Accounts in Bank Account Details should be indicated. |
| Currency Code | Specifies the code of the currency for the amounts on the journal line. |
| Amount | Specifies the total amount (including VAT) that the journal line consists of. |
| Recipient Bank Account | Specifies the bank account that the amount will be transferred to after it has been exported from the payment journal. |
| Payment Assignment | Specifies the purpose of the payment. |
| Payment Order Status | If export is required, select For Export from the options. |
After flling out the Lines in Bank Payment Journal and Changing Payment Order Status (with For Export), you can select Process-> Export Payments. The system will notify that export was successful, and Payment Order Status will change to Exported.
If any information is missing in the payment line, the system notifies about it. If there is incorrect information in a field, for example Recipient Bank Account is not valid, the Payment Order Status changes to ERROR, and an Error Message field is filled out with the reason of not exporting a payment.
Check Payment Status function allows you to check the status of exported payments (for individual and package payments):
- Select the lines in the bank payment journal for which you want to check the status;
- Actions -> Functions -> "Check Payment Status";
- The status received from the bank will be filled in the "Transaction Status" field
Importing Payments
In Bank Payment Journal, click Import Bank Extract from the menu and choose the dates of payments you want to import. For the import to be completed, Bank Extract should be empty. If there are some lines in it, the system won’t import the payments.
After successful import, the payments will be imported in the Bank Extract Buffer window (Bank Extract -> Open Bank Extract):
Flow of the Checkup process of imported transactions in Bank Extract Buffer to identify transactions:
- By Document No. in case Checkup by Document No. is activated for the Bank Account Card. When payments from the bank payment journal are exported successfully with "Document No", wchich is unique and we also receive it when importing payments. The Account Type and Account No. will be filled from the identified transactions by Document No. from bank payment journal.
- According to the Bank Account Details which sets up rules for recognizing transactions by transaction codes
- Customer/Vendor identification:
- if the amount is positive (outgoing amount) the search is first performed in Vendors by Cor. Settlment Account, then by VAT Registration No., if not found: in Customers by Cor. Settlment Account, then by VAT Registration No.. If found, the Account Type and Account No. are filled in. If Account type=Vendor -> Document type=Payment, if Customer -> Document type=Refund.
- if the amount is negative (ingoing amount), the search is first performed in Cusomers by Cor. Settlment Account, then by VAT Registration No., if not found: in Vendors by Cor. Settlment Account, then by VAT Registration No.. If found, the Account Type and Account No. are filled in. If Account type=Customer -> Document type=payment, if Vendor -> Document type=Refund.
By clicking the Check Up button you can update checking process.
-The lines colored in red are payments that the system doesn’t recognize by any of the Checkup Process. When clicking Import to Bank Payment Journal, red Payments stay in Bank Extract Buffer.
-The lines in black are payments which were recognized by the system and can be transferred into Bank Payment Journal by clicking Import to Bank Payment Journal on the ribbon of Bank Extract Buffer.
Process of checking for duplicate entries:
Imported Payments shouldn’t be duplicated in the system, so the Check Bank Extract for Duplicate Entries should be activated. When importing payments from Bank Extract Buffer to Bank Payment Journal, lines will be checked if the operation is already posted in General Ledger Entries or generated in Bank Payment Journals, this payment won’t be transferred to Bank Payment Journal.
- When checking in Bank Account Ledger Entries, the following parameters are checked: Bank Account No., External Document No.", Posting Date, Account No., Reversed=false, Amount
- When checking in Bank Payment Journal, the following parameters are checked: Account Type, BankAccount. No., Account No., External Document No., Posting Date, Amount
Matching Process of exported and the relevant imported transactions:
- The following fields must be matched to identify the exported transaction from the bank payment journal with the imported transaction in the bank extract buffer: payment order status must be exported, Account type, Account No, Document Type, Amount, Vat Registration No., Recipient Bank Account.
- Including all the above fields, you can additinally check transactions by document number where Document No (buffer)=Document No (bank payment journal) if the Compare Document No. function is activated on the Bank Account Card.
- Additionally, the matching process can only be performed by matching the Document No. field only if the Matching by Document No for exp. transactions is activated on the Bank Account Card.
If all fields match -> Payment Order Status will change to Paid and update the posting date in journal from the Extract Date field (buffer). Matching transactions will not be duplicated in the bank payment journal.
Check Bank Account Details
If you want to check if a Cor. Settlement Account exists for Customers/Vednors in the system, you can activate "Check Bank Account Details" function on the Bank Account Card. If such a cro. settlebemt account is not fund -> the system will notify you about the need to add Bank Account Card
If Payments aren't between own accounts, the system checks the company's VAT Registration No. to identify if the imported payment is incoming or outgoing. If the Imported field value in Bank Buffer Cor. VAT Registration No. = VAT Registration No from Company Information, and VAT Registration No. doesn't equal the Cor. VAT Registration No. for that line on Bank Buffer, then during the import of bank statement, the values are switching for the following fields:
-Settlement Account to/from Cor. Settlement Account,
-VAT Registration No. to/from Cor. VAT Registration No.,
-Account No. to/from Cor. Account No.
Payment Сheckup logic for Credit Card transactions:
In order to match imported Credit Card Payments that may not have Cor Settlement Account/ Cor Vat Registration Account or both of them in the statement, it is mandatory to fill out the following settings:
In Bank Account Details setup:
• Account Tupe=Vendor/Customer, with Account No=empty
• Transaction Code= CCO,PLC (any codes provided in bank statement for payments that have Cor. Settlement account/Cor. VAT registration not empty in the bank extract)
• Type=None
• Payment Assignment=text1; text2; text3: "Search Name" randomtext:
• It is forbidden to add the line with the same values from fields above, including currency and IBAN.
In Vendor/Customer card setup: Search Name
Note. When Cor.settlement account=filled, Cor Vat Reg No=empty, after finding customer/vendor via Search, name filter system also looks for IBAN from the found vendor's/customer's bank account. Account No is assigned only if IBAN matches. If not, it remains empty.
Reverse posted transactions
The cancellation of the transactions must be performed from the Bank Account Ledger Enties using the action Reverse Transaction.
Web Request Logs
To create log of requests and returned responses, set up the following:
- Go to Bank Account Card,
- Open Bank Extract Format,
- Check Log Web Requests,
- Go to Bank Payment Journal,
- Create payment and send to onlines banking,
- Go to Web Request Log,
- Download the Requests/Response files.
In the Bank Extract Buffer, a new button called 'Fill Date' has been added. This button ensures that if the Extract Date is empty, its value is filled with the Document Date, and vice versa.