> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # New Customers (30d), Sage > New Customers (30d) counts the customers added to your Sage customer master in the last 30 days versus the prior period, a clean read on growth and onboarding throughput that should be triangulated against ecommerce acquisition. How to read it, why it matters, and how to act on it. **Card class:** [Non-Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type) > Customers added to the Sage customer master in the last 30 days vs the prior period. A growth and onboarding-throughput signal; pair with ecom acquisition. ## At a glance > The number of new customer records created in your Sage customer master over the last 30 days, compared to the prior 30-day period. For a B2B operation this is the finance-side view of growth: not website signups or marketing leads, but customers that have actually been set up in the ledger with terms, credit limits, and tax details, ready to be invoiced. It is both a growth signal and an onboarding-throughput signal, because a customer cannot generate revenue until they exist in the master. Read it against your ecommerce acquisition numbers to see whether new commerce accounts are flowing through to Sage, and how long the gap is. The card reads the customer master creation dates, dimension-tagged in Sage Intacct so finance can pivot new accounts by Class, Department, Location, or Entity. | | | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **What it counts** | Distinct customer records created in the customer master in the trailing 30 days, compared to the prior 30-day window. The card reads the record creation date, not the date of first sale. | | **Created vs first-invoiced** | Default counts master-record creation. A stricter variant counts first-invoice date instead, which measures customers that became revenue-generating rather than just set up. Configurable in the field map. | | **B2B focus** | Primarily a B2B signal. DTC checkout customers are often not created as full ledger records, so for DTC-heavy businesses this card reflects wholesale and account-based growth specifically. | | **Reactivations** | A returning customer that already has a master record is not new. A genuinely new record for a previously-deleted customer counts. The field map governs reactivation handling. | | **Currency** | The count is currency-independent. Multi-Entity Console surfaces new customers per entity and de-duplicated across the group. | | **Entity scope** | Card respects the dashboard entity filter. | | **Dimensional cut** | New customer records carry Intacct dimensions through. Pivot by Class to see which brand or channel is winning accounts, by Department to attribute wins to a sales team, by Location for regional growth. | | **Time window** | `30D vs prior` | | **Alert trigger** | None by default. This is a growth and throughput signal, not an alarm. Configure a floor if a stall in new-account creation is something you want flagged. | | **Roles** | owner, finance, marketing | ## Calculation Calculated automatically from your Sage data. The card counts distinct customer records created in the trailing 30 days and compares the count to the prior 30-day period. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading. ## Worked example A UK B2B skincare brand on Sage Intacct, single entity, GBP base currency, roughly 13M GBP annual revenue selling wholesale to salons and pharmacies on Net-30 terms through a BigCommerce B2B portal, with a Shopify DTC line on the side. Snapshot 14 Apr 26. The card reads the last 30 days against the prior 30. | New-account source (this period) | New records | Prior period | | ---------------------------------- | ----------- | ------------ | | Salon accounts (independent) | 41 | 33 | | Pharmacy and chain accounts | 9 | 14 | | Distributor / wholesale partners | 4 | 3 | | DTC accounts promoted to wholesale | 6 | 5 | | **New Customers, 30d (this card)** | **60** | **55** | Five things to notice: 1. **60 new accounts this period vs 55 prior is healthy, modest growth, but the composition matters more than the headline.** A flat or rising count built on the right customer types is good; the same count built on low-value one-off accounts while high-value chain accounts dry up is a warning dressed as growth. Here the salon segment grew strongly (41 vs 33) while pharmacy and chain accounts fell (9 vs 14). The net looks fine; the mix shift is the story, and the Class dimension cut is what surfaces it. Pair this card with [Sage Top Customers by Revenue](/nerve-centre/kpi-cards/sage/sage-top-customers-revenue) to check whether new accounts skew toward the segments that actually drive revenue. 2. **This is master-record creation, not first revenue.** A new record means a customer is set up and ready to invoice; it does not mean they have ordered. The gap between accounts created and accounts that place a first order is itself a signal: a healthy onboarding converts most new records into orders quickly. If new-account creation is strong but [Invoiced Revenue](/nerve-centre/kpi-cards/sage/invoiced-revenue) is flat, accounts are being set up but not activated, which points at a sales or onboarding follow-through gap. 3. **The cross-channel read is the most valuable one: do ecom signups become Sage customers, and how fast?** Pair this card with [Ecom Customers Absent from Sage](/nerve-centre/kpi-cards/sage/ecom-customers-absent-from-sage). A B2B portal that registers new trade applicants on BigCommerce should see those accounts flow through to the Sage customer master within the onboarding SLA. If the portal shows 80 new trade signups but Sage shows 60 new records, 20 applicants are stuck somewhere between commerce and finance, unable to be invoiced. That gap is lost or delayed revenue, and only the cross-connector view exposes it. 4. **Onboarding throughput is a real constraint for B2B.** Setting up a wholesale customer in Sage is not instant: it needs terms, a credit check, a credit limit, tax and VAT details, and approval. A surge in trade applications can exceed onboarding capacity, so new-record creation plateaus not because demand fell but because the finance team is the bottleneck. Reading this card against the volume of pending ecom signups tells you whether onboarding is keeping pace. A widening gap is an operational capacity flag, not a demand problem. 5. **Watch for a fall in high-value account creation even when the total holds.** The most dangerous pattern is a steady headline masking a shift away from valuable accounts. Here the drop in pharmacy and chain accounts (your higher-value, higher-volume segment) is worth a conversation even though salons more than offset it on count. Pivot by Class and weight new accounts by expected value, not just number, so a comfortable headline does not hide a deteriorating mix. ## Sibling cards merchants should reference together | Card | Why pair it with New Customers (30d) | | ----------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | | [Sage Active Customers](/nerve-centre/kpi-cards/sage/sage-active-customers) | The stock to this card's flow: new accounts add to the active base. | | [Ecom Customers Absent from Sage](/nerve-centre/kpi-cards/sage/ecom-customers-absent-from-sage) | The onboarding gap: ecom signups that never reached the Sage master. | | [Sage Top Customers by Revenue](/nerve-centre/kpi-cards/sage/sage-top-customers-revenue) | Tests whether new accounts skew toward revenue-driving segments. | | [Invoiced Revenue](/nerve-centre/kpi-cards/sage/invoiced-revenue) | Confirms new accounts are activating into actual billing, not just sitting set up. | | [Customer Churn Signals](/nerve-centre/kpi-cards/sage/customer-churn-signals) | The other side of the ledger: net growth is new minus churned. | | [Active Vendors](/nerve-centre/kpi-cards/sage/active-vendors) | The vendor-master mirror of this customer-master hygiene read. | | [Sage B2B Payment Terms Mix](/nerve-centre/kpi-cards/sage/sage-b2b-payment-terms-mix) | New accounts shift the terms mix; watch credit exposure as you grow. | ## Reconciling against Sage **Where to look in Sage:** The native Sage Intacct views to run side by side with this card: > **Accounts Receivable → Customers** (the full customer master with creation dates; filter to records created in the window) > **Reports → Accounts Receivable → Customer List** (exportable master list with created-date fields) > **Reports → Accounts Receivable → New Customer Report** (where configured, the closest native match for newly added accounts) > **Reports → Accounts Receivable → Customer Activity** (to cross-check which new records have actually transacted) > **Interactive Custom Report (ICR)** built on the AR customer data source filtered to records with a creation date in the trailing 30 days, pivoted by Class and Department dimensions The card reads the customer master creation date, so the cleanest reconciliation is to filter the Customers list to records created in the same 30-day window. If your card is configured to count first-invoice date instead, reconcile against Customer Activity rather than the master creation date, because the two populations differ by exactly the not-yet-invoiced new accounts. For Multi-Entity Console accounts, a customer shared across entities created once but transacting in several should count as one new customer; confirm whether your master uses shared or per-entity customer records. Common reconciliation pitfalls: * **Creation date vs first-invoice date.** These count different populations. The card uses one per the field map; reconcile against the matching native view. * **Reactivated customers.** A returning customer reusing an existing record is not new; a previously-deleted customer re-created as a fresh record is. Reactivation handling is a field-map choice. * **Duplicate records.** The same customer entered twice counts as two new customers until merged, the same hygiene issue as on the vendor side. **Why our number may legitimately differ from a Sage Intacct Customer List:** | Reason | Direction | Why | | ----------------------------------- | ------------------- | --------------------------------------------------------------------------------------------------------------------------- | | **Creation vs first-invoice basis** | Either | Master-creation count vs first-invoiced count are different populations; the gap is not-yet-activated accounts. | | **Window alignment** | Either | A strict trailing-30-day window vs a calendar-month filter counts different records at the boundaries. | | **Reactivations** | Either | Whether re-created previously-deleted customers count as new is a field-map setting. | | **Duplicate records** | Card may overstate | Un-merged duplicate customers count more than once until merged. | | **DTC checkout customers** | Card may understate | DTC buyers not set up as full ledger records do not appear; this is a B2B-leaning count. | | **Bulk imports** | Card may spike | A one-off import of historical customers stamps many records with the same creation date, inflating the count artificially. | | **Shared vs per-entity records** | Either | Multi-Entity Console: a shared new customer may be one record or several. | **Cross-connector reconciliation:** | Card | Expected relationship | What the comparison reveals | | ----------------------------------------------------------------------------------------------- | --------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | [Ecom Customers Absent from Sage](/nerve-centre/kpi-cards/sage/ecom-customers-absent-from-sage) | Onboarding gap | Ecom signups exceeding Sage new-record creation means applicants are stuck between commerce and finance, unable to be invoiced. | | [Invoiced Revenue](/nerve-centre/kpi-cards/sage/invoiced-revenue) | Activation | New accounts should convert into billing. Strong creation with flat invoicing means accounts are set up but not activated. | | [Sage Active Customers](/nerve-centre/kpi-cards/sage/sage-active-customers) | Flow into stock | New customers feed the active base; net growth is new minus churn. | | [Customer Churn Signals](/nerve-centre/kpi-cards/sage/customer-churn-signals) | Net growth | Read together to see whether you are genuinely growing the base or just replacing leavers. | | [Sage B2B Payment Terms Mix](/nerve-centre/kpi-cards/sage/sage-b2b-payment-terms-mix) | Credit exposure | New accounts on generous terms grow credit exposure; watch the mix as you scale. | The cross-channel value is that the commerce platform sees signups and the finance system sees customers, and the two should agree but rarely do without watching. A new trade applicant on BigCommerce is not a customer you can invoice until they exist in the Sage master with terms and a credit limit. This card, read against the commerce signup flow, measures exactly how well onboarding bridges that gap, and the dimensional carry-through attributes new wins to the sales team or channel that earned them. ## Known limitations / merchant FAQs **Does this count website signups?** Not directly. It counts records created in the Sage customer master, which for a B2B operation means accounts that have been set up with terms, credit, and tax details, ready to invoice. A website trade signup only appears here once it has been onboarded into Sage. The gap between website signups and Sage new records is itself a valuable read, surfaced by pairing this card with [Ecom Customers Absent from Sage](/nerve-centre/kpi-cards/sage/ecom-customers-absent-from-sage). **Master-creation date or first-invoice date?** The default is master-creation date, which measures onboarding throughput (accounts set up). The alternative is first-invoice date, which measures activation (accounts that became revenue-generating). They answer different questions and count different populations. A business worried about onboarding capacity wants the creation read; one worried about whether new accounts actually buy wants the first-invoice read. Set the basis in the field map and reconcile against the matching native view. **Why is the count low for my DTC business?** Because DTC checkout customers are often not created as full ledger records in Sage; they transact through the commerce platform's own customer store and may only summarise into Sage as aggregate sales. This card is primarily a B2B and account-based growth signal. For a DTC-heavy business it reflects wholesale account creation specifically, not consumer acquisition, which lives in your ecommerce analytics instead. **A bulk import spiked the number, is that real growth?** No. Importing a batch of historical customers stamps many records with the same creation date, which the card reads as a surge of new customers even though no real acquisition happened. After any bulk import, expect a one-period spike that is a data event, not growth. If imports are frequent, consider the first-invoice basis instead, which is immune to import-date artefacts because it counts actual transacting. **How are reactivated customers handled?** A returning customer reusing their existing master record is not new and does not count. A previously-deleted customer re-created as a fresh record does count, because it is genuinely a new record. If reactivations are common in your business, the field map can suppress re-created records to avoid double-counting customers you already knew. Decide based on whether you want to measure relationships or records. **Sage Intacct vs Sage 50 / 100 / 200 / X3?** This connector targets Sage Intacct. Every Sage product has a customer master with creation dates, so the concept ports directly, but the structure, status model, and API differ. Sage 50 and 200 are UK SMB products; Sage X3 is a different mid-market ERP. The field map and connector are specific to Intacct. If you run one of those, reach out about connector availability. **How do duplicate records affect the count?** The same customer entered twice counts as two new customers until merged, inflating the headline and fragmenting their activity across two records. This is the same hygiene issue as on the vendor side. A periodic duplicate-merge keeps the count honest; the number drops cleanly once duplicates are consolidated, which confirms the merge worked. **Multi-entity: shared or separate counting?** It depends on whether your master uses shared (group-level) or per-entity customer records. A shared customer created once but transacting in several entities should count as one new customer. Per-entity records make the same customer appear multiple times. The card de-duplicates within a single record model but cannot merge what the master holds separately. Confirm your configuration before reading the consolidated count. **How fresh is the data?** The card refreshes on the standard cadence, typically within 5 to 15 minutes of a new customer record being created in Intacct. A customer onboarded this morning appears on the next refresh. Because the comparison is a rolling 30-day window, the prior-period baseline shifts each day, so small day-to-day movement in the comparison is normal. *** ### Tracked live in Vortex IQ Nerve Centre *New Customers (30d)* is one of hundreds of KPI pulses Vortex IQ tracks across Sage and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.