Connect AI and cloud spend to the engineering work it paid for

A model-provider invoice can establish that a company incurred a charge. By itself, it rarely explains which experiment used the service, what the team learned or whether the expenditure belongs in a particular R&D tax calculation.

The missing connection is often mundane: a project reference that never reached the usage export, an experiment that used a shared account, or a credit applied in the following month. Solving these problems creates a useful management record even before anyone considers a tax claim.

The method below is an operating recommendation based on provider documentation and FinOps sources checked on October 7, 2026. It is not an accounting policy or a jurisdiction-specific eligibility test.

Keep three questions separate

Reconciliation asks whether the records explain the bill. Attribution asks which work consumed the resource. Treatment asks how the supported amount should be classified for management, financial reporting or tax.

A neat project tag helps with attribution. It cannot settle the other two questions. Likewise, a technically successful experiment does not establish how its costs were recognized in the accounts.

Choose the cost basis explicitly. FOCUS 1.2 distinguishes billed cost, which supports invoice alignment, from effective cost, which incorporates applicable amortized prepaid amounts and discounts. Those measures serve different analyses; they are not interchangeable columns to sum together. FOCUS billed cost and effective cost.

For an initial evidence review, start with the actual invoice and its supporting export. Add a management allocation view separately, with a clear explanation of any adjustment.

Create a small, durable chain of references

You do not need a new time-tracking program to start. Agree on a project reference and, for experimental work, an experiment reference. Carry those identifiers through the records you already produce.

Keep source identifiers intact when normalizing spreadsheets. A friendly project name can change; a provider invoice ID should continue pointing to the original document. Preserve the original currency and record any conversion separately, with rate, date and purpose.

Understand what provider metadata actually covers

Google Cloud’s billing export includes usage, cost, credits, projects and labels. Its documentation warns that invoice month can differ from usage month, and that label-specific cost data begins when the label was applied. A label added today does not create evidence of yesterday’s allocation. Google Cloud export schema.

AWS similarly distinguishes resource tags from activated cost-allocation tags. The latter must be activated for their use in cost reporting. A tagging policy in an infrastructure repository is therefore not evidence that the expected tag appeared on a historical billing record. AWS cost-allocation documentation.

Check a real export early. Inspect a few known resources and periods, then compare them with the bill. Record missing metadata as missing. Do not silently fill historical gaps using the resource’s current owner.

A worked example with an honest unallocated balance

Illustrative example. A company receives a $10,000 AI-services invoice after a $1,000 credit against $11,000 of charges. All amounts are in USD. Its supporting export and credit note identify:

The credit belongs to the retrieval experiment because the credit note identifies those charges. Allocating it evenly would change the project economics without support.

For the shared account, retained run records support $800 of usage for the retrieval project and $400 for another investigation. The remaining $800 lacks a reliable work reference. The resulting view is $4,800 for retrieval, $400 for the second investigation, $4,000 for production and $800 unallocated.

All four amounts still total $10,000. The unallocated balance is a work item, not an embarrassment to hide. A reviewer can now request the missing run log, determine whether another reasonable allocation basis exists, or leave the amount outside a project-specific analysis.

This example assumes the exported charges and credit fully reconcile to the invoice, without separate taxes, marketplace items or currency conversion. A real reconciliation must explain those items when present. None of the project assignments decides whether an amount qualifies for an incentive.

Choose allocation rules that fit resource consumption

Direct identifiers are strongest when they describe what actually consumed the service. For shared infrastructure, document the rationale for a proxy: GPU duration, measured resource consumption or another observable driver. Equal splits or headcount may be useful management conventions in some settings, but they are assumptions and should be labeled as such.

Token counts alone can mislead when model, input/output mix, cache treatment or contractual terms differ. Prefer provider-reported charges where available, and retain the rate logic when calculating an estimate. Reconcile estimates later; never relabel them as invoiced actuals merely because they have two decimal places.

Version the allocation rule. If a resource changes teams on the fifteenth, record that effective date. If a reviewer changes the basis, retain both the earlier calculation and the reason for the correction.

Connect cost to a result someone cares about

Once attribution is credible, choose a useful denominator. Cost per attempted evaluation answers a different question from cost per accepted outcome. FinOps guidance encourages connecting technology costs to business value and expanding AI measures beyond tokens. FinOps unit economics.

For the retrieval example, a practical review might compare total evaluation cost with the number of cases meeting a predefined answer-quality threshold, while also reporting failures and human review effort. If acceptance standards change, mark the break in the series. A cheaper run is not necessarily a better investment if it produces unusable results.

Proforma can start with supplied invoices, cloud exports and project records. Initial preparation may be manual; uploading an invoice does not automatically allocate it or reconcile it. The broader Workspace can support investigation of available files and data with a configured agent. Start by assembling one project’s evidence chain, then expand the method where it proves useful. See supported inputs.

Sources and scope

• FOCUS 1.2: billed cost
• FOCUS 1.2: effective cost analysis
• Google Cloud: standard billing export schema
• AWS: cost-allocation tags
• FinOps Foundation: unit economics

The example uses invented records and amounts. Tax and accounting treatment require a separate assessment of the applicable rules and company facts.