Enterprise Financials — Admin Configuration Guide
Enterprise Financials is where project financials (Estimate, Budget, Forecast, Actuals, Commitments, Revenue) are entered — EnterpriseFinancials/EFMain.aspx. Before that is usable, an admin has to work through a chain of setup screens under Admin. The order below follows real dependencies: required dropdowns in the UI and foreign keys in the database.
1. Decide the Master Financial Settings First — This Locks Once Data Exists
Screen: Admin/Configuration_Financials.aspx → “Financials” tab
Turn on Enable Financial Management.
This setting becomes permanently read-only the moment any financial data exists: Budgets, Forecasts, Commitments, Actuals, or Estimates. Decide it correctly before anyone enters a value.
Also set: Start of Financial Year, fiscal calendar usage, visible end-user tabs, iteration source per tab, iteration labels, manual-entry or role restrictions for Actuals and Commitments, and import enablement.
If using Advanced Project Forecasting, changing the current forecast period or turning on Project Forecast Submission is blocked while Submit Forecast or EAC workflows are in flight for any project.
2. Configure Currency Before Anything Cost-Related
Screen: same page → “Currency” tab
Configuration Item | Guidance |
|---|---|
Multi-currency | Decide “Enable Multi Currency” and “Allow FX Rate at Project Level” up front. |
Project-level FX | When FX-at-project-level is disabled, all projects use the latest FX rate for their base/local pair. |
Base currency | A fresh install auto-seeds EUR as the base currency if none exists — replace this deliberately if it is wrong for your organisation. |
Exchange rates | Exactly one currency must be flagged Base, it cannot be archived, and every currency needs at least one effective-dated exchange rate. |
3. Build the Chart of Accounts — Strict Parent-First Order
Screen: Admin/Configuration_Budget.aspx (“Budget Configuration”)
Order | Configuration Area | Dependency / Notes |
|---|---|---|
1 | Global Site | Name, Current Actuals/Forecast Period, CBS Code Structure, Default Capital/Expense Code (must differ), Is Master. |
2 | Account Group | Requires selecting a Global Site. |
3 | Account Sub Group | Requires selecting an Account Group. |
4 | Account / Account Code | Requires selecting a Sub Group; also references Element of Cost, Default Distribution Curve, and VAT Applicable. |
This order is enforced by required fields in the UI and cascading foreign keys in the database. Deleting a parent deletes all its children.
Before creating Account Codes, populate the lookups they reference on the same page: Element of Cost, Distribution Curves (changing a default curve only affects new projects going forward), and VAT Rate.
Also on this page: Budget Type, Operational Codes, Contract Bands, Allowed Roles, Grant, Expenditure Category, Finance Localization, and File Types.
A few tabs — Payment Schedule, Client Link, Supplier PO & Invoice, and Client Invoice — are hidden in markup and are likely legacy or customer-specific. Confirm whether your environment needs them.
4. Link Budget Types to Operational Codes
Screen: Admin/BudgetType_Linking.aspx
Requires step 3’s Budget Types and Operational Codes to already exist.
Use this step to align financial categorisation before users start entering project data.
5. Configure Cost Book
Screen: Admin/Configuration_CostBook.aspx
Sequence | Area | Key Notes |
|---|---|---|
1 | Cost Book Registers | Set up register foundations first. |
2 | Cost Book Submission | Configure submission behaviour before admin settings. |
3 | Cost Book Admin | Largest settings surface: Project Forecast Period, Forecast in Current Month, Display Invoice Lines, Capex/Opex Totals, Rollup Internal Order, Forecasting Level, Lock Current/Future/Previous Year Budget, and Cashout Forecast Profiling. |
4 | Cost Book Columns Admin | Configure visible and managed columns. |
5 | Cost Book Attributes | Complete attribute setup after core configuration. |
Gotchas: Fixing the Forecasting Level applies to all projects, not per project. Two settings are explicitly flagged “should only be used under guidance of Cora Systems”: Direct Cost Committed = Direct Cost Actual, and Add Down Payment to Actuals.
6. Configure the Rate Matrix
Screen: Admin/Configuration_Rate_Matrix.aspx
Rate Matrix Configuration
Options — checking “Apply Burden Costs” makes Overhead Code, Overhead Rate IDs, and Sub Category required.
Rate Adjustments — min/max, by Skill and/or User.
Burden Rule Matrix
Burden Costs — effective-dated overhead percentages.
7. Configure Invoicing (If Used)
Screen: Admin/Configuration_Invoicing.aspx
Configure Invoicing Admin first.
Then configure Invoicing Localisation.
8. Map Financial Registers
Screen: Admin/Configuration_Financial_Registers.aspx
Map each Business Case and Contract register to Status, Capital, and Revenue values.
Mappings must be unique per register.
9. Configure Funding Sources (If Used)
Screen: Admin/Funding/FundingSource.aspx
Set “Number of Attributes” first.
Then add funding sources with per-year percentage allocations.
10. Configure VAT Categories (If Applicable)
Screen: Admin/Vat/ProjectIrrecoverableVat.aspx
11. Configure Contract Budget Log Localisation (If Used)
Screen: Admin/Configuration_ContractBudgetLog.aspx
12. Configure Financial Data Import (If Pulling Actuals/Budgets From an External System)
Screen: Admin/configuration_financial_import.aspx
Configure Labor and Non-Labor selectors.
Set the Unique Transaction ID.
Configure the active file location.
SAP and Oracle integration toggles also exist but look customer-specific.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article