This web serivce offers three methods to import cash transactions in Yuki. The web service runs via SOAP.

Web address

You will find the web service, a test application, a description of the fields and the procedures at the web address below:

https://api.yukiworks.nl/ws/Pettycash.asmx

Pettycash methods

There are three methods to import cash transactions in Yuki:

• ImportSingleStatementLine
  Imports a single cash statement line  as a cash statement. If the imports is unsuccessful then an error message is returned.
• ImportSingleStatementProjectLine
  Imports a single cash statement line woth projectcode as a cash statement. If the imports is unsuccessful then an error message is returned.
• ImportStatement
  Imports the given cash statement in the Yuki CSV format. If the import is unsuccessful then an error message is returned.
  In Yuki you can find the cash statement as a CSV file in the Archive > Bank > Petty cash.
  
  The Yuki CSV file is attached at the bottom of this article.

ImportSingleStatementLine

Below is a description of the different fields.

accountGlCode

This is the cash GLaccount you want to book the transactions on. 

transactionCode

The accountant can create processing rules based on this code to book the transaction on the correct offset account, vat code and relation.

offsetAccount

The accountant can create processing rules based on the offset account to book the transaction on the correct offset account, vat code and relation.

transactionDate

Date of the cash transaction

transactionDescription

Give more information about the transaction. The accountant can create processing rules based on the description to book the transaction on the correct offset account, vat code and relation.

amount

Amount of the transaction. Costs are negative amounts, revenues positive amounts.

ImportSingleStatementProjectLine

Below is a description of the different fields.

accountGlCode

This is the cash GLaccount you want to book the transactions on. 

transactionCode

The accountant can create processing rules based on this code to book the transaction on the correct offset account, VAT code and relation.

offsetAccount

The accountant can create processing rules based on the offset account to book the transaction on the correct offset account, VAT code and relation.

transactionDate

Date of the cash transaction.

transactionDescription

Give more information about the transaction. The accountant can create processing rules based on the description to book the transaction on the correct offset account, VAT code and relation.

amount

Amount of the transaction. Costs are negative amounts, revenues positive amounts.

ProjectCode

In this field you can enter the code of the project to which you want link the document. Recording this parameter makes the parameter 'ProjectID' irrelevant. 

To be able to use this field, a user with the 'Management' role must have selected the Medium, Large or Unlimited bundle via the Yuki Store in the domain.

ProjectName

In this field you can enter the name of the project to which you want to link the document. This parameter is only relevant if the parameter 'ProjectID' is not given. 

To be able to use this field, a user with the 'Management' role must have selected the Medium, Large or Unlimited bundle via the Yuki Store in the domain.

ImportStatement

The following is a description of the required column headers of the Yuki CSV format. 

ATTENTION!

The column headers must be identical.

Ledger account Petty Cash

This is the ledger account number of the petty cash in Yuki that you would like to import. This is a 100XX GLaccount.

Petty cash description

This is the description that belongs to the chosen ledger account number of the petty cash. If the description does not equal the description of the ledger account, the import will not be accepted.

Transaction code

You can choose this code yourself. Based on this code, the accountant can generate match rules for the cash transactions to improve automation. The code can be 10 characters long. This is not a mandatory field.

Suspense account

This is not a mandatory field. For example, you can enter the ledger account number upon which you wish to book or the contact code. Based on this description, the accountant can generate match rules to improve automation.

Name suspense account

This is not a mandatory field. For example, you can enter the name of the supplier that you paid. Maximum 34 characters.

Date transaction

Date of the transaction in format dd-mm-yyyy.

Description

The description can’t consist of “;” . Maximum 1024 characters.

Amount

Positive for transactions that increase the cash balance, negative for transactions that decrease the cash balance. Thousand separators cannot be used.

Balance petty cash

Is the real value on the respective date in the petty cash account, once the transaction of that line is processed. This value is not mandatory under the following conditions:

• In case there is a balance specified, the transactions have to be in chronological order, by which the oldest transaction is at the top of the list and the most recent transaction at the bottom.
• In case there is no balance specified, the order of transactions does not matter.
• In case values of the balance is not consistently specified, meaning that in some lines it is specified and in other lines not, the blank values will be considered as an amount of 0,00.

Project code

This is not a mandatory field. Code of the project.  

To be able to use this field, a user with the 'Management' role must have selected the Medium, Large or Unlimited bundle via the Yuki Store in the domain.

Project name

This is not a mandatory field. Name of the project. 

To be able to use this field, a user with the 'Management' role must have selected the Medium, Large or Unlimited bundle via the Yuki Store in the domain. 

General methods

Authenticate(accessKey)

Returns a session ID based on a valid Web Service access code.

AuthenticateByUserName(userName, password)

Returns a session ID based on an existing Yuki username and password.

Domains(sessionID)

Returns all domains that can be approached via the access code used.

SetCurrentDomain(sessionID, domainID)

Set the current domain for the session.

GetCurrentDomain(sessionID)

Returns the ID of the current domain for the session.