Commercial agreements and invoicing
Status: Upcoming — not yet available.
Section: DOC-EN-commercial-agreements#overview.
An organization already runs an application and now needs negotiated rates, purchasing approval and invoices its finance team can reconcile. Follow the buying recipe below: agree the offer, retain the approved revision, activate the covered services in the existing workspace, then verify the first invoice.
Have an authorized buyer and payer, the workspace and projects covered, expected usage, deployment/support needs and any procurement requirements. A new customer also completes first-project onboarding; an existing customer keeps its projects unless it chooses a separate migration.
Availability: Quote, onboarding, plan-change and invoice interfaces are planned. For an agreement or billing question now, use the approved terms and contacts supplied by your contracting parties. This page sets no price, payment deadline or service commitment.
1. Compare a complete offer for the application
Status: Upcoming — not yet available.
Section: DOC-EN-commercial-agreements#configure-and-review-quote.
Work with the Travila commercial team to assemble an offer for your intended workload: capabilities, quantities, usage assumptions, commitments, add-ons, deployment and support. Resolve unavailable options or incompatible combinations before purchasing approval. Compare the complete recurring and usage-based cost; a lower fixed fee is not necessarily a lower total bill.
Record the selected cloud provider, operating arrangement, any dedicated deployment, primary, backup and recovery regions, and private connections. The offer identifies the agreed charges for these choices, including any setup, reserved capacity, cloud- and region-specific infrastructure or transfer, connection operation and support charges. Review what is included, how additional usage is measured and which prerequisites must be ready; no deployment choice becomes available merely by appearing on a quote.
Compare the recurring, usage-based and one-time charges, currency, applicable discounts, expected tax treatment and the assumptions behind any estimate. Check the offer's validity and required approvals. An estimate based on expected usage is not a promise that your final invoice will equal that amount.
Keep the exact revision you accept. A revised scope or price needs the applicable approval again; an expired or withdrawn offer cannot be newly accepted. Accepting the quote and activating the agreed services are separate steps.
2. Approve the exact terms and payer
Status: Upcoming — not yet available.
Section: DOC-EN-commercial-agreements#agreement-review.
Before accepting an agreement, review the scope and the people authorized to approve it:
- Identify the contracting organizations, the offering and accounts or projects covered, and the people authorized to approve on each party's behalf.
- Identify the legal payer and confirm that its authorized representative approves the covered billing scope and obligations. A billing contact or invoice recipient may have a different role.
- Review the proposed currency, charging units, custom rate revision, commitments, allowances and overage rules. Record any agreed allowance expiry, carryover or renewal treatment explicitly.
- Confirm the agreement's effective dates, renewal or termination terms, billing cadence and negotiated payment terms. Check which revision will apply when usage crosses a change date.
- Provide the applicable billing name, contact and addresses, required invoice identifiers and a purchase-order reference where agreed. Have the contracting parties confirm applicable invoicing and tax requirements.
- Retain the exact approved agreement and its references. A revised price or expanded payer obligation needs the applicable approval before it becomes effective.
Keep the approved revision with its scope, dates, prices and payer consent. Missing approval or an incomplete charging rule leaves the proposal unresolved. Historical price examples and informal account settings do not establish the agreed terms.
3. Bring the agreed services into use
Status: Upcoming — not yet available.
Section: DOC-EN-commercial-agreements#enterprise-onboarding.
Follow one onboarding plan with your sponsor and Travila contact. It covers the workspace, security and procurement reviews, billing, deployment prerequisites and handover. Each milestone shows its progress; a blocked step names the person responsible and the next action.
For a new organization, creating the first project is part of onboarding. Obtaining its credentials is a separate explicit step. For an existing workspace, onboarding reuses the projects and integrations you already operate unless you expressly choose a separate migration.
Your onboarding plan shows readiness separately for the deployment, sign-in policy, support arrangement and any regulated-data use. Signing the quote does not complete those steps. See first-project onboarding and assurance and support.
For the selected deployment, carry the approved cloud provider, deployment configuration, dedicated scope, data locations and private connection requirements into the setup plan. Assign customer and Travila owners for provisioning, access, network approvals, a representative application check and recovery checks. Handover records the supported configuration, operating responsibilities and any blockers before the affected services can become ready. Keep any move from an existing deployment, cloud provider or region in a separate approved migration plan.
Existing customer: apply the agreement to the current workspace
Status: Upcoming — not yet available.
Section: DOC-EN-commercial-agreements#standard-to-enterprise.
Apply accepted Enterprise terms to your existing eligible workspace without recreating its projects. Review the payer, covered scope, effective date, billing treatment and readiness work before approving the transition.
The conversion preserves project and resource identities, authorized credentials and integrations, usage records and invoice history. It does not merge organizations, move data to another cloud provider or region, reset a signup allowance or grant a person more access. A separate migration or identity change requires its own approved plan.
Until all required steps are confirmed, the transition shows what is pending or blocked and which terms are active. A successful billing update alone does not establish that every contracted capability is ready.
4. Reconcile the first invoice against the agreement
Status: Upcoming — not yet available.
Section: DOC-EN-commercial-agreements#invoice-review.
Use the approved agreement revision and billing period from the buying steps above. Match each line to its project or agreed scope, quantity, unit and rate, then account for allowances, credits and adjustments. Keep any unexplained difference tied to the original invoice for the dispute workflow.
The invoice should identify the following information:
| Information | What it explains |
|---|---|
| Issuer, billed organization and invoice identifier | Which parties and document the invoice concerns |
| Agreement and rate revision | Which accepted commercial terms produced the charges |
| Billing period and attributable scope | Which project or agreed billing scope incurred the charge and when |
| Quantities, units and prices | How usage or commitments contribute to each line |
| Allowances, overage and credits | How the applicable agreed rules change the amount due |
| Currency, issue date, due date and PO reference where agreed | How to match the invoice to approved purchasing and payment terms |
| Payments, adjustments and remaining balance | What has been reconciled and what remains outstanding |
A later price, billing address or renewal does not rewrite an issued invoice. Corrections identify the original invoice and preserve its history.
5. Follow payment and any remaining balance
Status: Upcoming — not yet available.
Section: DOC-EN-commercial-agreements#invoice-and-payment-status.
An invoice can be issued while delivery is pending or failed. Sent records delivery status; it does not mean the invoice is paid. Due and overdue depend on the agreed payment terms and remaining balance. Paid requires reconciled payment or applicable credit allocation. A partial payment leaves a visible remainder. An uncertain payment stays pending or unknown until reconciled.
Voided preserves the original document and its history under the applicable correction rules. If money was already allocated, its disposition needs a separate explanation. A credit note or adjustment can change the amount due; it does not by itself confirm a cash refund.
Recover a disputed charge or uncertain payment
Status: Upcoming — not yet available.
Section: DOC-EN-commercial-agreements#billing-disputes.
Keep the invoice identifier, affected line references, agreement/rate revision and relevant payment references. Use the billing dispute channel agreed with the contracting parties and request a tracked outcome. Avoid sending payment secrets or complete card details.
The dispute record identifies what is under review and any resulting approved correction. Raising a dispute does not itself establish a changed due date, waived charge or refund. If a payment outcome is uncertain, have it reconciled before initiating a replacement payment. Preserve both the original invoice and any linked credit note or adjustment.
See billing and spend for allowances, spending controls, usage records and payment uncertainty. See assurance and support for evaluating service commitments, and Travila for Enterprise for the documentation map.
Variant: expand, reduce or renew the agreement
Status: Upcoming — not yet available.
Section: DOC-EN-commercial-agreements#change-enterprise-plan.
Start an expansion, reduced commitment or renewal by reviewing the proposed replacement terms. Compare what changes, which services are ready, who pays and when the new terms take effect. The agreed date may depend on the contract and required preparation; this guide sets no immediate-upgrade default.
Changing the cloud provider, dedicated capacity, the operating arrangement, a hosting region or private connectivity also needs the applicable deployment change and readiness checks. Review any setup, ongoing, transfer or retirement charges in the revised offer. A commercial tier change alone does not move data, hand over operations or remove a private connection.
Before accepting, inspect the treatment of the remaining billing period, incurred and late-reported usage, commitments, unused allowances, paid or promotional credits, possible prorations and outstanding invoices. A lower fixed fee can still have higher usage charges, so compare the complete offer.
The transition status distinguishes a proposed or scheduled change from one already applied. If confirmation is lost, recover the original transition before submitting another. After an effect has occurred, an authorized correction preserves the earlier terms and financial history.
Variant: return to a smaller or standard plan
Status: Upcoming — not yet available.
Section: DOC-EN-commercial-agreements#downgrade-or-exit.
Begin before the requested change date. Choose a narrower Enterprise package or an eligible standard plan, then review notice terms, remaining obligations and the exact capabilities, limits and support arrangements that would change. Downgrading is separate from deleting the workspace.
Before the change takes effect, Travila identifies features and resources that the target plan cannot support, including Enterprise sign-in, user provisioning, retention, regional controls and active integrations. Review the affected items and complete the stated prerequisites, including a working sign-in and recovery route for an authorized administrator. Required protections, held records and customer data stay protected while you resolve the transition.
The transition explains blockers, permitted remedies, any restriction on new work and the approved read/export arrangements. If the target cannot support required security or processing commitments, the affected change needs an approved alternative or migration. This guide promises no automatic grace period, refund, debt waiver or release from a processing agreement.
Withdraw or reschedule a pending change when the agreement and current state permit it. An already applied change needs a separately authorized correction; it cannot erase issued invoices or reverse a payment by changing a plan label.
Document ID: DOC-EN-commercial-agreements. Section identities and revisions.