ARMADA application
Contract-based previewReports
Reports emphasise source and business context instead of isolated numbers, with period, company, and branch filters over approved data sources.
Contract-defined reporting scope
Contract-based preview — not connected to live data
Reports
Outcomes
What changes in your operation?
Explicit company and branch context
A path from summary to source document
Operating journey
From start to outcome
- 1
Choose context
Select the period, company, and branch.
- 2
Read the measure
See a summary with a clear metric definition.
- 3
Trace the source
Move to the documents behind the result.
Application scope
Core capabilities
A practical scope that explains what this application covers and where its current boundary sits.
Contextual filtering
Read a period, company, and branch within the user's available scope.
- Known period
- Explicit organisational context
Defined measure
Present a number with the meaning of what it measures, not as an unexplained value.
- Metric definition
- Visible operating source
Summary to source
Move from an aggregate view to the documents that contributed to the result.
- Traceability path
- Easier discrepancy review
Control and governance
How does the work stay controlled?
Operating controls that preserve context, permission, and a reviewable trail.
No number without a source
A view is built from approved operating or financial facts, not a separate manual value.
Permissioned scope
A user cannot read a company or branch outside the approved role scope.
Explicit period and time
Timestamps are stored in UTC and presented to the user in Baghdad context.
One shared core
How does it connect to other applications?
Intended connections to the shared ARMADA core. Only the integrations covered by the approved scope are enabled.
ReportsContract-defined reporting scope
Sales
Approved orders and documents can source sales views when enabled.
Inventory
Receipt, transfer, and delivery movements can source location-aware operations views.
Accounting
Financial views come from posted, balanced entries under the ledger contract.
Implementation approach
From operating study to acceptance
A practical sequence that starts with the real operation and ends with clear acceptance of the agreed scope.
- 1
Define the business decision
Agree on the question the report must answer and who will use it.
A measure tied to a real decision - 2
Review source and definition
Fix each field source, calculation, period, and material exclusion.
An auditable definition - 3
Reconcile a real sample
Compare report output with known source documents before acceptance.
Confidence grounded in reconciliation
Designed for
Fits different teams and operating models
ManagementFinanceBranch managersOperations
Before you decide
Common questions about this application
Can I see where a number came from?
The intended experience retains a path from summary to operating or financial source for the implemented report.
Can branches be compared?
Views can be designed by company and branch within permissions after source data and comparison definitions are approved.
Are the examples on this page connected to live data?
The page explains the contracted scope. Live binding is established only after source connection and reconciliation testing.