Valqio Docs
Platform

Billing sync

How Valqio connects runtime usage outcomes to billing-provider workflows.

Valqio does not replace your billing provider. Billing providers invoice, collect payment, manage taxes, and hold commercial records. Valqio records the runtime usage, decisions, reservations, commits, releases, and evidence those billing workflows need.

What Valqio sends downstream

Valqio can prepare billing-facing records from runtime activity:

  • customer and environment context
  • product action, meter, or usage-control key
  • quantity and billing period
  • allow, deny, commit, release, or usage outcome
  • idempotency key and request identity
  • draft invoice preview lines
  • export readiness and Stripe provider status

Use this evidence to explain how runtime activity became a billable or non-billable billing record.

Draft invoices

Draft invoices are reviewable previews. They help finance and operators answer:

  • Which customer generated usage in the period?
  • Which meters or product actions contributed to the preview?
  • Which usage lines are ready to export?
  • Which lines are blocked, failed, or need review?
  • Which Stripe connection will receive the export?

Nothing should be sent to a billing provider until the draft invoice is ready and an authorized operator or automation exports it.

Provider boundary

ResponsibilityValqioBilling provider
Decide before product work runsYesNo
Record runtime evidenceYesNo
Track usage transaction lifecycleYesNo
Prepare usage for billing syncYesSometimes
Create invoicesNoYes
Collect paymentNoYes
Manage taxes and commercial recordsNoYes

This boundary is deliberate. Billing sends invoices. Valqio decides whether the product action should run and records what happened.

Operational checks

Before exporting usage, verify:

  1. The customer has the expected billing relationship.
  2. The usage period matches the invoice period.
  3. The draft invoice lines match runtime evidence.
  4. The Stripe connection is active.
  5. Export readiness has no blocking errors.
  6. Support can trace a line back to decision evidence or runtime activity.

If billing sync is delayed, your app should still call Valqio before product work. The runtime decision path remains the authority for whether work should run.

Draft invoice export path

For billing provider export, currently Stripe, review:

  1. The draft invoice customer, period, currency, and total.
  2. Usage source context for each metered line.
  3. Recent usage by meter for the same customer and period.
  4. Exportable lines and lines that are blocked or failed.
  5. The selected Stripe connection.
  6. Provider IDs returned by Stripe and export evidence after a successful export.

This gives finance a review step without moving decision authority into the billing provider.

On this page