Fortnox integration for magazine publishers

Use RunMags to sell, invoice and collect, then synchronize advertiser invoices, credit notes and customers to Fortnox, where you manage the cost side of your business - vendors, expenses, salaries - to get a comprehensive view of your Profit & Loss. Payments recorded in Fortnox are pulled back into RunMags. Subscription invoices are not synced to Fortnox yet; that is on our roadmap.

When you operate your business on RunMags, you eliminate the need for cumbersome dual-entry of data in your commercial process.

The product information, pricing and terms in your advertising contracts are seamlessly pulled into the invoice so all you have to do is to approve it before it is emailed to your clients.

The Fortnox sync covers advertiser invoices: customers, advertiser invoices and credit notes sync per legal entity. Subscription invoices are not part of that sync.

Two-way syncronization with Fortnox

Two-way synchronization with Fortnox

If you are subscribing to our Fortnox integration, advertiser invoices are synced over to Fortnox after invoices are created in RunMags billing, and you can also start a sync from RunMags. If the client record does not already exist in Fortnox, it is created there as well.

Payments you register in Fortnox are synced back to RunMags, so you can see in RunMags which invoices are paid.

How the Fortnox sync works

Each legal entity in RunMags connects to its own Fortnox account. You approve access in Fortnox, and the sync covers advertiser invoices dated from the day you first connect unless another start date is set. Subscription invoices are not part of the Fortnox sync.

What RunMags sends to Fortnox

  • Customers: RunMags looks for the customer number RM_ followed by the RunMags customer number and creates the customer if it is missing, with name, address, registration number, VAT number and finance email. For an existing customer, the email and VAT number are updated.
  • Invoices: each advertiser invoice is created with its Fortnox invoice number taken from the RunMags invoice number. Invoice rows are linked to Fortnox projects, for example one per publication issue.
  • Credit notes: a RunMags credit note credits the original invoice in Fortnox.

What comes back to RunMags

On each sync run, RunMags checks Fortnox for payments on invoices that are still open and records new payments in RunMags, so your team can see which invoices are paid. During onboarding you can also import your Fortnox customers.

When the sync runs

A sync starts after invoices are created in RunMags billing, and you can also start one from RunMags. If an invoice fails, it is tried again on the next run. Each run records its invoice and payment counts and any errors. If the Fortnox authorization expires, the run stops and RunMags records that Fortnox needs to be reconnected.

Setting up the Fortnox integration

  1. Connect Fortnox from RunMags for the legal entity and approve access in Fortnox.
  2. Before the first sync, check with our team which sales account and VAT rate invoice rows are sent with.
  3. Import your Fortnox customers if you want to, then run a sync and check the first invoices in Fortnox.

Agree the accounting handover with finance

Fortnox is one of the accounting integration options for RunMags. Begin with your publishing business's sales and billing structure: the legal entity issuing invoices, the types of revenue you record and the accounts finance uses. Include the people who maintain Fortnox in this discussion so that the proposed handover reflects the accounting process they actually manage.

Prepare a representative advertising sale and, where relevant, a subscription example. Review the customer details, agreed amounts and account mapping that need to be understood between systems. Confirm the supported integration scope and setup with our team. A named integration does not mean every record or field will synchronize automatically in both directions.

Once the intended handover is agreed, test a small scenario and review the result together. Decide who checks the source information and who handles exceptions. Keep a record of unresolved mapping questions before switching a live workflow. Explore smooth accounting, billing and payments and integration planning to see how the accounting connection fits the wider publishing process.

Keep account mapping decisions with the people responsible for finance. Review a representative result together, including the explanation staff will need if a record requires attention. The goal is a handover the team can maintain confidently as publishing activity changes.