This guide explains how to upload Accounting KPI Actuals in FAM. Actual uploads allow you to break down how revenue booked in the financial statements is derived from:
Production (MWh)
Price per MWh
Accounting adjustments
Ancillary or other income
This helps reconcile operational performance with the revenue recognised in the financial accounts.
⚠️ Important:
The system does not perform validation checks against financial statements. Users are responsible for ensuring uploaded data supports the revenue booked in their accounts.
Overview of the Upload Process
Uploading Accounting KPI actuals is a two-step process:
Upload Production Data (KPI Production)
Production per CGU (Cash Generating Unit).Upload Pricing Data (KPI Pricing)
Revenue drivers per GL code, including pricing and adjustments.
Both uploads are done through the Import Data section.
Step 1 – Upload Production Data
Production data represents actual generation for the reporting period, recorded at CGU level. Each site has at least one CGU.
Navigate to Import Data
Go to Accounting
Select Import Data
Choose Data Type → KPI Production
Select the Period (month) you are uploading
Click Generate
The system will display all entities in the organisation and indicate whether production data has already been uploaded.
⚠️ Important:
If you upload production data for an entity where data already exists, the system will delete the existing data and replace it with the new upload.
Upload the Production File
Click Import Data
Download the Production Template
Populate the file
Upload the completed file
Production Template Structure
| Column | Description |
|---|---|
| Entity Ref ID | External reference ID of the entity - this should be populated in the General Details section before proceeding |
| Site/CGU Ref ID | Reference ID of the CGU or site - this should be populated in the General Details section before proceeding |
| Production | Production for the period (MWh) |
Example:
| Entity Ref ID | Site/CGU Ref ID | Production |
|---|---|---|
| AssetExRef | Site 1 | 3200.44 |
| AssetExRef | Site 2 | 1100.00 |
📌 Notes
Production must be uploaded before pricing data.
Production should represent actual metered generation for the period.
Step 2 – Upload Pricing Data
Pricing data explains how booked revenue is generated from production and other income streams.
This is typically uploaded at GL code level per CGU.
Navigate to Pricing Upload
Go to Accounting → Import Data
Select Data Type → KPI Pricing
Select the same reporting month
Click Generate
Click Import Data
Pricing Upload Logic
For each CGU and GL code, the user must determine whether revenue is:
1️⃣ Production-Driven Revenue
Example: PPA income or merchant electricity sales.
The user should provide:
GL Code
Average Price per MWh
Adjustments
The revenue implied by the row should equal:
Production (MWh) × Price per MWh ± Adjustments
Where production is taken from the Production upload in Step 1.
Adjustments capture accounting differences such as:
True-ups
Prior period adjustments
Hedge settlements
Accounting reclassifications
⚠️ Adjustments are a mandatory field
If no adjustment exists, enter 0.
2️⃣ Ancillary or Other Income
For revenue not linked to production, such as:
Grid services
Capacity payments
Other non-MWh income
Users simply enter the value in the Adjustments/Ancillary Income field.
The Pricing field can be left as zero if the income is not production-driven.
Pricing Template Structure
| Column | Description |
|---|---|
| Entity Ref ID | External reference ID of the entity |
| Site/CGU Ref ID | CGU or site reference |
| GL Code | Financial statement GL account |
| Pricing | Average price per MWh (reporting currency) |
| Adjustments / Ancillary Income | Accounting adjustments or non-production revenue |
Example:
| Entity Ref ID | Site/CGU Ref ID | GL Code | Pricing | Adjustments |
|---|---|---|---|---|
| ExtRefId | CGU Site 1 | 500000 | 50.44 | 100 |
| ExtRefId | CGU Site 1 | 510000 | 45.00 | 12 |
Important Rules
Upload Order
Production must always be uploaded before pricing.
Data Replacement
Uploading a new file for the same entity and period replaces existing data.
Organisation-Level Upload
Files are uploaded at the organisation level, meaning:
One file can contain multiple entities
All entities within the organisation can be included
Responsibility for Accuracy
The system does not validate revenue totals. Users must ensure that:
Uploaded data supports their financial statements
Revenue derived from the upload aligns with booked revenue
Recommended Workflow
Upload Production (MWh)
Upload Pricing per GL code
Confirm revenue breakdown aligns with the financial accounts
Common Issues
Production Not Appearing in Pricing
Ensure production has been uploaded for the same entity and CGU.
Revenue Does Not Match Accounts
Check:
Price per MWh
Adjustments field
Correct GL codes
Production values
Data Overwritten
Re-uploads replace existing data. Always ensure the latest file contains all rows required.
✅ Tip:
Many users export their GL revenue breakdown from the accounting system and then derive price per MWh using the production uploaded in Step 1.
If you want, I can also help you create:
A cleaner user guide with diagrams of the workflow
A validation logic proposal (which would dramatically reduce user errors)
A better pricing model structure (most renewable funds struggle with the GL-to-production reconciliation problem you're solving).
Comments
0 comments
Article is closed for comments.