Financial Transactions

The following fields in the arctrans table will be auto-completed by the API:

*** The value used for a client will always be the value set in the companyId

• account: This field is auto-completed as follows:

  1. When the supplierId is provided and Line Type AP is provided but account is empty, account is auto-completed with the account assigned to Supplier Group for given Supplier.

  2. When the customerId is provided and Line Type AR is provided but account is empty, account is auto-completed with the account assigned to Customer Group for given Customer.

  3. Account for GL line is never autocompleted and needs to be provided.

• apar_id: If a PaymentInformation Data Transfer Object (DTO) is provided, the value for this field is taken from the transaction line referred to by the parameters within Payment Information (Customer or Supplier ID).

• apar_name: This field is auto-completed with a Supplier name from the Supplier master file.

• apar_type: The value for this field depends on the information provided in the JSON format.

  1. If Invoice DTO information is provided, it will be: a. ‘P’ when the supplierId is provided.
     b. ‘R’ when the customerId is provided.
  2. If a PaymentInformation Data Transfer Object (DTO) is provided, it will be: a. ‘P’ when the transaction line referred to by the parameters within Payment Information is related to a Supplier.
     b. ‘R’ when the transaction line referred to by the parameters within Payment Information is related to a Customer.

• arrival_date: If no value is set for it, this field will be auto-completed with the UpdatedAt value and then converted to Time Zone which is set in Company Information.

• arrive_id: If no value is set for it, this field will be auto-completed with the Transaction Number value. However, in case of Registration of GL transactions, this auto-completion will be the standard behaviour and the field will be read-only.

• collection: This field is auto-completed in taxes lines. The value for this field depends on the taxCode setup.

  1. Value will be 0 when Cash Principle flag is not selected.
  2. Value will be 1 when Cash Principle flag is selected.

• ext_ref: This field is auto-completed with the externalReference value provided at the Transaction level of the JSON request. The value is populated in all rows, including generated Tax rows. This field is used to pass on external references with financial transactions posted based on integrations/interfaces from external systems.

• factor_short: This field is auto-completed for AP/AR rows as follows (it will not be auto-completed on Secondary open items):

  1. When the supplierId is provided, factor_short is auto-completed with the payment recipient assigned to the supplier in the Supplier master file.

  2. When the customerId is provided, factor_short is auto-completed with the payment recipient assigned to the customer in the Customer master file.

• fiscal_year: The fiscal_year for the selected acc_period and period_id = GL, extracted from the acrperiod table.

• last_update: Date on which the API was called

• line_type: If no value is set for it, this field will be auto-completed based on account.

• pay_currency: This field is auto-completed as follows:

  1. When the supplierId is provided, pay_currency is auto-completed with the same value as currency on AP line.

  2. When the customerId is provided, pay_currency is auto-completed with the same value as currency on AR line.

• pay_flag: The value for this field depends on the information in each Detail DTO provided in the JSON format.

  1. Value will be 0 when no PaymentInformation DTO is provided.
  2. Value will be 1 when a PaymentInformation DTO is provided.

• pay_method: This field is auto-completed as follows:

  • For AP/AR rows:

    1. When the supplierId is provided for the invoice, pay_method is auto-completed with the payment method assigned to the supplier in the Supplier master file.

    2. When the customerId is provided for the invoice, pay_method is auto-completed with the payment method assigned to the customer in the Customer master file.

  • For secondary open item rows: When pay_method is not provided, it is auto-completed with the payment method assigned or auto-completed in the related AP row.

• period: This field is auto-completed based on GL period assigned for given transaction date

• reg_amount: This field is auto-completed with the cur_amount value.

• sequence_no: This field is auto-completed following this logic:

  1. Per Header (voucher_no), a consecutive number is assigned to each Transaction Detail. The first detail of each header is assigned number 1.

  2. In SecondaryOpenItems, it takes the next value assigned to the Detail it corresponds to.

  3. In TaxInformation rows, it takes the next value assigned to the Detail it corresponds to.

  4. In TaxInformationDetail, it takes the next value assigned to the TaxInformation it corresponds to.

