> ## Documentation Index > > Fetch the complete documentation index at: https://lithi.ai/llms.txt > > Use this file to discover all available pages before exploring further. --- title: Invoices and NET30 terms description: >- Read the due date from the agreement that applies to your account, check the invoice, and request an adjustment or raise a dispute through the supported path. route: /docs/compute/billing/invoices-and-net30 page_id: docs-compute-billing-invoices-and-net30 page_type: howTo content_layer: guided documentation surface_profile: guided_docs audience: Compute finance and procurement teams handling an invoice voice: D reader_question: When is my Compute invoice due, and what do I check before paying it? primary_action: Open your current invoice source_locale: en-US source_status: APPROVED source_version: docs-compute-billing-invoices-and-net30-en-us-2026-09-05-v1 last_updated: '2026-09-05' robots: index claim_registry_pinned: true claim_registry_resync: "npm run governed:tsx -- scripts/build-compute-public-claim-registry.ts --write" --- ## Before you start NET30 names a payment term where an invoice falls due thirty days after it is issued. Your account may or may not be on it. The agreement signed for your account states the term that actually applies. Read the due date from the invoice and the agreement, never from this page. You need a member role that can read finance records. A work key cannot read or settle an invoice. ## Find the due date that applies 1. Open the invoice for the period you are paying. 2. Read the issue date, the due date and the currency printed on it. 3. Check that due date against your signed agreement, in case an amendment changed the term. Where the invoice and the agreement disagree, treat the agreement as the authority and raise the difference before you pay. ## Check the invoice before you approve it Confirm the legal entity, the account or project, the billing period and the currency. Then confirm the totals against the statement for the same period. A resolved question is worth recording. Note where each confirmed fact came from, so the next person does not re-open it. Do not guess a tax treatment, an entity or a purchase-order rule to make an invoice fit a template. An unresolved fact is a question for your finance owner. ## Request an adjustment An adjustment corrects a charge that the evidence does not support. It arrives as a new line rather than an edit to the invoice you already hold. Send the invoice reference, the period and the line you are questioning. See [adjustments and disputes](/docs/compute/billing/adjustments-and-disputes) for the full evidence list and the escalation path. ## Raise a dispute A dispute is the escalation when an adjustment request has not resolved the difference. It stays attached to the specific invoice and line. While a dispute is open, the rest of the invoice keeps its own due date. Nothing about an open dispute changes a payment record on its own. ## What stays outside automation Legal and tax interpretation is never decided by an automated step. That includes entity determination, tax treatment, withholding and any accounting classification. Interest, late-payment consequences and any early-payment term are stated in your agreement. No figure of that kind is published here or inferred from an example. Your invoice remains the Lithi billing record. A label applied inside your own finance system is an annotation, not settlement — [payment states](/docs/compute/billing/payment-states) sets out that boundary exactly.