Amazon KDP Royalty Flow Tracker (free 2026 tool)

What this tool does

Tracks monthly royalty payments from Amazon KDP to your Delaware LLC bank account by territory (US, UK, EU, etc.). Captures withholding rates per territory and treaty-rate verification.

Who needs it

Amazon KDP authors using Delaware LLC for royalty operations.

How it works

1. Connect KDP royalty reports.
2. Tool categorizes by territory and tracks withholding.
3. Annual summary for CPA's Form 5472 preparation.

Inputs

• Monthly KDP royalty reports

Output

Annual royalty summary with withholding breakdown.

What does the KDP royalty tracker actually compute?

This tracker takes the monthly royalty reports Amazon Kindle Direct Publishing (KDP) produces for your titles and turns them into a single annual picture organized by marketplace territory. KDP does not pay you one lump sum. It pays separately for the United States store, the United Kingdom store, the combined European stores, and the other regional storefronts where your books sell. Each of those streams can carry a different withholding rate before the money ever reaches your Delaware LLC bank account. The tool reads each monthly statement, groups the lines by territory, applies the withholding figure Amazon reported for that territory, and adds everything up so you can see gross royalty, tax withheld, and net deposited side by side.

The reason this matters for a non-resident founder is that the numbers your bank shows you are net numbers. The deposit that lands in your account has already had foreign tax taken out at the source in some territories. If you only look at the bank balance, you will understate your gross income and you will lose track of tax that may be creditable or refundable under a treaty. The tracker keeps the gross and the withholding visible so that when your CPA prepares Form 5472 and the attached Form 1120 for the LLC, the figures match what Amazon actually reported rather than what merely arrived in the account. It is a bookkeeping aid, not tax advice, and it does not file anything for you.

How do you read each input the tool asks for?

The only input the tracker needs is your set of monthly KDP royalty reports. KDP lets you download these from the reports area of your publishing dashboard, usually as a spreadsheet that lists each title, the marketplace it sold in, units, the royalty rate, and the royalty earned in the local currency of that marketplace. When you connect or upload twelve months of those reports, the tool reads the marketplace column to decide which territory each line belongs to, and it reads the royalty column to capture the gross amount. You do not need to pre-sort anything. The point of feeding raw monthly reports rather than a hand-built summary is that the source data carries the territory tag and the withholding tag that the tool depends on.

Pay attention to currency when you read your own reports. The UK store reports in pounds, the European stores often report in euros, and the US store reports in dollars. The tracker groups by territory first, so each territory keeps its native currency until you convert. If your reports mix currencies, do not add the raw numbers together by hand before uploading, because that destroys the per-territory withholding detail the tool is built to preserve. Upload the reports as KDP generated them. A clean twelve-month set with no missing months gives you an annual summary you can hand to a CPA without further cleanup, which is the whole purpose of the exercise.

How do you read the output?

The output is an annual royalty summary with a withholding breakdown. For each territory you will see three core figures: gross royalty earned, tax withheld at the source, and the net that reached your account. Reading across a row tells you the story of one marketplace. Reading down a column tells you your total exposure. The gross column is your true income for that store. The withholding column is the foreign tax Amazon already remitted on your behalf in territories that require it. The net column should reconcile, after currency conversion, to the deposits your Delaware LLC bank account received from Amazon during the year.

The single most useful thing the output gives a non-resident is a reconciliation anchor. When you later look at your Mercury, Wise, Relay, Lili, or Payoneer statement and see a year of Amazon deposits, you can compare the net column of this summary to those deposits. If they line up, your bookkeeping is internally consistent. If they do not, the gap usually points to a missing monthly report, a currency conversion difference, or a withholding line you had not noticed. The summary is meant to be the document you place next to your bank export and your formation paperwork when you sit down to close the books for the year.

Why is withholding tracked separately by territory?

Different Amazon marketplaces sit under different tax regimes, and the rate withheld on royalties is not uniform across them. The US marketplace withholds on royalties paid to foreign persons under US rules, and the rate that applies depends on whether a valid treaty claim is in place. Other territories may withhold little or nothing depending on local rules and the entity receiving the payment. Because the rates differ, a single blended number would hide the detail that actually drives your tax position. The tracker keeps each territory in its own bucket so that the rate you see attached to US royalties is the US rate and the rate attached to UK royalties is the UK rate.

