For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
LoginSandbox
Platform GuidesAPI DocsSDKMCP ServerChangelog
Platform GuidesAPI DocsSDKMCP ServerChangelog
  • Getting started
    • Introduction
    • Concepts
    • Onboarding guide
  • Use cases
    • Monetizing an AI agent
    • Pricing models for AI products
    • Configuring entitlements for AI products
  • Usage metering & events
    • Meters
    • Usage events
    • Unmatched events
    • Event reprocessing
  • Products & plans
    • Product Catalog
    • Pricing Plans
    • Features & Entitlements
  • Wallets & credits
    • Credit types & wallets
    • Credits in pricing plans
  • Customers & subscriptions
    • Customers
    • Subscriptions
    • Quotes
  • Invoicing
    • Invoices
    • Invoice corrections
      • Credit Notes
      • Refunds on Credited Invoices
    • Payment Collections
    • Tax
    • Currencies & Exchange rates
    • E-invoicing
  • Analytics & reporting
    • Insights
    • Report downloads
    • Revenue Recognition & Deferred Revenue
  • Integrations
    • CRM
    • ERP
    • Email Providers
    • Data Imports: Event File Uploads
    • Data Exports
    • Payment Service Providers
  • Settings & admin
    • Billing entities
    • Payment Options
    • User management
    • Customising invoices
    • Custom fields
    • Default platform settings
    • API key creation
    • Alert Rules
    • Workflows
  • Workflows
    • Workflow Triggers
    • Workflow Actions
    • Monitoring and Audit
    • Common Use Cases
  • For developers
    • Introduction
    • Authentication
    • Local development setup
    • API
    • Errors
    • Troubleshooting
    • Query Parameters
    • Expanding Responses
    • Idempotency
    • Timestamp formatting
    • Webhooks
    • Locale
    • MCP Server
LoginSandbox
On this page
  • Negating events
Invoicing

Invoice corrections

Was this page helpful?
Previous

Credit Notes

Next
Built with

There are several ways to correct invoices. Depending on the use case and what you’d like to show on the invoice to the customer:

  • Ingest negative events for the billing period: negate the events you have sent to the total usage on the invoice is correct
  • Create invoice line adjustments: manual line adjustments for draft or open invoices
  • Issuing a credit note: in case the invoice was already in final status, you can credit it


Negating events

The cleanest way to correct wrongfully ingested usage data is to send negation events. This makes sure the total invoice quantity and events are correct, meaning the customer can still see the correct usage and there is no need to have an extra invoice line with a refund.

Important to note is that you need to create the event as a ‘mirror’ event with the same meter properties, in case you have price rules that might be triggered by the event.

The correction event can be ingested either manually, with a file upload, or through the API just like in your regular ingestion process.