budget-consolidation

Budget Submission Chase and Consolidation

Drives a planning cycle end to end: who owes what, who is late, what the numbers say when combined, and what leadership needs to decide.

When NOT to Use

• Building one cost center's budget model — use xlsx instead.
• Prepping for a review meeting — use forecast-review-prep instead.
• Month-end close status — use close-status-digest instead.
• Explaining actuals against plan — use variance-commentary instead.

Related Skills

Hand off rather than overlap:

• Recurring deliverables calendar and invites — use quarterly-workback instead.
• General data joining and profiling — use dataset-analysis-report instead.
• A written summary for leadership — use exec-update instead.
• A slide prep pack for a meeting — use pptx instead.
• Valuation or returns modeling — use dcf-valuation or lbo-model instead.
• Client portfolio reviews, peer trading multiples, or deal document extraction — outside this skill's scope.
• Variance narrative on a closed period — use variance-commentary instead.
• Quarterly results of a public company or an investment committee recommendation — outside this skill's scope.

Workflow

1. Establish the submission list

Determine what a complete cycle looks like: which cost centers, departments, or entities owe a submission, the template they use, and the deadline. Take it from a tracker the user supplies, the prior cycle's list, or ask once with core-AskUserQuestion.

Never invent the list of owners. Resolve every name with me_profile-SearchPeople; an unresolved owner is recorded as unassigned, not guessed.

2. Determine what has arrived

Search in parallel: m365_search-SearchM365 with sources=["email","files"] for submissions, sharepoint_onedrive-GetDriveChildren on the collection folder, and outlook-ListMessages filtered to each owner.

Classify every line as Received, Received but incomplete, Not received, or Not required. Match on content, not filename — an empty template is not a submission.