• status: This field is auto-completed with the following values:

  1. In Detail rows, ‘N’ is assigned for rows where the trans_type value is AP or AR. It is left empty for rows where the trans_type value is GL.

  2. In TaxInformation rows, this field is always assigned the value ‘X’.

• tax_seq_ref: This field is auto-completed with the following values:

  1. In Detail rows, the value is -1.

  2. In TaxInformation and TaxInformationDetail rows, this field takes the same value as the sequence_no of its parent row.

• terms_id: This field is auto-completed as follows:

  1. When the supplierId is provided, terms_id is auto-completed with the payment term assigned to the supplier in the Supplier master file.

  2. When the customerId is provided, terms_id is auto-completed with the payment term assigned to the customer in the Customer master file.

• trans_date: The same value as the voucher_date field

• trans_id: If this value is provided in the PostingCycle field of the JSON format, it is directly assigned. Otherwise, the API selects one of the following values from the acrtransgr table:

  1. The oldest trans_id for the selected vouch_series (trans_type) and period with status N or P. If not found, the API selects...

  2. The trans_id for the selected vouch_series and fiscal_year. If not found, the API selects...

  3. The trans_id for the selected vouch_series and fiscal_year 0. If not found, the field is left empty.

• trans_type: In general, this field takes the account_type for the selected account and period, extracted from the aglaccounts table. In TaxInformation rows, it takes the value ‘TX’, except when linked to an exempt-type tax system, in which case it takes the value ‘TE’.

• user_id: User ID of the currently logged-in API user.

• unro_amount: The same value as the amount field.

• unro_cur_amount: The same value as the cur_amount field.

• vat_reg_no: This field is auto-completed as follows:

  1. When supplierId is provided, vat_reg_no is auto-completed in tax lines (trans_type = TX) with the VAT registration number assigned to the supplier in the Supplier master file.

  2. When customerId is provided, vat_reg_no is auto-completed in tax lines (trans_type = TX) with the VAT registration number assigned to the customer in the Customer master file.

• voucher_no: The next available value in counter for the selected posting cycle (trans_id), extracted from the acrperiod table.

In this section, you can find how the autocomplete of Analytical Information is carried out for all the categories defined in the Account rule and not sent in the DTO.

The Analytical Information DTO, which is an array, can be completed with all the analytical details (Dimension 1 to 7 and Dimension Values 1 to 7).

The Account rule allows you to autocomplete these values in three ways:

1. Through the value of an attribute that is also an owner of another attribute. For example, if we have an Account rule where Cost Center (Category 1) is the owner of Project (Category 2), then the value of the first attribute is completed depending on the value entered in the second attribute.
2. Through a defined Value Matrix where one or more attributes (up to 4) can be combined to get the value of another attribute.
3. Through a default value.

The attribute values are always auto-completed (if applicable), regardless of the values in the User input field in the Account rule window. However:

1. If the User input value is Optional - The user can set a different value. Empty is a valid value.
2. If the User input value is Mandatory - The user can set a different value except for Empty.
3. If the User input value is Fixed - The user cannot set a different value.
4. If the User input is No check - The user can send any value even though it does not exist in the database as a valid attribute value. However, the value cannot exceed the length and it must be aligned with the type (numeric/alphanumeric) of the attribute definition.

We take into account the following information in the calculations:

• Attributes:

• Project 1000 - Relation group:

• Attribute values - OFFICE:

• Attribute values - COMPANY:

• Attribute values - COSTC:

• Attribute values - PROJECT:

• Attribute values - OFICINILLA:

• Attribute values - BUILDING:

• Chart of Accounts:

• Account rule - OFFICECOST:

• Account rule - BALANCE/FINANCE:

• Account rule - TAXES:

• Account rule - DEPENDENCIES:

• Account rule - RENTALCOST:

• Account rule - TAXES2:

• Account rule - RENTALCOSTMATRIX:

• Account rule - TRAVEL EXPENSES:

• Tax Code 1X:

• Value matrix - COMPLETECOSTCENTER:

Matrix Rows

Value matrix

Based on the information mentioned above, the Analytical Information will be autocompleted as the following scenarios show.

In this section, you can find how to autocomplete the Currency code.

User input of Currency code in the account rule can be Mandatory or Fixed.

