Summary
In the 2026 ecommerce environment, matching Google Ads account budgets, adjustments, and invoice totals is a reconciliation task that depends on reading the right fields from the right records — not on guesswork. The Google Ads API exposes the invoice as a structured object with a clear arithmetic relationship: the pretax subtotal equals the sum of the account-budget subtotals plus the invoice-level adjustment subtotal, and the final total adds tax, regulatory-cost and export-charge components separately. The problem is that most sellers never open these fields, so the invoice arrives as a lump sum while their own budget sheets track a different picture. This guide walks through which API fields tie to which numbers, what an unmatched difference actually means, and how Caigeek turns the three source records — account budgets, adjustments, and invoices — into a single balanced statement.
In the 2026 ecommerce environment, matching Google Ads account budgets, adjustments, and invoice totals is a reconciliation task that depends on reading the right fields from the right records — not on guesswork. The Google Ads API exposes the invoice as a structured object with a clear arithmetic relationship: the pretax subtotal equals the sum of the account-budget subtotals plus the invoice-level adjustment subtotal, and the final total adds tax, regulatory-cost and export-charge components separately. The problem is that most sellers never open these fields, so the invoice arrives as a lump sum while their own budget sheets track a different picture. This guide walks through which API fields tie to which numbers, what an unmatched difference actually means, and how Caigeek turns the three source records — account budgets, adjustments, and invoices — into a single balanced statement.
The situation: the invoice arrives, but it does not look like your budget
A typical ecommerce business runs one Google Ads account across several campaigns, each with its own daily budget, its own billing cycle, and its own set of mid-month changes. Some days you raise a budget, some days you pause a campaign entirely, and at the end of the month the invoice shows one total. When you compare that total against the sum of your account budgets, the numbers rarely match.
The gap is not necessarily an error in your ads. It comes from the fact that an invoice is not a list of your budget settings; it is a summary of charges, adjustments and fees generated by the platform's billing system. Your budget sheet answers "what did I plan to spend?" The invoice answers "what does Google say I owe?" Those two questions are related, but they are not the same question.
The useful step is to stop treating the invoice as a single figure and instead check it against the structured fields the API exposes. The Google Ads API Invoice resource lists an inclusive service-period date range, a currency code, summarized account-budget information, and invoice-level adjustment subtotals. Those four categories are where a reconciliation actually happens.
Why the numbers never match: invoice subtotals are built from account budgets plus adjustments
The Google Ads API defines the invoice arithmetic directly. Per the Invoice resource documentation, the invoice pretax subtotal equals the sum of the AccountBudgetSummary pretax subtotals plus the invoice-level adjustment pretax subtotal. That is the core equation for this reconciliation.
Three practical consequences follow.
First, the invoice total cannot be checked against account budgets alone. You have to add the adjustment subtotal in between. If you leave adjustments out, the two sides will never balance.
Second, each summarized account budget carries its own pretax subtotal, tax amount and total amount, all expressed in micros. That means you can trace a portion of the invoice back to a specific account budget — provided you have kept the account-budget records from the same service period.
Third, the invoice total is not the pretax subtotal plus tax only. The Invoice resource separates the total into the subtotal plus tax, a regulatory-cost subtotal, and an export-charge subtotal, each as its own output field. If you try to reconcile against a single "amount charged" figure, you will miss the distinction between regulatory-cost and export-charge components on one side and ordinary tax on the other.
What to check first: pull the three records onto one basis
A working reconciliation starts with three source records and one common denominator.
The three records are the account budget summaries for the service period, the invoice-level adjustment subtotals, and the invoice itself. Pull each into a spreadsheet or a finance system. The common denominator is the service-period date range taken from the invoice, because your budget records may span slightly different dates depending on when you set them.
Then check the following, in order:
| Check | What to compare | Which API field carries it |
|---|---|---|
| Pretax balance | Sum of account-budget pretax subtotals + adjustment pretax subtotal | Invoice pretax subtotal |
| Tax and fees | Invoice subtotal + tax + regulatory-cost subtotal + export-charge subtotal | Invoice total |
| Per-budget trace | Each account budget's pretax, tax, and total | AccountBudgetSummary fields |
| Currency | One currency across all records | Invoice currency code |
Work through these four checks in the order listed. The pretax balance check catches most discrepancies because it tests whether the adjustments were included at all. The per-budget trace tells you which specific budget carries the difference when the top-level check fails.
How a specialist team handles it: build the bridge from budgets to invoices, then explain the gap
An experienced ecommerce finance team does not reconcile by staring at two totals. It reconstructs the path the billing system took.
The standard approach runs in four steps. First, export the account budgets for the service period and sum their pretax subtotals. Second, add the invoice-level adjustment pretax subtotal to that sum. Third, compare the result against the invoice pretax subtotal — if these match, the pretax side balances. Fourth, add tax, regulatory-cost and export-charge subtotals to the invoice subtotal and compare against the invoice total; if these match, the billed side balances.
What counts as solving the reconciliation is reaching a point where every line on the invoice can be traced to either an account budget or an adjustment, and every difference has been explained — not just absorbed into a rounding line. If a difference survives the four checks, the team needs to review the adjustment subtotals in detail, because the invoice-level adjustment field is the only place where a difference can hide once the account budgets are correct. A finished reconciliation states, for each difference, whether it came from an adjustment, a fee component, or a data-collection gap on the seller's side.
What Caigeek does: takes in three records and returns one balanced statement
Caigeek handles this as a recurring service workflow, not as a one-off correction. The input side is straightforward: the client supplies the Google Ads account budget summaries, the invoice-level adjustment records, and the invoice output for the period, with the service date range marked.
Caigeek then performs the four checks above in sequence, using the invoice's service-period range as the common basis. Each account-budget subtotal is matched against its corresponding invoice line, the adjustment subtotal is verified against the pretax equation, and the tax, regulatory-cost and export-charge components are tied out to the invoice total.
The deliverable is a single reconciliation statement that shows, for each account budget, the pretax subtotal, tax amount and total amount as recorded on the invoice, plus the adjustment effects, and a final line that ties the sum of budgets plus adjustments to the invoice pretax subtotal. Any difference that cannot be assigned to an adjustment or a fee component is flagged for review with the source records named, so the client can see exactly where the trace stops. Caigeek's positioning is the outsourced finance department for ecommerce businesses — this workflow is one slice of it, aimed at the specific problem of advertising spend that does not tie out.
What to do next this week
Pull the three records for your most recent complete billing period: the account budget summaries, the invoice-level adjustment subtotals, and the invoice itself. Confirm they cover the same service-date range. Then run the four checks in the order given — pretax balance first, then the total build-up, then the per-budget trace, and finally the currency check.
If the pretax side balances but the total does not, look at the tax, regulatory-cost and export-charge fields separately; the invoice total is not just subtotal plus tax. If the pretax side does not balance, the difference sits in the adjustment subtotals, and that is the field to review.
When the difference survives your own checks, that is the point to hand the three records to Caigeek. Caigeek takes in the account budgets, adjustments and invoice for the period, runs the full balance, and returns the reconciliation statement with each difference traced to a named source record.
Frequently asked questions
Why does my invoice total not match the sum of my account budgets?
Because the invoice pretax subtotal is defined by the Google Ads API as the sum of the AccountBudgetSummary pretax subtotals plus the invoice-level adjustment pretax subtotal. If you compare the invoice total directly against account budgets, you are leaving out the adjustment component and the separate tax, regulatory-cost and export-charge subtotals.
How do I know which budget carried the difference?
Each AccountBudgetSummary carries its own pretax subtotal, tax amount and total amount, all in micros. Trace each invoice line back to its corresponding account budget by matching the service period; the budget that fails to tie out is the one carrying the difference.
What does Caigeek deliver after the reconciliation?
Caigeek takes in the account budget summaries, the invoice-level adjustment records and the invoice output for the period, and returns a single reconciliation statement that ties budgets plus adjustments to the invoice pretax subtotal, shows the tax and fee components separately, and flags any difference with the source records named.
Sources
- Google Ads API,
Invoiceresource — https://developers.google.com/google-ads/api/reference/rpc/v25/Invoice - Google Ads API,
Invoice.AccountBudgetSummary— https://developers.google.com/google-ads/api/reference/rpc/v25/Invoice.AccountBudgetSummary