Integration

Connect PrestaShop to Twinfield: every order as a sales transaction in the right journal

Twinfield does not book a sale as an invoice object, but as a transaction with three kinds of lines: a total line on the debtor, detail lines on revenue and VAT lines on the VAT account. PrestaShop supplies the raw parts for that: orders, order lines, addresses and tax rates. Schakel converts them into a correct sales transaction in the journal of your administration, with a key that may only read in PrestaShop.

InvoicesContactsVAT

All PrestaShop integrationsAll Twinfield integrations

Start free Free to start · 30 days unlimited
The link

What travels across the link

Everything this connector moves between PrestaShop and Twinfield, and how often.

  1. Total line on the debtor

    The customer becomes the debtor on the total line, with the amount incl. VAT. Twinfield otherwise takes the debtor’s default ledger account, unless you specify one of your own.

  2. Detail lines per product

    Each product becomes a detail line on the revenue account, excl. VAT, with a VAT code. On a detail line you can also pass a cost centre or project, so you can report per shop.

  3. VAT lines that add up

    Twinfield validates the VAT calculation and rejects the transaction if it does not. Schakel computes the VAT lines from the same detail lines, so total, revenue and VAT balance to the cent.

  4. Provisional or final

    A transaction can be created provisionally first and booked as final later. Only a provisional transaction can still be changed or deleted. That is how the connector starts, until you have checked the first one.

  5. How PrestaShop and Twinfield talk

    Twinfield signs in via login.twinfield.com and returns a cluster address per organisation where the SOAP services live; transactions go through the ProcessXml service, per office code. PrestaShop returns XML and rights per resource. The invoice number may be at most 40 characters, so a long order reference is shortened.

  6. Worked example (fictional)

    Example: an order of 100.00 excl. with 21% VAT becomes a transaction with a total line of 121.00 on the debtor, a detail line of 100.00 on revenue and a VAT line of 21.00 on the VAT account. The amounts are invented.

Field mapping

Where each PrestaShop field ends up in Twinfield

Twinfield thinks in lines with dimensions. This is how we translate an order into those lines.

Order

PrestaShop

reference of the order

Twinfield

invoicenumber of the transaction, shortened to 40 characters

Order date

PrestaShop

Date of the order

Twinfield

date of the transaction; the period follows from it

Customer

PrestaShop

customers and the invoice address

Twinfield

dim2 on the total line: the debtor

Total incl. VAT

PrestaShop

Total paid incl. tax

Twinfield

Total line (type total), debit

Product line

PrestaShop

order_details with price excl. VAT

Twinfield

Detail line (type detail) on the revenue account in dim1

VAT rate

PrestaShop

taxes via tax_rules

Twinfield

vatcode on the detail line and a VAT line (type vat)

Shop

PrestaShop

Shop of the order with multistore

Twinfield

Cost centre in dim2 of the detail line, if you set that

Credit slip

PrestaShop

order_slip

Twinfield

Sales transaction with reversed sides

What you get out of it

What PrestaShop to Twinfield saves you

  • Twinfield no longer rejects a transaction over a VAT difference.
  • You keep the dimensions and cost centres Twinfield is strong in.
  • A provisional state gives you time to check the first entries.
  • Your shop key cannot change anything in your shop.
In four steps

Setting it up

  1. 01

    Create a key in PrestaShop

    You switch the webservice on and create a key with read rights on orders, order lines, customers and addresses.

  2. 02

    Grant access to Twinfield

    You sign in to Twinfield and give Schakel permission. You choose the office, so the administration, the transactions should go into.

  3. 03

    Choose journal and accounts

    You give the sales journal, the revenue account, the VAT codes and optionally a cost centre. The transaction code of the sales journal (often VRK) differs per administration.

  4. 04

    Check and let it run

    The first transactions stay provisional. Once you see they are right, you switch off the provisional state and new orders follow the same way.

What you need

  • A PrestaShop shop with the webservice on and a key with read rights
  • A Twinfield administration with a sales journal, revenue accounts and VAT codes

Where it runs

Inside your Shopify admin, as an app. You sign in through Shopify, no separate account.

Free to start

Then from €10 a month billed yearly, or stay on free. See the tiers

Start free

Need this exact integration, or something it does not do yet? Tell us what you need and we reply within 24 hours.

Another pair

Connect a different pair

PrestaShop and Twinfield is one of many. Pick two systems and see what travels between them.

Systems · 183
From
To

Common questions

Is the PrestaShop to Twinfield connector available?

Request this connector and get access. You let us know you want to link PrestaShop to Twinfield, and we make sure you can get started. You hear from us within 24 hours.

What is a sales transaction in Twinfield?

It is the entry behind a sales invoice: a total line on the debtor, detail lines on revenue and VAT lines. Twinfield distinguishes it from the sales invoice itself, which you send to the customer. Schakel books the transaction; sending the invoice stays with your shop.

Why does Twinfield reject a transaction?

Usually because the VAT does not match the amounts, or because the journal code does not exist in that administration. That code, often VRK, may be called something else for you. The Twinfield error message is in the log.

Can I use a different cost centre per PrestaShop shop?

Yes. A detail line can carry a cost centre, so you link each shop to its own cost centre and report per shop in Twinfield.

How do I book the provisional transactions as final?

You switch off the provisional state in the connector settings. The waiting provisional transactions are booked as final in the next round. A final transaction can no longer be deleted afterwards.

Can I use several administrations in Twinfield?

Yes. Twinfield has several offices under one organisation. You choose per connector which office the transactions go into, for example one per shop or per client if you are an accountant.

Can you connect PrestaShop to Twinfield?

Yes. Schakel connects through the official APIs of PrestaShop and Twinfield, so you install nothing on your own server and nothing travels outside those two parties.

Which VAT rate do my sales get in Twinfield?

The rate is set per line: 21%, 9% or 0%. Sales to Belgium and other EU countries get the rate of the destination country, ready for your OSS return.

Missing something you need?

Tell us what PrestaShop and Twinfield should do for you. If it is not in here yet, that is usually because nobody has asked. We reply within 24 hours.