Onboard ERP Integration
1. Introduction
Section titled “1. Introduction”ERP integration for your client enables the structured and efficient synchronization of invoice-related data between ERP systems and Quiddly. Each connection includes a dedicated ERP connection and standardized core workflows that support effective invoice operations.
The following standard workflows are included:
- Retrieving invoices
- Sending vouchers
- Sending payments
Onboarding is automatically adapted to the ERP system used by each client, ensuring a consistent and efficient setup regardless of ERP choice. For the integration to function, a target system for synchronization is required.
2. Onboard Client ERP
Section titled “2. Onboard Client ERP”This step describes the process of connecting to the client’s ERP for the possibility of automatically pulling new invoices and pushing bookkeeping.
2.1 Initiate Connection by Operator
Section titled “2.1 Initiate Connection by Operator”- “Select ERP that should be connected”: Select “Strawbay”. This is Quiddly’s supplier for ERP integrations.
- Press [Connect]
- Press [Create Integration]
- Press [Close]
- You have now started the connection process to the client’s ERP. Inform the client to login into the “Client Portal” and finish the connection.
2.2 Establish Connection by Client
Section titled “2.2 Establish Connection by Client”- Press [Connect]
- The client will now be redirected to the onboarding interface provided by Strawbay.
- Navigate through the onboarding process to authorize the connection.
- Once finished, the client will be redirected back to the Client Portal, which will show a success message.
- The client is now connected to the ERP and can start fetching invoices.
- Navigate to [Invoices]
- Press [Sync New] to fetch new invoices, / Press [Sync Expired] to fetch expired invoices.
- Finished
Prerequisites Fortnox
Section titled “Prerequisites Fortnox”To create a connection, the following criteria must be met:
- The ERP account must have the API module/license enabled.
- The user must be a System Administrator in Fortnox to authorize the connection.
- New Invoices must be in the following state for them to be retrieved: Not Booked, Not Sent, Not Completed, and Unpaid.
- Expired Invoices must be in the following state for them to be retrieved: Booked, Expired, and Unpaid.
2.3 Verify Connection by Operator
Section titled “2.3 Verify Connection by Operator”- Verify that Connected ERP is Strawbay.
- Verify that the Integration Id is provided.
- Verify that the Integration Status is Connected.
- Ongoing and historic syncs can be viewed in the “Invoice Sync” list. It shows Id, External Id, Status (Pending while running, then Finished or Failed), who started the sync and when it was created and finished.
- Finished.
2.4 Remove Connection by Operator
Section titled “2.4 Remove Connection by Operator”- Press [Remove connection to ERP]
- Confirm in the dialog “Remove connection to ERP”.
- The connection will now be removed: invoice sync is switched off for the client and the connected ERP and the Integration Id are cleared. To use an ERP again, start from section 2.1.
- Finished.
2.5 Fetch or Abort an Invoice Sync by Operator
Section titled “2.5 Fetch or Abort an Invoice Sync by Operator”Two client actions let an operator work with the invoice fetch on the client’s behalf. Using them requires a right, see Rights, roles and users and the rights catalogue.
| Action | What it does |
|---|---|
| Fetch invoices from ERP | Starts a fetch of new invoices, the same as [Sync New] in the Client Portal. Confirm in the dialog. |
| Abort invoice fetch from ERP | Ends a fetch that is still Pending: the sync is marked Failed in the “Invoice Sync” list and the client can start a new one. |
2.6 What the Client Receives After a Sync
Section titled “2.6 What the Client Receives After a Sync”When an invoice fetch has finished, the client’s e-mail recipients receive an e-mail with the reference of the sync, how many invoices were created and, for each invoice that could not be created, the invoice’s ID in the ERP and the reason. The client corrects those invoices in the ERP and syncs again. The e-mail is the client’s report of the result; the “Invoice Sync” list in the Operations Portal shows only the status and times of each sync.
The e-mail is one of the system e-mails, see When each email is sent. The default text is in Swedish.
Appendix: Available ERP Systems
Section titled “Appendix: Available ERP Systems”| ERP Name | Supported flows | Invoice Initiation | Configuration Effort |
|---|---|---|---|
| Fortnox | Invoices, Payments, Vouchers | Sync Button in Client Portal | No configuration needed |
| Spiris by Visma | Invoices, Payments, Vouchers | Sync Button in Client Portal | No configuration needed |
| Procountor | Invoices, Payments, Vouchers | Sync Button in Client Portal | No configuration needed |
| Björn Lundén | Invoices, Payments, Vouchers | Sync Button in Client Portal | No configuration needed |
| Xledger | Invoices, Payments, Vouchers | Invoice created in ERP | No configuration needed |
| Power Office Go | Invoices, Payments, Vouchers | Invoice created in ERP | No configuration needed |
| Tripletex | Invoices, Payments, Vouchers | Invoice created in ERP | No configuration needed |
| Microsoft Business Central | Invoices, Payments, Vouchers | Invoice created in ERP | Configuration in ERP is needed |
| Microsoft Finance & Operations | Invoices, Payments, Vouchers | Invoice created in ERP | Implementation project needed |
| Visma.NET | Invoices, Payments, Vouchers | ||
| Younium | Invoices, Payments, Vouchers |