Invoices and manual uploads

Uploading a bill for a vendor you already connect books those dollars twice. Anthropic, OpenAI, OpenRouter, Azure, Bedrock, Vertex, Gemini, and a gateway each arrive on their own connection. A second file for the same spend is a second copy. Reconciliation does not merge a hand-uploaded invoice with a connector row. Use one source of record.

Upload steps and the file types are in the manual import guide. This page is attribution. The upload form is Uploads.

What you set up

1. Open Uploads and choose the vendor by the name on the invoice. The listed names are OpenAI, Anthropic, OpenRouter, Azure, AWS, Google Cloud, Together AI, Groq, Perplexity, Mistral AI, Cohere, AI21, Replicate, and Hugging Face.
2. If the invoice is not one of those, choose Other vendor.
3. You can also type a bill in without a file. Same attribution afterward.
4. Create any rule or agent you will assign to, under Agents & allocation, before you expect the rows to leave the inbox.

What Meridian receives

One charge per parsed invoice line, or per line you typed. The grain is the line on the file. It is not a per-request log unless the file itself is that detailed. Token columns are kept when the file has them. A PDF that only states a monthly total becomes a coarse line.

The vendor on the row is the vendor you selected at upload, not a guess from the letterhead.

How it's attributed

Rows arrive unattributed. A rule can match the vendor or the model, ignoring letter case on both. A person can assign selected rows. Rules are tried from the lowest Priority number. The first one that matches wins. A rule does not replace a row a person has assigned, and it does not replace a mapped, inherited, or declared row.

Nothing on a generic invoice declares an agent. If the file has no column Meridian recognizes as a project or a department, the line stays one total.

What lands unattributed, and how to fix it

Every accepted line lands unattributed until a rule or a person assigns it. The Reason column is empty. The vendor and the model are what you have to match on.

Assign the lines, or add a rule and choose Apply rules now. Unlocked dates update. A locked month shows the change as an adjustment on a later draft. Unassigned dollars still post, on unallocated (suspense), so the month balances.

A file that mixes three agents on one line cannot be split after upload. Split them in the file, one line per agent, only if you also have a rule or a field that distinguishes the lines. A single monthly total has nothing to distinguish. Use a workspace, a project, a gateway, or OASA events when you need that split. The invoice remains the tie-out.

Limits

• Other vendor is a real bucket. It is not a named connector, and a rule has to match the vendor value stored for it.
• Together AI, Groq, Perplexity, Mistral AI, Cohere, AI21, Replicate, and Hugging Face are upload vendors. They are not scheduled API pulls.
• A branded invoice Meridian cannot parse still fails the upload. Fix the file or enter the bill by hand. Failed lines are not silently dropped into a department.
• Uploading the same spend that a connector already pulls double-counts it. Reconciliation does not merge a hand-uploaded invoice with a connector row by guessing they are the same bill.