The field is optional in the DTO, but if the user doesn’t provide a value and the system is unable to auto-complete it, an error message is displayed.

The Currency code field can be autocompleted in the following way:

• For GL rows, the logic is the same as the one for autocompleting analyticalInformation.
• For AP/AR rows:
  • If User input of the account rule is Fixed, the logic is the same as the one implemented for analyticalInformation.
  • If User input of the account rule is Optional/Mandatory:
    • We get the value from the Customer/Supplier information.
    • If a value cannot be found in the Customer/Supplier information, we get it from the account rule.
• For the TX line, the value is inherited from the parent.

We take into account the following information in the calculations:

• Supplier 1001 - INVOICE

Currency
Norwegian Kroner - NOK

• Attribute values - Company

Attribute value	Description	Owner	Value	Period from	Period to	Status
EN	ERP DEMO (EN)		0	0	209999	Active
NO	Agresso Demo AS (Norway)		0	0	209999	Active
SE	Agresso Demo AS (Sweden)		0	0	209999	Active

• Value matrix. COMPLETECURRENCY

Source Attribute 1	Source Attribute 2	Destination Attribute
COMPANY	COST	CURRENCY

MATRIX ROWS

InterCompany Company	Cost centre	Currency Code
EN	100	GBP
NO	100	NOK
NO	110	EUR
SE	100	EUR
SE	115	SEK

• Chart of accounts

Account	Description	Rule	Group	Period from	Period to	Type	Status
6210	Rent	RENTALCOST	620	200001	209912	General Ledger	Active
2011	Accounts Payable International Suppliers	Balance/Finance	200	199401	209912	Accounts Payable	Active
1320	Ingoing VAT	Balance/Finance	130	199401	209912	General Ledger	Active

• Account rule. RENTALCOST

	Attribute	User input	Auto-completion	Default value	Validation relation
Account	ACCOUNT
Category 1	COSTC	Mandatory
Category 2	PROJECT	Optional
Category 3		Fixed
Category 4		Fixed
Category 5		Fixed
Category 6		Fixed
Category 7	COMPANY	Mandatory
Currency	CURRENCY	Fixed	COMPLETECURRENCY	GBP
Tax code	TAXCODE	Fixed		0
Tax system	TAXCAT	Optional		EX
Factor VAT	FACTOR_VAT	Optional

• Account rule. Balance/Finance

	Attribute	User input	Auto-completion	Default value	Validation relation
Account	ACCOUNT
Category 1	COSTC	Mandatory
Category 2		Fixed
Category 3		Fixed
Category 4		Fixed
Category 5		Fixed
Category 6		Fixed
Category 7		Fixed
Currency	CURRENCY	Mandatory		GBP
Tax code	TAXCODE	Fixed		0
Tax system	TAXCAT	Optional
Factor VAT	FACTOR_VAT	Optional

• Tax Code 1G defined in the database:

Tax Code	Account	Vat Percentage	Net flag	Reduction	Non-recoverable VAT account	Date from	Date To
1G	1320	23	True	100		01-01-1992	12-31-2099

Based on the information mentioned above, Currency will be autocompleted as the following scenarios show.

Scenario 1. Autocomplete Currency in the two details of an AP/AR invoice

GIVEN that a Financial Transaction needs to be posted with the supplier 1001
AND a Financial Transaction API with a POST endpoint that can autocomplete the currency where possible
AND a transaction document is sent, with the following information:

Line Type	Account	Amount	Currency amount	ID	Value	ID	Value
GL	6210	1000	1000	C1	100	NB	NO
AP	2011	-1000	-1000

WHEN posted to the transaction resource in the API
THEN the transaction is posted and returns a 202 response (Accepted)
AND the information is autocompleted as follows:

Account	Amount	Transaction type	Currency
6210	1000	GL	NOK
2011	-1000	AP	NOK

Scenario 2. Autocomplete Currency in the two details of an AP/AR invoice triggering compute tax logic

GIVEN that a Financial Transaction needs to be posted with the supplier 1001
AND a Financial Transaction API with a POST endpoint that can autocomplete the currency where possible
AND a transaction document is sent, with the following information:

