100-Day Plan
Financial Baseline

—Contents

—Executive Summary

This baseline was prepared directly from the platform's NetSuite production instance. All statement figures are drawn from NetSuite's standard financial reports at consolidated level and were independently re-derived from general-ledger transaction detail; the two methods tie to the dollar. Three findings materially affect the sponsor's view of the business and the sequencing of the 100-day plan.

Finding 1 — The revenue run-rate is bimodal, and the deal model must choose

For ten consecutive months (August 2025 – May 2026) revenue held a tight band around $594K per month. In June and July 2026 it stepped to $1.38M per month — a 2.3× increase driven by organic invoice volume (monthly invoice count rose from 81 to approximately 220, concentrated in the US 1 subsidiary). Annualized, the two regimes imply $7.1M versus $16.6M of revenue and $0.8M versus $8.0M of EBITDA. Determining whether June–July represents a durable new run-rate, seasonality, or channel pull-forward is the single most consequential diligence item against the deal model. The reported June–July gross margin (58–69% against a 34–43% historical band) coincides with a manufacturing go-live and large cost-of-sales credits, and should be treated as a costing artifact until inventory absorption is reconciled (§2.2).

Finding 2 — $2.89M of receivables and payables have no counterparty

$1.76M of accounts receivable (53% of the aging) and $1.13M of accounts payable (47%) consist of 69 journal entries posted with no customer or vendor. $1.30M of the receivable portion is aged beyond 90 days. These are characteristic of migration opening balances that were never rebuilt in the subledger. Until resolved — collected, reclassified, or written off — the opening balance sheet cannot be certified, and every aging metric is distorted (§3).

Finding 3 — There is no functioning monthly close

Accounting periods January–August 2025 were closed in bulk on a single date (December 10, 2025). Every period from September 2025 to the present — eleven-plus months — remains open, and posting transactions exist with dates as far forward as October 2026. Prior-period figures can still move at any time. Instituting a close calendar is the foundational reporting-readiness action (§4).

1Opening Balance Sheet

Consolidated, end of July 2026. Source: NetSuite Balance Sheet (report −202), subsidiary context “Headquarters (Consolidated)”. Annotations reflect GL-level verification.

2Run-Rate Revenue & EBITDA Validation

2.1 Monthly bridge and margin trend

Independently rebuilt from general-ledger detail (transactionaccountingline) and tied to the NetSuite Income Statement (report −200): TTM revenue $8,699,672 ✓ · TTM net income $1,802,107 ✓.

2.2 The June–July structural break — evidence

2.3 Run-rate scenarios and sensitivity

3Working Capital & Cash Conversion

Ranked opportunities

4Reporting-Readiness Assessment

Grading scale: A institutional-grade · B functional, needs tightening · C material gap · D not fit for sponsor reporting.

5Recommended 100-Day Sequence

6Risk Register

AAppendix A — Assumptions & Methodology

