Skip to content

weclapp: Mapping customers & articles ​

Two mappings connect the Multiverse numbers with weclapp: customer → weclapp customer and metric → weclapp article.

The weclapp view is organized into three tabs: Invoice run (generate and track invoices), Article mappings (global metric→article assignments) and Customer (customer-specific settings including line-item order).

Customer mapping ​

The list shows all (merged) Multiverse customers; a click assigns the matching weclapp customer to each one. Search and filters help with large lists; labels on each row show whether overrides, extra articles or deviating settings are active. In the mapping form, both dropdowns only offer unmapped entries — in "Customer (Multiverse)" as well as in "weclapp customer", whatever is already assigned disappears. This keeps the selection short while working through the list, and neither a Multiverse nor a weclapp customer can accidentally be mapped twice. Customers hidden in the customer view (e.g. ALSO tenants without own services) stay out of the "Customer (Multiverse)" dropdown as well.

  • Anchor month per product (for all non-monthly periods): The anchor month is set per product row — in the line-item dialog of a service (or per extra article) under "Configure per customer". It defines the phase of the cadence: the item lands on that month's monthly invoice (appended below the monthly positions) and then — depending on the period — again every 3 (quarterly), 6 (semi-annually) or 12 (annually) months. This is needed because a customer can have several such line items with different start months (bought mid-year). In all other months, the run skips them. Without an anchor month set, the line item is never billed — the invoice run lists the affected products by name as a warning. As a reference point, "Configure per customer" shows the customer's earliest ALSO term end.
  • Unmapped customers are not billed — the invoice run lists them beforehand as a warning.
  • A mapping belongs to its customer and cannot be moved to another name: everything the customer is billed by (overrides, extra articles, flat rates, additional invoices, the position order) hangs on the name. Delete the mapping and map the other customer — or, where two names are one customer, merge them in the customer view.

Article mapping ​

Each metric per portal (e.g. ninjaone/servers, ALSO products, Autodesk products) is assigned to a weclapp article. Unmapped metrics do not appear on invoices.

  • The metric names of each integration are listed on its integration page.
  • The dialog shows the article price — customer-specific weclapp prices are highlighted.
  • Period per product: By default almost every product goes on the monthly invoice, because in practice most annual licenses are billed monthly ("1 year paid monthly" — the article price is the monthly price). The true "… (jährlich, Prepaid)" licenses (annual prepayment) are the exception: they default to annual — monthly would make no sense there. Switching is possible at any time; like every non-monthly period, they only invoice once an anchor month is set (until then the invoice run warns). The "Prepaid" suffix makes these subscriptions findable in the product search; the underlying metric is still called "… (jährlich)". Besides monthly and annual, quarterly and semi-annual are also available — per product (globally), per customer as an override, or per extra article. Every non-monthly period is explicit configuration and needs an anchor month; in the anchor months the invoice run appends these line items below the monthly positions of the customer's ONE monthly PRE invoice.
  • Price-protection hint: For ALSO products, the service row (and the line-item dialog) shows "Price protection until …" below the weclapp price — red for expired price protection, yellow for price protection expiring within 60 days. That way, when setting the sales prices it is visible how long the purchase price is fixed.
  • Reset all mappings: After confirmation, the red button next to the product search removes all global article mappings and period settings (audit-log entry included). Customer-specific overrides, extra articles and services are kept; until re-mapped, the products appear on no invoice.

Customer-specific adjustments ​

Line items can be refined per customer — everything takes effect automatically from the next invoice on:

ToolPurpose
Overridesoverride the line-item name, quantity, amount or purchase price (EK, cost basis of the controlling margin — never on the invoice) of a mapped line item
Extra articlesfixed additional line items (e.g. flat fees), optionally with their own line-item text, unit price (sales price) and purchase price (for the controlling margin)
Invoicesadditional invoices of the customer (e.g. "Licences", "Extra articles"): positions assigned to one bill on a document of their own, the rest on the main invoice
Servicesrecurring service line items per customer, with a price per row

Merges in the customer view automatically move all these settings along.