Line Type	Account	Amount	Currency amount	ID	Value	ID	Value
GL	6210	1460	1230	C1	100	NB	NO
AP	2011	-1460	-1230

WHEN posted to the transaction resource in the API
THEN the transaction is posted and returns a 202 response (Accepted)
AND the information is autocompleted as follows:

Account	Amount	Transaction type	Currency
6210	1460	GL	NOK
2011	-1230	AP	NOK
1320	-230	TX	NOK

In this section you can find how to autocomplete the dueDate and discountDate fields.

For AP/AR lines

This autocompletion will only happen for transaction types whose treatment code is 1, 2 or 5.

As dueDate and discountDate are optional fields of Invoice DTO, the user may send them or not:

1. If the dueDate and discountDate values are sent by the user, the sent values are kept.

2. If the dueDate and/or discountDate are not sent but creditTerms is set (the user sent it or API autocompleted it), dueDate and/or discountDate is autocompleted as explained below.

The calculation of dueDate and discountDate is done according to the creditTerms configuration. The logic already implemented in UBW is directly used by API. Check documentation of UBW for more details.

This calculation logic uses a referenceDate to determine the final dueDate and discountDate values.

API determines the referenceDate value as a replication of UBW logic:

• In case of AR line, referenceDate is always transactionDate.

• In case of AP line, referenceDate is set according to the DUE_DATE_AP system parameter as follows:

  a. If parameter is Active and has value “2”, referenceDate is set to valueDate (from AP line)
  b. If parameter is Active and has value “3”, referenceDate is set to registeredDate.
  c. For any other parameter configuration, referenceDate is set to transactionDate.

For secondary open item lines

When dueDate is not provided, it is auto-completed with the due date assigned to the related AP row.

In this section, you can find how to autocomplete Tax system, Tax code and Factor VAT.

User input of Tax code in the account rule can be Mandatory or Fixed.

The field is optional in the DTO, but if the user doesn’t provide a value and the system is unable to auto-complete it, an error message is displayed.

User input of Tax system in the account rule can be Optional, Mandatory, or Fixed.

The field is optional in the DTO. An empty value is valid when User input is Optional in the account rule.

The Tax code and Tax system fields are auto-completed in the detail line as follows:

• For GL rows, the logic is the same as the one for auto-completing analyticalInformation through the account rule.
• For AP/AR rows:
  • If User input of the account rule is Fixed, the logic is the same as the one implemented for analyticalInformation.
  • If User input of the account rule is Optional/Mandatory:
    • The system takes values from the Customer/Supplier information. If the value of Tax system is Fixed and empty, it is also taken into account.
    • If no values can be found in the Customer/Supplier information, they are taken from the account rule.

User input of Factor VAT can be Optional, Mandatory, or Fixed.

The field is optional in the DTO. An empty value is valid when User input is Optional in the account rule.

This field is auto-completed in the detail line as follows:

• For GL rows, the logic is the same as the one for auto-completing analyticalInformation through the account rule.
• For AP/AR rows:
  • If User input of the account rule is Fixed, the logic is also the same as the one implemented for analyticalInformation.
  • If User input of the account rule is Optional/Mandatory, values are taken from the account rule.

For TX lines, Tax System, Tax code and Factor VAT are auto-completed by copying them from the detail line. When the TX line generates a GL line, Tax code, Tax system and Factor VAT are set as empty.

We take into account the following information in the calculations:

• Supplier 1001 - INVOICE

Currency	Tax code	Tax system
Norwegian Kroner - NOK	Gross 23% - 1G

• Attribute values - Company

Attribute value	Description	Owner	Value	Period from	Period to	Status
EN	ERP DEMO (EN)		0	0	209999	Active
NO	Agresso Demo AS (Norway)		0	0	209999	Active

• Value matrix - COMPLETEFACTORVAT

Source Attribute 1	Source Attribute 2	Destination Attribute
COMPANY	COST	FACTOR_VAT

MATRIX ROWS

InterCompany Company	Cost centre	Factor VAT
EN	100	1C
NO	100	1D

• Chart of accounts

