PlaysbyMoat8
Back to the library
The workflow guideFinance

Prepare a project expense classification for accounting review

Compare project spending with the approved capitalization policy. Give the accountant evidence for the proposed treatment.

5 implementation stepsIntermediate

How this works

Compare project spending with the approved capitalization policy. Give the accountant evidence for the proposed treatment. Use this to organize an accountant's review of mixed project spending. The assistant should assemble factual evidence and policy passages, then present a proposed classification with unresolved conditions.

Treat the current accounting policy as a versioned input rather than a universal rule. Keep individual expense lines separate because implementation, maintenance and training may have different treatment. A qualified accountant decides the final classification and any journal entry.

Before you start

Applicable policy

Obtain the approved policy, entity, effective date and relevant accounting framework from finance.

Project evidence

Collect the business purpose, project milestones, asset description and invoices supporting each cost.

Review authority

Identify the accountant responsible for classification and the period affected.

Prepare the inputs

project_record
Required

ID, purpose, milestone dates and asset description

Flag unknown readiness dates instead of estimating them.

expense_lines
Required

date, amount, currency, description and document ID

Reconcile every line to an invoice or accounting export.

accounting_policy
Required

versioned approved document

Confirm it applies to the entity and expense period.

supporting_documents
Required

contracts, specifications and acceptance records

Preserve provenance and distinguish draft from signed evidence.

Implementation, step by step

  1. Build the cost inventory

    • List all proposed project costs and their supporting document references.
    • Separate bundled charges when itemized evidence exists; leave unallocated bundles visible.

    Checkpoint: The cost inventory reconciles to the submitted total.

  2. Retrieve relevant policy

    • Locate policy rules about recognition, eligible expenditure, exclusions and readiness for use.
    • Record exact section references and applicability questions without supplying an unsupported legal interpretation.

    Checkpoint: A policy-evidence map covers each cost type.

  3. Prepare line-level reasoning

    • Compare documented facts with each rule and draft a proposed treatment.
    • Explain missing conditions such as asset control, useful life or completion status; avoid filling gaps from project enthusiasm.

    Checkpoint: Each line has a rationale and unresolved questions.

  4. Assemble the accounting packet

    • Calculate proposed category totals with formulas and retain uncertain amounts separately.
    • Show alternative totals if an unresolved classification changes the result.

    Checkpoint: The reviewer sees both classification reasoning and numerical consequences.

  5. Record the decision

    • Capture the accountant's treatment, corrections and policy interpretation for each line.
    • Prepare an export only after the decision; keep posting authority and journal execution distinct.

    Checkpoint: The packet records decided and undecided costs separately.

Decisions along the way

Invoice combines training and implementation

Request an itemized split; do not allocate by an invented percentage.

Policy version changed

Ask finance which effective version applies to the transaction period.

Project not ready for use

Surface the milestone evidence gap for the accountant rather than setting an amortization date.

What you will produce

capitalization-review.xlsx

Spreadsheet

A formula-backed review workbook with traceable classification evidence.

Include: expense_id · amount · policy_section · proposed_treatment · uncertainty · decision

accounting-questions.md

Markdown

A focused request list to resolve accounting judgments.

Include: expense_id · missing_fact · requested_evidence · owner

Check the result

  • Reconcile line totals with source invoices and the project expense export.
  • Verify every policy citation against the applicable document version.
  • Confirm uncertain amounts are excluded from decided totals or shown separately.
  • Check that reviewer decisions cannot be confused with the assistant's proposals.

When something goes wrong

No approved policy available

Produce an evidence inventory and questions only; defer classification.

Conflicting asset descriptions

Retain both sources and request project-owner clarification.

Foreign currency basis missing

Keep original currency amounts separate until finance supplies the conversion basis.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Synthetic: prepare a review of project P9 expenses.

Inputs

P9 has implementation 8,000 and staff training 2,000 USD. Policy section 4 explicitly excludes training; implementation eligibility depends on an unsigned acceptance record.

Expected result

Synthetic result: identify 2,000 USD training as proposed expense with section 4 evidence; keep 8,000 USD implementation undecided pending acceptance and accountant review. Do not call the full 10,000 USD capital expenditure.

Run a small pilot

Start small

Review a small set of completed projects with previously decided accounting treatment.

Record the baseline

Record preparation time and facts the accountant had to retrieve manually.

Agree success criteria

Agree acceptable evidence completeness and correction levels; compare against prior decisions.

Stop or revise

Stop classification drafts when policy applicability cannot be established.

Keep the scope clear

  • The workflow prepares accounting evidence and does not provide a final accounting determination.
  • Do not post journals, establish useful lives or authorize spending from a generated proposal.

Check before using

An accountant verifies facts, policy applicability and the final treatment.

Business activities

  • Manage finances and accounting

Editorially adapted workflow; not independently tested.

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 documents · Current accounting policy

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