AI_Sandbox/vk-gramatvediba
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

FG3-5 executable build — business-trip settlement process

Browse Source 
Upgrades the FG3-5 sub-process from a composition stub to a Level 4 atomic
executable: BPMN process Process_KomandejumaNorekina (trip-request processing,
cancellation branch, expense-report submission and approval, VPC processing,
reconciliation and outcome handling across the Nodarbinatais/Iestade/VPC
lanes), DMN decision Decision_KomandejumaNorekins (FIRST hit policy,
advance-vs-expense reconciliation with carry-forward to a next approved trip),
resource roles/agents/mappings and policies metadata. Transcribed from the
Valsts Kase FG3 register section 3.5.3. Validates against the UAPF 2.2.0
schemas and the uapf-cli validator.
This commit is contained in:
Rihards Gailums
2026-05-19 21:16:39 +00:00
parent e0cf11e4ae
commit 37000f77f5
9 changed files with 455 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

76
processes/fg3-5/README.md
View File

@@ -1,16 +1,76 @@
# FG3-5 — Komandējuma norēķina veikšana
Business-trip settlement: processing of travel advances and post-trip expense settlements against approved travel orders.
Level 4 atomic executable process for business-trip (travel) settlement — the
processing of trip requests, cancellations, post-trip expense reports and the
reconciliation of travel advances against documented expenses. The third FG3
sub-process taken to executable depth.
- **UAPF level:** L4 (atomic sub-process)
- **UAPF level:** L4 (atomic executable)
- **Package id:** `vk.gramatvediba.fg3-5`
- **Source:** Valsts Kase *Grāmatvedības uzskaites procesu apraksts* — FG3
schema and process register.
- **Included by:** `processes/fg3` (function group FG3).
- **Source:** Valsts Kase *Grāmatvedības uzskaites procesu apraksts* — FG3
process register, section 3.5.3 (*Komandējuma (darba brauciena) dokumenti un
to kustība*), with the advance-repayment tail in section 3.5.4.
## Process
`bpmn/komandejuma-norekina.bpmn` (`Process_KomandejumaNorekina`) transcribes
the business-trip settlement flow across three lanes mapped from the source
RACI columns:
- **Nodarbinātais** — submits the trip request (3.5.3.1) and, after the trip,
the expense report (3.5.3.3).
- **Iestāde** — approves the trip expense report in its defined flow.
- **VPC** — processes the request, annuls it if the trip is cancelled
(3.5.3.2), processes the report (3.5.3.4), reconciles it, and prepares a
repayment request, an additional payment, or posts the document.
Flow: request processing → cancellation branch → expense-report submission and
approval → VPC processing → reconciliation decision → one of three outcomes.
Two terminating states: *settlement posted* or *trip request annulled*.
## Decision
`dmn/komandejuma-norekins.dmn` (`Decision_KomandejumaNorekins`) is a `FIRST`
hit-policy decision table that sets the outcome variable `norekinResultats`
from two inputs:
| Input | Values |
|-------|--------|
| `avansaSituacija` | `nav-avansa`, `avanss-lielaks`, `avanss-vienads`, `izdevumi-lielaki` |
| `nakamaisKomandejums` | `ir`, `nav` |
Outcomes: `papildu-izmaksa` (no advance, or expenses exceed the advance —
the difference is paid to the employee), `slegts` (advance equals expenses),
`parnesums` (the advance exceeds expenses and the employee has a next approved
trip from the same funding — the balance carries forward to that trip),
`atmaksa` (the advance exceeds expenses with no next trip — the difference is
repaid). The `Task_NoteiktRezultatu` business-rule task evaluates it.
## Resources
`resources/mappings.yaml` binds every BPMN user task and the DMN decision to a
target in `resources/roles.yaml` / `resources/agents.yaml`. Human steps are
`manual`; the AI agent `agent.komandejumu-asistents` is bound `assisted` to the
request processing, the report processing and the reconciliation decision — it
extracts document data and proposes the outcome, the accountant decides. No
step is `autonomous`.
## Transcription note
The trip request itself is prepared and approved in the personnel-management
process (PP); FG3-5 begins where the request enters accounting handling, so
the start event represents that hand-off. Advance disbursement, the additional
payment and the detailed advance-repayment steps (3.5.4) are executed in their
own processes and are referenced rather than duplicated here. The carry-forward
rule (`parnesums`) transcribes the 3.5.4 condition that an advance surplus is
retained against a next approved trip from the same funding. Step identifiers
use stable BPMN/DMN element ids; reconciliation against the register `process
nr.` numbering is a tracked follow-up and any schema/register discrepancy is
recorded rather than silently resolved (see `docs/conventions.md`).
## Status
Draft composition placeholder. The sub-process is identified and wired into
FG3 via `includes`; its executable build (BPMN + DMN + resource mappings)
follows in a later step. FG3-1 is the sub-process taken to executable depth in
this proof-of-concept.
Draft. The package is structurally complete and validates against the UAPF
2.2.0 schemas; lifecycle status advances to `review` once the source-numbering
reconciliation is signed off.