Account	Description	Rule	Group	Period from	Period to	Type	Status
6210	Rent	RENTALCOST	620	200001	209912	General Ledger	Active
6250	Electricity	ELECTRICITYCOST	620	200001	209912	General Ledger	Active
2011	Accounts Payable International Suppliers	Balance/Finance	200	199401	209912	Accounts Payable	Active
1320	Ingoing VAT	Balance/Finance	130	199401	209912	General Ledger	Active

• Account rule. RENTALCOST

	Attribute	User input	Auto-completion	Default value	Validation relation
Account	ACCOUNT
Category 1	COSTC	Mandatory
Category 2	PROJECT	Optional
Category 3		Fixed
Category 4		Fixed
Category 5		Fixed
Category 6		Fixed
Category 7	COMPANY	Mandatory
Currency	CURRENCY	Mandatory		NOK
Tax code	TAXCODE	Fixed		0
Tax system	TAXCAT	Optional		EX
Factor_VAT	FACTOR_VAT	Optional

• Account rule. ELECTRICITYCOST

	Attribute	User input	Auto-completion	Default value	Validation relation
Account	ACCOUNT
Category 1	COSTC	Mandatory
Category 2	PROJECT	Optional
Category 3		Fixed
Category 4		Fixed
Category 5		Fixed
Category 6		Fixed
Category 7	COMPANY	Mandatory
Currency	CURRENCY	Mandatory		NOK
Tax code	TAXCODE	Fixed		0
Tax system	TAXCAT	Optional
Factor_VAT	FACTOR_VAT	Mandatory	COMPLETEFACTORVAT

• Account rule. Balance/Finance

	Attribute	User input	Auto-completion	Default value	Validation relation
Account	ACCOUNT
Category 1	COSTC	Optional
Category 2		Fixed
Category 3		Fixed
Category 4		Fixed
Category 5		Fixed
Category 6		Fixed
Category 7		Fixed
Currency	CURRENCY	Mandatory		NOK
Tax code	TAXCODE	Mandatory		0
Tax system	TAXCAT	Optional
FACTOR_VAT	FACTOR_VAT	Optional

• Tax Code 1G defined in the database:

Tax Code	Account	Vat Percentage	Net flag	Reduction	Non-recoverable VAT account	Date from	Date To
1G	1320	23	True	100		01-01-1992	12-31-2099

Based on the information mentioned above, taxCode, Tax system, and Factor VAT will be auto-completed as the following scenarios show.

Scenario 1. Autocomplete Tax system, Tax code, and Factor VAT in the two details of an AP/AR invoice

GIVEN that a Financial Transaction needs to be posted with the supplier 1001
AND a Financial Transaction API with a POST endpoint that can autocomplete the currency where possible
AND a transaction document is sent, with the following information:

Line Type	Account	Amount	Currency amount	ID	Value	ID	Value
GL	6210	1000	1000	C1	100	NB	NO
AP	2011	-1000	-1000

WHEN posted to the transaction resource in the API
THEN the transaction is posted and returns a 202 response (Accepted)
AND the information is autocompleted as follows:

Account	Amount	Transaction type	Tax code	Tax system	Reduction code
6210	1000	GL	0	EX
2011	-1000	AP	0

Scenario 2. Keep values sent by the user and auto-complete where there is no value set for taxCode, Tax system, and Factor VAT

GIVEN that a Financial Transaction needs to be posted with the supplier 1001 AND a Financial Transaction API with a POST endpoint that can autocomplete the currency where possible
AND a transaction document is sent, with the following information:

Line Type	Account	Amount	Currency amount	ID	Value	ID	Value
GL	6210	1000	1000	C1	100	NB	NO
AP	2011	-1000	-1000

WHEN posted to the transaction resource in the API
THEN the transaction is posted and returns a 202 response (Accepted)
AND the information is autocompleted as follows:

Account	Amount	Transaction type	Tax code	Tax system	Reduction code
6210	1000	GL	0	0
2011	-1000	AP	0	0

Scenario 3. Autocomplete Tax code, Tax system, and Factor VAT in the two details of an AP/AR invoice triggering compute tax logic

GIVEN that a Financial Transaction needs to be posted with the supplier 1001
AND a Financial Transaction API with a POST endpoint that can autocomplete the currency where possible
AND a transaction document is sent, with the following information:

