The control station, in brief
This station links several tools into one journey. The agent follows the steps in order, and every step goes through the rules below.
It can
- Reconcile bank and accounting
- Chase an invoice up to 2 times
It asks a human for
- Lock the period
It never has access to
- Lock with open gaps
Scenario Replays
An agent works through the station. Simulated scenarios, no real data, no key required.
Copy the station, change a limit or an approval step in its configuration file, and get your own station.
The configuration in detail
Everything the station does fits in this file. The replay above applies it, and a copy starts from it. The values are examples to adapt, not a recommendation.
station:
id: month-end-close
kind: process
policies:
- {policy: max-chases, at: submit}
- {policy: no-open-gap, at: submit}
- {policy: human-for-lock, at: submit}
global:
language: en
timezone: Europe/Paris
apis:
- id: bank-accounting
operations:
reconcile: {access: write, risk: medium}
- id: mail
operations:
chaseInvoice: {access: write, risk: low}
- id: accounting-lock
operations:
lockPeriod: {access: write, risk: high}
profiles:
finance-assistant:
allow: [reconcile, chaseInvoice, lockPeriod]
policies:
max-chases:
type: rule
budget: {action: chaseInvoice, max: 2, per: invoice}
effect: deny
reason: "An invoice is chased at most twice by the agent."
no-open-gap:
type: rule
when: "action == lockPeriod and open_gaps > 0"
effect: deny
reason: "A period is not locked with open gaps."
human-for-lock:
type: rule
when: "action == lockPeriod"
effect: needs-human
reason: "Locking needs the accounting lead's approval."
skills:
- {id: reconcile, uses: reconcile}
- {id: chase-invoice, uses: chaseInvoice}
- {id: lock-period, uses: lockPeriod}
playbooks:
- id: close-the-month
tasks: [reconcile, chase-invoice, lock-period]Shared copies
Copies that their authors choose to share will appear here. Each one keeps a link to this original station.