Tenant Configuration — Admin Guide

The settings on Admin → Configuration that describe your company to the platform: who you are, where your books live, which modules are on, and how Arcvue signs its own emails.

Who does this: an administrator, mostly once during setup. A handful of these change later; most never do.

How to read this page

Settings are grouped on screen, and the groups are the useful unit — each one is a different question about your company. Only a few settings carry an explanation underneath them; most show their label alone, so this page exists to say what the rest are for.

warning

This page does not list the values each setting accepts. Where a setting has a fixed set of choices the screen offers them, and where it does not the server is what decides. A written list of legal values in a document is a second copy of a fact the code already owns, and second copies drift — read the control.

Company Settings

Who you are, and how figures are labeled everywhere else.

• Company Name — the full legal name, used wherever the platform names you.
• Short Name — the compact form, for places a full name will not fit.
• Organization Type — what kind of business this is, and it decides which screens appear. A government contractor sees every screen. A commercial business does not see the ones built only for government contracting, such as indirect and provisional rates, the incurred-cost submission, cost pools and government property; a link to one of them shows a note saying so instead. Nothing is deleted when you change it: change it back and those screens return with everything they held. A company that has never chosen reads as a government contractor.
• Fiscal Year Start Month — the month your fiscal year begins. Almost every period, comparison and roll-forward in the platform is derived from this, so it is the one on this card to get right first.
• Currency — the currency figures are presented in.
• First Display Year — the earliest year the platform will show. Use it to keep pre-Arcvue history out of views that would otherwise open on empty columns.

ERP Connection

Where your books live, and how Arcvue reads them. To choose the source itself, see Connecting Your ERP Source — this section covers what sits around that choice.

Connection

• ERP Type — the accounting system of record.
• Connection String — how Arcvue reaches it, where an external system needs one.
• Statements Source — whose book the Income Statement, Balance Sheet and contract actuals are rebuilt from on each sync: the ERP feed above, or the Arcvue Accounting posted book for every period it holds. Choose the book once your history is posted there; an external feed keeps running for everything else until it is switched off. Left empty it reads as the ERP feed, unless the ERP Type is Arcvue Accounting.
• CRM Type — the pipeline source feeding business development.

Division

• Division Field — which field in your ERP carries the division.
• Division Mapping — how those values map onto the divisions Arcvue shows. Get this wrong and the numbers are right while the org chart is not, which is harder to notice than a wrong total.

Close Dates

• Close Date Source — whether the books-closed date arrives from your ERP on sync, or an admin sets it here by hand.
• Close Date Method — how your monthly close actually works: on a predictable schedule, on a date that varies and is set by hand, or directly by your accountant.
• Close Date Reminder — whether Arcvue reminds you as a close approaches. It changes notifications only: no reminder moves a close date or holds a period open. Turn it off if the reminders are noise rather than help.

Consolidated legal entities — the entity codes included in consolidated financial statements. This is a consolidation instruction, not a filter on who exists: an entity left out still has its data, it simply does not roll up here.

• Legacy ERP name — the accounting system this company is moving from, as the product should name it wherever it refers to the prior system. Empty gives a generic phrase.

Platform

AI

• AI Enabled — the master switch for every AI-backed feature.
• LLM Provider and LLM Model — which model answers.

Workforce

• Billable Hours per FTE — the annual denominator under utilization.
• Has SCA Labor — whether Service Contract Act work applies to you, which changes what the platform asks for elsewhere.
• Invite New Hires from Payroll — when on, each morning's payroll roster gives every newly added person an Employee login and an email invitation. Only people added after you switch it on are invited; see the Users, Permissions and Access guide.
• Switch Off Former Employees' Logins — when on, the login of anyone who has left payroll is switched off once the grace period below has passed. Administrators are never switched off automatically; see the Users, Permissions and Access guide.
• Days Before a Former Employee's Login Is Switched Off — the grace period, in days after the payroll termination date (3 by default), so a final timesheet can still be entered.

Modules & Misc

• Active Modules — which modules this tenant has.

On their own

• Historical Win Rate — the default win-rate assumption for pipeline value. It is an assumption, not a measurement — the pipeline uses it until there is enough of your own history to speak for itself.
• Indirect Rate Correlation — the correlation method behind indirect rate trends.
• NEO Whitelist Users — the usernames with NEO access, comma-separated.

Advanced

• Telemetry Enabled — whether the platform reports its own usage.
• Platform Name — what the product calls itself in your instance.
• MFA Issuer Label — the name that appears in an authenticator app beside a user's code. Set it to something a person recognizes: it is what they will read at 8am while trying to log in, and a default label beside six other entries is how the wrong code gets typed.
• Revenue account prefixes and Operating expense account prefixes — under Lender model export. The lender model export decides which GL accounts count as revenue and which as operating expense by the leading digits of the account code. The defaults (["4"] for revenue, ["7", "8"] for opex) match the chart most GovCon firms start with. Change them only if your chart numbers those accounts differently; the value is a JSON list of prefixes, and a prefix that matches nothing silently drops that side of the export to zero. These two were hidden until 2026-09-02 on the belief that nothing read them; the export does.

Email & Branding

Email

• Email Provider — who sends platform mail.
• From Address — the address it comes from.
• Footer Text and Footer URL — the line at the bottom of every message and where it points.

Branding

• Primary Brand Color and Secondary Brand Color — the two colors applied to platform mail and branded surfaces.
• Brand Font — the font name written into the report documents Arcvue exports for you (the Excel and PowerPoint files carry it; a viewer without that font substitutes its own). Barlow unless you set one.

Covenants

The definitions the covenant engine uses. These are not the covenants themselves — they are how the platform reads yours.