This separation also matters because withholding is where treaty relief shows up or fails to show up. If you are entitled to a reduced rate under a tax treaty and the correct rate was applied, the withholding column for that territory will reflect the reduced figure. If the full statutory rate was taken instead, the column will show the higher number, and that is your signal that a treaty claim was missing or rejected. Keeping territories apart is what lets you spot that signal. A founder who lumps everything together would never see which specific marketplace overwithheld, and would have no way to chase the correction.

What is treaty-rate verification and why does the tool flag it?

Treaty-rate verification is the tool checking whether the withholding rate Amazon actually applied to your US royalties matches the rate your tax treaty allows. Many countries have an income tax treaty with the United States that reduces the withholding rate on royalties below the default statutory rate that applies when no treaty is claimed. To get the reduced rate, the beneficial owner of the royalties has to make a valid treaty claim through the tax interview Amazon runs when you set up your KDP tax profile. If that claim is valid, Amazon withholds at the treaty rate. If it is missing or invalid, Amazon withholds at the higher default rate.

The verification step compares the rate on your reports against the rate your treaty position implies and surfaces a mismatch. A mismatch does not always mean an error on your side, but it almost always means something worth investigating before year end. The two common outcomes are that your treaty claim lapsed or was never completed, or that the entity on file with Amazon does not line up with how the income is being reported. Catching this through the tracker is far cheaper than discovering it after a full year of overwithholding, because once tax has been withheld at the wrong rate, recovering it generally means dealing with a return rather than a quick fix in your KDP profile.

A worked example: a single-author Delaware LLC selling in three stores

Suppose a non-resident author forms a Delaware LLC, completes the KDP tax interview with a valid treaty claim, and publishes one book that sells in the US, UK, and EU stores. Over the year the US store reports 4,000 dollars of gross royalty, the UK store reports 1,200 pounds, and the EU stores report 900 euros. The US royalties were subject to withholding at the author's treaty rate, the UK royalties had no withholding applied, and the EU royalties had none either. When the author uploads twelve monthly reports, the tracker produces three rows. The US row shows 4,000 dollars gross, the treaty withholding amount, and the net. The UK and EU rows show gross equal to net because nothing was withheld.

The value of this example is what the author does next. The gross figures across all three rows are the income the Delaware LLC earned, and that total is what flows into the LLC's federal reporting through Form 1120 with Form 5472 attached. The US withholding figure is the foreign tax already paid at source. By keeping the three currencies in separate rows, the author can convert each at the rate that applied and then reconcile the combined net against the Amazon deposits that hit the LLC bank account. Without the tracker, the author would likely have recorded only the converted deposits and lost the gross and the withholding entirely, which would understate income and discard a credit.

How the summary feeds Form 5472 and Form 1120 preparation

A single-member Delaware LLC owned by a non-resident is generally treated as a disregarded entity for US tax purposes and must file Form 5472 together with a pro forma Form 1120. Form 5472 reports reportable transactions between the LLC and its foreign owner, and the failure-to-file penalty starts at 25,000 dollars, which is why getting the underlying figures right matters so much. The annual royalty summary this tracker produces is designed to be the input a CPA uses to populate those forms. It gives the gross income earned by the LLC, the foreign tax withheld, and the net received, all reconciled by territory.

The tracker does not prepare or file Form 5472 or Form 1120, and it does not replace a CPA. What it does is remove the most error-prone step, which is reconstructing a year of multi-currency, multi-territory royalty flows from scattered statements at filing time. Handing a clean annual summary to a preparer is faster and less risky than handing over twelve raw spreadsheets and a bank export and asking them to figure out which deposit corresponds to which month and store. Because the filing deadline and the penalty are fixed, the time you save by having reconciled figures ready is time you are not spending under pressure as the deadline approaches.

Common mistakes non-resident KDP authors make with royalty data

The first mistake is treating bank deposits as income. Deposits are net of withholding and net of currency conversion, so a founder who books only deposits will understate gross royalty and will never see the tax that was withheld. The second mistake is mixing currencies before the data is grouped, which collapses the per-territory detail the tracker needs. The third is skipping the KDP tax interview or letting the treaty claim lapse, which silently raises the US withholding rate for the rest of the year.

• Recording only the net Amazon deposit and calling it royalty income, instead of capturing gross and withholding separately.
• Converting all marketplaces to one currency by hand before uploading, which erases the territory and withholding breakdown.
• Leaving the KDP tax interview incomplete so the default withholding rate applies to US royalties all year.
• Uploading an incomplete set of months, which makes the annual total too low and breaks the bank reconciliation.
• Assuming every territory withholds the same way and not checking the US row against the treaty rate.