1. Entity naming. The platform is presented as “Acme Food & Beverage” per the sponsor's instruction. The NetSuite instance carries a different internal label; all data is drawn from that single production instance. The A/P vendor “ACME Industries” is an unrelated third-party trade vendor.
2. Consolidation basis. All statement figures use subsidiary context “Headquarters (Consolidated)” (id −1). The account is single-currency USD; no translation adjustments apply.
3. TTM window. August 2025 – July 2026 (accounting periods 199–215). July 2026 is the latest period with a full month of activity at the report date. August 2026 was in progress and is excluded from all TTM figures.
4. EBITDA definition. Gross profit less operating expenses, excluding depreciation & amortization identified as the 6800-series accounts ($167,667 TTM). D&A identification is by account-number prefix “68”, verified against the income-statement grouping. Other income/(expense) of $(52,503) is excluded as non-operating. No interest or tax lines exist in the ledger.
5. Trade vs. journal split. “Trade” A/R and A/P exclude balances carried on journal entries with no customer/vendor (verified: the entire entity-less A/R balance of $1,768,695 sits on 69 journals). Aging-report totals ($1,764,070 A/R) differ from the GL query ($1,768,695) by $4,626 due to report bucketing of unapplied credits; the report figure is used in aging tables, the GL figure in the journal-resolution workstream.
6. Net-income reconciliation. Balance-sheet net income ($1,523,850) is fiscal-year-to-date; the income-statement figure ($1,802,107) is TTM. Both are correct for their respective windows; the difference is the window, not an error.
7. Ratio bases. DSO = trade A/R ÷ TTM revenue × 365. DPO = trade A/P ÷ TTM COGS × 365. DIO = inventory ÷ TTM COGS × 365 (TTM COGS $4,735,249). Ratios use point-in-time balances at 8/17/2026 against TTM flows; no averaging of opening/closing balances was possible given data-integrity findings.
8. Scenario C construction. June–July revenue volume at the historical gross-margin midpoint (≈38%) and the baseline monthly opex run-rate (≈$185K including D&A add-back treatment consistent with assumption 4). It is an estimate for planning, not a booked figure.
9. Future-dated transactions. Posting transactions exist with dates through October 2026. TTM figures are unaffected (period-filtered), but open-period contamination is flagged as a close-discipline finding.
10. Dormant-account measure. An account is “used” if at least one posting transaction hit it between 8/1/2025 and the report date; 100 of 216 active accounts met this test.
11. Data extraction date. All queries and reports were executed August 17, 2026 against the live production instance. Aging reports are as of that date; statement reports are period-filtered as noted.

BAppendix B — Data Lineage: Reports & Queries

Every figure in this document traces to one of the following NetSuite standard-report executions (R1–R5) or SuiteQL queries (Q1–Q10). Reports were run in the NetSuite reporting engine; queries were run against the NetSuite SuiteQL endpoint. Both operate on the same general ledger; where both cover a figure, they were cross-tied.

Standard reports

SuiteQL queries

SELECT a.accttype, COUNT(*) AS total_accts,
       SUM(CASE WHEN a.isinactive = 'T' THEN 1 ELSE 0 END) AS inactive,
       SUM(CASE WHEN a.acctnumber IS NULL THEN 1 ELSE 0 END) AS unnumbered
FROM account a
GROUP BY a.accttype
ORDER BY COUNT(*) DESC

SELECT COUNT(*) AS active_accounts, SUM(used) AS used_ttm
FROM (
  SELECT a.id,
         CASE WHEN EXISTS (
           SELECT 1 FROM transactionaccountingline tal
           JOIN transaction t ON tal.transaction = t.id
           WHERE tal.account = a.id AND t.posting = 'T'
             AND t.trandate >= TO_DATE('2025-08-01','YYYY-MM-DD')
         ) THEN 1 ELSE 0 END AS used
  FROM account a WHERE a.isinactive = 'F'
)

SELECT t.type, COUNT(*) AS cnt, MIN(t.trandate) AS earliest, MAX(t.trandate) AS latest
FROM transaction t
WHERE t.posting = 'T' AND t.trandate >= TO_DATE('2025-08-01','YYYY-MM-DD')
GROUP BY t.type
ORDER BY COUNT(*) DESC

SELECT c.entityid AS customer, COUNT(t.id) AS overdue_invoices,
       ROUND(SUM(t.foreignamountunpaid),2) AS overdue_balance,
       MAX(TRUNC(SYSDATE) - TRUNC(t.duedate)) AS max_days_overdue
FROM transaction t
JOIN customer c ON t.entity = c.id
WHERE t.type = 'CustInvc' AND t.status = 'A'
  AND t.duedate < TRUNC(SYSDATE) AND t.foreignamountunpaid > 0
GROUP BY c.id, c.entityid
ORDER BY SUM(t.foreignamountunpaid) DESC
FETCH FIRST 15 ROWS ONLY

SELECT COUNT(*) AS open_bills, ROUND(SUM(t.foreignamountunpaid),2) AS open_ap,
       SUM(CASE WHEN t.duedate >= TRUNC(SYSDATE) THEN t.foreignamountunpaid ELSE 0 END) AS not_yet_due
FROM transaction t
WHERE t.type = 'VendBill' AND t.status = 'A' AND t.foreignamountunpaid > 0

