...
Índice maxLevel 4 exclude CONTENTS style none
EFD-PIS/COFINS is a digital file established by the Public Digital Bookkeeping System – SPED, for the use of private legal entities to book PIS/PASEP and COFINS tax payments, in non-cumulative and cumulative calculation systems, based on the set of documents and operations that represent the revenues earned, as well as the costs, expenses, charges and acquisitions that generate credits from non-cumulative taxation.
The bookkeeping documents and operations that represent the revenues earned and the acquisitions, costs, expenses and charges incurred are listed in the EFD-PIS/COFINS file pertaining to each legal entity organizations. The bookkeeping of social contributions and credits is centralized by the parent company of the legal entity.
This routine performs PIS, COFINS and CPRB calculations in accordance with EFD Contribution calculation rules, saving bills and accounting entries so it becomes easier to check and view the values calculated, thus leaving the values ready for creating text files in the future.
The calculation of deemed credit and bookkeeping of record F100 grouped by supplier and item, in compliance with Decree 12,058/2009, is available from February 2015 onwards.
To use the calculation routine, access it in menu Miscellaneous/Calculations and select option
EFD Contributions Calculation, to open the calculation home screen.
The home screen displays a list of auxiliary routines pertaining PIS/COFINS values, to centralize and make the user experience easier. The routines below are displayed:
Aviso |
---|
Report FISR020 was moved to obsolete. Therefore, this option is no longer available on the menu. The report that fulfills this purpose is the EFD Contributions Checking Report (FISR101). |
When selecting one of the options, the relevant routine is executed, enabling the maintenance of operation values.
The option that performs the calculation is "Process Calculation of EFD Contributions". When clicking this options, the following questions must be answered:
Aviso |
---|
Centralizing Parent Company To use the system routine, the system must necessarily be logged onto the branch regarded as parent company. Processing is entirely based on this premise. |
Start Date and End Date: In these questions, enter the period for processing. As the calculation is monthly, the start date and end date must be in the same month.
Record: Enter the number of the Tax Record to be processed for the operations saved in Tax Record (SFT/SF3) tables. To use all records, enter asterisk (*).
Select Branch: Enter Yes if you want to add one more branch in the processing. If this question is set to No, the branch logged onto the ERP is used for processing.
Taxes: Enter the taxes you want to process, through options:
1-PIS/COFINS: Only PIS and COFINS are used for processing;
2-Only CPRB – Only CPRB is used for processing;
3-PIS/COF+CPRB: in this option, the processing uses PIS, COFINS and also CPRB.
PIS/COFINS System: In this question, select the calculation system from the options below:
...
1-Comp.N-Cumul.: Select this option to use the Exclusively Non-cumulative system;
...
2-Comp.Cumulat: This option indicates the system uses the Exclusively Cumulative system, following Competence system criteria;
...
3-Cash Cumulat: In this option, the system uses the Exclusively Cumulative system, following Cash system criteria.
...
4-Cumul/N-Cumul: This option indicates the system selected is Cumulative and also Non-cumulative in the same period.
PIS Payroll: Enter whether PIS must be processed on Payroll. These values originate in the GPE module.
Cooperative Company: Enter whether to process exclusions from the calculation base related to Cooperative Company. You may register the origin of the exclusions in routine FISA039, table CE9.
Institution: If the taxpayer is classified in accordance with §§ 6th, 8th and 9th of ART. 3 of DECREE No. 9,718/98 and Normative Instruction RFB No. 1,285 from 2012, you must set this question to option 1-Yes, for the calculation to make the proper integrations with modules Financials and Health, calculating PIS and COFINS in accordance with the registers and operations of these modules.
Deferral: The PIS and COFINS deferral values are processed and saved through routine FISA054. For the calculation to use these values already processed, select option Yes, so the credits and debits
deferred in the period of from previous periods are used in the calculation.
Tax Receipt: To use operations with Tax Receipts in the calculation, select option Yes in this question.
Cash System Details: Use this question to indicate how PIS and COFINS values must be grouped, in accordance with the options available:
Customer – Group them by customer code;
Bill – Group them by bill number;
Tax No. – Group them by tax document number;
Item Sold – Group them by product code
Generate Bill: By selecting Yes in this question, the routine records the PIS and COFINS bills payable, with the values calculated. Up to 4 bills are generated per calculation:
Bill for Non-cumulative PIS;
Bill for Cumulative PIS;
Bill for Non-cumulative COFINS;
Bill for Cumulative PIS.
Informações | ||
---|---|---|
| ||
Where the revenue code is found, this code is only taken to records M205 and M605, for completion of field Withholding Code in the financial bill, you need to set parameters MV_CODPIS and MV_CODCOF to move the data to the bill generated. |
Book Entry: Enter Yes for the routine to book the entry with the calculated PIS and COFINS values.
To book the entry, Standard Entry 605 for PIS and Standard Entry 606 for COFINS are executed. These entries are only executed when bills are generated in Accounts Payable, an occasion in which you can use values from table SE2, which is selected. You can also read tables CL3 - Summary x Value Payable and CKR - EFD Contributions Calculation.
Aviso | ||
---|---|---|
| ||
For bookkeeping purposes, we usually recommend using the values saved in table SE2; however, if you need to return values from the calculation table, handle the process so as to avoid returning duplicated data, given that field _TRIB contains the same information (one for the cumulative system and another for the non-cumulative one). Note: The configuration of the Standard Entries above is for illustrative purposes only. The customer is responsible for their own configurations in accordance with their business rules. |
Aviso | ||
---|---|---|
| ||
The following Standard Entry codes were created for processing PIS and COFINS Deferrals: 757 - PIS Deferral in Month (Period) In this case, table CKS - PIS/COFINS Debits is selected and we recommend using field CKS_DIF (Deferral in Period) and CKS_DIFANT (Previous Period Deferral). |
Process Withholdings - Outflows: Enter Yes to process withholdings in outgoing documents for later generation of record F600. If you do not need to generate the aforementioned record, enter No.
Cumulative System Indicator: When generating the SPED file, fill this out in detail. If consolidated, select option Consolidated.
Edit Generated Bill?: If set to Yes, all bills generated for adding required data are displayed
Recording Option: The data may be processed two ways, the first is in Grouped form, in which all information and values form all selected branches are consolidated in the Parent Company (which is the branch logged onto to ERP); that is, we have one calculation with values from all branches. The second way is the Individualized one, in which you must be logged onto the branch that generates the Calculation, so there is one distinct calculation for each branch generated, with no centralization in the Parent Company. In this case, the values are processed separately by branch.
When you confirm these options, the processing starts and the calculation screen opens at the end. The calculation is divided in 7 screens, regardless of system/segment, all screens are displayed. If the taxpayer has not determined a value due to system or segment, these data are set to zero.
On this screen, the user can view the totals of all outflow operations used in the calculation process. It displays totals for each outflow CST, separated by system. At the end the totalizer displays values taxed and not taxed. Here on this screen, we get the calculation base values and operation value, not yet the Contribution value.
We get a level of detail for each CST value. Click the value twice to open a new screen with details on this total. We can check the source of this value. For example, it can be by invoice, bill or tax receipt.
To use the values of a given operation on this screen, this operation must fill out at least the CST of PIS and COFINS. We have a line for each CST offered by Federal Revenue. Each line has the totalized value of operations with the corresponding CST.
To define whether revenue is taxable or not, the CST is also checked. For taxable revenue, operations with codes 01, 02 and 03, or yet 05 with rate greater than zero, are used. The other outflow operations with CST 04, 05 with rate set to zero, 06, 07, 08, 09 and 49 are all regarded non-taxable revenues.
Aviso | ||
---|---|---|
| ||
For operations with settled tax value (CST 03), only the revenue value is stated, as the calculation base is composed through measurement unit and quantity. These data are saved in table CL0 – Summary by CST. |
This screen displays all inflow operations used when processing the calculation of EFD Contributions. Here we also have the calculation base values and operation value totalized by CST, whether the operation has or lacks right to credit. Likewise, here we have a level of detail. By clicking the value desired twice, we can check the source of this information, which can be incoming invoice, bill or fixed asset, for example. These values are not yet the credit values.
All operations with CST of PIS and COFINS between codes 50 and 66 are regarded as entitled to credit. Other operations with codes after 66 are regarded as lacking the right to PIS and COFINS credit.
These data are saved in table CL0 – Summary by CST.
On this screen, we can see the debit value composition to be used in the calculation. We have two data groups. The first has information pertaining the Non-cumulative System and the second has information from the Cumulative System. The values are displayed in totalized form and by system. For this Composition of Debits screen, only taxable PIS and COFINS operations are used.
The deferral values of the period or from previous periods are fetched from the Preprocessing (FISA054) routine, which must be previously processed.
In this line, we have the sum of the contribution value of all taxed operations.
Here we have all adjustment values of contribution addition and reduction used in the calculation. We can see these contribution adjustments in detail by clicking twice the PIS or COFINS adjustment value, opening a screen that displays all adjustments used.
In this line, the total deferred values of the contribution in the period that were used in the calculation are stated.
In this line we also have deferral values; however, these values were deferred in previous periods and receipts occurred in this period, thus being taxed.
We get the total contribution value calculated after reduction, addition and deferral adjustments. This value goes to the calculation. The values of credits and withholdings are deducted from it. Double-click this line to view details on the values processed by rate, CST and contribution code.
This information is saved in tables CKS – PIS/COFINS Debits and CLA – PIS/COFINS Adjustments.
On the credit composition screen, we get details on inflow operations with right to credit, stated in totalized form. Because they are credit values, we have no division by system, as the taxpayer is entitled to credit only in Non-cumulative operations.
See below the origin of the data on the lines of this screen:
Calculation Base by Inflows: Operations with CST entitled to credit (CST between codes 50 and 56) are used in this line;
Calculation Base of Deemed Credit: Operations with CST entitled to deemed credit (CST between codes 60 and 66) are used in this line;
Calculation Base Fixed Assets - Depreciation: In this line, operations of integration with the Fixed Assets module are used, configured to generate credit using depreciation criterion;
Calculation Base Fixed Assets - Acquisition: In this line, operations of integration with the Fixed Assets module are used, configured to generate credit using acquisition criterion;
Calculated Calculation Base Total: Here we have the sum of the calculation bases of the aforementioned lines.
Calculated Credit Total: Here all credit values calculated before going through adjustments and deferrals are used.
Addition and Reduction Adjustment Total: Here we have all adjustment values of credit addition and reduction used in the calculation. We can see these credits in detail by clicking twice the PIS or COFINS adjustment value, opening a screen that displays all adjustments used.
Aviso | ||
---|---|---|
| ||
In the deemed credit calculation, if the need arises to generate a reversal resulting in reduction adjustment, we have the auxiliary registers: FIS0104 PIS and COFINS Reversal Percentages Register and FIS0103 Registration of PIS and COFINS Credits Liable to Reversal. |
Total Credit Deferred in the Period: Here we have credit values deferred in the period.
Total Available Credit in the Period: In this line we have the total credit value after reduction, addition and deferral adjustments. We can view credit values in detail, separated by rate, credit code and credit calculation base code. This value is carried over to the calculation screen, to be used for deducting the debit value.
The data on this screen are filled out if the system is equal to Non-cumulative exclusively or Non-cumulative and Cumulative in the same period. This information is saved in tables CL8 – Consolidated PIS/COF Credit, CL9 – Detailed PIS/COF Credit and CLA – PIS/COFINS Adjustments.
Aviso | ||
---|---|---|
| ||
Tables CL8 - Consolidated PIS/COF Credit and CL9 - Detailed PIS – COF Credit are only recorded with the period has credit. Otherwise, these tables are not recorded and, consequently, the records pertaining the calculation are not generated, since there is no credit in the period. Moreover, not generating these records does not cause any errors of validation or delivery of the file created. |
On this screen, we start with the debit and credit values already stated on previous of debit and credit composition screens. Here we can also check the withholdings of the period and from previous periods. We have values separated in two groups: Cumulative System and Non-cumulative System values. If there are balances of credits or withholdings, they are used on this screen. The utilization source follows:
Credits from previous periods, credits of current period, withholding from previous periods, withholdings of current period.
If the value of credit or withholding exceeds the debit value, these values are used in credit and withholding balances, thus being carried over to the next period.
Here we can have up to 4 values payable, which are Non-cumulative PIS and COFINS, and Cumulative PIS and COFINS.
The final PIS and COFINS values payable are carried over to the tab below the payment information, in which the user must enter the revenue code and due date. See line details below:
Aviso | ||
---|---|---|
| ||
The revenue code may be filled out automatically, through parameter MV_CDRCEC. For more information on how to use this parameter, access:TUTEDN_TD_REVENUE_CODE_M205_M605. The credits are only used in the period if field Cred Reserve (CCY_RESCRE) is set to option "No or Blank". |
Contribution Total Value: Sums of calculated values on Debit Composition screen;
Discounted Credit Value - Previous Period: Credit balance value used for deducting the contribution value;
Discounted Credit Value - Current Period: Credit value of current period used for deducting the contribution value;
Contribution Value Due: Contribution value after using the credits.
Tax Value Withheld – Previous Period: Withholding value of previous period used for deducting the contribution value;
Tax Value Withheld – Current Period: Withholding value of current period used for deducting the contribution value;
Other Deductions in Period: Value of other deductions used for deducting the contribution value;
Non-cumulative Contribution Value Payable: PIS/COFINS contribution value payable, after using credits, withholdings and other deductions.
Credit Balance to Carry Over to Next Period: Current credit balance after calculation to be carried over to the next period. Here we can double-click values to view their details by credit code and source period. These values are saved in tables CCY and CCW.
Aviso | ||
---|---|---|
| ||
If you need to set priority for credit codes (table 4.3.6) to be consumed first, use parameter MV_OCODCSC. Example of completion of parameter MV_OCODCSC: 101, 201, 301. In this example, the processing order for credits follows the codes 101, 201 and 301. The order described is first applied to the previous credit balance and then applied to the current credit balance. |
Withholding Balance to Carry Over to Next Period: Here the withholdings balance is stated after calculation. We can also double-click these values to view their details. We can check details by withholding nature indicator. These values are saved in tables SFV and SFW.
Aviso | ||
---|---|---|
| ||
The information is only saved in tables SFV and SFW if there is a balance to be carried over to the next period. For further information on how to request Refund/Compensation for PIS and COFINS Withholdings, refer to PIS/COFINS Withholding Control |
At the end of the calculation, if the questions for bill generation and bookkeeping are set to YES, then bills payable are saved with the contribution value and the standard entry for bookkeeping is executed.
The calculation values are saved in table CKR - EFD Contributions Calculation, and the payment data are saved in table CL3 - Summary x Value Payable.
Revenue code values can be broken down. For further information, refer to bulletin FIS0082_for_PIS_COFINS_Revenue_Code_Rules
PIS Payroll: On this screen we have the values returned by integration with GPE module. They are on a separate screen because this PIS value on Payroll cannot be mixed with the calculation value. On this screen we do not have any value details.
CPRB: CPRB is also handled on a screen other than the PIS/COFINS calculation screen. Here we have the totals of this contribution, displaying total gross revenue values and the revenues subject to CPRB, as well as exclusion values, reduction and addition adjustment and, finally, the CPRB value payable.
This screen is only filled out if, in question Taxes the option to process CPRB is set, considering integrations with the HR module or Billing, in accordance with parameter MV_SPCBPRH. This information is saved in the following tables:
CKV – CPRB Consolidated
CKX – CPRB Detailed
CKW – CPRB Adjustments
To the right of the routine home screen, you can view the calculations already performed, by period and by tax. These values are saved in tables. If you need to view the calculation, there is no need to perform all calculations and processing again, just click View or double-click the calculation desired to load the data onscreen. In view mode, you cannot edit or generate bills/book entries.
If you need to generate bills from a calculation you did not generate before, just click the calculation at issue onscreen and click edit to load the data, then you can make adjustments or generate bills/book entries.
If you need to delete any processed calculation, just select the calculation desired and, in related features, click delete. The data of the calculation at issue will be deleted.
Aviso | ||
---|---|---|
| ||
You can only delete or edit calculations that did not yet generate bills and/or book entries. In this case the calculation must be reprocessed to undo the bills and bookings. |
If you need to reprocess a calculation because of some wrong registration information, or of some invoice, bill or tax receipt not entered before, access the initial calculation routine, click Process EFD Contribution Calculation, fill out the fields of the initial questions and confirm them. The routine will thus identify that a calculation already exists for that period and branch, then ask whether you want to reprocess the values. If you answer Yes, the bills generated are deleted and the booking is undone through standard entry 611 for PIS reversal and 608 for COFINS Reversal.
After this process, the reprocessing questions are displayed, in which some options are available for you to select which types of information to reprocess or not. If you select option Yes, then the information at issue is reprocessed. If you enter No, this information is not reprocessed and the data already saved in reprocessing is used. These are the available reprocessing options:
Incoming Invoice: Enter Yes to reprocess incoming invoices;
Outgoing Invoice: This option indicates whether outgoing invoices are reprocessed;
Incoming Bill: This option defines whether bills not linked to the document that represents inflow operations are reprocessed;
Outgoing Bill: This option defines whether bills not linked to the tax document that represents revenue are reprocessed;
Fixed Assets: Enter whether Fixed Asset operations entitled to credit must be reprocessed;
Tax Receipt: Enter whether operations with Tax Receipt must be reprocessed.
CPRB: Enter whether CPRB values must be reprocessed.
Thus you can choose which operations must be reprocessed. If you only want to reprocess Fixed Asset operations and keep the other data, then set only the Asset question to Yes and leave the other questions set to No. Only operations from Fixed Assets are reprocessed, thus updating the calculation.
Aviso | ||
---|---|---|
| ||
We cannot control the reprocessing of other sources as entry point. These operations are always reprocessed. |
When the amount of data in the customer's database is large and the routine takes too long to perform the calculation, we recommend Multithreaded processing to divide the processing load and take less time to perform the calculation. To enable Multithreading, you must edit parameter MV_QTDTAEC by entering the quantity of threads to be processed in the calculation. By default, this parameter is set to 0 (zero), in which case Multithreading is disabled. When the content is greater than 1, Multithreading becomes automatically enabled. Just edit this parameter. Other questions and settings remain the same.
While performing the calculation, the processing log is saved with the start time and end time of the calculation, plus calculation process details. To access this log, click View Log in Related Features.
The user can perform the calculation two ways. The first is by grouping all the information and values in the parent company (the one logged) and, in the case of manual adjustment entries, the values of all branches are combined and added to the parent company, thus generating a single calculation containing the values of all branches. To do this, the question Recording Option must be set to "Grouped". In this generation option, adjustments that are manually entered and added to the branches are only disregarded if added to the centralizing parent company view.
The second way is by performing the calculation by branch distinctly, each branch having its own calculation. When all values are correct, the calculations of each branch can then be consolidated into a single one in the company view. To do this, you must set question Recording Option to "Individualized" and log onto the branch to generate the calculations individually. After checking the data, the user must click option Group Branch -> Parent Company, enter the company in which to consolidate the calculations, then fill out in which calculation period to group them, then select which branches must have their calculations consolidated. Once these data are confirmed, the routine groups the data of all branches selected.
Point of Attention
By selecting option Individualized EFD Contributions Calculation and clicking Group Branch -> Parent Company, the values of the branches processed are grouped at the branch selected as grouping company; that is, only Credit is added to Credit and Debit to Debit.
No new processing of EFD Contributions Calculation occurs. This means the system displays data on Debits and Credits as calculated individually, without applying calculation of Debit - Credit to compose block M.
Aviso | ||
---|---|---|
| ||
To use this feature, the sharing of tables CCW, CCY, SFV, SFW, CF3, CF4 and CF5 must be set to exclusive, to perform the calculation and control balances by branch. If these tables are shared, the user must change the sharing mode through the configurator. Field CLA_FILORI enables the system to generate records M225 and M625 in grouped as well as individualized form. |
When the calculation is performed with Cumulative and Non-cumulative systems in the same period, there must be a criterion per operation to distinguish the system it belongs to. For operations saved to Tax Records, the routine checks parameter MV_M996TPR, which defines whether the system of operation is described in the register of TIO, Product or Customer, set through fields: F4_TPREG, B1_TPREG or A1_TPREG, respectively.
To calculate EFD Contributions, the data have multiple possible sources, listed below:
Inflow and/or outflow operations saved to Tax Records (SFT/SF3) are used, depending on the system. By following EFD rules, the following document models are used:
01, 02, 04, 06, 07, 08, 09, 10, 11, 13, 18, 21, 26, 28, 29, 22, 2D, 55, 57, 1B, 8B
Be mindful that we have no model for documents of services rendered or contracted, so when the model is blank and the document pertains to a service, it is also used in the calculation.
Yet with tax document operations, there is a procedure for revenue CFOP in which we can define whether a given CFOP is used as revenue or not, as set in these parameters:
Aviso | ||
---|---|---|
| ||
Invoices with types: NFPS, NFS, NFSE and RPS are used as Revenue in tab Outflow Operations, regardless of the CFOPs entered in parameters MV_CFAREC and MV_CFEREC. You must enter the invoice CFOPs with these types in parameter MV_CFAREC if the CFOP is not handled by the standard. Thus, the values are booked as Gross Revenue Total in tab CPRB. Invoices model 65 and 59 (types NFCE and SATCE respectively) are considered revenue value when the CFOP ends in 949 and is one of the revenue CSTs (01/02/03/04/05/06/07/08/09), regardless of whether they have been entered in parameter MV_CFAREC. |
The tax receipts used are those recorded to Tax Records (SFT/SF3) that have configured Z reduction and ECF machine registration.
The bills used are those recorded in module Financials that are not linked to a tax document, as long as they have been correctly configured with the Financial Nature.
The Assets used in the calculation are those registered in module Fixed Assets and entitled to PIS and COFINS credit.
Aviso | ||
---|---|---|
| ||
Concerning assets added through incoming document not configured for PIS and COFINS credit calculation, with CST, Calculation Base Code of Credit, Rate, etc.; this information must be complemented in the Asset classification, in module Fixed Assets, to correctly configure the asset for use in the calculation. |
The calculation uses the operations registered in routine Other Documents (FISA048). These operations are not linked to the tax document.
Operations with tax withholdings that are correctly generated in module Financials are used.
Some Entry Points created to handle values in routine SPEDPISCOF that generate revenues or credits are also used. They are:
Some data also registered in auxiliary routines in module Tax Management are used in the calculation, in accordance with the table below:
Routine Name | Program |
PIS/ COFINS Exclusions | FISA039 |
PIS/COFINS Deduction | FISA041 |
PIS/COF Credit Adj. | FISA042 |
PIS Credit Contr. | FISA044 |
COFINS Credit Contr. | FISA045 |
PIS Withh. Contr. | FISA216 |
Withh. Contr. COFINS | FISA217 |
Extemporan. Credit | FISA046 |
Opening Inventory | FISA049 |
PIS/COFINS Comp.Res. | FISA050 |
Deferral Preprocessing | FISA054 |
Still in module Tax Management, some taxable PIS and COFINS operations are not recorded in tax records, such as sales off premises and billable telecommunication operations. Details on these operations are found in tables SF2 and SD2, not in SFT and SF3; hence, these are the only hypothetical operations with invoices not recorded in Tax Records. The data to be used pertain the outflows of the period, configured for PIS and COFINS calculations. We will not risk duplicating values when reading SFT and SD2 because these operations are not recorded in the book.
Regarding the Cash system, the source of the information begins with the receipts registered in module Financials and the taxation is a function of this percentage.
For this group of companies, the source of information is in module Financials and/or module Health Insurance. These integrations are configured in parameter MV_INTBLCI.
The code of the Financial Nature (SED) to be recorded in Accounts Payable bills can be entered in parameters:
MV_PISAPC - Enter the nature to be used for the PIS bill in cumulative system. If the parameter is blank, the content of parameter MV_PISNAT is used.
MV_PISAPNC - Enter the nature to be used for PIS bill in non-cumulative system. If the parameter is blank, the content of parameter MV_PISNAT is used.
MV_COFAPC - Enter the nature to be used for the COFINS bill in cumulative system. If the parameter is blank, the content of parameter MV_COFINS is used.
MV_COFAPNC - Enter the nature to be used for the COFINS bill in non-cumulative system. If the parameter is blank, the content of parameter MV_COFINS is used.
If the parameters above are not filled out, the routine then uses parameters MV_PISNAT and MV_COFINS to get the Financial Nature for PIS and COFINS, respectively.
If the due date of the bill generated by the calculation is not a business day, you can define whether to advance the due date to the last business day or postpone it to the next business day. You can define this through parameter MV_VENCPIS.
If the content of the parameter is equal to .T., then the due date is postponed to the next business day. If its content is equal to .F., then the due date is advanced to the previous business day.
You can configure this procedure through parameter MV_DTMREG. In this parameter, enter the date on which the change from accruals to cash method happened. Once you have configured it, the contributions of the documents issued up to the date entered, calculated by the cash system, are voided through generation of contribution reduction adjustments, so that the revenue taxed previously in the period of issue by the accrual system is not taxed again and is also presented in the EFD for transparency purposes. If more than one change exists, the parameter should always contain the date of the last change.
The purchase return may occur in the purchase period itself or in a later period. If the return occurs in the period itself, then the credit calculation base is reduced in accordance with return percentage. If the return occurs at a later period, then a credit reduction adjustment is appropriate. Be mindful that we only get purchase returns in the Non-cumulative system
The sales return can also occur in the sales period itself or in a later sales period, whether in the Cumulative system or in the Non-cumulative system. For the Cumulative system, if the return occurs in the sales period itself, then the contribution calculation base is reduced in accordance with the return percentage. If it occurs at a later period, then the reversal is done through contribution reduction adjustment.
For the Non-cumulative system, whether the return is in the period itself or in a later sales period, in both cases there is credit hypothesis and no contribution reversal.
There are two procedures to cancel outflow operations, one for cancellations within the issue period and another for cancellations outside the issue period.
For cancellations within the period, these revenues do not compose the calculation base, so no adjustment is needed.
For cancellations at a later period, the contribution must be reversed through a contribution reduction adjustment. In parameter MV_SPDAJCA, we can set the quantity of previous months the routine uses for reversing the contribution.
Card documentos | |
---|---|
|
|
...