> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jadenet.id/llms.txt
> Use this file to discover all available pages before exploring further.

# Executive Report

> Use dashboards, monitoring, profit/loss, volume, and report views using the standard business-page format.

## Purpose

Use Executive Report to monitor operational and financial performance, identify exceptions, analyze job profitability and volume, and navigate from management indicators to source records.

## Preconditions

* The user has authorized dashboard/report access and the correct office/company scope.
* Reporting periods and filters are understood.
* Source operational and financial transactions are saved, approved, and posted as required.
* The user understands whether each report uses transaction date, posting date, job date, or another date basis.
* Material decisions will be reconciled to source records and formal reports.

## Workflow

1. Select dashboard/report and reporting scope.
2. Review exception indicators first.
3. Drill down or navigate to source records.
4. Assign and complete corrective actions.
5. Refresh and confirm the exception clears.
6. Retain or communicate the reviewed management result.

The process map shows the read-only report review cycle. Reports do not use the transaction-approval engine.

```mermaid placement="top-right" theme={null}
%%{init: {'flowchart': {'defaultRenderer': 'elk'}}}%%
flowchart LR
    A([Select report scope]) --> B[Refresh dashboard]
    B --> C[Review exception indicators]
    C --> D{Exception found?}
    D -- No --> H[Confirm management result]
    D -- Yes --> E[Drill down to source]
    E --> F[Assign corrective action]
    F --> G[Complete action and refresh]
    G --> C
    H --> I[Export if authorized]
    I --> J([Retain or communicate result])

    classDef start fill:#714B67,stroke:#56364E,color:#FFFFFF;
    classDef work fill:#EFE6ED,stroke:#714B67,color:#2F2933;
    classDef approval fill:#F8E6A0,stroke:#B8860B,color:#3B2E00;
    classDef done fill:#D9EED8,stroke:#4F8A4C,color:#183817;
    classDef exception fill:#F5D8DC,stroke:#B54A59,color:#4A1720;
    class A start;
    class B,C,E,G,H,I work;
    class D approval;
    class F exception;
    class J done;
```

## Step-by-step

<Steps>
  <Step title="Open the required view">Choose Dashboard, Monitoring, Profit/Loss, List of Reports, or Volume Statistics.</Step>
  <Step title="Set scope">Confirm company/office, period/date, service, customer, salesperson, currency, status, and other parameters.</Step>
  <Step title="Review exceptions">Prioritize empty/unbalanced journals, estimates without actual cost, actual cost without estimate, reimbursement issues, unbilled jobs, and unusual profit/loss.</Step>
  <Step title="Inspect the source">Open or search the related job, journal, bill, invoice, voucher, payment, or receipt.</Step>
  <Step title="Correct through the source workflow">Assign the responsible role and use the approved correction/approval/posting process.</Step>
  <Step title="Re-run the view">Refresh with the same parameters and confirm the result changed as expected.</Step>
  <Step title="Communicate and retain">Export or distribute only authorized report data and record management follow-up where required.</Step>
</Steps>

## Screenshots

<Note>No sanitized current-version Executive Report screenshots are stored in the repository yet.</Note>

Recommended captures: dashboard selector; filter/parameter area; monitoring exceptions; Profit/Loss detail; Volume Statistics; source drill-down.

## Result

Management receives a scoped, traceable view of performance and exceptions, with material issues linked to source records and assigned corrective action.

## Approval

Viewing generally requires access approval rather than transaction approval. Report publication, distribution, or management sign-off follows organizational policy. Corrective source transactions still require their normal approvals.

## Accounting Impact

Dashboards and reports are **read-only** and create no accounting entry. They reflect source data according to posting status, date logic, permissions, exchange-rate treatment, and filters. Corrections made in source financial workflows can change reported balances and profitability.

## Common Errors

| Error                               | Resolution                                                                    |
| ----------------------------------- | ----------------------------------------------------------------------------- |
| Dashboard total differs from report | Match filters, date basis, status, currency, office, and posting cut-off      |
| Report is empty                     | Verify parameters, permissions, and posted source data                        |
| Exception remains after correction  | Refresh, confirm posting, and check whether another source record drives it   |
| Profitability looks incomplete      | Review missing actual cost, estimate, billing, accrual, and closed-job status |
| Export exposes excess data          | Reduce scope/columns and follow data-distribution policy                      |

## Related Functions

* [Sea Freight](/modules/seafreight)
* [Air Freight](/modules/air-freight)
* [Land Freight](/modules/land-freight)
* [Cashier Management](/modules/cash-and-bank)
* [Accounting and Finance](/modules/accounting)
* [Job closing](/workflow/job-closing)