Default Calculation Method: The Accrual Engine calculates periodic accrual amounts using the formula: planned costs minus actual costs. This calculation method assumes that planned costs accurately reflect reality.
Concrete Example:
- Date: 31.05.2018
- Purchase Order: 4711, Item 10
- Proposed Accrual Amount: 2,000 EUR
- Planned Costs: 5,000 EUR
- Posted Invoices (Actual Costs): 3,000 EUR
- Calculation: 5,000 EUR – 3,000 EUR = 2,000 EUR accrual
Basis of Planned Costs: The 5,000 EUR in planned costs was derived by linearizing the PO item net value of 12,000 EUR across the purchase order's lifetime—spanning from the PO creation date (01/2012) to the planned final delivery date (12/2018).
Underlying Assumption: The 2,000 EUR accrual amount assumes that the company has already received goods or services valued at 5,000 EUR, but the corresponding invoice has not yet been posted (e.g., because the supplier has not sent it).
Nature of Accrual Proposals: The accrual amounts calculated by the Accrual Engine are merely proposals based on assumptions, not definitive figures.
Review Necessity: Given the assumption-based nature of these calculations, it is essential that a qualified person reviews and/or approves the proposed accruals to validate whether the underlying assumption is correct.
Best Practice Recommendation: Rather than reviewing accrual amounts directly, it is recommended to review the planned costs instead.
Review of Planned Costs Instead of Accruals
Default Configuration:
- The Accrual Engine calculates accruals as planned costs minus actual costs (default and recommended setting)
- When using this method, the review process should be activated for planned costs rather than accrual amounts
Rationale for Reviewing Planned Costs:
- Reviewer Expertise: Reviewers are often project leads or other non-accounting personnel who lack understanding of accrual accounting concepts
- Late Invoice/Goods Receipt Handling: Accruals automatically reduce when invoices or goods receipts arrive after the review/approval phase is complete
- Progress Representation:
- Planned costs represent actual project progress
- Accruals represent only the missing/outstanding costs
- When percentage of completion is reviewed, planned costs (not accruals) accurately reflect this progress metric
Key Point: Although reviewing planned costs may seem counterintuitive initially, it is more practical and suitable than directly reviewing accrual amounts for the reasons outlined above.
Difference between Review And Approval
The Accrual Engine implements review and approval of periodic accrual amounts with the following characteristics:
Review Process:
- Review is always optional
- If no one reviews the proposed accrual amounts for a purchase order item, the system automatically posts the proposed amount
Approval Process:
- Approval is mandatory for posting
- The system only posts the proposed accrual amount for a purchase order item if the approver grants approval
Concurrent Implementation:
- Both review and approval steps can be active simultaneously
- This enables a 4-eye principle (dual control) system where, for example, the purchase order owner performs the review and a G/L accountant performs the approval
Adjustment Capabilities:
- Both reviewers and approvers can adjust the proposed accrual amounts or planned costs
- When adjusting amounts, users must enter a reason code and may optionally add a comment explaining the adjustment
- The system creates change documents each time a user adjusts an amount
- Change documents can be displayed using transaction POACTREE03 (Display Changes)
- Attachments can be added in review and approval screens to provide further explanation for any accrual amount or planned cost adjustments
Source link