Skip to content

Financial Statements

Backlog fieldValue
Story IDAP-ACC-005
EpicAccounting
Story typeReport
Review statusDraft - business analyst and business owner review required
Source evidenceAppsPortal.Apis controller, application command/query handlers, validators, domain entities, and matching MFE workflow where available
Last source review2026-07-10

User story

As finance managers, I want to produce income statement and financial-position reports so that management can assess performance and position.

Acceptance criteria

  1. Only authorized users can view or execute the feature's actions.
  2. Required business data, active dependencies, tenant/branch scope, and current document state are validated.
  3. Invalid requests return actionable validation errors without applying a partial change.
  4. Search, list, view, print, and export operations use the same authorized business scope.
  5. Material create, edit, status, approval, posting, reversal, and integration actions are auditable where applicable.
  6. Financial or stock effects are applied atomically and no more than once.

Business rules

Required

Statement date/period and configured account hierarchy/classification are required.

Optional or conditional

Comparative periods, cost centers, levels, branches, and zero rows are optional filters.

Action behavior

Reports aggregate posted journals only and create no status, balance, or GL change.

Blocking rule or downstream effect

Income statement and financial position totals must trace to trial balance under identical filters.

Frontend page coverage

The following UI coverage is sourced from the pulled MFE route configuration. A Module-level supporting artifact mapping is evidence of a reachable screen, but requires BA confirmation that it belongs to this story rather than a more specific feature story.

Route/pageComponentModeRoute permission/guardMapping confidenceSource
statement-of-financial-positionStatementFinancialPositionComponentList/navigationNo route-level permission/guard found in source windowFeature token matchapps/accounting/src/app/remote-entry/report/report-routing.module.ts:10

Observed frontend fields and validation

ComponentControlObserved frontend ruleComponent source
HeaderReportStatementComponentBranchesVisible control; optional or API-dependentapps/accounting/src/app/remote-entry/report/component/header-report-statement/header-report-statement.component.ts
HeaderReportStatementComponentrangeRequired in component validatorapps/accounting/src/app/remote-entry/report/component/header-report-statement/header-report-statement.component.ts
HeaderReportStatementComponentviewZeroBalanceVisible control; optional or API-dependentapps/accounting/src/app/remote-entry/report/component/header-report-statement/header-report-statement.component.ts

Observed frontend actions

ComponentClick action/handlerBusiness review requirementComponent source
HeaderReportStatementComponentprintTableGenerate the printout for the selected record and authorized branch/tenant; use posted/current values and surface print, template, ZATCA/ETA, or popup failures without changing transaction state.apps/accounting/src/app/remote-entry/report/component/header-report-statement/header-report-statement.component.ts

Page-specific frontend acceptance criteria

  1. statement-of-financial-position - List/navigation: Load an authorized paged/searchable list or navigation page; preserve filters/sort/paging and expose only permitted row and bulk actions. Security observed: No route-level permission/guard found in source window

Internal Documentation — Microtec