Record directly as revenue

Modified on Thu, 28 Mar 2024 at 09:35 AM

Disclaimer

All screenshots in the article were taken in the Dutch version of Yuki.


All bank transactions uploaded to Yuki end up in the 'Bank transactions to be processed' workflow. There can be three situations for the processing of bank transactions

  • IDR has recognised the bank transaction and suggests a match with a payment
  • IDR has recognised the bank transaction but cannot suggests a direct match with a payment
  • IDR did not recognise the bank transaction, so the transaction must be processed manually.


This article describes the third situation.


The Record directly as revenue action is used to record revenue with VAT for which no sales invoice has been submitted.


Only a user with the 'Back office' role in a domain can process bank transactions in the 'Bank transactions to be processed' workflow.


To start processing bank transactions, open the domain. The Back office workflow screen always opens by default. In this screen, click on the Bank tile to open the Bank transactions to be processed workflow.


In the now-opened screen, click on the > in front of a bank transaction line, click on the Actions button and then click on the Record directly as revenue menu option. 


The following screen may appear:



Now enter for example 'Revenue item group 1' in the 'Ledger account' field and 'A.H.J. Takkenberg ' in the 'Relation' field.


Under 'Tax code' you have a number of choices:

  • Non-deductible
  • VAT 0%
  • VAT reverse-charge
  • Export outside the EU
  • Export services inside the EU (2010) 
  • Export goods inside the EU (2010)
  • VAT 6%
  • VAT 21%.


The tax codes shown depend on the name and address of the debtor.

Click on the Save button. You will now see the following screen:



Click on the Completed button which will show the next transaction in the workflow.


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