Notification
This routine was adjusted to comply with the Data Protection General Regulation (Law No. 13.70), so that some fields containing data regarded as sensitive and/or personal are blurred, becoming illegible.
Through its routines and processes, Protheus controls the banking account inflows and outflows. It is possible to add transactions and to transfer values among banks.
The first stage of implementing bank transactions is in the registration of bank information where your company transacts. Several banks can be registered.
Procedure manually performed through the Bank Transactions routine (FINA100), with the display of the screens involved in the process - actions/commands from the user are required
Procedure automatically performed in the Bank Transactions routine (FINA100) without the display of screen - no interaction from the user required.
Used in customizations in which the process does not require user's interactions (MSEXECAUTO).
Documentation: Inclusion of Automatic Bank Transactions - FINA100
Important
As this is internal control, the field "Type of Transaction" (E5_TIPODOC) has these features:
From 11/04/2020, this field began to be recorded as "DH".
This option allows adding an amount payable to the bank transactions.
This option allows adding amounts receivable to the bank transaction.
This option allows viewing the bank transaction registered, both payable or receivable.
It displays the query with the transaction accounting entry if this has been accounted for.
It displays the caption chart and meanings related to the transaction status
This operation allows deleting the bank transaction both payable and receivable, deleting the database record
This operation performs the counterpart of the transaction, which means reversing the value paid or received.
This operation allows viewing the accounting apportionment applied to the bank transaction.
Research the transaction in the bank transactions file, resulting in the transaction placed and highlighted in the browser.
It executes two bank transactions in a single operation: outflow from the source account and inflow into the target account.
It reverses the transfer executed, returning the values to the source accounts
This option allows the accounting of a bank transaction.
List of parameters applied to FINA100 and its processing
Question |
Description |
Group Entries? |
Enter option "YES" so the accounting entries generated through the transactions are grouped in a single entry |
Display Acc.Entry? |
Enter option "YES" so the accounting entries generated through the transactions are displayed on screen or "NO", otherwise |
Accounts online? |
Enter "YES" if an accounting of entries related to transactions online, or "NO", otherwise. |
Inf. Cc. in the Apportion? |
Select option "Yes" so the accounts related to the apportionments are informed, or "No", otherwise. |
Parameters (SX6)
Question |
Description |
Default |
MV_FINLMCH |
||
Indicates if the accounting flags of the offline routines are selected through the accounting entry transaction - SIGACTB. |
.F. |
|
MV_EXDTDSP |
It allows changing the availability date in the integration via automatic routine (FINA100). |
.F. |
It allows the use of a retroactive date from the system database to add bank transactions. |
.F. |
|
MV_USEFRE |
It controls the Checkbooks (not found in the BRA environment) |
.F. |
MV_NUMLIQ |
Settlements sequence number. The maximum quantity allowed is of 6 characters. |
000001 |
MV_LIBCHEQ |
Option to release bank balance when checks are generated before posting. |
S |
MV_CLIPAD |
Standard customer for pre-dated checks |
000001 |
MV_ESTADO |
Acronym of the system user company to calculate the ICMS (7, 12 or 18%). |
SP |
MV_FORPAD |
Standard supplier for pre-dated checks. |
999999 |
Number of continuous days the user may have in relation to the base date when adding the bank transaction |
30 |
|
It determines the number of days to be added to the system base date to determine the credit date of a bank transfer (FINA100) |
0 |
|
MV_MOEDA |
||
MV_SIMB |
It configures the symbol used by the currency 1 of the system (not found in the BRA environment) |
BRL |
MV_FATOUT |
Time out to select user record (in seconds). If the user takes longer, the screen is closed. |
900 |
MV_MCONTAB |
Accounting module used by the Advanced CTB = SIGACTB (Managerial Accounting) CON = SIGACON (Accounting) |
CTB |
Finance General Cash |
CX1/00001/0000000001 |
|
Codes of banks in the portfolio. |
||
MV_CMC7FIN |
Indicates the use of CMC7 reader in the Financial Content . S = Use CMC7 N = Do not use CMC7 |
N |
It does not allow posting payment date earlier than the date in the parameter MV_DATAFIN (1=Allow, 2=Do not Allow) |
2 |
|
Deadline for financial operations |
19800101 |
The Bank Transaction is used to perform entries between accounts by feeding the balance in the SE8 - Bank Balances table, and by registering the transactions in the SE5 = Bank Transaction table. This basic characteristic does not generate revenues and expenses for the company, only controlling inflows and outflows of values between accounts.
Procedures
To add transaction payable:
Tip
a. In case of manual bank transaction, and the value is wrong, execute the opposite entry, which means executing a bank transaction receivable. All transactions in the “Bank Transaction” are registered without being deleted, for information security.
b. For any option chosen in the Cash (E5_MOEDA) field, there will be a bank transaction, updating the SE8 (Bank Balances), SE5 (Bank Transaction), FK5 (Bank Transactions), and FKA (Transactions Tracking) tables.
Procedures
To add transaction receivable:
Tip
a. In case of manual bank transaction, and the value is wrong, execute the opposite entry, which means executing a bank transaction payable. All transactions in the “Bank Transaction” are registered without being deleted, for information security.
b. For any option chosen in the Cash (E5_MOEDA) field, there will be a bank transaction, updating the SE8 (Bank Balances), SE5 (Bank Transaction), FK5 (Bank Transactions), and FKA (Transactions Tracking) tables.
Procedures
To add transaction payable/receivable
If parameter MV_DATAFIN is set wit a date later than the transaction that is deleted, the system will not allow the deletion, as it would be manipulating a record in the closing period, once the option Delete does not generate a counterpart transaction.
Procedures
To cancel a transaction payable/receivable
If parameter MV_DATAFIN is set with data later than the transaction that will be canceled, the system will allow it, as long as the reversal is after the blocking date, as a new counterpart transaction is generated out of the blocking date.
Procedures
For transfers:
Tip
a. In case of a Bank Transfer, and the value is wrong, enter an opposite entry. All of the transfers in “Bank Transfer” are registered for information safety.
b. For any option chosen in the Tp.Trans. (Type of Transfer) there will be a bank transaction, updating the SE5 (Bank Balance), SE5 (Bank Transaction), FK5 (Bank Transactions), and FKA (Transactions Tracking) tables.
c. Characteristics of bank transfer transactions between Checking Account:
Type of Transaction |
Number Check (E5_NUMCHEQ) |
Document (E5_DOCUMEN) |
Origin/Outflow |
Even if the bank transaction if not executed in check (CH type, for example), this field is filled out with the document number displayed on the screen. This is the legacy manner to check the outflow process, but there will not be the generation of a check in the SEF table, even if the transaction is in cash ($ type) or bank transfer (TB type). |
Not completed. |
Target/Inflow |
Not filled out. |
Even if the bank transaction if not executed in check (CH type, for example), this field is filled out with the document number displayed on the screen. This is the legacy manner to check the inflow process, but there will not be the generation of a check in the SEF table, as the transaction comes from another checking account. |
d. Only the use of an asterisk ( * ) is allowed when typing the document number for “Trans Type” equal to “TB” or "CH".
For example:
e. You cannot transfer with credit dates on non-business days (holidays or weekends - see MV_SABFERI), with the exception of transfers between cash, where the accounts must have at least one of these rules:
f. Even with the start of PIX, which enables transactions on weekends and/or holidays, BACEN has not changed the accounting rules. Therefore. the accounting date of the transaction remains the business day following the transaction (E5_DTDISPO).
g. To meet the Decree CAF-G nº 27, dated 10.20.2017 - DOE SP dated 10.04.2017, which determines a bank transfer to be credited on the next business day (d+1), the parameter MV_DIASCRD was created to determine in how many days, and the system database, the values of the target account are available (E5_DTDISPO). For transfers between cash, this parameter has no effect.
Procedures
To reverse transfers:
LP | Generator Fact | On | Off (CTBAFIN) |
516 | Addition of bank transaction payable with apportionment | X | X |
517 | Addition of bank transaction receivable with apportionment | X | X |
557 | Cancellation of bank transaction payable with apportionment | X | X |
558 | Cancellation of bank transaction receivable with apportionment | X | X |
560 | Bank transfer - source bank outflow | X | X |
561 | Financial transfer - source bank inflow | X | X |
562 | Bank transaction payable | X | X |
563 | Bank transaction receivable | X | X |
564 | Cancellation bank transaction payable | X | X |
565 | Cancellation bank transaction receivable | X | X |
Configuration of standard entries for this routine
Entry point | Description |
F100BROW | The entry point is executed before the bank transaction browser. |
FA100PAG | The entry point will be used after the recording of the accounting data of accounts payable in the bank transaction. |
FA100REC | The entry point is used after the recording of data and the accounting of the accounts receivable in the bank transaction. |
FINATROC | Executed after the recording of all transactions receivable and accounting data. Used only by the SIGALOJA environment. Document: FINATROC - Recording of transaction receivable data – 12069 |
FA100VLD | Allows the user to create validations in relation to access to deletion and cancellation of bank transaction. |
FA100CA2 | executed after the confirmation of Deletion of Bank Transaction, before the deletion and accounting. |
FA100CAN | The entry point will be used after the deletion of bank transactions before the accounting. |
FA100Get | allows the customer to fill out the bank transfer screen data automatically. |
FA100TRF | executed before the transfer and returns .T. to record the transfer or .F. otherwise. |
F100DOC | used to edit the check number during the transfer between banks and bank branches. |
A100BL01 | executed after the recording of bank transfer data. |
FA100DOC | Is used to manipulate the variable cDocTran. Return: value that must be in cDocTran Parameters: cBcoOrig, cAgenOrig,cCtaOrig,cTipoTran |
A100TR01 | used in the recording of bank transaction transfer. |
A100TRA | A100TRA entry point complements the A100TR01 entry point. This entry points receives a parameters array with this content: lEstorno, cBcoOrig, cBcoDest, cAgenOrig, cAgenDest, cCtaOrig, cCtaDest, cNaturOri, centuries, cDocTran,cHist100. |
A100TR02 | used during the recording of bank transfer data |
A100TRB | A100TRB entry point complements the A100TR02 entry point.This entry point receives a parameters array with this content: lEstorno, cBcoOrig,cBcoDest, cAgenOrig, cAgenDest,cCtaOrig,cCtaDest,cNaturOri,cNaturDes,cDocTran, cHist100. |
A100TR03 | executed after the recording of the bank transfer data. After recording the SE5 of Source/Target banks after the accounting. |
A100TRC | A100TRC entry point complements the A100TR03 entry point.This entry point receives a parameters array with this content: lEstorno, cBcoOrig, cBcoDest, cAgenOrig, cAgenDest, cCtaOrig, cCtaDest, cNaturOri, cNaturDes, cDocTran, cHist100. |
F100TOK | Validates the bank transaction data. |
FA100TRF | The entry point FA100TFR is executed before the transfer and returns .T. To record the transfer or .F. otherwise. |
FA100ROT | Allows the addition of customized buttons in theEnchoiceBar of the Bank Transaction routine. |
FA100OKP | Used to block the addition of transactions payable in the Bank Transactions routine. If it returns true, the transaction is regularly performed, otherwise, there will not be addition of transaction. Logic return. |
FA100OKR | Used to block the addition of transactions payable in the Bank Transactions routine. In case the return is true, the transaction is regularly executed, otherwise, the transaction will not be added. Logic return. |
A85CHPDT | Allows the user to perform the own treatment to select the third party checks that may be used in the type of payment entered in the option differentiated payment. |
F100FBRW | The entry point is executed before the bank transaction browser. |