AWS Global Site Invoicing for AWS Agency Payments

So You’re Invoicing AWS… But Not Like a Normal Vendor

Let’s get one thing straight: invoicing for AWS Agency Payments isn’t like sending an invoice to your local coffee roaster. There’s no ‘please pay within 30 days’ footnote that actually matters. No ‘PO required’ checkbox you can casually ignore. And definitely no ‘oops, I forgot to add VAT’ do-over. This is AWS — where the billing engine runs on quantum-level precision, caffeine, and a healthy dose of passive-aggressive email auto-replies.

First: What Even Is AWS Agency Payments?

Short version: It’s how AWS lets agencies (think digital shops, SaaS resellers, managed service providers) bill their clients *through* AWS — while still getting paid *by* AWS. You don’t just slap a Stripe link on your proposal and call it a day. Instead, you become an authorized billing agent. Your client’s AWS usage appears under *your* consolidated bill (with your own AWS account ID as the payer), and AWS cuts *you* a check — after deducting their 15% agency fee (yes, it’s baked in, yes, it’s non-negotiable, and yes, we’ll talk about how to price around it).

Crucially: You’re not reselling AWS like a telco. You’re acting as a billing conduit — with strict compliance guardrails. That means every line item on your invoice must map cleanly to what AWS reports in your Agency Billing Report, not your gut feeling or last month’s Slack thread titled ‘Billing WTF?’

The Invoice Isn’t Your Opinion — It’s a Forensic Document

Your invoice isn’t creative writing. It’s evidence. AWS doesn’t care if your logo looks great in Pantone 294C. They care if your invoice number matches the InvoiceID field in the AgencyBillingReport.csv they generated on the 5th. Mismatch? Rejection. Typos in the client’s legal name? Rejection. Decimal misplaced in the tax amount? Rejection — followed by a 72-hour processing delay and a support ticket that replies, ‘Please resubmit per Section 4.2 of the Agency Program Agreement.’

Required fields (non-negotiable, no exceptions):
• Client’s full legal name *exactly as registered in AWS Organizations*
• Your agency’s legal name and tax ID (no DBAs unless pre-approved)
• AWS Account ID(s) covered (comma-separated, no spaces)
• Invoice date + due date (must be ≥15 days from submission)
• Line items mapping 1:1 to AWS service codes (e.g., AWS EC2 - On-Demand - Linux, not ‘Cloud Servers’)
• Usage period (start/end dates must align with AWS’s monthly cycle: 1st–last day of calendar month)
• Taxes applied — and proof you’re legally authorized to collect them (more on this below)

Tax? Oh, You Thought You Could Wing That?

Here’s where agencies quietly implode. AWS doesn’t collect sales tax, VAT, or GST on your behalf. You do. And AWS requires *proof* — not just a checkbox. If you’re billing a German client and charging 19% VAT, AWS expects either:
• A valid German USt-IdNr (VAT ID) on file with them *before* invoicing, and
• A line-item breakdown showing net amount, tax rate, and gross — with VAT clearly labeled (not buried in ‘service fee’).
Same goes for US states: If you charge Texas sales tax, AWS wants your TX comptroller registration number linked to your agency profile. No number? No tax line. And if you accidentally charge tax where you’re not registered? That’s not a ‘friendly correction’ — that’s a compliance violation flagged in your quarterly audit.

Pro tip: Use AWS’s Tax Exemption Certificate Upload Portal *before* month-end. Don’t wait until you’re drafting the invoice. Certificates take 3–5 business days to validate. And yes — AWS checks expiration dates. A certificate expiring on June 30th won’t cover a July invoice. Surprise!

Reconciliation: Where Dreams Go to Die (and Then Get Fixed)

Your invoice total ≠ AWS’s payout. Never assume. Here’s why:
• AWS applies their 15% agency fee *after* taxes — so if your invoice says $10,000 + $1,000 VAT = $11,000, AWS pays you $8,500 ($10,000 × 0.85), *then* adds back the $1,000 VAT (since they don’t keep tax).
• Credits (RIs, Savings Plans, promotional balances) reduce your gross bill *before* the fee — meaning your fee is calculated on the *net* spend.
• Disputes or adjustments from prior months show up in the current report — often without warning.

Always cross-check three files:
1. Your submitted invoice (PDF + XML if using EDI)
2. The AgencyBillingReport.csv (downloaded same day you submit)
3. The PaymentSummary.csv (sent 5 days post-month-end)
If totals don’t reconcile down to the cent, don’t blame finance — dig into line-item mismatches. Hint: Check for services marked Reserved Instance Application — those don’t appear on your invoice but reduce your payable amount.

Top 5 Ways Agencies Get Rejected (and How to Avoid Them)

• PO mismatch: Your client’s PO number is ‘ABC-2024-001’. AWS expects exactly ‘ABC-2024-001’ — not ‘ABC2024001’, not ‘PO: ABC-2024-001’, not ‘abc-2024-001’. Case-sensitive. Hyphen-sensitive. Life-sensitive.
• Wrong currency: Invoice in EUR but client’s AWS account is USD-based? Rejected. AWS pays only in the currency of the payer’s billing address — and it’s immutable per account.
• AWS Global Site ‘Managed Services’ line item: AWS doesn’t recognize vague buckets. ‘Cloud Management Fee’? Nope. ‘AWS Optimization Support’? Still no. You must use AWS-defined service codes — even for professional services bundled under MSP agreements.
• Missing signature: Yes, even digital invoices need a signed PDF. Not a typed name. Not a stamp. A verifiable e-signature tied to your company domain (DocuSign, PandaDoc, Adobe Sign — not ‘signed on iPhone in Notes app’).
• Weekend submissions: AWS’s invoice portal processes submissions Mon–Fri, 6 AM–6 PM PST. Submit Friday at 6:01 PM? It queues for Monday. Missed payment cycle? You wait another month. Set calendar alerts. Or better yet — automate with AWS’s API + Zapier.

Bonus: Real Talk About Timing & Cash Flow

Don’t believe the ‘net 30’ fantasy. AWS pays *30 days after month-end* — but only if your invoice clears all checks *by the 10th*. Submit on the 11th? Payment shifts to the next cycle (so 60 days from usage). Factor that into your runway. One agency we know nearly choked because they billed on the 12th — then realized their ‘July usage’ wouldn’t hit their bank until *September 3rd*. Their payroll software did not appreciate that surprise.

Solution? Build a hard internal deadline: ‘All invoices cut by the 7th. No exceptions. Not for birthdays. Not for vacations. Not for ‘the client asked for one more change.’’

Final Word: Stop Fighting the Machine

AWS Agency Payments isn’t broken — it’s just brutally consistent. Its rules aren’t arbitrary; they’re built for scale, auditability, and zero ambiguity. The agencies who thrive aren’t the ones with the flashiest dashboards — they’re the ones with Excel macros that auto-validate service codes against AWS’s latest taxonomy, tax ID trackers synced to renewal calendars, and a shared Slack channel named #invoice-qa where every draft gets peer-reviewed before submission.

So yes — it’s fussy. Yes — it’s detailed. Yes — you’ll mutter ‘AWS’ like a curse word at 2 a.m. when your CSV won’t import. But get it right, and you’ll get paid predictably, scale confidently, and never have to chase a client for an AWS credit card receipt again. And honestly? That’s worth memorizing the difference between EC2-Instances:Running:Hrs and EC2-Instances:Running:Linux:Hrs.