Project Finance
Project Financial Structure & Capitalization
Establishes the financial framework of a project so that costs and revenues can be captured, capitalized and followed up over the project life cycle. The project type (e.g. Capitalize Rev/Exp, Capitalize Expenses, Capitalize Revenue) determines whether transactions hit the result accounts immediately or are held on work-in-process/balance accounts. Cost/revenue elements and posting control setup underpin how every project transaction is classified financially.
Project Cost Capture & Cost Transfer
Captures cost, hours and revenue from connected objects (purchase orders, shop orders, work tasks, sales contracts, resources, documents) onto project activities using project cost/revenue elements. Values flow through defined stages (estimated, planned, committed, used, actual) and are reported in base, transaction and optionally project currency. Supports transferring and reposting costs between projects/activities and code strings.
Project Invoicing (Progress / Milestone)
Generates customer invoices for projects from invoiceable transactions or from an invoicing plan (progress/milestone billing). Preliminary invoices are created and released, with support for including normal invoiceable transactions alongside plan amounts and for project-unique billing. Invoicing plans carry planned sales amounts used for both billing and WIP estimation.
Project Forecasting & WIP
Handles accrued income by executing the Work in Progress (WIP) routine for invoiceable but not-yet-invoiced project transactions, creating a period-end voucher that is auto-reversed on the first day of the next period. Uses estimated WIP revenue amounts from invoicing plans and supports correction/rerun. Underpins financial follow-up and forecasting of project cost, revenue and margin.
FM Budgeting, Recharge & Cost Allocation
Builds and controls the FM cost base for a whole estate and pushes it back out to whoever pays for it. Cost is captured at the point of work against the Work Order and its Functional Object so it rolls up by building and service line automatically, then apportioned to occupiers or business units and raised as a Customer Order and Invoice. Variance and lifecycle re-forecasting close the loop each period.
Everything you can see here is real and current, the names, the structure and the counts come straight out of the ModelIFS library and change as it grows. What sits behind the license is the worked-out content itself: the execution steps, the data each one needs, the configuration decisions, the KPIs, the integration points, the workshop questions and the diagrams. That is the part you would otherwise spend a program building from nothing.
Sign in to open it