Review invoices and payment settings
Review invoice identity, period, currency, tax, line items, and payment configuration without exposing financial credentials.
Audience, roles, and scope
Admin invoice and payment-setting views; the issued invoice, contract, payment processor, and finance ledger are authoritative.
Who this is for
- Authorized billing and finance users
Roles
- Billing administrator
- Finance reviewer
Before you begin
- Billing authorization
- Known legal entity and billing period
- Approved secure finance workflow
Article tags
- invoices
- payments
- billing
- tax
- reconciliation
Procedures
Follow the sequence and stop when identity, authorization, target, or result differs from the article.
Review an invoice
Reconcile the document before approval or dispute.
- 1Confirm invoice identity
Verify legal entity, invoice number, issue and service dates, currency, tax identifiers, and payment status.
- 2Reconcile line items
Compare products, quantities, rates, discounts, taxes, credits, and totals with approved orders and subscription changes.
- 3Resolve through the finance path
Approve under policy or open a sanitized billing case with disputed lines and supporting order references.
The invoice is reconciled or a specific, traceable discrepancy is raised without disclosing payment secrets.
Security and data handling
- Use only the identity, tenant, role, and data scope approved for the task.
- Verify targets and expected effects before saving, sending, publishing, exporting, deleting, or approving.
- Keep secrets and regulated data out of screenshots, URLs, free-text diagnostics, and ordinary support messages.
- Never place full payment-card details, bank credentials, or unredacted invoices in ordinary support messages.
Known limitations
- UI status can lag payment-processor or accounting records and does not change contractual payment obligations.
- Supported payment methods and editable fields depend on region, contract, processor, and deployment.
Troubleshooting
You cannot open Vianordis Admin
Likely cause: The session expired, the account is not entitled, or the required tenant or role claim is missing.
- Open the service through the approved Vianordis entry point and sign in again.
- Confirm the intended organization, tenant, and account are in use.
- If access remains denied, record the time and request an entitlement check; do not attempt direct-URL bypasses.
A documented control or navigation item is not visible
Likely cause: The current role, subscription, tenant configuration, release status, or feature flag does not expose it.
- Confirm the audience, role, prerequisites, and limitations in this article.
- Refresh after a new sign-in and verify the correct tenant context.
- Ask the responsible administrator whether the capability is enabled before reporting a defect.
A saved change or background result is not visible
Likely cause: Validation failed, processing is incomplete, the view is stale, or the feature is locally simulated rather than persisted.
- Review inline validation, status indicators, filters, and the selected tenant or workspace.
- Refresh once and search by a stable identifier before repeating the action.
- Do not repeat irreversible or externally visible actions until the first operation's state is known.
Source verification
Invoice list/detail and payment-settings interfaces were reviewed in the pinned source.
Reviewed paths at 8f3a86e
src/app/(base)/subscription/invoices/InvoicesView.tsxsrc/app/(base)/subscription/payment/PaymentView.tsxsrc/database/invoices.tssrc/database/billing.ts
Contact support
Contact support when
- A repeatable Vianordis Admin error blocks an approved task
- Expected access, tenant scope, data, or status appears incorrect
- A security, privacy, financial, compliance, or data-loss concern is suspected
Include
- The page, action, expected result, and exact error text
- The time of occurrence with time zone and whether it is reproducible
- Your tenant, role, browser, and sanitized record or correlation identifier
- The troubleshooting steps already completed
Never include
- Passwords, access tokens, API keys, recovery codes, session cookies, or private keys
- Unredacted personal, financial, health, student, employee, or other regulated data
- Confidential documents or message bodies unless support provides an approved secure channel