Line Type	Account	Amount	Currency amount	ID	Value	ID	Value
GL	6210	1460	1230	C1	100	NB	NO
AP	2011	-1460	-1230

WHEN posted to the transaction resource in the API
THEN the transaction is posted and returns a 202 response (Accepted)
AND the information is autocompleted as follows:

Account	Amount	Transaction type	Tax code	Tax system	Reduction code
6210	1460	GL	0
2011	1230	AP	1G
1320	-230	TX	1G

Scenario 4. Autocomplete Currency, Tax system, Tax code, and Factor VAT in the two details of an AP/AR invoice

GIVEN that a Financial Transaction needs to be posted with the supplier 1001
AND a Financial Transaction API with a POST endpoint that can autocomplete the currency where possible
AND a transaction document is sent, with the following information:

Line Type	Account	Amount	Currency amount	ID	Value	ID	Value
GL	6250	1000	1000	C1	100	NB	NO
AP	2011	-1000	-1000

WHEN posted to the transaction resource in the API
THEN the transaction is posted and returns a 202 response (Accepted)
AND the information is autocompleted as follows:

Account	Amount	Transaction type	Tax code	Tax system	Reduction code
6250	1000	GL	0	0	1D
2011	-1000	AP	0

In this section, you can find how to autocomplete the discountPercentage and discountCurrencyAmount fields.

This autocompletion will only happen for transaction types whose treatment code is 1, 2 or 5.

As discountPercentage and discountCurrencyAmount are optional fields in the Invoice DTO, the user may send them or not.

The CALC_PAY_DISC_AP/AR system parameter is considered in the discountCurrencyAmount auto-completion with the following settings:

• When parameter is Not Active, the discountPercentage is applied to the currencyAmount of the AP/AR row.
• When parameter is Active with value “0” or “1”, the calculation depends on the “Payment discount on tax” flag in the supplier/customer information:
  • If it is selected, the discountPercentage is applied to the SUM of currencyAmount of all GL and taxes rows.
  • If it is not selected, the discountPercentage is applied to the SUM of currencyAmount of all GL rows.

See validations on discountCurrencyAmount field: Scenario_136, Scenario_137 and Scenario_138.

There may be accounts set as excluded from the payment discount calculation. The following scenarios are possible:

1. If the discountPercentage and discountCurrencyAmount values are sent by the user:

   • The discountPercentage is ALWAYS kept.
   • The discountCurrencyAmount is ALWAYS kept.

2. If only the discountPercentage value is sent by the user:

   • The discountPercentage is ALWAYS kept.
   • The discountCurrencyAmount is calculated based on the setup of the CALC_PAY_DISC_AP/AR system parameter and the “Payment discount on tax” flag in the supplier/customer information.

3. If only the discountCurrencyAmount value is sent by the user:

   • The discountPercentage is autocompleted based on the creditTerm definition.
   • The discountCurrencyAmount is ALWAYS kept.

   In this case, the discountPercentage and discountCurrencyAmount values may not be aligned.

4. If neither the discountPercentage nor the discountCurrencyAmount values are sent by the user:

   • The discountPercentage is autocompleted based on the creditTerm definition. If no creditTerm is available, then, first, the creditTerm in the supplier/customer information will be autocompleted.
   • The discountCurrencyAmount is calculated based on the setup of the CALC_PAY_DISC_AP/AR system parameter and the “Payment discount on tax” flag in the supplier/customer information.

Based on the information mentioned above, the DiscountPercentage and DiscountCurrencyAmount will be auto-completed as the following scenarios show.

• Supplier 10000 - INVOICE

Payment terms
11 (10 days - 1.5%)

• Credit term ID: 11

WHEN posted to the transaction resource in the API
THEN the transaction is posted and returns a 202 response (Accepted)
AND the information of the AP line is autocompleted as follows:

Due date	Discount date	Discount percentage	Discount currency amount	Credit terms
11/09/2020	11/09/2020	5	49.2	11

The Debit/Credit value is derived from the currencyAmount sign. The mapping logic is the following:

currencyAmount	debitCreditSign
> 0	1
< 0	-1
= 0	0

In this section, you can find how the Tax Transaction lines are generated depending on the data provided in the Tax Information section.

