FOCUS and cloud billing uploads

The product overview of FOCUS in Meridian is at FOCUS. You upload the file on Uploads. This page is attribution only. There is no separate setup guide yet for creating the export in AWS, Azure, or Google Cloud.

What you set up

1. Produce a FOCUS Cost and Usage file from the cloud billing tool. Meridian reads FOCUS 1.2 and 1.3, and is forward-tolerant of 1.4 columns.
2. For Amazon Bedrock, tag application inference profiles and activate the tag keys before the usage you care about. The daily Cost Explorer connector is a different path. See AWS Bedrock.
3. Use tag keys Meridian reads. The defaults are CostCenter, Department, or cost-center for the department, Agent for the agent, Project for the project, and Customer for the customer. The OASA keys are different. Tagging explains the gap and how a saved mapping changes the list.
4. Create departments whose code or name matches the cost-center value, and agents whose name matches the Agent value. Meridian does not create agents from the tag.
5. On Uploads, choose the file. The account-to-department crosswalk is optional. It maps an account id to a department when the row has no matching tag.

While the Bedrock Cost Explorer connector is connected, Bedrock lines in the file are held. The upload asks you to resolve that reconciliation item before choosing a source of record.

What Meridian receives

One spend row per accepted line in the file. The grain is whatever the export used: often a resource for a day, sometimes an invoice line. The billed amount on the FOCUS row is the charge. Token-level request logs are not in this file.

Tags AWS, Azure, or Google copied onto the billing row are the identity. A tag that never made it into the export is not visible here. (AWS FOCUS 1.2)

How it's attributed

A cost-center tag that matches a department code or name sets the department. The row is inherited from the tag. An Agent tag sets the agent only when that name already exists. A department match stands even when the agent name does not match. Project and customer tags are stored with the row. They do not, by themselves, set the department.

If no tag matches, the account crosswalk can still set the department. A rule does not replace an inherited department. A person's assignment does not replace it either.

A correction row for a date in an earlier period keeps that period. When the month is locked, it becomes an adjustment line on a later draft. The inbox shows a prior-period correction only when that correction is also unattributed.

What lands unattributed, and how to fix it

Untagged or unmatched rows stay unattributed and show a reason:

• "Invoked by model ID, no inference profile." For Bedrock, call through an application inference profile.
• "No cost allocation tags." Activate the keys and upload a file that contains them. Activation can take up to a day to appear and up to a day to take effect. (Activating tags)
• "Agent or other tags present, but no cost center tag." Add a cost-center key Meridian reads.
• "Cost center value not mapped." Add the department, or ask Onaro to pin the value. There is no screen for the pin.

An Agent tag does not create the agent. Create the agent with that exact name, then upload new rows. Rows already inherited keep the department they had. They are not rewritten.

Held Bedrock lines are not in the inbox and not in the ledger until you choose a source of record. If Cost Explorer is the source of record, those dollars stay the daily total, which is unattributed. See the Bedrock page.

Limits

• The inference profile ARN is not the agent. The tag value is.
• Cost from before the tag existed on the resource is empty. Backfill does not create tags the resource never had.
• This upload does not pull a cloud bill on a schedule. You bring the file.
• Azure tags and Google labels reach this path only when your FOCUS file actually contains them. The Azure OpenAI and Vertex connectors do not copy their tags into this upload for you.
• Early access. The badge is in the status section below.