Skip to navigation

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.

Yes No No Yes No Yes No Yes Yes No Event accepted Reference used before? Duplicate, not billed Subscription active at the eventtimestamp? NO_PRICING_PLAN_SUBSCRIPTION Schedule covers the timestamp? NO_PRICING_PLAN_SCHEDULE Pricing on the plan matches the event? NO_PRICING Invoice for that period already FINAL? AFTER_INVOICE_FINAL Matched and billed

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:

List not-matched events
curl "https://test.api.solvimon.com/v1/events?meter_id=metr_wwFi4Kd0mPq7TsRxz16L&customer_id=cust_AwFi7Hn0cLs3VbEr1tQ9&processed_details_type=NOT_MATCHED&limit=20" \
-H "X-API-KEY: <apiKey>"

Each not-matched event has a processed_details object. The reason is in processed_details.not_matched.variant:

Response
{
"data": [
{
"object_type": "METER_DATA",
"id": "mdat_awFi5Lq0fPv8YeRw1kZT",
"reference": "txn_3ba00656_b6fe_4bea_81b6_3afd98749d27",
"type": "INGEST",
"customer_id": "cust_AwFi7Hn0cLs3VbEr1tQ9",
"meter_id": "metr_wwFi4Kd0mPq7TsRxz16L",
"timestamp": "2026-07-09T07:55:12Z",
"created_at": "2026-07-09T07:55:12.786367Z",
"meter_properties": [
{ "id": "metp_zwFi9Gm0eNu6XdDxy1FR", "value": "DE" }
],
"meter_values": [
{ "id": "metv_NwFi2Jp0dMt5WcFgj1OK", "number": "10000" }
],
"processed_details": {
"type": "NOT_MATCHED",
"not_matched": {
"variant": "NO_PRICING_PLAN_SUBSCRIPTION"
}
},
"deleted": false
}
],
"page": 1,
"limit": 20
}

To check a single event, fetch it by ID or by your own reference:

Get one event
curl "https://test.api.solvimon.com/v1/events/txn_3ba00656_b6fe_4bea_81b6_3afd98749d27" \
-H "X-API-KEY: <apiKey>"
FieldValuesDescription
processed_detailsobject or absentAbsent when Solvimon matched and billed the event.
processed_details.typeNOT_MATCHED, DUPLICATEWhy the event is not on an invoice.
processed_details.not_matched.variantSee reasonsSet when type is NOT_MATCHED.
processed_details.duplicate.of_meter_data_idevent IDSet when type is DUPLICATE: the earlier event with the same 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

ReasonDesk labelWhat it meansTypical causeHow to fixPicked up by reprocessing
NO_PRICING_PLAN_SUBSCRIPTIONNo pricing plan subscriptionNo subscription applies to the customer at the event timestamp. For child customers that only process usage, Solvimon checks the parent’s subscriptions.The customer has no subscription. The subscription starts after or ends before the event. The subscription is still a draft, or you voided it. The event names the wrong customer, pricing_plan_subscription_id or subscription selector values.Create the subscription or correct its start or end date. Alternatively, correct the event and send it again with a new reference.Yes, after the fix
NO_PRICING_PLAN_SCHEDULENo pricing plan scheduleThe subscription exists, but none of its schedules covers the event timestamp.A gap between schedules after a plan change.Adjust the schedule dates so that the schedules cover the period.Yes, after the fix
NO_PRICINGNo pricingThe subscription and schedule exist, but nothing on that pricing plan version prices this event.The meter’s usage metric is not linked to a product item on the plan. The product item conditions are not met. No pricing rule matches the meter properties in the event. A property that is missing from the event never matches a rule.Add the product item or pricing rule to the plan, or send the expected meter properties.Yes, after the fix
AFTER_INVOICE_FINALAfter invoice finalThe event matched a subscription and a price, but the invoice for its billing period was already FINAL.Late events from upstream systems. Backfills with a historical timestamp. An invoice that became FINAL before Solvimon processed all events.Turn on late usage on the next invoice to prevent it. For events that are already affected, see the same section.No
INVOICE_VOIDEDInvoice voidedThe event was billed on an invoice that you voided.You voided the invoice directly, or you voided its subscription.Usually nothing. The void schedules a reprocess that matches the event to the replacement subscription. If the event stays not matched, it shows the new reason.Yes, automatically
PRICING_PLAN_SUBSCRIPTION_VOIDEDPricing plan subscription voidedThe event was billed on a subscription that you voided.You voided an incorrect subscription to correct pricing.Make sure a correct subscription covers the period. The reprocess that follows the void matches the event to it.Yes, automatically
BOOKED_TO_ONE_OFF_INVOICE_LINEBooked to one off invoice lineSolvimon support moved the total of this usage to another invoice as a one-off line.A billing correction done by Solvimon.Nothing. The other invoice bills the amount.No, by design
NO_INVOICENo invoiceSolvimon archived usage from an old period that never got an invoice.Rare. Data housekeeping by Solvimon.
Contact support.No

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

1

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.

2

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.

3

Group by reason

Count events per processed_details.not_matched.variant. One reason usually explains most of the gap.

4

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.

5

Fix the cause

Use the table above. Correct the subscription, schedule or pricing. Alternatively, correct the events and send them again with new references.

6

Reprocess

Reprocess the customer so that Solvimon matches the not-matched events against the corrected setup. See Reprocess after fixing.

7

Verify

Fetch a few of the affected events again. Matched events no longer have processed_details. Check that the invoice total changed.

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}:

Bill late usage on the next invoice
curl -X PATCH https://test.api.solvimon.com/v1/platforms/<platformId> \
-H "X-API-KEY: <apiKey>" \
-H "Content-Type: application/json" \
-d '{
"processing_settings": {
"put_after_invoice_final_on_next_invoice": true
}
}'

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 FINAL invoice 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:

POST
/v:version/report-generate-requests
curl -X POST https://test.api.solvimon.com/v1/report-generate-requests \
-H "X-API-KEY: <apiKey>" \
-H "Content-Type: application/json" \
-d '{
"report_code": "INVOICE_LINE",
"parameter_values": [
{
"name": "from_date",
"value": "2026-09-01T00:00:00Z"
},
{
"name": "to_date",
"value": "2026-10-01T00:00:00Z"
},
{
"name": "statuses",
"value": "FINAL"
}
]
}'
Response
{
"object_type": "string",
"id": "string",
"customer_id": "string",
"invoice_id": "string",
"generate_at": "2024-01-15T09:30:00Z",
"report_code": "INVOICE",
"parameter_values": [
{
"name": "report_date",
"value": "string"
}
],
"status": "string",
"report_subscription_id": "string",
"report_configuration_id": "string",
"run_type": "string",
"export_location": {
"integration_id": "string",
"variant": "BIGQUERY",
"stream_name": "string",
"bigquery": {
"dataset_id": "string"
},
"s3": {
"bucket_path": "string",
"path_format": "string",
"format_type": "CSV"
},
"gcs": {
"bucket_path": "string",
"path_format": "string",
"format_type": "CSV"
}
},
"format": "CSV"
}

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_FINAL events 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.