Integration
Tripletex integration
Invoices, supplier invoices, customers and projects moving between Tripletex and the rest of your systems, without exporting and importing by hand.
Tripletex has a large API, and most of what you see on screen can also be read or written from another system. Typical jobs are sending invoices from an order system or web shop, pulling supplier invoices for checks and reporting, or keeping customers and projects the same in both places.
Access is set up with an API token that an administrator on your side creates in Tripletex. That keeps you in control of which company the integration can see, and you can revoke it whenever you like.
What can be connected to Tripletex
- Outgoing invoices and credit notes from an order or sales system
- Supplier invoices for checks, approval or reporting
- Customers, suppliers and contact people
- Projects, activities and hours
- General ledger and balances, when the numbers go out to a warehouse or dashboard
Access and setup
An administrator on your side creates an API token in Tripletex under the company settings, which requires the integrations module to be enabled. The token gives access to that one company, and it can be deleted at any time if you want to shut the integration off.
I build it to cope with Tripletex being down for a while, and so a run can be repeated without anything being posted twice.
Common questions
- Do we need a separate Tripletex module for integrations?
- The integrations module has to be active for you to create an API token. Check your Tripletex subscription, or ask me and I'll help you sort it out.
- Can you connect Tripletex to our web shop?
- Yes. Orders from the shop can become invoices in Tripletex, and payments from Stripe or Vipps, for example, can be reconciled against them.
- How do you avoid duplicate entries?
- Everything that's sent carries a fixed reference from the system it came from. If it's sent again, the integration sees it already exists and skips it.