Frequently asked questions

Vista Recon is Altura's settlement reconciliation product for multi-channel commerce brands on NetSuite. It turns marketplace, processor, and wholesale settlement files into controlled journal entries, holds unresolved differences for review, and keeps a human as the posting authority. Nothing posts to your books until a person has seen the tie-out and approved it.

Vista Recon reads the source file, applies finance-approved mappings, separates the accounting components behind the net deposit (sales, fees, refunds, taxes, reserves, and adjustments) and builds a proposed NetSuite journal entry. The tie-out and source trail remain visible before a human approves the post, so every line in the entry traces back to a line in the settlement file.

Vista Recon fails closed. Unresolved lines and differences are held back for finance review instead of being guessed, hidden, or force-posted. NetSuite does not change until the exception is resolved and a human approves the result. That is the difference between automation you can audit and automation that moves the reconciliation problem into your general ledger.

No. Vista Recon works from settlement and remittance files, so the reconciliation path is independent of the integration platform that delivered the commerce transactions. The first walkthrough starts with the file and the NetSuite accounting path already in use.

Vista Recon is designed for marketplace, payment-processor, and wholesale or first-party remittance files: Amazon, Shopify payouts, Mirakl-style marketplaces, and wholesale partners among them. Fit depends on the file structure, the available NetSuite records, and the controls required for the resulting journal entry.

The person who owns settlement reconciliation or the NetSuite close should join, along with anyone who can explain the source file and approve the accounting treatment. The session follows one representative file from source to proposed posting path. If your own data will improve the walkthrough, Altura agrees on a secure transfer path before any file changes hands; otherwise we demonstrate with a generic example.

The AI Accelerator is a focused adoption program, not open-ended AI consulting. Altura starts with your operating workflow, teaches safe daily AI use, and packages governed pilot candidates with decision cards, data contracts, risk tiers, owners, and a 30/60/90 measurement path.

Not at the start. The baseline and workshop can begin from interviews, workflow walkthroughs, sample artifacts, and controlled exports. Production access is only considered when a pilot becomes real implementation work, and anything near money, inventory, customers, or controls needs explicit approval and a defined access path.

Start with a workflow that is frequent, painful, explainable, and safe to govern. Good first candidates usually have repeated exceptions, known source systems, clear owners, and a human approval point. The goal is not the flashiest use case; it is the first workflow the team can trust, measure, and repeat.

The Accelerator is designed to leave operators with a shared method, not dependency on a consultant. By the end, the team should understand the decision card, data contract, risk tier, owner, approval points, and measurement path for each candidate. Build support is a separate choice.

After the pilot, there are two doors. Some teams keep ownership internally using the runbook, decision cards, and measurement plan. Others move proven workflows into AlturaCare continuity so Altura helps operate, monitor, and improve them as systems, channels, volume, and exception patterns change.

Success is measured against evidence the workflow can actually produce: fewer unresolved exceptions, clearer ownership, safer approvals, faster root-cause triage, cleaner handoffs, and decisions the team can explain. Altura avoids invented percentages and sets the 30/60/90 path around observable operating signals.

Training is part of it, but the center of the work is governed automation: Altura maps the job, source data, approval path, and risk tier behind a real workflow while operators learn safe daily AI habits. The output is a governed pilot candidate, a workflow ready to run with controls and an owner, not a generic training deck.

Bring the operator who does the work, the leader accountable for the outcome, and the systems owner who understands NetSuite, Celigo, spreadsheets, or the source tools involved. The best sessions include people who know the exceptions and people who can approve how risk is handled.

That is normal and useful. The Accelerator does not require a new tool choice before the work begins. It helps the team turn scattered AI usage into governed operating practice: structured context, approved data boundaries, repeatable prompts where appropriate, human approval, and measurement.

No. The program is designed to make operators more effective and make risky handoffs more governable. AI can help classify, summarize, draft, or route repeatable work, but human approval stays where decisions affect cash, inventory, customers, compliance, or the audit trail.

That is the exact gap the Accelerator closes. Most teams have scattered tabs and pilots that went nowhere because the work started with tools instead of the workflow. We baseline where AI is already hiding, teach your operators to use it safely on your real NetSuite, Shopify, and Celigo stack, then package the highest-friction work into governed pilots with an owner and a measurement path.

A course teaches tools and prompts that detach from your controlled NetSuite work. The Accelerator starts from your operating workflow: what an AI-assisted step can read, what it must return, who approves it, and how the result is measured. Your operators learn safe daily habits while Altura converts a real, top-friction task into a governed pilot with a decision card, data contract, and risk tier, not a training deck.

Vista LaunchPad is Altura's productized delivery system for NetSuite and Celigo channel and trading-partner onboarding. It starts from components Altura has already built and tested, adapts them to the customer's NetSuite and Celigo, and validates the complete flow before it carries live volume: match the requirement, adapt the pattern, test and accept, go live with ownership. That applies from the first channel, and the mappings, logic, and change path stay in the environment the customer controls.

No. Vista LaunchPad supports storefront, marketplace, fulfillment, wholesale, and retail EDI work. The common idea is a repeatable channel-onboarding path rather than a new custom project each time.

TradeBridge is the B2B and EDI capability inside Vista LaunchPad. It organizes trading-partner specifications and validation patterns, and runs your partner's exact documents through a test harness before the partner ever schedules a certification test. It is not a separate product or a managed EDI network.

Managed EDI typically puts connectivity and changes through a provider's operating model: every change is another ticket in someone else's queue. LaunchPad deploys into your NetSuite and Celigo environment, so your team owns the flow, the documentation, and the change path.

Altura scopes the partner's actual specification, identifies which patterns fit, and designs the remaining work before build. New or incomplete requirements receive discovery rather than an unsupported speed promise.

Vista LaunchPad is built for NetSuite and Celigo. Altura brings deep NetSuite and Celigo delivery experience as a Celigo Advanced Partner, while each channel or partner still starts with its real requirements.