Overview
Expenses represent the monthly financial data loaded into Yarken before cost allocation begins. This includes actual spend from the general ledger, as well as planning data such as budgets and forecasts. Actual spend is loaded into the Spend model, while planning data is loaded into the Budget and Forecast models.
Expenses are the starting point of the Yarken cost model. Once loaded, expense data becomes available for Cost Pool allocation and then flows through the downstream model.
The typical flow is:
Expenses → Cost Pools → Towers → Assets → Solutions → Consumers
Use the Expenses section in Yarken Designer to load, view, edit, and manage monthly spend, budget, or forecast data.
What expenses include
Expenses may include:
-
Monthly actual costs from the general ledger
-
Journal-level spend records
-
Budget and forecast data used for planning
-
Monthly records loaded into a selected model type.
-
IT-related expenditure categorized as:
-
OpEx – operational expenditure
-
CapEx – capital expenditure
-
Each month tile shows the loaded expense amount and the last load date.
Why expenses matter
Expenses are used to:
-
provide the source spend for the TBM model,
-
enable Cost Pool allocation,
-
support budget and forecast comparisons,
-
provide transaction-level reporting,
-
support variance and trend analysis,
-
enrich downstream reporting across Towers, Solutions, and Consumers.
If expenses are missing or incomplete, downstream allocation and reporting will also be incomplete.
Key capabilities
The Expenses area supports:
-
Monthly data loading
Load spend, budget, or forecast data by month. -
Manual expense creation
Add individual expense records directly in the application. -
Bulk upload
Upload expense files using supported templates. -
Expense review and filtering
Search, filter, group, and inspect expense records by key dimensions. -
Editing GL spend records
Update supported GL line items directly in the application. -
Upload rules
Standardize or enrich expense data during upload. -
Uploaded file tracking
Review upload status, mapped fields, and loaded records.
Expense fields
|
Field name |
Description |
|---|---|
|
Expense Type |
Defines the type of expenditure, such as OpEx or CapEx. |
|
Account Code |
The general ledger account code associated with the expense. |
|
Cost Center Code |
The cost center responsible for the spend. |
|
Amount |
The actual spend amount for the expense record. |
|
Transaction Date |
Date when the spend or financial transaction occurred. |
|
Foreign Amount |
Spend amount in a foreign currency, if applicable. |
|
Foreign Currency |
Currency used for the foreign amount. |
|
Exchange Rate |
Rate used to convert the foreign amount to the reporting currency. |
|
Vendor Code |
Vendor identifier from the financial system. |
|
Application ID |
Application associated with the spend record. |
|
Invoice |
Vendor invoice number. This can support invoice drill-down and linkage to purchase orders or contracts. |
|
Journal ID |
Identifier for the journal entry or transaction. Multiple records can reference the same Journal ID. |
|
Journal Line |
Line description associated with the journal entry. |
|
Project ID |
Project identifier from project portfolio or related systems. |
|
Entity Code |
Entity responsible for the expenses. Defaults to the Default entity code if unspecified. |
|
RGT Model |
Run, Grow, Transform classification. |
|
Cost Type |
Cost classification, such as Cloud Accrual, Cloud Invoice, or Cloud Accrual Reversal. |
|
SKU |
Stock keeping unit or product/service identifier. |
|
Cost Pool |
Cost Pool associated with the expense, if already known. |
|
Sub Cost Pool |
Sub Cost Pool associated with the expense. |
|
Tower |
Tower associated with the expense, if already known. |
|
Sub Tower |
Sub Tower associated with the expense. |
|
Exclusion Type |
Used to mark expenses that should be excluded from GL transaction processing or downstream use. |
Next step
Related content