Skip to content

weclapp: Invoice run ​

The invoice run generates one PRE invoice covering the previous month for every mapped customer.

Every document carries the service period of the billed month — from its first to its last day (for the October run: 01.10.2026 – 31.10.2026) — in the invoice's own service period fields in weclapp, where the document templates print it. A customer with several invoices gets the same period on every document of the month. Non-monthly positions (quarterly, semi-annual, annual) additionally carry their own period on the position: the cadence they bill, starting with the billed month — a quarterly position billed with October covers 01.10.2026 – 31.12.2026, an annual one 01.10.2026 – 30.09.2027 (merged lines included); monthly positions carry no period of their own, the document's month applies to them.

Quantity determination ​

A month's invoice bills what the customer had at most in that month — the same figures the monthly CSV export shows. The scheduled run on the 1st bills the previous month that way, and a run made later for a past month (say the October invoice on November 6) bills exactly the same figures, never the current ones.

  • Unit-count metrics (seats, servers, users …): the month's peak — the highest figure of any snapshot day in the month. There is no minimum duration and no proration: a licence that was there on one day of the month bills for the full month, also when it was reduced or cancelled before the month's end. The month after no longer carries it.
  • Amounts (€) (manual portals, Azure consumption): the figure of the month's last snapshot — the amount accrued by the month's end, not its highest value (a credit may lower it). An amount that is no longer listed at the month's end is not billed: an Azure subscription that is gone cannot be told from one that was renamed and whose consumption runs on under the new name — both would be billed.