Numbers in these forms — quantity, price, purchase price, manual amount — can be typed with a decimal comma or a decimal point, also with grouping ("1.234,56" or "1,234.56") and a trailing € sign. What cannot be read with certainty is refused instead of guessed: "1.200" or "12,500" may be thousands or decimals — write "1200,00" or "1,2000". Quantities and prices are stored with up to five decimals, exactly as they are billed.

A change shows at once. Flipping the "On invoice" switch or moving a position to another invoice takes effect on the screen the moment it is clicked: the control shows the new value, a small spinner beside it says that the change is being saved, and the expected invoice amount follows. If a change could not be saved, the control goes back to its previous value, a message says so, and the card is read again from the server (a change that was not answered may still have been stored). While a position's change is being saved, a second change of the same position waits. Picking another article shows the pick at once and then reloads the card, because the article's number, prices and billing period come from weclapp.

The table holds still while you work. Every column has a fixed width and the table fits its card (a long text wraps or is cut — pointing at it shows it in full), a position keeps its height whichever way its switch stands, and when the card is read again the prices of the positions that were not changed stay on the screen until the new ones are there (a position that was given another article says "price loading…" meanwhile). Nothing moves under the pointer when a switch is flipped. A position that is off the invoice is shown dimmed.

Finding a position. Above the table, a search field and a filter choose which positions are shown. The search reads what a row says — the position's name, its article (name or number), its invoice — and every word you type has to occur somewhere in the row. The filter shows all positions, those on the invoice, those switched off, or those without an article, each with its count. A position you edit stays in the list it was found in: flip a switch under "On invoice" and the row stays where it is until the filter is chosen anew. The expected total keeps counting every position, and sorting rests while only a part of the list is shown. The search is for one customer; the filter stays when you move on to the next.

Positions of one invoice line stand together. With "One invoice line per article" several positions bill on one line, at the place of the first of them. Positions that bill on one line and follow each other in the list form a block: a bracket at the left of their names ties them together. When such positions are spread over the list, Bring together above the table puts them below the first of them in one click (a new order, saved like every move). Blocks sort as one: the arrows of a block's first row move all of it past the block beside it, the arrows of its other rows sort inside the block, and a single position hops over a block instead of landing in its middle; dragging the first row takes the block along, and a drop never lands inside another block. A block holds exactly what the invoice combines: a position that bills on a line of its own although it shares the article (a pure € pass-through beside a flat rate, a position without a price) is not part of it and sorts freely. A position that is switched off, or that bills on another invoice, between the positions of a block stays inside the bracket, without a tick — the invoice of that line does not know it is there, so the block is not taken apart; at the edge of a block it is out of it. When the block is moved, a position of another invoice inside the bracket keeps its place: a line that moves changes the order of its own invoice only. With the keyboard, the focus stays on the arrow that was pressed, also where the arrow rests at an end; an arrow that rests says why when pointed at. Without "One invoice line per article" there are no blocks, the arrows swap two neighbours as before.

What a click changed lights up. When an amount changes — the row's, the line it is combined into, a part of the expected total — it is highlighted for a moment. Nothing lights up while prices are being read, or on a card that was just opened.

Another month keeps the card in view. Changing the Month field leaves a dimmed picture of the card on the screen while that month is read. The picture cannot be edited; it gives way to the new card, goes at once if the load fails, and after a few seconds if the load takes long.

The card always belongs to the selected customer. Switching to another customer empties it at once; if its data cannot be loaded, the card says so and stays empty rather than showing the customer picked before.

Jumping to a customer quickly: In the customer mapping, clicking the customer name — or one of its service chips (e.g. "10 services") — leads directly to the Customer tab and opens that exact customer's configuration there.

The small Refresh button next to the customer selection reloads just the panel's weclapp data — customer and article lists, line items including prices and the expected amount. Handy when something was changed directly in weclapp (new article, changed price): just click instead of reloading the page. Multiverse keeps the weclapp customer and article lists so the view never has to wait for weclapp to open: lists older than 10 minutes are shown at once and read again in the background (the pickers take the new lists a few seconds later; if weclapp does not answer, a warning says so once and names when the lists shown were read), and the price rows behind a card are kept for one minute. A customer or article just created in weclapp, or a price just changed there, shows at once after a click on this button — the button reads weclapp directly. The invoice run, the controlling and the price dialog never use what is kept: they read weclapp themselves, every time.

