Skip to content

weclapp: Invoice run

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

Quantity determination

  • Unit-count metrics (seats, servers, users …): based on the previous month's snapshot values.
  • Amounts (€) (manual portals, Azure consumption): the value as of the last snapshot day of the month.

Services (HaloPSA times) are not part of the license invoice — they are a separate invoice document and are posted individually via the weclapp posting report.

Starting a run

TriggerBehavior
Schedule (recommended)generates the previous month's invoices automatically at the start of the month (Schedules); replaces its own not-yet-finalized drafts in the process
Manualbutton in the weclapp view, optionally filtered to individual customers — 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).

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.
  • 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).

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.