• DSCR Instrument Types — which debt instruments count toward debt-service coverage.
• Leverage Instrument Types — which count toward leverage.
• EBITDA Definition — the EBITDA basis your agreements are tested on.

warning

Your lender's definitions govern, not the platform's defaults. A covenant computed on the wrong instrument set or the wrong EBITDA basis produces a confident number that does not match the certificate you have to sign. Read these against the agreement before you rely on a covenant result.

Treasury

How the treasury page classifies cash movements. Each pattern list is a JSON list of UPPERCASE substrings matched against the GL description of a movement; a match files the line under that class.

• Payroll patterns — descriptions that mark a movement as payroll.
• Debt service patterns — descriptions that mark a movement as debt service.
• Intercompany patterns — descriptions that mark a movement as intercompany.
• Line of credit patterns — descriptions that mark a draw or paydown on the line of credit.
• Agency prefix overrides — a JSON dict of your own counterparty prefixes to readable names (subcontractors, JV partners), so their deposits and payments carry a name instead of a code.

M&A

What the M&A engine and Value Builder read about the acquirer.

• Acquirer entity — the entity code whose actuals feed the acquirer side of the M&A historicals.
• Existing debt account map — a JSON dict mapping the acquirer's existing debt GL accounts to the role each plays in a deal. Empty lets the note patterns decide.
• Surviving note patterns / Retirable note patterns — JSON lists of substrings matched against the acquirer's note names; a match marks the note as surviving the transaction, or as retired at close.
• Surviving note label / Retirable note label — what the pro forma and the sources and uses call those two groups.
• Show implied multiple — set to 1 to show the implied valuation multiple on Value Builder. The engine computes it either way; this only shows it.

Waterfall

• Org prefix map — a JSON dict mapping the legacy ERP's project-owning-org prefixes to the entity codes the contract waterfall reports under.
• Minimum attribution year — the earliest year the waterfall renders contract-level revenue and gross profit. Earlier years are clamped out, for history booked in bulk with no project to attribute it to.

AI Configuration — the provider key

Three controls sit on the key, and they are deliberately separate acts:

Control	What it does
Save Key	Checks the key in the field with the provider, then stores it. A key the provider refuses is not stored. Reads Saving... while it works.
Test Connection	Checks the key in the field with the provider and reports back without storing it, reading Testing... while it waits.
Confirm Remove	Deletes the key, reading Removing... while it works.

Both buttons act on the key in the field, and only Save stores it. Save clears the field once the key is stored, so both stay unavailable until you paste a key again.

Separate from the settings list, AI Configuration is where the model provider's API key lives. Choose the provider — Anthropic (Claude), Google (Gemini), OpenAI or Azure OpenAI — pick a Model (the list is Arcvue's supported catalog for that provider; a model the provider does not serve is refused when saved, and switching provider moves the model to that provider's default), and paste the key; the card links to the provider's console and shows the key prefix it expects, so a key pasted from the wrong provider is caught before it is saved.

Saving checks the key with the provider first. Save runs the same check as Test Connection before it stores anything. A key the provider refuses is not saved, and the provider's reason stays beside the field, so a key that would fail on every call never reads as configured. A key that passes is saved and the card reads Connected. Saved — not yet tested shows only for a key that has not been through a check, and Not configured — AI disabled when there is no key. To check a stored key again, paste it back into the field and press Test Connection. Remove Key deletes it.

Azure OpenAI asks for one more thing than the others, because it is reached at your own resource rather than a shared address: an Endpoint beside the key, which is the URL on your Azure OpenAI resource's Keys and Endpoint page. Its model list is deliberately the same as OpenAI's, and that is a constraint rather than a convenience. Azure sends the deployment name where the other providers send a model id, so the deployment you name here has to be the one serving that model. Name your Azure deployment after the model it serves and the two stay in step; call it something else and the key will test clean while calls fail, because Arcvue is asking Azure for a deployment that does not exist.

Without a key, every AI-backed feature is unavailable — NEO says so in as many words when you open it.

Token budget — a monthly ceiling you can see coming

Below AI Configuration, the Token budget card holds two settings and one meter. Monthly token budget is a whole number of tokens (your provider's unit, because it is your key); Save stores it, and 0 or blank removes it. When the budget is reached is what the platform does at 100%: Warn only (the default) keeps model calls running and turns the meter red; Stop model calls at 100% has the platform refuse every further model call for this tenant -- the Bookkeeper, contract and invoice extraction, NEO, the observer, every AI-backed feature -- until the month rolls over or the budget is raised. Each refusal names the budget and points back here. The choice saves as you make it and takes effect within a minute. The This month meter -- the panel heads it Token budget this month -- puts what your model calls have used since the first of the month — context sent, read from cache, written to cache, and the answers, across both the Financial Intelligence and Accounting ledgers — against that budget: green under 80%, amber from 80%, red at 100%. The meter reads Tokens used against the monthly budget, which is the right way to read it: consumption against a ceiling you set, not a bill. Under it, the pace line says where the month lands if use continues at the average rate so far and, if that line crosses the budget, the day it would cross. A ledger that could not be read is named rather than counted as zero. The last line states plainly whether the budget stops model calls or only warns here -- and when a ledger cannot be read, a stop is unenforceable rather than exceeded: calls proceed and the platform says so, because it never refuses on a number nobody measured.

Editing

Settings edit in place. Cancel abandons the edit and leaves the stored value alone; nothing changes until you save.

Related

• Connecting Your ERP Source — choosing the accounting system itself.
• Account Access — users, roles and what each may reach.
• Configuration You Must Get Right in Week One — the accounting-side setup (GL mapping, indirect pools, exclusions, workable days, P&L structure).