The Month field beside it shows the line items with the quantities and amounts of that month — exactly what that month's invoice run bills: the month's peak of every count, the month-end figure of every € amount and of Printix users, Veeam VB365 users and Bitwarden seats; the current month shows its peak so far. Handy before invoicing a past month late: switch to October and the table, the prices and the expected amount show October's figures (e.g. 3 Printix users instead of today's 4, October's Azure consumption instead of November's). A past month is stated above the table together with the snapshot day. A position that was higher during the month than at its end says "peak of" and the day with the figure now (a product that has left: "last booked on"). A position whose figure comes from an older snapshot than the rest of the card (the portal took no snapshot since, or its newest one could not read this customer or value — see quantity determination) says "as of" and the day below its name.

Line-item table & order (drag & drop) ​

In the Customer tab, all line items — mapped services and extra articles — sit in one shared line-item table in invoice order. Each row carries its own controls: for services the article override, the "On invoice" toggle and adjusting text/quantity/price; for extra articles editing (article, quantity, unit price, purchase price, line-item text, description, billing/anchor month) via the pencil button, and deleting. An extra article without its own unit price shows the resolved weclapp price the invoice would bill in its price column (customer price before standard price) — the plain "article price" label only remains while no price is known. Description texts (position dialog and extra articles) are edited in a small rich-text editor — bold, italic, underline and lists carry over to the weclapp line-item description. The desired order is set via the drag handle (drag & drop) or the up/down arrow buttons — services and extra articles can be mixed freely, and every move is saved automatically (a short status next to the table title confirms it — there is no save button to forget). The form for adding extra articles sits below the table.