A customer with several accounts in one portal (a department counted towards its company, two merged organizations, a split part beside the customer's own tenant) bills the sum of its accounts per product — added up per day, so licences that move from one account to another are not counted twice.

Under Configure per customer a position that was higher during the month than at its end says so below its name: "peak of" and the day, with the figure now — or "last booked on" for a product that has left. Why a month bills more than the customer has at its end is visible before the invoice is created.

Printix users, Veeam VB365 users and Bitwarden seats are billed with the month's end, not its peak. These are the figures that domain rules can split between several customers. A rule that is added, changed or deleted moves users from one customer to another without anything changing in the portal — with a peak per customer they would be billed to the customer they left and to the one they went to, and nothing in a snapshot says whether a figure is such a part. They are therefore read from the month's last snapshot, for every customer: one day's distribution, which adds up to the tenant's figure. (The Printix figure is the active users of a billing period anyway, no daily count.)

An account that changes its customer name during the month counts for the name it ends under. A NinjaOne organization renamed to the name of an existing customer joins that customer (the rename is not applied); its devices are in that customer's month and no longer in the old name's. Where the customer's name is the only link — a Balena assignment, a Hetzner token, a manual entry — a re-assignment during the month looks like one customer cancelling and another one buying, and bills both for that month; the run names the position, and a quantity override corrects it.

What the month's snapshots could not read keeps its last figure. A month's figure is never below what its last day reads: per portal the newest snapshot up to and including the month's last day (at most 45 days before it). A product that is not in that snapshot is gone — a licence cancelled in ALSO, a removed Meraki model, a deleted manual entry drops out with the next snapshot, and the following month no longer bills it.

In that reading an older figure counts in three cases only, each at most 45 days old:

  • The portal took no snapshot that day (its API was down for the night): its newest snapshot counts.
  • The snapshot could not read this account — a failing Bitwarden API key, a Meraki organization without access or with a licence read that failed, a MailStore instance whose name or archive count could not be read, a Balena assignment whose organization is missing. Every snapshot records which accounts it could not read; such an account keeps the figures of its last successful snapshot instead of dropping off the invoice. An account that is simply missing from the snapshot — a deleted Bitwarden key, Meraki organization or MailStore instance, a domain rule pointed at another customer — is gone at once. (Snapshots from before 10 November 2026 carry no such record: where one of them is a portal's newest snapshot, a missing Bitwarden, Meraki, Microsoft 365, MailStore or Elovade account keeps its last figures for up to 45 days, as before.)
  • A single value was not delivered that night (MailStore storage when one archive store reports no size) or is implausible: the last valid one counts.

In all three cases the position shows "as of" and the day below its name under Configure per customer, so a figure that is not from the newest snapshot is visible before the invoice is created.

A manual portal whose last entry was deleted records an empty snapshot — the entry is gone from the next snapshot on, like any other product.

ELOVADE has no daily figures: its snapshot holds the purchased storage of the last day of the previous month. A month therefore has two ELOVADE figures — the one it started with (its own snapshots) and the one it ended with (the snapshots taken after it; the run on the 1st takes that snapshot itself before it bills) — and bills the higher of the two. Storage that grew in September is on the September invoice of October 1, storage given up in September is still billed for September, and a tenant the snapshot after the month lists with nothing cannot empty an invoice. While there is no snapshot after the month (it is still running, or ELOVADE could not be read) the figure the month started with is billed, and the run says so.

The Month field under Configure per customer shows these figures for any month before you create the invoice (Mappings).

Starting a run ​

TriggerBehavior
Schedule (recommended)generates the previous month's invoices automatically on the 1st at the configured time (Schedules) — the month before that day in the schedule's timezone; replaces its own not-yet-finalized drafts in the process. If Multiverse was not running at that minute (a restart, a deployment), the run is caught up the same day
Manualbutton in the weclapp view, optionally filtered to individual customers — and, for a customer with several invoices, to individual invoices — e.g. for stragglers or corrections

Before generating, the view shows per customer what to expect — including warnings for unmapped customers (they would be missing).

What a run reports ​

Besides created, skipped and error per customer, a run names everything it could not rely on — in the result of a manual run and in the audit log entry of the scheduled one:

  • Portals with an old snapshot. A portal whose newest snapshot is older than the billed month's last day (older than yesterday while the month is still running) is billed as of that older day; one without any snapshot in the 45 days before is not billed at all. Both are named with their day, e.g. "ninjaone: the newest snapshot is of 2026-10-12 — its positions are billed as of that day, not as of 2026-10-31". A portal that has not been snapshotted for half a year counts as retired and is not mentioned.
  • ELOVADE billed with the figure the month started with. ELOVADE's figure of a month's end is read after the month (see quantity determination). A run for a month that is still running, or one for which ELOVADE could not be read on the 1st, bills the figure the month started with — the one of the month before — and names it: "elovade: its figure of 2026-10 is read after the month has ended and is not there …". Take an ELOVADE snapshot and run the customers again with "Overwrite existing".
  • Positions billed with more than the month ended with. Every such position is named with the created invoice ("Month's peak: …" in the run's result, and in a list of its own in the email of the scheduled run) — "ALSO Microsoft 365 Business Premium: 12 billed — the month's peak, of 2026-10-12; the month ended with 10", or "… it was no longer there at the month's end". That is the rule (the month bills its peak); it is also what a figure looks like that sat with the wrong customer for a night or was typed wrong and corrected the day after, so the list is worth a look before the invoices are booked. A quantity override on the position bills its own figure instead.
  • Positions of an account its portal's snapshot could not read, with the day their figure is from.
  • What the snapshot said about its own figures: a shared tenant (Printix, Veeam, Bitwarden) that was split by the users of an earlier read or not at all, a Balena mapping whose organization is not listed any more, an ALSO account whose subscriptions came back empty, an Azure consumption that could not be read.
  • Positions weclapp priced at 0,00 € because the article has no valid sales price.
  • Unmapped products and non-monthly positions without an anchor month.

Only one run works at a time: a second one started meanwhile (another operator, the schedule) is refused until the first has finished, so a month is never created twice. One customer's failure never ends the run for the others — its line says what happened.

Quantities and unit prices go to weclapp with up to five decimals (what weclapp carries); every position is a cent amount, and a merged amount line is exactly the sum of the parts its description lists.

After the run ​

  • The invoice list in Multiverse shows every generated PRE invoice with a deep link to weclapp and the actual invoice amount from weclapp. The list shows at once; the amounts are read from weclapp in the background and fill in a moment later (the CSV export is available once they are there).
  • The search above the list looks at every column as it is shown — customer, invoice number, month (also by its name, e.g. "October"), billing, invoice ("Main invoice" or the additional invoice's name), net and gross amount (in either spelling, 1.234,50 or 1,234.50) and creation date. Several terms must all match, e.g. "bieker 2026-10"; the CSV export then exports exactly the invoices found.
  • Review and finalization happen in weclapp — Multiverse never touches finalized invoices.
  • Individual PRE invoices can be deleted from Multiverse and regenerated (e.g. after a late mapping).
  • Overwrite existing replaces the month's drafts document by document: an invoice that is no longer a draft in weclapp (booked) stays as it is and is reported — also on the invoices created beside it, because positions moved between the two since the booking would be on both. The customer's other drafts are replaced. A draft the month no longer needs (nothing left to bill on it) is removed. weclapp is asked for the status of the existing invoices first; if that fails, nothing is replaced and the run reports it as an error. If weclapp cannot answer for one single invoice, only that invoice's document stays as it is (an error for that customer) — everything else is replaced as usual; run that customer again. A draft that was removed for an invoice which then could not be created is named in the error, and the next run creates it.
  • An invoice cancelled in weclapp no longer counts: its month can be billed again, and removing it from the list here only drops Multiverse's record (the cancelled document stays in weclapp).
  • An invoice deleted in weclapp no longer counts either — also in a run without Overwrite existing: the run asks weclapp for every invoice it knows, and one weclapp no longer has stops blocking its month (the new document says so). Multiverse only concludes this from weclapp's own answer for that invoice; if weclapp cannot be asked, nothing changes.
  • While another run is still working — in this instance of Multiverse or, during a deployment, in the one that is being replaced — a second run is refused instead of creating the month's documents beside it.
  • A customer who already has some of the month's documents is skipped with a note naming the ones that are missing — tick them in the manual run to create them.

Several invoices per customer (invoice groups) ​

By default the run creates one PRE invoice per customer and month. A customer who wants separate documents — say the licences on one invoice and the extra articles on another — gets additional invoices under Configure per customer (Mappings): create an invoice with a name, then pick the invoice per position below its "On invoice" switch in the line-item table; positions without a choice stay on the main invoice. The run then creates one document per invoice that has positions this month (an invoice without positions produces no document); the article merge, the position order and the periodic positions work per document, nothing merges across documents. Duplicate protection and "Overwrite existing" span every document of the customer's month, so a re-run replaces all drafts of the month at once. To create only some of a customer's invoices, pick the customer in the manual run: a customer with additional invoices then shows a checkbox per invoice (all ticked). Only the ticked invoices are created, and duplicate protection and "Overwrite existing" look at these alone — e.g. create the additional invoice of a month whose main invoice already exists, or replace a single draft without touching the others. The invoice list names the invoice each document belongs to, and so do the run's result lines (customer · invoice). Removing an invoice moves its positions back to the main invoice; documents already created stay as they are.

Periodic invoices (quarterly/semi-annual, annual) ​

The run generates one monthly PRE invoice per customer. Non-monthly line items join that invoice only in the anchor month of the respective product row (and then every 3/6/12 months) (Mappings) — in the remaining months the run skips them automatically. On the document they are always appended below the monthly positions, in ascending cadence (quarterly, semi-annual, annual), never mixed in between; the article merge still works per period, so a monthly and an annual line on the same article never collapse into one position. Line items with non-monthly billing but no anchor month are never billed; the run reports them by name as a warning. Months that were already (partially) billed under the earlier one-invoice-per-period scheme are protected: any existing tracked document of the month blocks a re-run unless "Overwrite existing" is used.

Annual-license line items automatically receive a line-item description in the format "Article description - Term end: DD.MM.YYYY": the description from the weclapp article plus the actual ALSO contract end (from the latest snapshot). This also applies to ALSO annual commitments paid monthly on the monthly invoice — so the customer sees on every invoice when their annual license ends. A description stored per customer (Mappings, line-item dialog) takes precedence; without a known ALSO date, only the article description appears.