Accounting - Functional description of fields general journal entries XML

Modified on Fri, 24 Dec 2021 at 12:18 PM

This article describes the functional development in the software of a number of fields in the general journal entries XML. These must be supplied with the web service Accounting - ProcessJournal(sessionID, administrationID, xmlDoc) method.


ATTENTION!

It is recommended to examine the XML scheme below, this information is most complete and described in English.  


Web address of the XML scheme of the general journal entries


http://www.yukiworks.nl/schemas/Journal.xsd


Example


<Journal xmlns="urn:xmlns:http://www.theyukicompany.com:journal" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

        <AdministrationID>REPLACE WITH ADMINISTRATIONID</AdministrationID>

        <AdministrationCoCNumber>12345672</AdministrationCoCNumber>

        <DocumentSubject>Trx import april</DocumentSubject>

        <JournalType>GeneralJournal</JournalType>

        <JournalEntry>

                <ContactName>Apple Sales International</ContactName>

                <ContactCode>9921</ContactCode>

                <EntryDate>2012-12-31</EntryDate>

                <GLAccount>20000</GLAccount>

                <Amount>22.22</Amount>

                <Description>Inkopen hardware</Description>

        </JournalEntry>

        <JournalEntry>

                <ContactName>Apple Sales International</ContactName>

                <ContactCode>9921</ContactCode>

                <EntryDate>2012-12-31</EntryDate>

                <GLAccount>10005</GLAccount>

                <Amount>-22.22</Amount>

                <Description>Retour hardware</Description>

        </JournalEntry>
</Journal>


Description of fields

Below you will find a description of the fields. The XML scheme itself also contains a description of the fields and which values and data types are expected in them. 


Journal: AdministrationID / AdministrationCoCNumber

In domains with several administrations it is required to complete one of those two fields. In this way you indicate in which administration you want to create the general journal entries.


ATTENTION!

Give 'AdministrationID' or 'AdministrationCoCNumber'. If you give both you will get the Error: The element 'Journal' has invalid child element 'AdministrationID'.

Journal: DocumentSubject

The subject of the file created.


Journal: JournalType

This field indicates the type of the general journal entries. Possible values are 'GeneralJournal' for an normal general journal entry, 'EndOfYearCorrection' for an year-end correction and 'FiscalCorrection' for a fiscal correction. The entry dates of the year-end corrections and fiscal corrections must be on the last day of the financial year.

Journal: ProjectID 

ID of the project to which you want to link a document. If this parameter is given then the 'ProjectCode' parameter is  redundant. The Yuki Projects module must have been activated in the contract.

Journal: ProjectCode

The code of the project to which you to link the document. This parameter is only used when the 'ProjectID' parameter is not given. De Yuki Projects module has to have been activated in the contract.


JournalEntry: ContactCode / ContactName

If the relatiecode is given then there will be searched for an existing contact with this contact code. If you don't give a relatiecode then there will be searched for an existing contact with the same name. If no contact can be found then a new one will be created.


JournalEntry: EntryDate

The entry date.

JournalEntry: GLAccount

The code of the GL account. A list of all available GL accounts and the corresponding codes can be found in the chart of accounts in your domain in Yuki.


JournalEntry: Amount

The amount of the entry in EURO. Give a negative amount for credit entries and a positive amount for debit entries.

JournalEntry: Description

The description of the entry. Descriptions longer than 256 characters will be shortened.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article