EarnedValueEntry — data reference
All 20 fields BSuit stores for EarnedValueEntry (Projects), with the record types they refer to.
On this page
#About EarnedValueEntry
EarnedValueEntry is a record type in the Projects area of BSuit. This page lists everything BSuit stores for each earnedvalueentry — 20 fields. No dedicated page for it was found in the menu; records may be created by other screens, imports or automatic processes.
#Fields
Every field stored for a earnedvalueentry. “Stored as” is the technical field name, useful when talking to support or building reports.
| Field | Stored as | Type | Required | Max length | Refers to |
|---|---|---|---|---|---|
| Project Id | ProjectId | Text | No | — | — |
| Period Date | PeriodDate | Date | No | — | — |
| Budget At Completion | BudgetAtCompletion | Number (decimal) | No | — | — |
| Planned Value | PlannedValue | Number (decimal) | No | — | — |
| Earned Value | EarnedValue | Number (decimal) | No | — | — |
| Actual Cost | ActualCost | Number (decimal) | No | — | — |
| Schedule Variance | ScheduleVariance | Number (decimal) | No | — | — |
| Cost Variance | CostVariance | Number (decimal) | No | — | — |
| Schedule Performance Index | SchedulePerformanceIndex | Number (decimal) | No | — | — |
| Cost Performance Index | CostPerformanceIndex | Number (decimal) | No | — | — |
| Estimate At Completion | EstimateAtCompletion | Number (decimal) | No | — | — |
| Estimate To Complete | EstimateToComplete | Number (decimal) | No | — | — |
| Variance At Completion | VarianceAtCompletion | Number (decimal) | No | — | — |
| To Complete Performance Index | ToCompletePerformanceIndex | Number (decimal) | No | — | — |
| Notes | Notes | Text | No | — | — |
| Project | Project | Text | No | — | — |
| Id | Id | Text | No | — | — |
| Created At | CreatedAt | Date and time | No | — | — |
| Updated At | UpdatedAt | Date and time | No | — | — |
| Is Deleted | IsDeleted | Yes / No | No | — | — |
#About this guide
Generated from BSuit’s data model on the date shown under “Seen on a running system”. Field names, types and lengths come from the model itself. References are inferred from field names (a field called “Ledger Id” is treated as pointing to Ledger); the model does not declare relationships, so an inferred link can occasionally be wrong or missing.
About this guide
- Status
- Partially reviewed
- Application
- BSuit ERP
- Audience
- Administrators, analysts and support staff
- Owner
- BSuit documentation team
- Reviewer
- Not yet reviewed
- Last verified
- Never
- Checked against
- Generated from source revision a36c7a086 on 2026-10-02
- Seen on a running system
- Not yet
- Help version
- 2026.0.0-preview
- Guide ID
erp:data/project.earnedvalueentry