Business Reconciliation
Application component: Revenue Accounting Contract Processing
App type: Transactional
Line of business: Finance
Leading industry: Cross Industry
Solution capability: Financial Accounting (S/4)|Revenue and Cost Accounting (S/4)
Description:  You can display the inconsistent data between sender components with SAP and Revenue Accounting and Reporting (RAR) that results from Run Business Reconciliation in Background. You can also reconcile data online for a very limited number of revenue contracts. You can handle the selection data of a business reconciliation as follows:  If you choose the Run Method as Display Background Check Results, you need to enter the company code, accounting principle, and other selection data, such as operational document and revenue contract. This specifies the reconciliation data that you want to display. The reconciliation data results come from the Run Business Reconciliation in Background Fiori app.   If you choose the Run Mode as Run Reconciliation Now, you need to enter the company code, accounting principle, sender component, logical system, and other selection data such as a limited number of revenue contracts or operational documents that helps to specify the data that should be reconciled now. The reconciliation result is saved into the FARR_D_BIZ_RECON table.   If you only want to view the inconsistent contracts, set Inconsistent Contracts Only as Yes.   If you only want to view the revenue contracts with data validation errors, set the Data Validation Check Results as Yes.   You can have a comprehensive look at selected revenue contracts or inconsistent contracts as follows:  The values for reconciliation between the sender component and RAR. For example, if Operational Document Price and Contractual Price from Operational Doc. are inconsistent, they are highlighted in red for the revenue contracts. They are also displayed in Standard View by default.   Data Validation Check Results for revenue contracts. You can navigate to Data Validations to check the details.   The values for revenue recognition, cost, contract liability and contract asset, such as Recognized Revenue, Recognized Cost, Posted Revenue in Company Code Currency, Posted Invoice Amount in Company Code Currency and Posted Contract Liability in Company Code Currency for revenue contracts. These are displayed in Accounting View by default.   The values in other currencies, such as in Local Currency 2 and Local Currency 3. These are hidden by default.   You can view the detailed information of performance obligations within each revenue contract as follows:  The values for reconciliation between sender component and RAR in Standard View are displayed by default.   The values for revenue recognition, cost, contract liability and contract asset, such as Recognized Revenue, Recognized Cost, Posted Revenue in Company Code Currency, Posted Invoice Amount in Company Code Currency, and Posted Contract Liability in Company Code Currency for revenue contracts. These are displayed in Accounting View by default.   The values in other currencies, such as in Local Currency 2 and Local Currency 3. These are hidden by default.   You can also view the details of all condition types per performance obligation:  The values for reconciliation between sender component and RAR are displayed for each condition type.   Note If a performance obligation has inconsistent condition types, then the performance obligation and revenue contract are also inconsistent even though the total amount may be same when you compare the sender component and RAR. Example A revenue contract is created with a subscription in Sales and Distribution. The pricing condition types of the subscription includes PR00 (1000 EUR) and PR01 (800 EUR). However, the pricing condition types of the subscription in RAR are PR00 (800 EUR) and PR01 (1000 EUR).If you perform Business Reconciliation for the revenue contract, then the result is displayed as follows:Reconciliation Revenue Contract   Revenue Contract   Operational Document Price   Contractual Price from Operational Document      RC01   1800 EUR   1800 EUR   Reconciliation Performance Obligations   Performance Obligations   Operational Document Price   Contractual Price from Operational Document      POB1    1800 EUR   1800 EUR   Reconciliation in Condition Types   Condition Types   Operational Document Price   Contractual Price from Operational Document      PR00   1000 EUR   800 EUR     PR01   800 EUR   1000 EUR    
Revenue Accountant can use this application to do reconciliation between sender components and revenue accounting engine side.
Key features:  Reconciliation Data for Revenue Contracts, Performance Obligations and Condition Types The app reconciles the data between the sender component and RAR, including price, cost, invoice amount, and quantity. If any of the situations outlined below occur, the revenue contracts, performance obligations and condition types will not be consistent. This means they will be highlighted in red.  Operational Document Price is not equal to the Contractual Price from Operational Document   Operational Document Cost is not equal to the Total Cost   Operational Document Invoiced Amount is not equal to the Invoiced Amount   Operational Document Quantity is not equal to the Order Quantity   For optimized inbound processing, the Operational Document Actual Cost is not equal to the Actual Cost   Note If you would like to check inconsistent data only, you can set Inconsistent Contracts Only as Yes in the search criteria. Data Validation Check Results If a revenue contract does not pass the data validation results from Data Validation, then the Data Validation Check Results are set as Error and highlighted in red. You can navigate to Data Validation to check the details. In all other cases, the Data Validation Check Results of the revenue contract will be empty. Standard View for Revenue Contracts, Performance Obligations and Condition Types You can view the reconciliation data between the sender component and RAR in Standard view for revenue contracts and performance obligations within a revenue contract, along with the condition types of each performance obligation. They are highlighted with red if the data is inconsistent. The following list pairs are the latest value for revenue contracts, performance obligations and condition types:  Operational Document Price and Contractual Price from Operational Document   Operational Document Cost and Total Cost   Operational Document Quantity and Order Quantity   Operational Document Invoiced Amount and Invoiced Amount are the total aggregated amount. Accounting View for Revenue Contracts and Performance Obligations You can see the values for revenue recognition, cost, contract liability and contract asset, such as Recognized Revenue, Recognized Cost, Posted Revenue, Posted Invoice, Posted Cost, Posted Contract Asset and Posted Contract Liability.  The value is the aggregated amount up to the current accounting period. 
Business roles: Revenue Accountant| Administrator - Revenue Accounting
Administrator - Revenue Accounting : 
Schedules and runs periodic jobs for RAIs processing,  revenue postings, etc. 

Revenue Accountant : 
Displays and edits revenue contracts relevant information, check and reconcile postings for revenue contracts.