The Project Accounting process is used to enter and follow up information on project accounting. Project accounting is an integrated part of IFS Financials and is based on one of the code parts B-J. Projects defined in IFS Project or IFS/Customer Orders are integrated with project accounting in IFS Financials. All projects belong to a project group in IFS Financials, which defaults the behavior of the individual project. The queries and reports in IFS/Project Accounting can show information for all projects, regardless of where they originate from.
The most important features of project accounting are the ability to:
Below is a summary of how to use project accounting. Before you do so, review the activities in the Define Financial Basics main process, the activities in Basic Data Requirements (BDR) for Project Accounting, Financials, and the topic descriptions for Project Capitalization and Financial Jobs.
Project accounting in IFS/General Ledger makes it possible to use different types of projects. Project types enable you to determine if and how project costs and project revenues should influence results during the lifetime of the project. Select the project type when entering information on a new project. You can use the following types of projects:
Provided that periodical capitalization is used, the same project can use one project type in the General Ledger and another in one specific Internal Ledger. This can be very useful when a company need to report according to two different accounting principles (GAAP).
Capitalize Rev/Exp projects can be used for customer projects and for your company own production of fixed assets. This project does not affect the result accounts during the lifetime of the project.
Queries and reports enable you to follow up on and analyze detailed information on the projects. When a project is reported as ready, a voucher is created which reverses postings for capitalized revenues back to the original accounts. Capitalized costs are also posted back to their original accounts or to the code strings (Reposting Rule) defined for the project.
Capitalize Expenses projects can be used for long-term projects that are partially invoiced on a continuous basis. Only cost transactions are capitalized. The real costs of the project do not affect the result accounts during the lifetime of the project. Just like for the Capitalize Rev/Exp projects, reversing entries for cost postings for the project are either created automatically in the update routine or in a separate periodical process. When posting revenue for the project, a preliminary cost is estimated on the basis of the contribution margin ratio specified for the project. This preliminary cost is posted to the account defined for posting type GP5 Calculated Project Cost in Posting Control. Counter posting is created for the account specified for the posting type GP3, Capitalized Project Cost. Revenues for the project are not capitalized and remains in the specified revenue account. This means that a preliminary cost estimated on the basis of the project's contribution margin is applied to the company's results. When the project is reported as ready, a voucher is created in which this preliminary cost is reversed and the capitalized cost is posted back to the original accounts, or to the code strings (Reposting Rule) defined for the project.
Capitalize Revenue projects can be used for long-term projects that are partially invoiced in advance on a continuous basis. Only revenue transactions are capitalized. The real revenues of the project do not affect the result accounts during the lifetime of the project. Just like for the Capitalize Rev/Exp projects, reversing entries for revenue postings for the project are either created automatically in the update routine or in a separate periodical process. Costs for the project are not capitalized and remains in the specified cost accounts. Preliminary revenue is calculated in the periodical Revenue Recognition process and applied to the company's results. The resulting revenue recognition voucher is automatically reversed in the next period. When the project is reported as ready, a voucher is created which reverses postings for capitalized revenues back to the original accounts.
No Capitalization projects are the simplest form of project accounting. The project's costs and revenues are not capitalized, but project accounting is still updated. Costs and revenues directly influence the company's result.
Project as Code Part means that it is just used as a standard code part. Project accounting is not updated. This is the only project type that can be used if IFS Financials is not installed.
Project accounting in IFS/Project Accounting uses different types of project origin to distinguish between projects created in IFS Financials, IFS Project, and IFS/Customer Orders. The following origins can be used:
When transactions have been posted to a project, the vouchers must be updated to the general ledger to affect the project accounting. This is done in the Update GL Vouchers assistant.
Project capitalization can be done in two different ways, defined uniquely per project:
When a project is finished it must be reported as complete. For projects of Capitalize Rev/Exp, Capitalize Expenses or Capitalize Revenue types, a voucher is created with postings from the project work-in-process (WIP) accounts back to the original cost and revenue accounts, or to the code strings (Reposting Rule) defined for the project. The default voucher type from function group P will be used in the normal case. The date of the project completion is set as the voucher date, but can be modified. The voucher is placed in the hold table for updating.
Provided that periodical capitalization is used, it is also possible to do one or more partial completions for capitalization projects.
For more information on how to complete/close a project that has Job as the project origin, see the topic description for Financial Jobs or the activity description for Complete Project.
Add investment transactions can be created at project completion to update fixed asset balances with changes in value caused by the project. These transactions can be modified after project completion.
The completion of a project can be rolled back, meaning that the project status will be switched back to Active and the project will be possible to use again. When the completion of a project is being rolled back, a new voucher belonging to the P function group will be created. This voucher will be an exact opposite of the voucher created when the project was completed.
A completed project can also be reopened. The project status will be switched back to Active and the project will be possible to use again. There is however no reversing voucher created. During this process, the project type and other settings for the project can be changed. This can be very useful when receiving warranty claims against a delivered customer project.
The Project Analysis folders in IFS/Project Accounting contain three query pages each for General Ledger and Internal Ledger, which can be used to follow up on projects:
In all these pages it's possible to group balances based on selected code parts and drill-down to underlying voucher rows.
The GL Project Analysis folder also contains a report for follow-up on projects, i.e. the Project Balance Report. This report contains information on balances for one or more projects. Projects which were completed prior to a specified date can be excluded. The balances can also be compared to budget.
As one of the code parts in the code string is being used for project accounting, follow-up reports for projects can also be designed in IFS/Report Generator.