Skip to content
Tejobit
Moloni ON logo

Billing

Moloni ON integration

Orders turn into Moloni ON documents, and product and stock changes flow back to your store through the platform's hooks.

Request this integration See all integrations

Overview

Moloni ON

Moloni ON is Moloni's newer platform (Moloni is part of the Visma group): modular online invoicing and business management where you add modules as the company grows. It has its own sign-up, account and API, separate from classic Moloni.

Its API is GraphQL, with dedicated operations per document type: invoices, invoice-receipts, simplified invoices, credit notes, receipts, estimates, pro forma invoices and delivery notes (guias de transporte), each with create, PDF and email operations. Moloni ON also lets an integration register hooks, URLs that get notified when a product is created or updated or when stock changes.

Tejobit uses both directions. On the sales side, a paid order creates the customer and the document. On the catalogue side, the connection listens to Moloni ON hooks and pushes prices and stock to the store or marketplace, so Moloni ON stays the single source of truth for products.

Use cases

What it is for

  • A shop with a counter and a website, where items sold in person in Moloni ON also drop out of online stock.
  • A wholesaler issuing a delivery note in Moloni ON as soon as goods leave the warehouse.
  • A product configurator on a website that produces an estimate or pro forma invoice on its own.
  • A company moving from classic Moloni to Moloni ON that needs its integrations rebuilt.
  • A catalogue with size and colour variants managed in Moloni ON and published to several stores.
IN

What the connection listens to

  • A Moloni ON hook when a product is created or updated.
  • A Moloni ON hook when an item's stock changes.
  • A paid order in the online store or marketplace.
  • A shipment prepared or dispatched in the logistics system.
OUT

What the connection does

  • Creates or updates the customer and issues the right document for the sale.
  • Generates the document PDF and emails it to the customer.
  • Issues a delivery note with the items and the loading and delivery addresses.
  • Updates price and stock in the store when Moloni ON reports a change.
  • Records manual stock entries and exits coming from another system.

How it works

From the request to a working connection

  1. 01

    Request

    The form names the integration, the tools involved and what should happen in each case.

  2. 02

    Review and proposal

    Tejobit confirms what the API allows and sends a proposal with the flow, the price and the timeline.

  3. 03

    Setup and testing

    The connection is set up with the business's own accounts and tested with real cases before it goes live.

  4. 04

    Maintenance and monitoring

    Tejobit hosts the connection, follows up on errors and adapts it when the API changes.

The connection runs on Tejobit's infrastructure. The monthly fee covers hosting, monitoring and API changes.

What to prepare

  • A Moloni ON account with the invoicing and stock modules the connection will use.
  • Moloni ON API credentials for the company being connected.
  • Matching item references in both systems, or a mapping table.
  • Warehouses and document series already configured in Moloni ON.

For security, do not send passwords, API keys or tokens through the form. Credentials are requested through a secure channel when the setup starts.

Limits

  • The Moloni ON API is not the classic Moloni API: an integration built for one does not work with the other.
  • Hooks cover product and stock changes; documents issued inside Moloni ON are picked up by scheduled queries.
  • API sessions expire and must be refreshed. The connection stores and renews tokens, but revoked access needs a new authorisation.

Frequently asked questions

Before you start

How is Moloni ON different from Moloni?

They are separate platforms from the same company, with different accounts and APIs. Moloni ON is the newer, modular one. A connection targets the platform the business actually runs on.

There is already a Moloni ON app for Shopify and a WooCommerce plugin. When is a custom integration worth it?

When there is more than one store, sales happen outside those platforms, document rules are specific, or tools like booking systems and CRMs also need to talk to Moloni ON.

Who reports documents to the AT?

Moloni ON, as certified invoicing software. The connection only supplies sale data; it never issues or signs documents itself.

Related integrations

See all integrations

Set up the Moloni ON integration?

Describe what should pass between the tools. The reply confirms feasibility, price and timeline.

Talk about your project geral@tejobit.com