Each of these is avoidable with the reports you already have. The tracker is built around the assumption that you feed it complete, unaltered monthly reports, so the discipline that prevents these mistakes is simply downloading every month and uploading them as they came from KDP. The verification flag then does the work of catching the withholding problem you might otherwise miss.

Edge cases: returns, currency swings, and mid-year entity changes

Royalty reports are not always clean. KDP can report negative royalty lines when readers return books or when a prior estimate is corrected, and those negative lines belong in the same territory bucket as the sales they offset. The tracker keeps them with their territory so the net for that store reflects reality rather than an inflated gross. Currency swings are another edge case. Because each territory holds its native currency until you convert, a sharp move in the pound or euro during the year does not corrupt the underlying gross figures, but it does mean the converted net you reconcile against your bank may differ from a naive single-rate conversion.

A trickier edge case is changing the entity on file with Amazon partway through the year, for example switching the KDP account from a personal tax profile to the Delaware LLC. When that happens, part of the year's royalties were reported under one tax status and part under another, and the withholding may differ across the split. The annual summary will show the blended result, so you and your CPA need to know the change date to interpret it correctly. The tracker organizes the data, but it cannot know that the entity changed unless the reports reflect it, so a mid-year change is one of the few situations where you should annotate the summary before handing it over.

What treaty rate applies, and what if no claim was made?

The withholding rate on US-source royalties paid to a foreign person depends entirely on whether a valid treaty claim is in place. With a valid claim, Amazon applies the reduced rate set by your country's treaty with the United States. With no claim, the default statutory rate for payments to foreign persons applies, and that default is meaningfully higher than most treaty rates. The tracker does not invent a rate for you. It reports the rate Amazon actually applied and compares it against the treaty position you indicated, so the number you see in the withholding column is the real figure from your statements rather than an assumption.

If the summary shows the default rate where you expected a treaty rate, the practical fix is to revisit the KDP tax interview and confirm that a valid claim is on file for the correct beneficial owner. Going forward, the corrected claim lowers the rate on future royalties. For the royalties already overwithheld, recovery generally happens through the US tax return rather than through Amazon, because the tax has already been remitted. This is exactly why the verification flag is worth acting on early. The longer a wrong rate runs, the more income gets overwithheld before you notice, and the larger the amount you have to chase back through a filing.

What should you do with the annual summary once you have it?

Treat the summary as a working document with three audiences. The first audience is you, reconciling the net column against your Delaware LLC bank deposits to confirm your books are internally consistent. The second is your CPA, who uses the gross income and withholding figures to prepare Form 5472 and the pro forma Form 1120. The third is your future self at the next year's close, who benefits from having a clean prior-year baseline to compare against. Save the summary alongside the underlying monthly reports and your bank export so the full trail exists if anyone ever needs to see how a figure was derived.

Concretely, a sensible sequence is to generate the summary after the year ends, reconcile it to your bank statements, resolve any treaty-rate flags by checking your KDP tax interview, and then deliver it to your preparer well ahead of the filing deadline. Because the Form 5472 penalty is fixed at 25,000 dollars and does not scale with the size of your royalties, even a small KDP operation has a strong reason to keep this reconciliation tidy. The tracker exists to make that reconciliation a routine end-of-year task rather than a scramble, and the output is only useful if you actually carry it through to the filing.

How this tool fits the wider Delaware LLC tax picture

Royalty tracking is one piece of running a US LLC as a non-resident, and it sits inside a calendar of other obligations. The Delaware Certificate of Formation costs 110 dollars to file, and the state charges a 300 dollar annual franchise tax due each June 1, with a 200 dollar late penalty plus 1.5% per month if it is missed. An EIN is free through Form SS-4 and typically takes about 8 to 10 business days for a non-resident applicant. Beneficial ownership information reporting was made exempt for US-formed LLCs under the FinCEN interim final rule of March 26 2025. The royalty summary does not touch any of these directly, but it lives in the same annual rhythm.

Keeping these items in view helps you sequence the year. Your franchise tax and your federal Form 5472 filing both have hard deadlines, and the royalty summary is the input that makes the federal piece manageable. By producing a reconciled, territory-by-territory picture of your KDP income and withholding, this tracker lets you walk into the Form 5472 conversation with figures that already tie out to your bank account. That is its narrow job. It does not form the LLC, file the franchise tax, or apply for the EIN, but it removes the bookkeeping friction from the one part of the year where multi-currency royalty data would otherwise be hardest to assemble.