Prepare a bonus calculation from accounting exports
Combine project revenue and expense records into a traceable calculation workbook. Apply the approved allocation rules and separate unmatched items before the accountant reviews the bonus calculation.
How this works
Combine project revenue and expense records into a traceable calculation workbook. Apply the approved allocation rules and separate unmatched items before the accountant reviews the bonus calculation. Use this when a bonus depends on project financial results spread across several accounting files. The calculation should be reproducible and keep unmatched costs, missing allocations and rule ambiguities visible to the accountant.
Consolidate revenue and expense lines with source references, apply the approved project allocation and bonus rules using formulas, and prepare an exception queue. Keep calculated proposals separate from approved payment amounts. Missing accounting data must not silently become zero cost or extra profit.
Before you start
Approved bonus rules
Obtain eligibility, calculation base, rates, exclusions and rounding policy.
Accounting exports
Collect revenue, expenses and relevant adjustments for the project and period.
Allocation rules
Confirm how shared costs and unassigned lines are treated.
Prepare the inputs
- calculation_scope
- Required
project IDs, period, currency and eligible population
Use a consistent cutoff and accounting basis.
- financial_lines
- Required
source ID, date, account, amount and project reference
Preserve original signs and supporting documents.
- allocation_policy
- Required
cost categories and allocation formulas
Do not invent a split for unassigned spending.
- bonus_policy
- Required
versioned formula, eligibility and limits
Separate discretionary decisions from formula-driven amounts.
Implementation, step by step
Inventory and reconcile sources
- List all required exports and compare totals with the accounting system.
- Identify missing periods, duplicate documents and currency mismatches.
Checkpoint: The input coverage is explicit.
Consolidate project lines
- Normalize fields while retaining source file and row references.
- Match project IDs carefully and keep unassigned lines in a separate queue.
Checkpoint: Every included amount is traceable.
Apply allocations
- Use the approved deterministic allocation rules for shared costs.
- Show unallocated amounts and their potential effect rather than assuming zero.
Checkpoint: The project result has a transparent basis.
Calculate proposed bonuses
- Apply the approved formula and rounding rules in a workbook.
- Keep eligibility exceptions, caps and manual adjustments visible.
Checkpoint: The proposed amounts can be reproduced.
Prepare accountant review
- Provide the calculation, source reconciliations and unresolved questions.
- Record accountant corrections and approval separately from payroll execution.
Checkpoint: The packet is ready for qualified review.
Decisions along the way
Cost line lacks a project ID
Place it in the exception queue and request allocation evidence.
Bonus rule depends on cash collection
Use verified receipts rather than invoiced revenue.
Policy allows discretion
Present the formula result and leave the discretionary decision to its owner.
What you will produce
bonus-review-workbook.xlsx
SpreadsheetA formula-backed proposal for accountant review.
Include: project · revenue · cost · allocation · base · rate · proposed_bonus · status
bonus-exceptions.csv
CSVUnmatched or ambiguous items affecting the result.
Include: source_line · reason · amount · question · owner
Check the result
- Reconcile source totals and duplicate handling.
- Inspect allocation formulas and sign conventions.
- Recalculate bonus amounts independently.
- Confirm unresolved costs and eligibility are not treated as zero or approved.
When something goes wrong
Exports use incompatible periods
Align the scope or keep results separate.
Formula references omit new rows
Repair ranges and recalculate all affected totals.
Late adjustment changes the base
Version the workbook and rerun the affected calculation.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Synthetic: prepare a project bonus calculation.
Inputs
Verified collected revenue is 20,000 USD, direct costs 12,000 USD and approved shared allocation 2,000 USD. Bonus is 10% of the resulting margin. A separate 500 USD cost is unassigned.
Expected result
Synthetic result: show a provisional 600 USD bonus from the confirmed 6,000 USD margin and flag the 500 USD allocation question. Do not approve payment or silently omit its possible effect.
Run a small pilot
Start small
Use one project-period with a previously reviewed calculation.
Record the baseline
Record consolidation time and accounting corrections.
Agree success criteria
Agree reconciliation and formula accuracy before broader use.
Stop or revise
Stop payment-ready labeling while material allocations or policy terms remain unresolved.
Keep the scope clear
- The accountant verifies final amounts; preparation does not authorize payroll.
- The workflow cannot invent allocation rules or determine discretionary compensation.
Check before using
An accountant checks completeness, formulas, allocations, and the final payment amounts. Preparing the workbook does not authorize payroll.
Business activities
- Manage finances and accounting
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Project accounting exports · Approved allocation and bonus rules
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow