This article explains two Fortnox invoice settings that control how prices and VAT are sent per order row, and documents an important limitation around post-purchase order modifications.
VAT included in order rows
This setting controls what the price you send to Fortnox represents.
Checked → you send the price including VAT (e.g. 125 kr)
Unchecked → you send the price excluding VAT (e.g. 100 kr)
It also works in reverse — when importing orders from Fortnox, it tells the system how to interpret the prices it receives.
Where to configure: Configure → Settings → Invoice Settings → VAT included in order rows
Add VAT on order rows
This setting controls whether you explicitly populate the VAT percentage field on each row when sending to Fortnox.
Checked → each row also gets a VAT percentage sent (e.g. 25%)
Unchecked → the VAT field is left empty, and Fortnox applies its own defaults
Where to configure: Configure → Settings → Invoice Settings → Add VAT on order rows
Note: In practice, very few merchants use the "Add VAT on order rows" setting. If you are unsure, leave it unchecked and let Fortnox handle VAT calculation from its own account configuration.
In short: the first setting is about the price format, the second is about whether to explicitly send the VAT rate per row. Both affect what gets pushed to Fortnox per order row.
Post-purchase modifications are not re-synced
Once an order has been synced and an invoice created in Fortnox, post-purchase modifications in the e-commerce platform are not automatically reflected in Fortnox.
This means:
If shipping is added to an order after it has already been synced, the existing Fortnox document will not be updated
If shipping is reduced or refunded in the e-commerce platform, no automatic credit invoice is created in Fortnox
If a new invoice is manually sent from the e-commerce platform after editing the order, this does not trigger a second invoice in Fortnox
The underlying reason is that Junipeer creates the Fortnox document based on the order state at the time it is first processed. Changes made after that point are not detected or re-processed.
Important: This is standard behavior for most ERP integrations. Once an order has been invoiced, it is considered closed for bookkeeping purposes. Corrections should be handled via credit notes in Fortnox.
Handling post-purchase corrections
If an order was modified after syncing, the recommended approach is:
In Fortnox, create a credit note against the original invoice to reverse it fully or partially
If needed, create a new invoice manually in Fortnox reflecting the corrected order
Contact support@junipeer.io if you need help determining the correct adjustment
For refunds triggered from the e-commerce platform (e.g. a return processed in Shopify), Junipeer does create a credit invoice automatically — the limitation above applies specifically to order edits, not to refund flows.
For related error codes and troubleshooting, see the Error Codes reference.