taxCode “0” represents no taxes, then this calculation will only happen for any taxCode other than “0”.

Take the following into consideration:

• All tax-related information is extracted from the combination of taxCode and Tax system, unless this information is explicitly given in the Tax Input section.
• The Tax point date is the date used to obtain valid values from taxCode or Factor VAT.
• The taxCode, Tax system, and Factor VAT fields from the detail line are copied to the line generated from the TX line. When the TX line generates a General Ledger line, taxCode is set to ‘0’, and Tax system and Factor VAT are set as empty.

We consider the following input:

• Tax Code 1E defined in the database:

• Tax Code 1H defined in the database:

• Tax Code 1N defined in the database:

• Tax Code 1C is defined as 1N (see above) but with Cash Principle flag selected

• Tax Code 1S defined in the database:

• Tax Code 1W defined in the database:

• Tax Code 1X defined in the database:

• Tax Code 1E defined in the database:

• Tax System EX and ER defined in the database:

• Tax System PD80 defined in the database:

• Tax system REV defined in the database:

• Factor VAT 1D defined in the database:

• Undeclared VAT account is set in the company as 1345
• Undeclared VAT for AP transactions account is set in the company as 1310
• Undeclared VAT for AR transactions account is set in the company as 1330

Based on the information mentioned above, the Tax Transaction Line will be calculated as the following scenarios show.

In this section, you can find how the Financial Transactions API calculates Amount, Amounts3 and Amounts4 when the consumer of the API posts or registers transactions in multiple currencies without providing values for all of them.

The same calculation is used for Amount, Amounts3 and Amounts4 in the SecondaryOpenItems DTO.

This calculation is also used when the DTO is in taxTransactionLine, Base (Amount, Amount3, Amount4, Currency amount), Original (Amount, Amount3, Amount4, Currency amount), Original base (Amount, Amount3, Amount4, Currency amount) and Reverse charge (Amount, Amount3, Amount4, Currency amount).

The amount fields are nullable, meaning that:

• They can be included in JSON with a specific value.
• They can be included with value: NULL.
• They don’t have to be included in JSON.

The calculation of Amount, Amount3 and Amount4 is based on the values in Currency amount and Currency, when:

• The values are not set in the JSON file
  or
• They are set with value: NULL
  and
• They are defined in the Company information tab in U4ERP.

The calculation of the amounts is triggered after the tax has been calculated.

It has the following rules:

• It is always possible to find an exchange rate to calculate the different amounts that are defined for the company.
• In case taxTransactionLines are included in JSON, the amounts (Base amounts, Original base amounts, Amount…) in this DTO will always have the corresponding amounts in the parent details (that is: if we have Amount3, Base amount3, Original base amount3, etc. in the taxTransactionLine DTO, the parent details will also have the same values available).

The calculation takes into account the following information:

• Company information - Currency - EN

• Currency codes

• Chart of accounts

• Account rule Costs (20)

• Account rule Balance/Finance (10)

• Exchange rate entry Rate in GBP company EN

• Exchange rate entry Euro rates company EN

• Exchange rate entry Rate in USD company EN

• Tax code 1N defined in the database

• Factor VAT 1D defined in the database

The amounts are calculated according to the following scenarios.

In this section you can find how to calculate the tax lines based on the input given in the “SummaryTaxInformation”.
The following rules apply:

• ‘Amounts’ or ‘VatPercentages’ set in the SummaryTaxInformation are to be used to create the Tax transaction lines (even though they are not aligned with values coming from Tax codes in U4ERP).

• To calculate the amount of the Tax transaction lines, the amounts given in the SummaryTaxInformation are proportionally distributed among the amounts in each detail line per combination taxCode/taxSystem. This is done by multiplying the amount in each detail line by the amount in SummaryTaxInformation corresponding to that combination. Then this result is divided by the sum of the detail line amounts with that same taxCode/taxSystem combination. Any rounding differences are assigned to the detail line with the greatest Currency Amount.

  In the example in Scenario 2, 35.2 is multiplied by 96, then this result is divided by 184 (the sum of the detail lines: 96 + 88). i Based on the information mentioned above, the Tax Transaction Line will be calculated as the following scenarios show.