How this works

A management P&L explains revenue, costs and profit for a defined entity and period. Build it from approved accounting records and an explicit account mapping, keeping the arithmetic reproducible. AI is useful for proposing classifications and drafting questions about variances; calculations, reconciliations and accounting judgments need separate checks.

Agree the reporting basis before processing transactions. A bank feed alone does not establish accrual revenue or expenses, and a budget is not an actual result. This workflow produces an internal management draft, not a statutory-compliance claim. Preserve missing records and uncertain classifications as exceptions rather than turning them into zero or silently adjusting totals to balance.

Before you start

Prepare the inputs

report_scope

Required

Entity ID, start/end dates, reporting currency, accounting basis, actual/budget/forecast

Dates are inclusive and periods do not overlap; entity and basis match the source export.

ledger_lines

Required

Unique line ID, posting date, account code, signed amount, currency, source reference

Amounts parse without locale ambiguity; duplicated line IDs and missing currency are exceptions; retain original debit/credit fields if supplied.

account_mapping

Required

Account code, approved P&L line or balance-sheet exclusion, treatment, version

One effective mapping per account and period; unresolved accounts remain unmapped.

adjustments

Optional / conditional

Adjustment ID, journal references, reason, period, approval status

Include only approved adjustments once. Keep proposed entries outside reported actual totals.

fx_policy

Optional / conditional

Approved rate source, dates, rate direction and translation rules

Required if multiple currencies occur. Do not aggregate unlike currencies or invent an exchange rate.

allocations

Optional / conditional

Cost pool, allocation driver, destination and approved percentages or units

Allocations reconcile to the original pool; avoid counting both original and allocated cost in consolidated totals.

comparison_period

Optional / conditional

Prior period or budget with matching scope and mapping

Identify restatements and incomparable definitions before calculating variances.

Implementation, step by step

1. 01

   Set the report basis

   • Write a cover note with the entity, reporting dates, currency, actual/budget/forecast label and accounting basis. Confirm whether a management-only grouping or an existing approved format is required.
   • Identify missing sources such as accruals, depreciation or approved period-end entries. Do not present an incomplete cash export as a complete accrual P&L.

   Checkpoint: The finance owner can see exactly which population and accounting basis the draft will represent.

2. 02

   Validate and normalize the ledger

   • Preserve the original export, its row count and control totals. Normalize dates and amounts into a staging table while retaining source line IDs, account codes and original values.
   • Test the debit/credit sign convention against known sample entries. Detect duplicate lines, reversed transactions, out-of-period entries and unparseable amounts; do not remove rows solely because amounts repeat.

   Checkpoint: Normalized totals reconcile to the source under the documented sign convention, with exceptions separately counted.

3. 03

   Apply the account mapping

   • Join ledger accounts to the approved mapping. Keep revenue, direct costs, operating expenses and other agreed lines distinct, and exclude balance-sheet movements using the mapping rather than descriptions alone.
   • Use the model to suggest treatments only for review. Retain the supporting account description and policy reference. Recognize that loan principal, capital purchases and recoverable taxes may require different treatment from operating expenses; ask the finance owner when unclear.

   Checkpoint: Every included amount has an approved classification or an explicit unresolved status; no unexplained catch-all silently absorbs missing mappings.

4. 04

   Calculate and reconcile results

   • Calculate line totals using deterministic formulas. Under an approved functional management layout, gross profit equals revenue minus direct costs, and operating profit equals gross profit minus operating expenses; define sign conventions once and avoid subtracting negative expenses twice.
   • Apply approved currency translation and allocations once. Compute other income, finance costs and tax only when supplied and mapped, then reconcile the resulting profit with the accounting control total or provide a documented reconciliation bridge.

   Checkpoint: Formula outputs can be reproduced from the mapped ledger; differences are zero or explicitly explained and reviewed, not forced away.

5. 05

   Explain movements and uncertainty

   • Compare with a compatible prior period or budget. Calculate absolute changes and percentages only when their denominators are meaningful; use not-applicable for a zero comparison base.
   • Draft explanations supported by transaction detail or owner notes. Separate observed drivers from hypotheses, and show the value and affected lines of unresolved entries without claiming the draft is complete.

   Checkpoint: Each material narrative claim has supporting records; unanswered classification and completeness questions remain visible.

6. 06

   Prepare the finance handoff

   • Deliver the P&L alongside its mapping, calculation logic, reconciliation and exception register. Preserve formulas or the runnable calculation source and include the report version.
   • Obtain finance review of classifications, allocations and completeness before treating the draft as approved. Reopen the exported workbook or CSV to check totals and formatting; do not post adjustments, file returns or circulate confidential figures without authorization.

   Checkpoint: The report is labeled draft or approved, includes reproducible totals and identifies its reviewer and outstanding limitations.

Decisions along the way

What you will produce

Check the result

• Recalculate report subtotals independently from the mapped source lines, using the same currency and precision.
• Account for all source rows as included, excluded under policy or unresolved; reconcile each group's value to the original export.
• Check duplicate line IDs, period boundaries, reversals and approved adjustments for double counting.
• Confirm that currency translation, allocations and subtotal formulas conserve the relevant totals.
• Verify that missing data, unknown tax and absent comparison periods are not displayed as zero.
• Trace every variance explanation to records or owner evidence and inspect the reopened export for broken formulas or hidden exceptions.

When something goes wrong

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Run a small pilot

Keep the scope clear

• This skill prepares internal reporting. It does not set accounting policy, certify compliance, file taxes, post journal entries or authorize payments.
• Keep payroll, client and transaction details in approved locations; use aggregated figures in the management view where sufficient.
• Do not present synthetic calculations as business results or infer profitability from incomplete cash data.