Table 320 "Tax Jurisdiction"

Base Application · Microsoft.Finance.SalesTax · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 466 “Tax Jurisdictions” (6 Learn pages).

Properties

Property	Value
Caption	Tax Jurisdiction
DataClassification	CustomerContent

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No.	Name	Type	Explanation	Notes
1	Code Δ BC29	Code[10]	Specifies the code you want to assign to this tax jurisdiction. You can enter up to 10 characters, both numbers and letters. It is a good idea to enter a code that is easy to remember.	NotBlank
2	Description Δ BC29	Text[100]	Specifies a description of the tax jurisdiction. For example, if the tax jurisdiction code is ATLANTA GA, enter the description as Atlanta, Georgia.
3	Tax Account (Sales)	Code[20]	Specifies the general ledger account you want to use for posting calculated tax on sales transactions. via Page 466 “Tax Jurisdictions”	TableRelation Table 15 “G/L Account” (G/L Account)
4	Tax Account (Purchases)	Code[20]	Specifies the general ledger account you want to use for posting calculated tax on purchase transactions. via Page 466 “Tax Jurisdictions”	TableRelation Table 15 “G/L Account” (G/L Account)
5	Report-to Jurisdiction Δ BC29	Code[10]	Specifies the tax jurisdiction you want to associate with the jurisdiction you are setting up. For example, if you are setting up a jurisdiction for Atlanta, Georgia, the report-to jurisdiction is Georgia because Georgia is the tax authority to which you report Atlanta sales tax.	TableRelation Table 320 “Tax Jurisdiction” (Tax Jurisdiction)
6	Date Filter	Date	—	FlowFilter
7	Tax Group Filter	Code[20]	—	TableRelation Table 321 “Tax Group” (Tax Group); FlowFilter
8	Unreal. Tax Acc. (Sales)	Code[20]	Specifies the general ledger account you want to use for posting calculated unrealized tax on sales transactions. via Page 466 “Tax Jurisdictions”	TableRelation Table 15 “G/L Account” (G/L Account)
9	Unreal. Tax Acc. (Purchases)	Code[20]	Specifies the general ledger account you want to use for posting calculated unrealized tax on purchase transactions. via Page 466 “Tax Jurisdictions”	TableRelation Table 15 “G/L Account” (G/L Account)
10	Reverse Charge (Purchases)	Code[20]	Specifies the general ledger account you want to use for posting calculated reverse-charge tax on purchase transactions. via Page 466 “Tax Jurisdictions”	TableRelation Table 15 “G/L Account” (G/L Account)
11	Unreal. Rev. Charge (Purch.)	Code[20]	Specifies the general ledger account you want to use for posting calculated unrealized reverse-charge tax on purchase transactions. via Page 466 “Tax Jurisdictions”	TableRelation Table 15 “G/L Account” (G/L Account)
12	Unrealized VAT Type Δ BC29	Option	Specifies how to handle unrealized tax, which is tax that is calculated but not due until the invoice is paid.	OptionCaption: ,Percentage,First,Last,First (Fully Paid),Last (Fully Paid)
13	Calculate Tax on Tax Δ BC29	Boolean	Specifies whether to calculate the sales tax amount with the tax on tax principle.
14	Adjust for Payment Discount Δ BC29	Boolean	Specifies whether to recalculate tax amounts when you post payments that trigger payment discounts.
15	Name	Text[30]	—

Keys

Key1: Code (clustered)
Key2: Report-to Jurisdiction

Procedures

GetSalesAccount(Unrealized: Boolean): Code[20]: Returns the appropriate sales tax G/L account based on realization status.
GetPurchAccount(Unrealized: Boolean): Code[20]: Returns the appropriate purchase tax G/L account based on realization status.
GetRevChargeAccount(Unrealized: Boolean): Code[20]: Returns the appropriate reverse charge G/L account based on realization status.
CreateTaxJurisdiction(NewJurisdictionCode: Code[10]): Creates a new tax jurisdiction with the specified code and default account setup.
GetDescriptionInCurrentLanguageFullLength(): Text[100]: Returns the tax jurisdiction description in the user’s current language. Falls back to the default description if no translation is available.
GetName(): Text[30]: Returns the jurisdiction name, defaulting to the code if name is empty.

Plus 3 local procedures.

Triggers

OnDelete, OnInsert

Relations

lookup page Page 466 “Tax Jurisdictions”
Reverse Charge (Purchases): TableRelation Table 15 “G/L Account”
Tax Account (Purchases): TableRelation Table 15 “G/L Account”
Tax Account (Sales): TableRelation Table 15 “G/L Account”
Unreal. Rev. Charge (Purch.): TableRelation Table 15 “G/L Account”
Unreal. Tax Acc. (Purchases): TableRelation Table 15 “G/L Account”
Unreal. Tax Acc. (Sales): TableRelation Table 15 “G/L Account”
Report-to Jurisdiction: TableRelation Table 320 “Tax Jurisdiction”
Tax Group Filter: TableRelation Table 321 “Tax Group”

Referenced by

11 fields in 10 objects relate to this table (TableRelation or CalcFormula).

Table 319 “Tax Area Line”: Jurisdiction Description, Tax Jurisdiction Code
Table 1571 “VAT Entry Posting Preview”: Tax Jurisdiction Code
Table 254 “VAT Entry”: Tax Jurisdiction Code
Table 256 “VAT Statement Line”: Tax Jurisdiction Code
Table 320 “Tax Jurisdiction”: Report-to Jurisdiction
Table 322 “Tax Detail”: Tax Jurisdiction Code
Table 327 “Tax Jurisdiction Translation”: Tax Jurisdiction Code
Table 379 “Detailed Cust. Ledg. Entry”: Tax Jurisdiction Code
Table 380 “Detailed Vendor Ledg. Entry”: Tax Jurisdiction Code
Table 383 “Detailed CV Ledg. Entry Buffer”: Tax Jurisdiction Code

Pages and codeunits on this table

Page 466 “Tax Jurisdictions” (source table)

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Codeunit 43 “Language” (1 call: GetDescriptionInCurrentLanguageFullLength → GetUserLanguageCode)

Countries that replace it

CA, MX, RU, US

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "table", object_name: "Tax Jurisdiction"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.