How to Categorize AWS in QuickBooks (and Xero)
The AWS bill hits for $1,247 this month. Last month it was $89. Nothing changed in the product. The invoice line items read like a foreign language: EC2, S3, RDS, NAT Gateway, data transfer out, Marketplace, CloudFront. You're the bookkeeper, and you need to drop this into the chart of accounts before close. Software? Utilities? Cost of Goods Sold? And what about that $12,000 Reserved Instance payment from January still sitting in a clearing account?
AWS is the messiest recurring expense in a modern SaaS company and one of the largest. Get the category wrong and you misstate gross margin, blow Section 174 R&D tagging, or expense $12K of prepaid infrastructure in one month. Here's the bookkeeper answer.
How do you categorize AWS in QuickBooks?
AWS goes to Computer & Internet Expenses in QuickBooks Online (Detail Type: Office/General Administrative Expenses), or a custom Cloud Services account under Operating Expenses for cleaner reporting. In Xero, use account code 408 Software & IT Expenses or a custom 412 Cloud Hosting. On Schedule C, AWS belongs on Line 25 (Utilities) for hosting and bandwidth, or Line 27a (Other expenses) if you separate cloud infrastructure as its own line. Do not use Line 22 Supplies. No 1099-NEC is required because Amazon Web Services, Inc. is a wholly-owned subsidiary of Amazon.com, Inc., a C-corporation (§6041 corporate exemption). Sales tax depends on state and service type. TX, NY, OH, and WA tax cloud infrastructure; CA and FL do not. AWS collects sales tax where required and shows it on the invoice.
Key Takeaways
- GL account: Computer & Internet Expenses in QBO, or a custom Cloud Services account for SaaS businesses that want clean gross-margin reporting. Xero: 408 Software & IT or 412 Cloud Hosting.
- Schedule C: Line 25 Utilities for hosting and bandwidth, or Line 27a Other expenses if you break out cloud infrastructure separately. Form 1120 / 1120-S: Line 26 Other deductions or Line 19.
- No 1099-NEC. Amazon Web Services, Inc. falls under the §6041 corporate exemption. Skip the W-9 request.
- Reserved Instances and Savings Plans are prepaid expenses under §263. A $12,000 1-year RI gets capitalized and amortized at $1,000/month, not expensed upfront.
- §174 post-OBBBA: Domestic R&D is 100% deductible in TY2025 and forward, but the §41 R&D credit still requires you to track R&D-eligible AWS spend separately by tag or sub-account.
- Marketplace charges (Datadog, MongoDB Atlas, others) are not AWS. Categorize as the vendor's expense type even though they show up on the AWS invoice.
What is AWS?
Amazon Web Services is the cloud infrastructure arm of Amazon. It sells compute (EC2), storage (S3), databases (RDS), serverless functions (Lambda), networking, AI/ML, and roughly 200 other services. Billing is usage-based with no minimum commitment, and there's no monthly contract by default. Bills swing from $50/month for a hobby project to $50,000/month for a scaled SaaS company on the same account, depending on traffic, architecture, and storage choices.
Where AWS goes in your books
The Difficult 20% — Where AWS gets complicated
Reserved Instances and Savings Plans
AWS lets you prepay for 1-year or 3-year commitments in exchange for 30 to 70 percent discounts on compute. These upfront payments are prepaid expenses under §263. The common mistake: expensing the full $12,000 upfront on a 1-year RI in January, which overstates expense in Q1 and understates it the rest of the year. Correct treatment: capitalize $12,000 to a prepaid asset, then amortize $1,000/month over 12 months. A 3-year RI at $36,000 amortizes the same way over 36 months. Same approach for Savings Plans.
Sub-accounts: production vs dev/test
AWS Organizations splits a single bill across tagged accounts. Production AWS supports live product and revenue, so it's Cost of Goods Sold for a SaaS business. Dev and test support engineering, so they're R&D or Operating Expense. Booking them as one bucket loses the gross-margin signal and blurs §174 R&D tracking. Ask engineering for the tag map and book sub-accounts to separate GL lines.
AWS Marketplace charges
Third-party software billed through AWS Marketplace shows up on the AWS invoice. Datadog, MongoDB Atlas, Snowflake, Confluent, and dozens more operate this way. These aren't AWS infrastructure. Categorize them as the vendor's normal expense type: Datadog = Software, MongoDB = Database/Hosting, Snowflake = Data Platform. Pulling the invoice detail line by line is the only way to catch it. The aggregate AWS total in QBO hides it.
AWS Credits
AWS hands out credits via startup programs, partner agreements, and promos. When credits offset your bill, book them as contra-expense (reducing AWS spend), not income. Track the unused balance in a memo or separate clearing account so you know when they expire. Booking credits as income inflates revenue and creates a deferred-tax mess.
Data transfer (egress) fees
For high-traffic apps, egress can be 20 to 40 percent of the total AWS bill. The fee covers data leaving AWS to the public internet. Category-wise, treat it the same as compute: Cloud Services or Utilities. Don't split egress to its own GL line unless you charge it back to a specific client, in which case it becomes a billable reimbursement.
§174 R&D classification post-OBBBA
OBBBA (TY2025+) restored 100 percent domestic R&D deductibility in the year incurred, removing the §174 amortization headache for SMBs. But the §41 R&D credit still requires separately tracking R&D-eligible spend, including AWS infrastructure supporting R&D projects. If engineering uses a dev sub-account for new product work, tag that spend and report it to the tax preparer at year-end. Foreign R&D (non-U.S. AWS regions used for development) still amortizes over 15 years.
How Growthy categorizes AWS automatically
Growthy's pattern learning recognizes the "Amazon Web Services" descriptor and suggests Cloud Services with a confidence score. First-time Reserved Instance prepayments (large outliers vs the monthly run rate) get flagged for bookkeeper review and approval before posting, so the $12K never lands in operating expense by accident.
FAQ
Is AWS tax deductible for my business?
Yes. AWS is an ordinary and necessary business expense under §162 for any company using it for trade or business purposes. Personal AWS use is not deductible.
What QuickBooks account do I use for AWS?
Computer & Internet Expenses (Detail Type: Office/General Administrative Expenses) is the default. For SaaS businesses that want clean gross-margin reporting, create a custom Cloud Services account under Operating Expenses (or under Cost of Goods Sold if the spend supports production).
What Schedule C line does AWS go on?
Line 25 Utilities is the most common placement for hosting and bandwidth. Line 27a Other expenses works if you want to break out "Cloud hosting" as a separate line. Do not use Line 22 Supplies. AWS is a service, not a supply.
Are AWS Reserved Instances a prepaid expense?
Yes. Upfront RI and Savings Plan payments are prepaid expenses under §263. Capitalize the full upfront amount to a prepaid asset, then amortize evenly over the 1-year or 3-year term. A $12,000 1-year RI amortizes at $1,000/month.
Do I issue a 1099 to Amazon Web Services?
No. Amazon Web Services, Inc. is a wholly-owned subsidiary of Amazon.com, Inc., a C-corporation. §6041 corporate exemption applies. Don't request a W-9, don't issue Form 1099-NEC.
How do I categorize AWS Marketplace charges?
By the underlying vendor, not as AWS. Datadog billed through Marketplace = Software expense. MongoDB Atlas through Marketplace = Database/Hosting expense. Pull the invoice detail to identify Marketplace line items, then split the journal entry.
Do I owe sales tax on AWS bills?
It depends on state nexus and service type. Texas, New York, Ohio, and Washington tax cloud infrastructure (IaaS) and SaaS. California and Florida do not tax most cloud services. AWS collects sales tax where required and shows it on the invoice as a separate line. Confirm your nexus before assuming no liability.
Is AWS R&D-eligible under §174?
Partially. Domestic AWS spend supporting R&D activities qualifies for §174 treatment and the §41 R&D credit. Post-OBBBA (TY2025+), domestic R&D is 100 percent deductible in the year incurred, so the deductibility timing issue is gone. Foreign AWS regions used for R&D still amortize over 15 years. Tag R&D-eligible spend by AWS sub-account so the tax preparer can compute the §41 credit accurately.
Related
Stop guessing on AWS line items. Get started with Growthy, pattern learning that knows EC2 from Marketplace.
Tax figures verified against tax-thresholds-2026.yaml on 2026-05-20. Sales-tax treatment varies by state, confirm your nexus.
