Sales by Manager
Payments → table of each manager's contribution
In short
If a manager is not recorded at the time of payment, the sales report turns into a manual investigation, and disputed or unattributed rows disappear from view.
Outcome
A read-only report calculates sales by transparent rules, separately shows returns, disputed and unattributed payments, and restricts visibility by the requester's role.
How the automation runs
Trigger
Authorized employee requests a report for a specified period
Automation steps
- Takes requester's identifier from trusted context, not from command text
- Applies role-based visibility and fixed period boundaries
- Links payments to managers by versioned attribution rules
- Separately accounts for returns, cancellations, disputed, and unattributed rows
- Returns aggregates and control sums without changing the payment database
Human check
The supervisor reviews disputed rows and approves rule changes; the report does not automatically make personnel or compensation decisions.
Outcome
A read-only report calculates sales by transparent rules, separately shows returns, disputed and unattributed payments, and restricts visibility by the requester's role.
Automation diagram
The overall logic is publicUsing it
When to use it
The payment circuit reliably links to the sales initiator, and the team needs a regular report with access differentiation.
How to verify
Totals match the payment register for the same timezone, returns are excluded by rule, the manager sees only the authorized slice, and an unattributed row is explainable.
Tools
Recipe details
Open every recipe through @venturehunter
We ask for no phone number, no password and no Telegram login on the site. @penioza_bot checks your subscription inside Telegram and brings you back here with access to every kit, not just this one recipe.
Need help putting this in place?
We will walk through your process and build this loop around your data, your limits and your people.
Message me — I will help
