The Netherlands
This section describes the Netherlands reports appendix.
Dutch Audit File Report - XML Schema / Field Mapping
The Dutch Audit File must comply with a specific XML schema required by Dutch tax authorities. In the schema depicted below, we include all the tag names for data values as well as the expected content of data value for that tag. Some tags are included in the XML schema but have no data in Maconomy. For some tags, you can exclude the tags if they do not have any representation in the software system. In order to keep the full overview of the XML schema, we strike through such tags, thereby emphasizing that even though they are part of the XML schema, they are not part of the XML file produced.
Where possible, we state the database field from where to find the content for the tag in Maconomy. If we indicate universe objects, this means that the value could come from another table, such as a dimension table, or may be the result of a calculation.
Some tags are the same for customer and vendor but just distinguished by some tag value. In these cases, we do not repeat all the tags for both customer and vendor but state the two table field options for the same tag.
| Tags | Technical Details |
|---|---|
| <auditfile> | |
| <header> | |
| <fiscalYear> | The selected fiscal year to run the report for (part of selection criteria). |
| <startDate> | Start date of the selected fiscal year.
FiscalYear.FiscalYearStart |
| <endDate> | End date of the selected fiscal year.
FiscalYear.FiscalYearEnd |
| <curCode> | Currency of the company for which the report is run.
EXCompanyInformation.Currency |
| <dateCreated> | Date the report was created. This is always current date.
Current Date |
| <softwareDesc> | Name of software product.
"Deltek Maconomy" |
| <softwareVersion> | Version of software, "2.6" - for instance. |
| <RGSVersion> | Optional element currently showing the value.
softwareVersion |
| </header> | |
| <company> | |
| <Commercenr> | Commerce number of customer/vendor.
CompanyCustomer.Telex CompanyVendor.Telex |
| <companyName> | The name of the company. |
| <taxRegistrationCountry> | Two-letter country code after the ISO standard.
Country.ISOCode |
| <taxRegIdent> | Tax number of customer/vendor.
CompanyCustomer.VATNumber CompanyVendor.VATNumber |
| <streetAddress> | |
| <streetname> | Streetname in address of customer/vendor.
CompanyVendor.Name2 CopmanyCustomer.Name2 |
| <number> | |
| <numberExtension> | |
| <city> | City of customer/vendor address.
CompanyVendor.PostalDistrict CompanyCustomer.PostalDistrict |
| <postalCode> | Postal code of customer/vendor address.
CompanyVendor.ZIPCode CompanyCustomer.ZIPCode |
| <country> | Country of the company.
CompanyVendor.Country CompanyCustomer.Country |
| </streetAddress> | |
| <customersSuppliers> | |
| <customerSupplier> | |
| <custSupID> | |
| <custSupName> | |
| <eMail> | |
| <commerceNr> | |
| <taxRegistrationCountry> | |
| <taxRegIdent> | |
| <custSupTp> | |
| <opBalDesc> | |
| <opBalTp> | |
| <clBalDesc> | |
| <clBalTp> | |
| <streetAddress> | |
| <streetname> | |
| <number> | |
| <numberExtension> | |
| <city> | |
| <postalCode> | |
| <country> | |
| </streetAddress> | |
| </customerSupplier> | |
| </customersSuppliers> | |
| <generalLedger> | |
| <ledgerAccount> | |
| <accID> | GL account number in chart of account.
Account.AccountNumber LocalAccount.LocalAccountNumber |
| <accDesc> | Name of the GL account in chart of accounts.
Acccount.AccountText LocalAccount.Description |
| <accTp> | States whether the account is P&L or Balance account.
Either states the text "P" or "B". Deduced from: EXAccount/EXLocalAccount.ProfitAndLossStatusCode |
| <RGScode> | |
| </ledgerAccount> | |
| <vatCodes> | |
| <vatCode> | The VAT code tags should be ordered by the tax code name. |
| <vatID> | Name of the tax code.
VATCode/FinanceVATCode.Name |
| <vatDesc> | Description of the tax code.
VATCode/FinanceVATCode.Rate |
| <vatToPayAccID> | Account for tax payable.
VATCode.FinanceAccountIncoming for VAT Codes. FinanceVATCode.FianceAccountVAT if VATDirection in (0, 2), else blank for Finance Vat Codes. |
| <vatToClaimAccID> | Account for tax receivable.
VATCode.FinanceAccountOutgoing for VAT Codes. FinanceVATCode.FianceAccountVAT if VATDirection in (1, 3), else blank for Finance VAT Codes |
| </vatCode> | |
| </vatCodes> | |
| <periods> | |
| <period> | There must be one period tag for each fiscal period in the selection criteria fiscal year. |
| <periodNumber> | The period number of the fiscal period. In Maconomy we can choose to display either in calendar numbers or fiscal period number. It needs to be decided what to use here. Possibly, fiscal period numbers.
FiscalYearPeriod.Period |
| <startDatePeriod> | The start date of the fiscal period.
FiscalYearPeriod.PeriodStart |
| <endDatePeriod> | The end date of the fiscal period.
FiscalYearPeriod.PeriodEnd |
| </period> | |
| </periods> | |
| <openingBalance> | |
| <linesCount> | The number of obLine tags corresponding to number of individual accounts for which an opening balance is given.
Only balance accounts are considered. |
| <totalDebit> | Sum of opening debit amounts for the fiscal year.
The sum must equal the debit sum of lines in obLine tags as these are a break down into accounts. sum(FinancePeriod.OpeningDebit) |
| <totalCredit> | Sum of opening credit amounts for the fiscal year.
The sum must equal the credit sum of lines in obLine tags as these are a break down into accounts. sum(FinancePeriod.OpeningCredit) |
| <obLine> | |
| <nr> | |
| <accID> | |
| <amnt> | |
| <amntTp> | |
| </obLine> | |
| </openingBalance> | |
| <transactions> | |
| <linesCount> | Number of finance entries, or the number of trLine tags below. |
| <totalDebit> | Summation of debit amounts (company currency) within the fiscal year.
Sum(FinanceEntry.DebitBase) |
| <totalCredit> | Summation of credit amounts (company currency) within the fiscal year.
Sum(FinanceEntry.CreditBase) |
| <journal> | |
| <jrnID> | |
| <desc> | |
| <jrnTp> | |
| <offsetAccID> | |
| <transaction> | |
| <nr> | |
| <desc> | |
| <periodNumber> | |
| <trDt> | |
| <Source> | |
| <User> | |
| <trLine> | |
| <nr> | |
| <accID> | |
| <docRef> | |
| <effDate> | |
| <settDate> | |
| <desc> | |
| <amnt> | |
| <amntTp> | |
| <custSupID> | |
| <invRef> | |
| <receivingDocRef> | |
| <shipDocRef> | |
| <cost> | |
| <product> | |
| <project> | |
| <workCostArrRef> | |
| <bankAccNr/> | |
| <offsetBankAccNr/> | |
| </trLine> | |
| <trLine> | |
| <nr> | |
| <accID> | |
| <docRef> | |
| <effDate> | |
| <settDate> | |
| <desc> | |
| <amnt> | |
| <amntTp> | |
| <custSupID> | |
| <invRef> | |
| <receivingDocRef> | |
| <shipDocRef> | |
| <cost> | |
| <product> | |
| <project> | |
| <workCostArrRef> | |
| <bankAccNr> | |
| <offsetBankAccNr> | |
| <vat> | |
| <vatID> | |
| <vatPerc> | |
| <vatAmnt> | |
| <vatAmntTp> | |
| </vat> | |
| <currency> | |
| <curCode> | |
| <curAmnt> | |
| </currency> | |
| </trLine> | |
| </transaction> | |
| </journal> | |
| </transactions> | |
| </company> | |
| </auditfile> |
Troubleshooting
Background Task Timeout
Reports with large volumes of records take longer to process and the background task may timeout. To prevent timeout errors, you must change the character stream size to 2000 or higher (on the BO server console), and set the background task duration to more than 24 hours (on Maconomy).
Set Character Stream Size
To prevent timeouts while running the report, you must change the character stream size on the Business Objects (BO) Central Management Console (CMC) prior to running the report.
To change the character stream size:
- On the BO CMC, log in as an Administrator.
- Click Servers and select Server List.
- From the list of server names, click WebIntelligenceProcessingServer.
- Select
Properties then edit the
Maximum Character Stream Size (MB) field value, from 15 to at least 2000 or your preferred value up to 4095.
Note: The recommended value when running the report is 2000.
- Click Save then close the dialog box.
- Right-click WebIntelligenceProcessingServer then select Restart Server.
Set Background Task Maximum Duration
If the default maximum duration time (1440 minutes) is not enough to generate the report, you can change the maximum duration for the background task.
To change the maximum duration:
- Generate a report to start a background task.
Click OK in the prompt.
- Go to
Setup » Background Tasks » Status and locate your task. It should be at the top of the list.
- Select the task and click the Abort action button.
- Click OK in the prompt.
- Right-click the task (the status displays as Failed) and click
Copy as Template.
A new task should display at the top of the list (the status displays as Pending.)
- Go to the Editing tab then locate and double-click the pending task.
Note: You may need to filter the list and show Inactive Pending Tasks.
- Edit the Max. Duration field to a higher value, such as 2880 for 48 hours.
- Click the Save » Activate action.
- Click OK in the prompt.
- Go to the Status tab and click the
Refresh action button.
The task should run and generate a report.
Note: If the background task still fails, you need to adjust the maximum duration time to accommodate the amount of records.