| Card |
|---|
| default | true |
|---|
| id | 1 |
|---|
| label | Parameters |
|---|
| Question | Description | Display Acc. Entry? | Select Yes or No to indicate whether to display the accounting entry when booking online. Example: No. | Group Acc. Entry? | Select Yes or No to indicate whether to group entries in a single line if accounts, cost center, item, and value class are the same in the entries. Example: No. | Account for issues? | Indicates by selecting between the options By the issuing dt. (Accounting Dt. = E2_EMIS1/E1_EMISAO) and By the Database (dDataBase). The accounting of accounts payable is based on the date of inclusion of the bill in the system. This occurs so that accounting postings are not made in periods already closed.
| Informações |
|---|
| The accounting of accounts payable is based on the date of inclusion of the bill in the system. This occurs so that accounting postings are not made in periods already closed. For example, when making a purchase on October 28, 2021, from a supplier in Manaus, the invoice is issued on October 28, 2021, and the cargo is delivered in Sao Paulo on November 3, 2021. Assuming that the company has already made the monthly closing of the accounting, it could not account using the date of issue of the invoice (October 28, 2021). Due to this type of circumstance, conceptually, we must account using the date of entry of the invoice into the system. |
For accounts receivable, the bill generation date is considered. Example: 06/24/2019 | From Date? | This indicates the start of the date interval to filter records for offline accounting. Example: 06/1/2019 | To Date? | This indicates the end of the time interval to filter records for offline accounting. Example: 06/30/2019 | From Portfolio? | Indicates, by selecting between the options Receivable, Payable, Check, or All, whether the accounting entry will filter by bill nature. Example: No. | Account postings? | Indicates, by selecting between options By Posting Dt. (by the bill's posting date), By Typing Dt. (by the time when the user typed it), or By Avail. Dt. (by the date of availability typed by the user to account in the date of the bill transaction, not by the bill's posting date), for the accounting entry filter. Example: No. | Cons. branches below? | Indicates by selecting Yes or No, whether the following two parameters will be considered in offline accounting or not through the branch filter that the user has access to. Example: No. | From Branch? | Indicates by typing which branch will be the beginning of the filter interval for offline accounting. Example: D MG 01 | To Branch? | Indicates by typing which branch will be the end of the filter interval for offline accounting. Example: ZZZZZZZZ | Update summarized? | Indicates, through the Yes or No options, whether summarized accounts (child accounts of detailed accounts) will be updated in offline accounting. Example: No. | Separate by? | Indicates through the Period, Document, or Process options. Example: · Period: For each Branch/Date informed, 01 (one) accounting document gathering the various financial processes will be generated; · Document: Each financial record must generate 01 (one) accounting document; · Process: 01 (one) accounting document will be generated for each financial process.
| Informações |
|---|
| 1. CTBAFIN treats as a financial document: - Each issue of a bill (payable or receivable);
- Each bill posting operation (payable or receivable - except those linked to a bordereau);
- Each bill posting operation linked to a bordereau (payment or receipt), with the bordereau being the Financial Document;
- Financial Application or Financial Loan;
- Redemption of financial application or payment of financial loan;
- Check issuance or posting;
- Advances or Rendering of Travel Accounts.
2. The CTBAFIN process is treated as: - Accounts Payable Issuance;
- Accounts Receivable Issuance;
- Posting of Accounts Payable;
- Posting of Accounts Receivable;
- Bank transactions (Applications, Redemptions, Deposits, Withdrawals, or Bank Transfers);
- Issuance and/or posting of checks;
- Travel-related operations (Advances, Rendering of Accounts, etc.).
|
| Account Bordereau? | Indicates, by means of the Total Bordereaux or Bordereau/Bordereau options, if the LP 532 accounting (Bosting of bordereau bills) will be dismembered or if daily accounting of the total of all bordereaux will take place (Documentation on the concept applied to the LP 532) Example: No. | Consider Source Branch? | Indicates, by selecting Yes or No,whether the following two parameters will be considered in offline accounting or not through the source branch filter. Example: No. | Branch From? | Indicates by typing which branch will be the beginning of the filter interval for offline accounting. Example: D MG 01 | To Branch? | Indicates by typing which branch will be the end of the filter interval for offline accounting. Example: ZZZZZZZZ | Book Prov. Bill? | Indicates whether provisory bills must be booked. Example: No. |
|
| Card |
|---|
| default | true |
|---|
| id | 2 |
|---|
| label | Parameters (SX6) |
|---|
| Parameter | Description | Default Content | MV_CFINTHR | The number of threads to be used to speed up the accounting queue (CTBAFIN), with a minimum of 2 and a maximum of 30.
Each processing instance requires that the minimum number of records be equal to or greater than 200.
Check this page MV_MXRCTHR
| 1 | MV_FINLOG | Indicates whether or not the financial module offline accounting will generate unaccounted records log (.T.) or alerts (.f.). Documentation: https://tdn.totvs.com/x/zN6pHg | .F. | MV_DIRDOC | The target directory where the files of the Knowledge Base will be stored. | \DIRDOC\ | MV_CTBUPRC | Defines whether to account using the new accounting model, with dynamic procedures for validations and inclusion of CT2 and CV3 data (.T.). | .F. | MV_TIPOLOG | Enter 1 to generate the log file in txt or 2 to generate the report. | 1 | MV_SLDBXCR | Indicates how the balance of the posting of the accounts receivable will be tracked, only when the check is compensated or at the time of the posting (B, C). The offline accounting uses the configuration of this parameter as follows: - Value B: Uses LP 520 through the posting record - SE5->E5_TIPODOC = VL
- Value C: Uses LP 559 through the record of the check compensation date - SEF->EF_DTCOMP
| B | MV_CTCHQBX | Defines when the check will be accounted for on the posted bill: 1 = Generation, 2 = Release. | 1 | MV_CTMOVPA | Indicates whether the LP 513 Offline Accounting will occur by the Bill (SE2) or Banking Transaction (SE5) of the Advance Payment, 1="SE2" / 2="SE5". | 1 | MV_CTBAGP | Defines whether PCC bills are accounted for by their groupings or not (Default = .F.). | .F. | MV_NATTROC | Determines which nature will be used in the generation of change outflow of SIGALOJA and FRONTLOJA. | "TROCO" | MV_GPDOCTB | Determines that LPs 560 and 561 (Bank Transfer) will be grouped into the same accounting document when the question "Separate by?" is set to Document. | .F. | MV_BXCNAB | Defines whether the CNAB return bill posts must be grouped, (S) Yes or (N) No. | N | MV_UNIAO | Identify the code given to the Federal Revenue for payment of Income Tax. | UNION | MV_MUNIC | Identifies the code of the finance department of the municipality for ISS collection. | MUNIC | MV_ORDLCTB | Sets the order of accounting postings in the integration batch/doc, "L"=Default standard entry order, "E" Inflow order, and "T" = Balance Type. | L | MV_CTBINTE | 1 - Accounting by bill, 2 - Accounting by sale (Use only for integration) | 1 | MV_DATADE | Start date of the period for entering valid entries for accounting. | 20010101 | MV_DATAATE | End date of the period for entering valid entries for accounting. | 20020531 | MV_CTBAIXA | Type of Post Booking (Acc. Payable): (B) Posting, in the generation of (C) Check or (A) Both cases. | C | MV_CARTEIR | Codes of banks in the portfolio. |
| MV_CTBFLAG | Indicates at which time the selection of the accounting flags in the financial records will be made:
- .T. value (Recommended) - through the accounting module - SIGACTB - where there is a transaction tracking (*);
- value .F. (Default) - Through the SIGAFIN module itself: CTBAFIN - where there is no transaction tracking, i.e. the flag selection occurs without checking that errors or cancelations have occurred.
| Informações |
|---|
| title | Database - Transaction Tracking |
|---|
| A transaction is a single work unit. If a transaction succeeds, all data changes made during the transaction are confirmed and become a permanent part of the database. If a transaction finds errors or needs to be canceled and or reversed, all data changes will be deleted.
Source: Microsoft - SQL documents |
| .F. (Default)
.T. (Recommended)
| MV_BX10925 | Defines when the withholding of PIS, COFINS, and CSLL taxes is processed: 1 = At Posting or 2 = At Issue. | 1 | MV_CTMSFIL | Used in offline accounting of the financial module with the question "Consider Source Branch" = YES. .T. = Consider FILORIG fields/.F. = MSFIL | .F. | MV_MXRCTHR | The minimum number of records for a thread to be used in multi-thread processing. | 200 | MV_CNOUTR | Trace/Log for analysis in the performance of the accounting integration - MV_CONOUTR |
|
|
|