One invoice line per article (per-customer switch above the table; the ? beside it opens these rules in the app): service positions that resolve to the same article are combined into a single line on the invoice. Quantity positions add up — e.g. all Meraki license metrics mapped to one article appear as one position with the total quantity (auto-priced rows are combined so weclapp determines one price for the summed quantity; scale prices then apply to the true total; manually priced rows sum when they share the price, and an auto-priced row at that same price joins them). A € position billed at the article's customer price turns the article into a flat rate: every position of that article — € subscriptions and quantity services alike — merges into ONE line and the fixed price counts ONCE (e.g. two Azure subscriptions plus a Veeam service on one 500 € flat article bill 500 €, not 3 × 500 €). Affected rows carry a "combined" chip; the merged line keeps the slot and the line-item text of its first row. An article can also be switched to a flat rate explicitly — the clickable "flat rate" chip on combined rows opens the choice per article: the merged line then bills one price at quantity 1 instead of summing quantities (e.g. four Meraki rows on one 19 € article bill 19 €, not 9 × 19 €). A price override on a participating row becomes the flat price (its purchase-price override feeds the group's cost in the controlling); without one, the article/customer price applies once. Everything else on one article — pure € pass-through amounts (no override, no customer price), alone or beside quantity rows, and rows at different prices — adds up into one amount line: quantity 1, price = the sum of the rows' amounts, and the line-item description lists every row with its amount, quantity rows with their quantity × price (e.g. two Azure plans on one "Azure Plan subscription" article become one 31.60 € line reading "DM-Motion: 11,44 € · OpenAI: 20,16 €"; an Azure override at 462.96 × 1.08 €, a 336.05 € pass-through and a Veeam service on the same article become one 838.21 € line). Pass-throughs never join a price-once flat rate; an auto-priced row whose weclapp price cannot be resolved stays a line of its own. The "flat rate" chip opens a small dialog with three choices per article: sum of the rows (the default above), flat rate (one price once) or a manual amount — quantity × price entered by hand. A manual amount replaces every row of the article, pass-through amounts included (the Blum example above becomes one 462,96 × 1,08 € = 500,00 € line instead of 838,21 €), and the line's description names the rows it covers ("Enthält: …"); the controlling counts it once per group. Extra articles always stay separate lines. The controlling mirrors the merged lines: a flat rate counts its fixed price once in revenue and margin (the costs of every participant keep counting, and the loss list checks the flat price against the group's summed purchase cost), and auto-priced quantity groups are priced at their summed quantity.

During the invoice run, the line items are then created in the PRE invoice in exactly this order. Line items that have not been sorted in yet (e.g. a newly added product) attach at the end and keep their previous order there — so the saved arrangement stays stable even as products change. The order belongs to the customer, not to the month the card shows: sorting while another month is selected moves the positions of that month among themselves, and a position only another month has (booked since, or cancelled since) keeps its place. A position that is new to the order and is sorted in goes directly before the position that follows it on the card; the others keep their places. If a save does not go through, the card says so and sends the order again with the next move, the next reload or when you leave the customer or the page.

Several invoices per customer ​

By default every position bills on one invoice per month. The Invoices block above the line-item table lists the customer's documents: the main invoice plus any additional invoices you create by name (rename with the pencil, remove with the ×). As soon as the customer has an additional invoice, every position gets an invoice choice below its "On invoice" switch: pick per position — service or extra article — which document it lands on; positions without a choice stay on the main invoice. The invoice run then creates one document per invoice that has positions this month; the article merge, the position order and the periodic positions work per document. The expected amount below the table is shown per invoice. Removing an invoice moves its positions back to the main invoice.

Expected invoice amount ​

Below the line-item table, Multiverse shows the customer's expected invoice amount — split into monthly and annual (net), without a PRE invoice having to be generated for it. The line stays at the lower edge of the window while the list is longer than it: the total is in view wherever you are in the list and shows at once what a switch did to it. The total is computed live from exactly the line items in the table, with the same price logic as in the invoice run: a set price override wins, otherwise the weclapp sales price applies (customer price before standard price); € pass-throughs count with their amount — unless the article carries a customer-specific weclapp price (a fixed-price deal, e.g. a flat Azure rate): then that fixed price is billed instead of the amount (a standard price alone never replaces the amount); the quantity comes from the override, otherwise from the snapshot. Disabled line items ("On invoice" off) are not included; line items without an article mapping or without a stored sales price are not counted but tallied in a hint next to it. A line item priced only by its override (its article has no sales price in weclapp) counts into its period's total like every other line item. Every change — toggling, override, extra article — updates the amount immediately. Annual line items still invoice only in their respective anchor month; the annual total states the entire annual volume.

The amount counts every line as weclapp bills it: each position is rounded to cents, a combined line counts once with its summed quantity. Non-monthly rows without an anchor month are never billed and stay out of the total (the hint beside it counts them), and rows that bill in different months — different anchor months — do not merge. Extra articles stay lines of their own also beside a flat rate with a manual amount. If the weclapp prices cannot be loaded, the card says so: without them a € position with a customer price would show as a pass-through of its amount — the prices and the expected amount are then not to be relied on ("Refresh from weclapp" tries again).

Invoice amount per row ​

The Invoice amount column of the line-item table shows, row by row, what the invoice run would bill — so the sum above is never a black box:

  • a plain row shows its amount with the formula and the price source underneath, e.g. "13 × 19,00 € · customer price" or "2 × 39,00 € · article price"; a price override is highlighted;
  • a € position billed at a customer price shows the fixed price and says which amount it replaces ("fixed price (customer price) instead of the amount 87,47 €"); a pure pass-through reads "pass-through amount (1 ×)";
  • with One invoice line per article on, the first participant of a group carries the whole line — "flat rate · customer price once for 5 rows", "combined · 10 × 6,50 € (3 rows)" or "amounts added up (2 rows)" — and the other participants read "included in the flat rate → …" / "quantity 3 counts in → …" / "amount 20,16 € counts in → …", naming the row that carries their line;
  • disabled rows, rows without an article and rows whose price is not (yet) known are marked as not billed.

Why a customer price is not charged ​

Under the article, each row names the weclapp price the run would charge ("Customer price X (standard Y)" or "Article price Y"). If weclapp holds customer-specific price rows on the article that do not apply, an orange hint explains why instead of silently falling back to the article price: "valid from 13.10.2026 only", "expired on 31.12.2024", "sales channel X ≠ customer's Y" (a price row bound to another sales channel than the customer's), "scale from quantity N" / "scale up to quantity N" (the scale step is not reached at the billed quantity) or "no usable price". The same hint appears in the position dialog. Expired rows are only listed while no other customer row applies — the price history of a working customer price stays quiet.