This article is part of this article series:
API Best Practices - Introduction
Introduction
The process of importing sales transactions from a webshop has seven steps. You can read the details of these steps in this article:
Importing sales transactions including customers
- Download all customers that currently exist in Twinfield
- Update the dimension type mask
- Add or update customers into Twinfield
- Find the available transaction types
- Find the available profit-and-loss ledgers
- Find the available vat codes
- Import new sales transactions
In the article above, we give a generic explanation of importing sales transactions including customers. Below you will find an explanation of the additional steps that need to be made by webshops specifically. The steps that are not described below are the same as in the generic article.
Important: There are two types of customers. Those who prepay their invoices by use of a payment provider and those who postpay their invoices by bank transfer.
Step 3: Add or update customers into Twinfield
This step is the first step where it is important to make a distinction between customers who prepay their invoice and customers who will pay for their invoice afterwards by bank transfer, also known as postpaid transactions.
Customers that prepay their invoice by use of a payment provider do not have to be sent or updated in Twinfield. This is because in this situation the amount of the invoice will not actually be received from the customer directly, but this amount will be received through the payment provider.
Only customers that have selected to pay their invoice afterwards by bank transfer should be added or updated to Twinfield. You can refer to the generic article above for more information about adding or updating customers to Twinfield.
Step 4: Find the available transaction types
In this step a distinction between customers who prepay their invoice and customers who will pay afterwards also needs to be made.
- Customers who prepay their invoice should be registered as a journal transaction.
- Customers who postpay their invoice should be registered as a sales transaction.
Important: Instruct the end-user to create two new transaction types for each webshop they use. This should be done by the end-user in the user interface of Twinfield. The first should be a journal transaction type for prepaid invoices. The second should be a sales transaction type for postpaid invoices.
To request the available transaction types for prepaid invoices you can use the Postman collection in the attachment of this article, specifically the request 'Find the available transaction types for prepaid transactions'.
To request the available transaction types for invoices that are paid afterwards you can use the request 'Find the available transaction types for postpaid transactions'.
After you have found all the available transaction types, let the end-user configure which transaction type they want to use.
Step 7: Import new sales transactions
This step is the last step where a distinction needs to be made between prepaid and postpaid transactions. As mentioned in the previous steps, customers who prepay their invoices don't have to be updated or added. The transaction type used for their invoice will also be different.
Importing prepaid transactions
For prepaid transactions, a single entry per day per payment provider can be made which totalizes all the revenue made with regard to a specific payment provider.
To import sales transactions into Twinfield for prepaid transactions you can use the Postman collection in the attachment of this article. You can use the request named 'Import new sales transactions for prepaid transactions'.
Importing postpaid transactions
For postpaid transactions specific entries per invoice and customer are needed to allow for the ability to match invoices with bank transfers at a later stage.
To import sales transactions into Twinfield for postpaid transactions you can use the Postman collection in the attachment of this article. You can use the request named 'Import new sales transactions for postpaid transactions'.
