--- title: "Services in detail" description: "Every ERP Access service with deliverables, how the output is checked, typical starting points and engagement shapes." url: https://erp-access.com/vendor/services/ updated: 2026-11-14 publisher: "ERP Access, Inc." --- # Services in detail ERP Access offers five services. They share one team and one rule: Claude reads and drafts, deterministic code verifies and calculates, and a named person approves anything that reaches a system of record. Most clients start with one service and add a second once the first is running. ## Claude systems for operations **Who it is for:** finance, leasing, lending and operations teams that re-key data by hand between documents, email and a system of record. **What gets built** - **Document-to-system pipelines.** Documents in (leases, letters of intent, UCC filings, invoices, vendor statements, email), validated records out. Each extracted value is traced to its source; a value the source doesn't support is refused and routed to a person. - **Agents on ERP data.** Claude reading and acting on NetSuite or SAP data through governed connectors, with every action logged. - **Portals for the people who approve.** A single web application where reviewers see what was drafted, what code verified, and what needs their decision. Access rules are enforced in the database, not only in the interface. - **Claude rollout.** Claude, Claude Code and connectors set up for a team and wired into the systems it already uses, with access matching the org chart. - **Evals and guardrails.** Regression test suites, evaluation sets, and independent review passes before anything goes live. **How it is checked** - Amounts, dates, rates and escalations are computed or checked by code against bounded rules. - Refusal is the default when evidence is missing. - Every exception a reviewer catches becomes a proposed rule. - A client-side reviewer approves releases. **Reference engagement:** George Urban Advisors (see [case studies](https://erp-access.com/vendor/case-studies/#george-urban-advisors)). ## Claude for NetSuite **Who it is for:** companies already on NetSuite that want Claude working with their ERP without putting the ledger at risk. Oracle publishes the NetSuite AI Connector Service, which connects AI clients such as Claude to NetSuite through the Model Context Protocol (MCP). Connecting is the easy part. ERP Access provides three stages, each useful on its own: **Connect, safely** - A dedicated NetSuite role for Claude with only the permissions the pilot needs, never an administrator role. - Sandbox first, then production for a small group, expanding role by role. - Read-only to start; record changes are enabled only for a tested workflow, with a person approving each change. - Integration capacity checked: NetSuite shares one web-services concurrency limit across all integrations, so heavy AI queries and extracts are scheduled so they don't starve existing feeds. - Protected health information stays out of the connector, because Oracle states it has not been assessed for HIPAA. - Roles and connector behavior re-tested in sandbox before each NetSuite release reaches production. **Assess what the account actually uses** (read-only, every action logged) - Configuration census: roles, scripts, workflows, custom records and fields, integrations and enabled features. - Transaction archaeology with SuiteQL: which transaction types are alive, how volume trends, and which records are created by people versus integrations. - Saved searches and reports: which still run. Reported as "no recorded UI execution," never "unused," because NetSuite doesn't stamp searches that scripts or integrations run. - Seats and roles: paid seats compared with the people who actually log in, from the login audit trail. - A keep, simplify or drop verdict for every area, with the evidence attached and an independent review pass before it reaches a renewal conversation. **Rebuild the custom layer, keep NetSuite as the ledger** - Approval chains rewritten as versioned, human-readable policy, checked by re-running recent vendor bills and comparing approvers with what NetSuite actually did. - Accruals and allocations computed by code and delivered as a journal import file a person posts, checked by recomputing last quarter's journals line by line. - Department income statements, cost reports and reconciliations built from ledger data, compared against current outputs for several periods. - Remittance and collection messages drafted for a person to send; nothing goes out automatically. - Cutover rule: a step goes live only after parallel runs show no unexplained differences. Real-time posting, payroll tax and statutory filings stay in NetSuite. ## NetSuite Admin-as-a-Service **Who it is for:** companies that need NetSuite run well week to week without a full in-house team, including through mergers, acquisitions and system transitions. **What it covers** - Integrations and file feeds, including SFTP. - User and role changes. - Period-close fixes and support. - Release upgrade preparation, in production and sandbox. - Claude in the loop for routine work, under the same review rules as everything else. **Also available:** legacy NetSuite consulting, including implementation, integrations, project recovery ("takeover") and trusted-advisor work on ERP decisions. Delivery uses short, reviewed sprints. **Reference engagements:** Medically Home through its combination with DispatchHealth; RAPT Therapeutics (see [case studies](https://erp-access.com/vendor/case-studies/)). ## NetSuite decommissioning and data archiving **Who it is for:** companies being acquired, merging or moving to a new ERP that still need years of NetSuite history. **Five steps, with client sign-off at each** 1. **Keep the lights on.** NetSuite stays supported and closing on time until the cut-over date. 2. **Inventory.** Transactions, master data, file cabinet attachments, payroll history, customizations and integrations are mapped. 3. **Extract and archive.** Transactions, attachments and NetSuite Payroll records go into archive reports in the format the receiving team asks for, starting with samples they sign off on. 4. **Reconcile and hand off.** Archived totals are tied back to NetSuite and delivered with the documentation auditors will ask for. 5. **Shut down cleanly.** Integrations, users and licenses are retired on a schedule, so nothing breaks and nothing is left running. **Facts buyers often miss** - Oracle's hosting policy gives a 60-day retrieval window after termination before data is deleted. Plan extraction before the contract decision. - Oracle documents that the Full CSV Export does not cover all data: transactions arrive only as a report extract, and File Cabinet attachments are not included. - ERP Access maps every route out: SuiteAnalytics Connect, SuiteQL and REST, saved-search and report exports, File Cabinet downloads, system notes for the audit trail, and SuiteCloud export for customizations. **Reference engagement:** RAPT Therapeutics. ## SaaS teardown and replacement **Who it is for:** finance and operations leaders paying for software they suspect they barely use, especially ahead of a renewal. ERP Access's open-source method, [SaaS Rebuild](https://github.com/chrbailey/saas-rebuild) (MIT license), audits a tenant the client administers: it preserves the data, shows which features are actually used, and produces an evidence-cited KEEP, SIMPLIFY, DROP or DEFER verdict for every feature, plus an export plan and preservation manifest. The schemas reject any verdict without cited evidence. The aim is to replace a whole tool or a whole manual role and save real money, not to add AI on top of what the client already pays for. ## Engagement shapes - **Fixed-scope assessment.** A read-only review of one process or one NetSuite account, ending in a written verdict and build plan. - **Build engagement.** One system built, tested and handed over with a client-side approver in place. - **Monthly retainer.** NetSuite Admin-as-a-Service, and ongoing support for systems ERP Access has built. Pricing is scoped per engagement. Ask info@erp-access.com for a quote. ## Federal and public sector As an SDVOSB registered in SAM.gov (UEI EG2FYMHACW73, CAGE 10PQ0), ERP Access can support set-aside opportunities for ERP support, data archiving and AI document processing. The firm monitors SAM.gov opportunities daily.