Unbilled usage
An invoice can show less usage than you sent. In that case, Solvimon accepted the missing events but did not match them to a subscription, a price or an open invoice. This page shows how to find those events, read the reason that Solvimon stores on each event, and correct the cause.
How Solvimon decides whether an event is billed
Solvimon accepts an event and bills it in separate steps. After ingestion, Solvimon looks for a subscription, a schedule and a price for the event. Then it adds the event to the invoice for the billing period that contains the event timestamp. If a step fails, Solvimon stores the event as not matched with a reason. The event then does not count towards an invoice.
The checks run in this order, and the first check that fails sets the reason. Events can also lose their match later. For example, this occurs when you void the invoice or subscription that billed them.
Find the reason for an event
Via API
To list the not-matched events for a meter, use processed_details_type=NOT_MATCHED. Optionally, add customer_id to list one customer only. meter_id (or reference) is mandatory:
Each not-matched event has a processed_details object. The reason is in processed_details.not_matched.variant:
To check a single event, fetch it by ID or by your own reference:
processed_details.duplicate_of_meter_data_id is deprecated. Use duplicate.of_meter_data_id instead.
To get a notification when an event is not matched, subscribe a webhook to METER_DATA.NOT_MATCHED. See Webhook event types. Solvimon sends this webhook event when a usage event fails to match at ingestion. It does not send it when a usage event stays not matched after a reprocess.
Via Desk
Go to Usage metering > Events and open a meter. Not-matched events show a Not matched status in the Processed details column. Hover over the info icon to see the reason, for example “No pricing plan subscription”. Open an event to see the same reason in the event details.
Reasons an event is not billed
A duplicate is not a not-matched reason. When Solvimon receives an event with a reference that it already received, it sets processed_details.type to DUPLICATE. duplicate.of_meter_data_id points to the original event. Internally, Solvimon records this as REFERENCE_NOT_UNIQUE. To bill a new event, send it with a new reference.
Platforms on Solvimon’s newer event engine can show different reason values in the same field, such as NoMatchingPricing or NoPricingContext. NoMatchingPricing means the same as NO_PRICING. For any other value of this kind, contact support.
Diagnose a short invoice
Confirm the gap
Compare the event count you sent for the period with the events on the invoice. Download the invoice usage report or the matched events report for the invoice.
List what did not match
Call GET /v1/events with processed_details_type=NOT_MATCHED for the meter and customer, or generate the unmatched events report for the period. Also check processed_details_type=DUPLICATE, because Solvimon never bills duplicates.
Group by reason
Count events per processed_details.not_matched.variant. One reason usually explains most of the gap.
Check the event timestamps
Solvimon bills an event in the period that contains its timestamp, in the customer’s time zone. Events with a timestamp in a period whose invoice is FINAL show AFTER_INVOICE_FINAL. Events that never reached Solvimon do not appear at all. Check your ingestion responses and logs for those events.
Fix the cause
Use the table above. Correct the subscription, schedule or pricing. Alternatively, correct the events and send them again with new references.
Reprocess
Reprocess the customer so that Solvimon matches the not-matched events against the corrected setup. See Reprocess after fixing.
Late usage and final invoices
A FINAL invoice cannot change. Thus, Solvimon does not match events that arrive later for that period. These events get the reason AFTER_INVOICE_FINAL.
To bill late usage on the next open invoice instead, turn on processing_settings.put_after_invoice_final_on_next_invoice for your platform with PATCH /v1/platforms/{id}:
With the setting on, Solvimon adds a late event to the subscription’s next DRAFT, OPEN or FUTURE invoice. The billing period of that invoice must start at or after the end of the event’s period. If there is no such invoice, the event stays not matched with AFTER_INVOICE_FINAL. The setting applies to events that Solvimon processes after you turn it on. It does not move events that were already not matched.
For events that are already AFTER_INVOICE_FINAL, you have two options:
- Bill them on a later invoice as a one-off charge.
- Credit the
FINALinvoice and build it again. See Event reprocessing.
Wait at least one business day after a billing period ends before you finalize its invoices. Solvimon can then still match delayed events. The most common cause of AFTER_INVOICE_FINAL is bulk finalization on the first day of the month.
Generate the unmatched events report
To review not-matched events in bulk, trigger the unmatched events report with POST /v1/report-generate-requests using report code NOT_MATCHED_METER_DATA:
Generation is asynchronous. Solvimon writes the finished report to your Solvimon Google Cloud Storage bucket. Each row contains the raw event data exactly as Solvimon received it, and the reason in the variant column. You can thus trace a not-matched event back to the data that your system sent.
If you do not have access to your Solvimon bucket, contact support.
Reprocess after fixing
A correction to a subscription, schedule or pricing does not change events that already failed to match. Reprocess the customer so that Solvimon matches them again. See Event reprocessing.
A customer reprocess picks up the customer’s not-matched events from the start of their earliest OPEN or DRAFT invoice period. It does not pick up:
- Events in periods whose invoices are all
FINAL. Thus,AFTER_INVOICE_FINALevents stay not matched. - Events with reason
BOOKED_TO_ONE_OFF_INVOICE_LINE, because Solvimon already billed that usage.
Reprocessed events count as new events towards your usage allotment.