Integrations for magazine publishing teams

RunMags is built to integrate with other platforms so you can increase productivity and employee job satisfaction. Use our API to integrate with you websites, ad servers, accounting systems and more.

Stripe payment processing

Stripe payment processing

RunMags is a Verified Stripe Partner and our free Stripe integration helps magazine publishers collect client payment methods and get paid. Billing and collecting payments for ad bookings and subscriptions is a tedious process, and RunMags runs it with Stripe: auto-renewing subscriptions are charged to the subscriber's saved card when your team runs the renewal batch. Let clients securely enter their payment methods online, bill them according to the contractual terms and Stripe will collect and transfer your hard earned cash directly to you bank account.

Explore Stripe payments for magazine publishers
Xero accounting

Xero accounting

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

Xero integration for publishers
Quickbooks accounting

Quickbooks accounting

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

QuickBooks sync for magazine invoices
Fortnox accounting

Fortnox accounting

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.

Fortnox integration

Plan integrations around a clear business handover

An integration should have a defined purpose. Identify which system owns a record, which information needs to move and who checks the result. Connecting two tools does not by itself establish an agreed workflow. Your team still needs to understand what happens when an account, customer detail or transaction needs attention.

RunMags integration options include Stripe, QuickBooks, Xero, Fortnox and WordPress. These names describe supported options, not a promise that every service offers identical synchronization or that every field transfers in both directions. Discuss the current scope and setup for your chosen connection with our team, using examples from your own publishing process.

Prepare representative examples

For an accounting discussion, bring the types of sales and invoices you issue, the legal entities involved and the account mapping you expect. For a website discussion, describe the reader or advertiser journey and where the publishing records should connect. For payments, explain how your team collects money and handles reconciliation. You do not need to send private customer records in an initial enquiry.

Test a small, agreed scenario before changing a live workflow. Review the source information, the receiving system and the responsibility for exceptions. Document assumptions so that staff know what the connection does and which steps remain theirs. Explore accounting workflows, the RunMags API and onboarding, or ask Maggie to help prepare your questions.

Also agree how you will recognize a successful handover. A connected account alone is not proof that the intended information reached the receiving workflow correctly. Have the responsible staff review a representative result before relying on the connection during normal publishing operations.