Partner programme

This section is for partners — companies that resell or implement fremforge for their own customers. It describes the commercial mechanics: what registering a deal buys you, how a customer becomes yours, how margin is calculated, and how you get paid.

Everything here is also available through the Partner API, so the whole flow can run from your own CRM rather than from a browser.

If you are looking for the platform documentation your customers use, start at Get started.

The shape of it

register a deal  ->  we approve it  ->  you win it  ->  you create the customer
      |                                                        |
      +-- 90-day protection on that company                    +-- margin counts
                                                                   from their first
                                                                   invoice onward

Four things happen in order, and each one is a state you can see in the portal or over the API.

1. Register the deal — early

A deal registration records that you are working a named company, and starts a 90-day protection window on it.

Register as soon as an opportunity exists, not when it is nearly closed. Protection is the point of registering, and it only protects from the moment you register.

We email you 14 days and 3 days before the window lapses, so a slow deal does not quietly lose its protection.

When two partners register the same company

The second registration comes back flagged. That is not an error and not a rejection — the deal is registered, and it sits with us.

We resolve conflicts on evidence of sales activity, never on who registered first. That is why sales_activity_evidence is worth filling in properly: it is the thing the decision is made on.

We deliberately do not tell you who the other partner is.

Do not retry a flagged registration. Retrying spends your daily registration allowance and changes nothing — the deal is already registered. There is a daily cap on registrations; exceeding it returns 429.

2. Bring the customer onto the platform

Once a deal is approved or won, you can create the customer yourself: their organisation is created, their administrator is invited by email, and the customer is assigned to you.

The customer starts on a trial, exactly as any self-service signup does.

The plan is deliberately not a parameter. Choosing it would be granting commercial terms, and that is not something an API call should do. The response carries a billing_setup_url where the customer adds a payment method and converts — the same link is emailed to them.

If the deal needs enterprise terms

Ask before you create the customer, using the enterprise-request endpoint or the portal. Your partner manager negotiates the terms and converts the customer.

Once the customer exists, converting it is an operator action — so a deal that clearly needs negotiated seat pricing is easier to handle if you flag it early.

3. How margin is calculated

Margin is a share of what the customer actually pays, aggregated from their real invoices.

Two consequences worth understanding, because both surprise people:

Margin counts from the assignment date. A customer assigned late earns you nothing for the months before the assignment. This is why creating the customer through your deal matters — it assigns them in the same action.
Nothing is pro-rated to month boundaries. A customer billed on the 17th is valued on the 17th. Statements are consolidated monthly; they are not an accounting period boundary.

The portal shows an “Accruing now” figure for the current, unbilled period. It is computed by the same code that builds the statement, so the preview cannot disagree with the statement that follows it.

4. Statements and getting paid

Statements are built on the 1st for the previous calendar month.

Settlement runs in a fixed order, and each step is visible to you:

step	what it means
`sent_at`	We have issued the statement to you
`partner_invoice_ref`	You have invoiced us, on your own document, and we have recorded your reference
`paid_at`	We have paid it

Payment is 30 days from receipt of your invoice. We do not pay before a partner invoice reference exists — your invoice is the document the payment is against.

Money fields are strings. Statement amounts are returned as decimal strings, exactly as stored. Do not re-round them or parse them as floats — your reconciliation will then disagree with the statement it came from.

Your account and access

Signing in

Partner users sign in with their fremforge account. We support ordinary accounts, and we prefer federated identity — if your company has an identity provider, ask your partner manager to connect it, and your team signs in with the accounts they already have.

Multi-factor authentication is required. On a non-federated account you are asked to set it up on first sign-in; with federated identity your own provider enforces it.

Paused vs terminated

agreement_status of paused is an abuse control on deal registration only. A paused partner keeps full access to their customers, statements and agreements — locking you out of your own commercial records would turn a rate limit into a billing dispute.

terminated ends access.

The frame agreement

Before you can transact, the frame agreement is signed electronically with a national eID:

Country	Credential
Denmark	MitID Erhverv (company-bound)
Sweden	Freja Organisation (company-bound)
Norway	BankID (personal)
Finland	FTN (personal)

The credential is chosen by your company’s country of registration — not by the territory you sell into. A Danish company selling into Sweden signs with MitID Erhverv.

Norway and Finland have no company-bound credential, so authority there rests on the recorded signatory title and the warranty in the agreement itself.

Doing all of this from your own systems

Every step above is an API call. Registering a deal from your CRM the moment an opportunity is created is the intended pattern — it is also the best way to make sure protection actually starts when the work does.

See the Partner API reference.