Production Readiness
Use this checklist before moving your Vayu billing workflows into production.
Production Readiness
Use this checklist before moving your Vayu billing workflows into production.
Production readiness is the point where your implementation moves from configuration and testing into live billing operations. Before go-live, confirm that the data entering Vayu is accurate, that your products and contracts reflect the commercial terms you expect to bill, and that invoices, payments, tax, and connected systems behave correctly from end to end.
Not every item applies to every implementation. Review the sections that match how you use Vayu, test representative billing scenarios, and make sure the teams responsible for each workflow know what to expect once production billing begins.
Usage Data
- Confirm that production events are reaching Vayu and mapping to the correct customers.
- Test retries, duplicate events, late usage, corrections, and backfills.
- Compare representative usage totals in Vayu with the source data.
Related documentation:
Customers and Contracts
- Verify customer details, billing contacts, currencies, payment terms, and legal entities.
- Confirm that production products, pricing, and contract terms are configured correctly.
- Review contract dates, billing cadence, and whether charges are billed in advance or arrears.
- Test the pricing models and contract changes you expect to use in production.
Related documentation:
Run a Test Billing Cycle
Before going live, run at least one complete billing cycle using representative customers and production-equivalent data.
Use this test to confirm that Vayu produces the invoices you expect.
- Confirm that the correct invoices are generated.
- Compare usage quantities with the underlying source data.
- Verify fixed and usage-based charges, discounts, credits, commitments, and proration.
- Compare draft invoice line items and totals with the signed contract or an independently calculated expected result.
- Include at least one relevant edge case, such as a partial period, contract change, or corrected usage.
The test is successful when the data entering Vayu, the pricing logic applied to it, and the resulting invoice all match the expected commercial terms.
Related documentation:
Invoices, Tax, and Payments
- Review the invoice workflow and define who reviews and approves invoices.
- Verify invoice dates, due dates, customer-facing details, and invoice templates.
- Confirm what should happen automatically when an invoice is approved, including issuing, emailing, syncing, or collecting it.
- Test the tax calculation method used by your implementation.
- If you collect payments through Vayu integrations, test successful and failed payments, refunds, credits, and manual payments.
- Make sure test invoices cannot reach real customers or production financial systems.
Related documentation:
Integrations and Reconciliation
-
Confirm which system is the source of truth for customers, invoices, payments, and tax.
-
Validate production credentials and required mappings.
-
Test both a successful sync and at least one failed-sync scenario.
-
Run the complete billing workflow through the systems you use:
Contract → Usage → Draft Invoice → Approval → Tax → ERP/Payment Provider → Payment Status -
Compare identifiers and financial totals between Vayu and each connected system.
Related documentation:
Operational Readiness
- Confirm that the correct workspace members and roles are configured in Vayu.
- Make sure the teams responsible for billing, finance, support, and engineering know which Vayu workflows they own.
- Define who handles usage discrepancies, failed integrations, invoice corrections, and other billing exceptions.
- Confirm that invoice delivery issues, failed dunning runs, integration errors, and webhook failures are reviewed by the appropriate team.
Related documentation:
Final Sign-Off
Before moving to production, confirm that each applicable workflow has been tested and that Vayu produces the expected billing and financial results.