Workflows · Finance systems · Tier 1 · first automations
Missing-mapping report with proposed mappings for approval
A scheduled report already lists accounts in actuals that are not in planning. The agent proposes the mapping from the descriptions; a person approves before the table changes.
By hand: Monthly, one to two hours · Anyone with an ETL mapping table.
The card, as it runs by hand
- Input
- The missing-mapping report and the source member descriptions.
- What I do to it
- For each unmapped member, find the likely target from the description and the neighbours. Prepare the proposal.
- Output
- A proposal table: source member, proposed target, reason.
- Who checks
- The finance-systems analyst approves each row before the mapping table is updated.
- How often
- Monthly, or whenever the report fires.
- How long
- One to two hours by hand.
- How long now
- Measured in the course after the first governed run, per card. Not estimated here.
As a governed workflow
- Stays in code
- Detection, and applying the mapping after approval.
- The AI does
- Proposing the mapping from descriptions, with the reason.
- A person still
- Approves each row. The table never changes without it.
- The log
- Proposals, approvals, the table version before and after.
AI does the preparation. A named person approves it. Nothing posts to the books without that approval, and every run is recorded.
Where it goes wrong
Auto-applying a proposal. Never. The approval is the trigger.
Why it lands in a room
Tight, safe, universal, and the report is already the trigger.