skills/101-index/resources/shared-resources/financial-risks-and-project-controls.md

# Financial Risks and Project Controls

Apply these rules after a successful technical gate for a general audit, or directly for a matching narrow request.

## Confirmation and warnings

- Calculate the primary analysis only from confirmed operations.
- Show unconfirmed operations separately as drafts, warn that they exist, and offer a separate estimate of their possible impact. Never add them to the primary figure.
- A probable duplicate is a pair of confirmed events with the same counterparty, type, and amount to the kopek within three calendar days. Compare project and positions when available. Treat it as a warning, not a proven error.
- If many events use one uninvited counterparty with a semantically generic name such as “shop” or “worker” in any language, warn that separate real counterparties are needed for end-to-end analytics and lower loss risk. Do not generalize from isolated cases.

## Service-price control in a project audit

- Service positions sourced from a price list or estimate are normal.
- Manually entered service positions are a price-control risk.
- Exclude goods from this warning; manual goods entry is normal.
- Show both the count and share of manual service positions among all reviewed service positions. State the denominator and sample boundary.
- Offer to prohibit manual positions through permissions on the relevant service expense articles. For a company owner or project manager, this is an available action only after explicit confirmation. A partner should contact the project manager.

## Permissions and mutations

An analytical result or recommendation never authorizes a data change. Before any mutation, verify permissions, show the proposed action, and wait for explicit confirmation. Never repair events, counterparties, articles, or permissions automatically.

## Compact result shape

1. Primary confirmed figures.
2. Drafts and their potential impact, separately.
3. Probable-duplicate and counterparty-quality warnings.
4. For a project, the count and share of manual services when positions are available.
5. Recommended actions with an explicit confirmation boundary.

## Common mistakes

| Mistake | Correct action |
| --- | --- |
| Adding drafts to the main total | Show a separate impact scenario |
| Deleting a probable duplicate automatically | Warn and propose verification |
| Generalizing from one generic “shop” | Require a repeated pattern |
| Treating manual goods as a service risk | Exclude goods from the metric |
| Blocking manual entry without confirmation | Verify permissions and obtain explicit confirmation first |