Guide · Finance
Country on a GGR row has to be defined
Tax authorities do not accept 'internet' as a country. Your revenue file needs a country per row, and everyone who uses the file needs to know which definition you picked.
7 min readUpdated By the Turnkeyxgaming team
Pick a definition and print it
Registration country, tax residence and geo at the time of the bet are three different fields. A player can have all three. The field you report is a policy choice made with counsel, not a default in the aggregator. Once chosen, write it in the file header. Switching definition between months moves revenue across borders and creates a tax restatement.
Payment files often use the card's country. That will not match the tax file, and it does not have to. Do not 'fix' the revenue file to match the PSP. Reconcile them as two views. VPN traffic is why geo country jitters. If your rule is geo, expect jitter and a fraud process. If your rule is registration, the VPN is irrelevant to the report and still relevant to whether you should have taken the bet.
Print the definition in the file header and keep it for the reporting period. A row that falls back from geo to registration to card country, depending on which field is filled, is three policies in one column. Leave the cell empty and listed in an exception count rather than quietly substituting another country. Counsel confirms the definition for each market you file in before the first return. Switching it next month moves revenue across borders and creates a restatement.
Three country fields that will not match
The revenue file needs one country per row, and the header has to say which definition that column uses. The other fields can exist. They cannot fill the gap.
| Field | What it answers | Safe use in this file |
|---|---|---|
| Registration country | Where the account was opened. | The column, if counsel told you to report that, and only that. |
| Geo at the time of the bet | Where the connection appeared to be for that stake. | The column, if that is the chosen rule. Expect VPN jitter and keep the fraud process next to it. |
| Card country on the payment file | What the PSP saw on the instrument. | A reconciliation view. Not a substitute when geo or registration is blank. |
| A blend of the three | Whichever was non-empty. | Not safe. The column no longer has a definition, so the return cannot be explained. |
Make the column boring
- 01
Name the field
State in the header which country definition the column uses.
- 02
Do not blend
Do not fall back from geo to card country inside the same column.
- 03
Counsel
Confirm the definition against each market you file in before the first return.
Do not edit the revenue file until it matches the PSP
Payment country and the country you report can differ for an honest player. Forcing them together hides the definition in the header and makes the next filing indefensible. Reconcile the two views. Do not merge them.
Worked example
A month of 1,000 rows and the exceptions you cannot blend away
Suppose the month has 1,000 revenue rows and your filed definition is geo at the time of the bet. 940 rows carry that signal. 45 carry only a registration country and no geo value. 15 carry neither. Leave the 60 incomplete rows out of the country total, count them as exceptions, and attach the count to the return rather than filling the cells with a different signal.
The exception count is the useful number. It tells you whether the gap is a technical problem, such as a missing geo lookup, or a policy problem, such as a market where the signal is unreliable. If the count grows month on month, fix the collection before the next filing. Blending registration country into the geo column hides both the technical and the policy issue inside a total that looks complete.
One month, one definition, three outcomes
| Row group | Count | What the file records |
|---|---|---|
| Geo signal present | 940 | The country under the filed definition |
| Registration only | 45 | Blank country, listed as an exception |
| No usable signal | 15 | Blank country, listed as an exception |
| Total | 1,000 | Country total plus a visible exception count |
FAQ
Questions operators ask
Does the aggregator decide the tax country?
No. We can include the country signals we are given. Which one you report is your decision with your advisers.
Will the aggregator pick the tax country for each row?
No. The file can carry the country signals you pass through. Which signal you report is a decision you make with your advisers, written in the header, and kept stable for the period.
What do we put in the column when the chosen signal is missing?
Leave it blank and count the row as an exception. Substituting card country or registration so the cell looks complete changes the definition for that row only, which is how a filing becomes a blend.
Can we fill a blank with the registration country and flag it?
A flag does not fix the definition. If the filed rule is geo, a registration-based value in the same column is a different measurement. Keep the cell blank, count the row, and explain the exception in the covering note.
Keep reading
Related pages
- Guide · FinanceGGR explainedCasino GGR is stakes minus wins. It is not NGR, and sportsbook GGR can swing on a single result, so the definition matters.Read
- Guide · FinanceThe daily GGR fileThe daily GGR file agrees stake, win and the difference in one closing timezone, with bonus-funded wins marked for reconciliation.Read
- Guide · CatalogueBlocking one titleHide one game in one country without switching the studio off. Account country and IP country can disagree, so decide the rule.Read
- Region · WorldwideWorldwideOne integration, a catalogue per market and multi-currency wallets, at 13% of GGR in Asia and 16% elsewhere, region by region.Read
Get a written quote and sandbox access
Tell us your licence, target markets and products. You get the GGR rate in writing, the studio list for your markets and sandbox credentials.