SELECT t.type, COUNT(DISTINCT t.id) AS txns, ROUND(SUM(tal.amount),2) AS ar_amount
FROM transactionaccountingline tal
JOIN transaction t ON tal.transaction = t.id
JOIN account a ON tal.account = a.id
WHERE t.posting = 'T' AND a.accttype = 'AcctRec' AND t.entity IS NULL
GROUP BY t.type
ORDER BY SUM(tal.amount) DESC

SELECT ap.periodname,
       ROUND(SUM(CASE WHEN a.accttype = 'Income' THEN -tal.amount ELSE 0 END),0) AS revenue,
       ROUND(SUM(CASE WHEN a.accttype = 'COGS' THEN -tal.amount ELSE 0 END),0) AS cogs,
       ROUND(SUM(CASE WHEN a.accttype = 'Expense' AND a.acctnumber NOT LIKE '68%' THEN -tal.amount ELSE 0 END),0) AS opex_ex_da,
       ROUND(SUM(CASE WHEN a.acctnumber LIKE '68%' THEN -tal.amount ELSE 0 END),0) AS d_and_a
FROM transactionaccountingline tal
JOIN transaction t ON tal.transaction = t.id
JOIN account a ON tal.account = a.id
JOIN accountingperiod ap ON t.postingperiod = ap.id
WHERE t.posting = 'T' AND ap.isquarter = 'F' AND ap.isyear = 'F'
  AND ap.startdate >= TO_DATE('2025-08-01','YYYY-MM-DD')
  AND ap.startdate <  TO_DATE('2026-08-01','YYYY-MM-DD')
  AND a.accttype IN ('Income','COGS','Expense')
GROUP BY ap.periodname, ap.startdate
ORDER BY ap.startdate

SELECT s.name AS subsidiary, ap.periodname, ROUND(SUM(-tal.amount),2) AS revenue
FROM transactionaccountingline tal
JOIN transaction t ON tal.transaction = t.id
JOIN transactionline tl ON tal.transaction = tl.transaction AND tal.transactionline = tl.id
JOIN account a ON tal.account = a.id
JOIN subsidiary s ON tl.subsidiary = s.id
JOIN accountingperiod ap ON t.postingperiod = ap.id
WHERE t.posting = 'T' AND a.accttype = 'Income'
  AND t.postingperiod IN (211,212,213,215)
GROUP BY s.name, ap.periodname, ap.startdate
ORDER BY ap.startdate, s.name

SELECT ap.periodname, t.type, COUNT(DISTINCT t.id) AS txns,
       ROUND(SUM(-tal.amount),2) AS revenue
FROM transactionaccountingline tal
JOIN transaction t ON tal.transaction = t.id
JOIN account a ON tal.account = a.id
JOIN accountingperiod ap ON t.postingperiod = ap.id
WHERE t.posting = 'T' AND a.accttype = 'Income'
  AND t.postingperiod IN (212,213,215)
GROUP BY ap.periodname, ap.startdate, t.type
ORDER BY ap.startdate, SUM(-tal.amount) DESC

SELECT ap.periodname, ap.enddate, ap.closedondate
FROM accountingperiod ap
WHERE ap.isquarter = 'F' AND ap.isyear = 'F' AND ap.closed = 'T'
  AND ap.startdate >= TO_DATE('2025-01-01','YYYY-MM-DD')
ORDER BY ap.startdate;

SELECT COUNT(*) AS pl_lines,
       SUM(CASE WHEN tl.department IS NULL THEN 1 ELSE 0 END) AS no_dept,
       SUM(CASE WHEN tl.class IS NULL THEN 1 ELSE 0 END) AS no_class,
       SUM(CASE WHEN tl.location IS NULL THEN 1 ELSE 0 END) AS no_loc
FROM transactionaccountingline tal
JOIN transaction t ON tal.transaction = t.id
JOIN transactionline tl ON tal.transaction = tl.transaction AND tal.transactionline = tl.id
JOIN account a ON tal.account = a.id
WHERE t.posting = 'T' AND t.trandate >= TO_DATE('2025-08-01','YYYY-MM-DD')
  AND a.accttype IN ('Income','COGS','Expense','OthIncome','OthExpense')