Software collection playbook
Finaloop: collect reports and same-age cohorts
Native financial reports and identified-buyer acquisition cohorts with different decision bases.
By Sam Yang · Updated
Does this report answer close, collections or cohort economics?
Choose the report for the decision. Close requires ledger and supporting-source review; B2B collection buckets and DTC cohort economics cannot substitute for that work or for one another.
Evidence basis: Saved native report guidance and inspected operational-review logic. The reviewed B2B bucket scope is a procedure limitation, not a verified vendor-wide channel exclusion. Source arithmetic verification is distinct from financial accuracy or ledger completeness. Some checks restate Level review safeguards (code rules, not observed vendor behavior).
Check current supported data access and native report/export coverage. Choose the source that retains the report definitions and complete financial population.
The owner wants overdue B2B receivables
Review eligible Open invoices and their due dates separately from Draft or Voided records. The reviewed procedure scoped this bucket to B2B invoices; it did not verify Shopify or marketplace coverage.
The owner wants acquisition payback by cohort
Compare the same platform, cohort age and predictive setting; inspect included spend, returns and methodology before comparing mature and young cohorts.
Use supported API or native report access for the required scope. A permitted browser session can collect a specific gap. Neither route proves reconciliation or complete costs.
Put the evidence to work
Does customer payback in Finaloop mean the company has recovered its cash?
No. A cohort profitability view, a company P&L and a bank bridge answer three different questions. Compare acquisition cohorts at the same observed age, inspect the current metric definitions and keep predictive values distinct. Then review overhead, unallocated spend and working-capital movements before concluding that the business can fund more acquisition.
Compare customer economics without rewarding older cohorts
- Select the acquisition platform and store identity, not just a visible store name; preserve the current report methodology and predictive setting.
- Compare the same age column and season. M3 is the fourth calendar month, not an exact day-90 measurement. Unreached future ages remain unavailable.
- Retain the current cost definition: True LTV subtracts product and delivery costs before acquisition and fixed overhead. CAC includes assigned store marketing, affiliate/giveaway costs and retention campaigns, while excluding marketplace or unassigned spend. Missing assigned spend is not proof of free acquisition.
- Keep observed cumulative profit separate from projections. Current methodology assigns actual returns to the orders they reverse and uses settled-store return estimates for recent unsettled months. Inspect those later revisions before calling a first CAC crossing sustained recovery.
- Verify acquisition-history coverage and identifiable-buyer scope. Store filters select where buyers were acquired; later eligible purchases elsewhere remain in those cohorts. A weighted Average is not one uniformly realized lifetime.
Bring to the review: A same-age cohort comparison with source definitions, customer counts and observed/projected labels.
Then decide: Validate raw acquisition spend and buyer history before treating provider-reported payback as a confirmed investment result.
Review company profit and available cash separately
- Collect the configured P&L and supporting ledger/TB workbook for the same entity, basis and period. Retain all sheets and distinguish formulas from cached results.
- Walk from net sales through delivery costs, variable marketing, overhead and financing. Preserve Unallocated amounts instead of silently redistributing them.
- Build opening-to-closing bank cash from actual bank activity. Display funds in transit, card debt, loan movements and distributions separately where relevant.
- Label exactly what passed: file extraction, arithmetic reproduction, source completeness or financial reconciliation. One does not prove the others.
Bring to the review: A company profit ladder plus a separately evidenced bank-cash bridge.
Then decide: Investigate unsupported balances and classification questions before using the report to authorize spending.
Which collection route answers this question?
Choose the route for the missing evidence and the access available in your account. The comparison below distinguishes documented coverage from coverage that still needs checking.
Supported API
- What it supplies
- This investigation did not verify a generally available Finaloop API endpoint that supplies the exact native financial workbook and cohort definitions.
- What still needs proof
- API availability, permission, history and cohort coverage remain account-specific unknowns. Unknown is not a claim that Finaloop has no API.
Choose it when: Use an already supported, verified connector only when it supplies the required source population and definitions.
Native export
- What it supplies
- Current Finaloop help documents configured Excel/Google Sheets financial-report exports and Export history. Active subscription is required for exports.
- What still needs proof
- A financial workbook does not establish a complete cohort export or independent settlement verification.
Choose it when: Close review requiring original native financial reports with their configuration.
Permitted browser
- What it supplies
- Dated saved observations establish native financial-report and Lifetime value views. Browser review can verify current cohort filters and preserve the complete displayed grid.
- What still needs proof
- Entitlements, current report versions and export controls must be read back; a requested emailed report remains pending until received.
Choose it when: The required native cohort definition or report population is unavailable through already verified access.
Reproduce the diagnostic
Fictional first crossing reversed by later costs
All records and amounts below are fictional teaching inputs. This example demonstrates the calculation, not a customer outcome or a reproduced software defect.
CAC is 300 / 10 = 30 per acquired buyer. Observed profit per buyer is 22 at M0, 34 at M1 and 28 at M2. M1 crosses 30; M2 is below it. The cumulative path falls in this constructed example because later cost/refund revisions reduce profit. No bank data is included.
What the CSV columns mean
- cohort: fictional acquisition-month label
- age: observed calendar-month index, M0 is acquisition month
- buyers: fixed cohort count
- cumulative_profit: teaching USD before acquisition and fixed overhead
- acquisition_spend: teaching cohort acquisition USD, a cohort constant repeated on each age row; use only the M0 row when summing
- CAC per buyer
- 30 USD
- Acquisition spend divided by the fixed ten-buyer cohort.
- M1 profit per buyer
- 34 USD
- First illustrated crossing, before acquisition and fixed overhead.
- M2 profit per buyer
- 28 USD
- Later observed value below CAC.
- M2 cohort profit after acquisition
- -20 USD
- 280 less 300, excluding fixed overhead and cash timing.
Inspect finaloop-cohort.csv
cohort,age,buyers,cumulative_profit,acquisition_spend demo,M0,10,220,300 demo,M1,10,340,300 demo,M2,10,280,300Download this CSV
Next decision: Keep M3 unavailable until observed. Investigate the later cost changes and separately test bank cash; this is not a projection.
Run the example locally
Save the CSV files, expected-results.json and reproduce.mjs in one folder. With Node.js installed, run the command below. It calculates the checks from the CSV bytes and rejects a changed input or expected result.
node reproduce.mjs expected-results.json
No software login, customer records or API key is required.
When the result does not make sense
The newest cohort looks worse than older groups
Check: Compare the same observed age rather than Overall; inspect unavailable cells and truncated acquisition history.
Resolve the question: Rebuild an age-matched comparison and retain warm-up/history limits.
LTV multiplied by buyers does not match the monthly P&L
Check: Compare order-month cohort timing, company recognition period, fixed overhead and marketing scope.
Resolve the question: Provide a definition bridge; do not force the cohort view into financial statements.
A cohort crossed CAC, then fell below it
Check: Inspect later returns, estimates replaced by actual results and revised costs.
Resolve the question: Show first crossing and current recovery separately; sustained recovery and bank cash remain separate claims.
Where automation earns its place
Good work for automation
- Retain complete grids and workbooks, compare the same cohort age and reproduce an explicitly defined profit ladder without duplicating cost subtotals.
Keep a person on these decisions
- Assess history censoring, cost allocation, provider estimates, revenue recognition and whether raw ad and bank evidence support the investment decision.
References behind these workflows
Product documentation supports the specific scope stated beside each source. Level's diagnostic methods and fictional calculations remain distinct from vendor capabilities.
- Finaloop lifetime-value methodology
Same-age cohorts, acquisition filters, recent-return estimates and differences from P&L. Definitions checked on the review date. Reviewed .
- Finaloop financial-report exports
Configured exports, profit ladder and Unallocated segment amounts; not independent proof a customer's books are reconciled. Reviewed .
Collect and verify the population
- Native GL/TB workbook
- Retain every sheet, entity, period and basis. Inspect formulas without treating uncached values as known totals.
- B2B invoice/customer population
- Preserve status and due-date definitions. A population difference from the books requires investigation, not an automatic error label.
- Lifetime-value cohort report
- Keep observed versus predictive settings explicit. Profit recovery and cash recovery are separate questions.
Select the correct company, report, period and basis; retain native XLSX and every sheet. For an emailed GL, wait for the actual file. Preserve original and derivative hashes; inspect formulas and cutoff. For cohort analysis, verify the current native lifetime-value report and its definitions. Compare the same store, platform, period and predictive setting, retaining the complete grid. Request an emailed export only when the collection authorization explicitly allows it; otherwise leave it pending for the account owner to obtain.
Evidence acceptance checklist
- Retain report, period, accounting basis and every workbook sheet.
- Identify formulas without cached results and preserve original versus derivative files.
- Keep platform, observed cohort age, predictive state and cost definitions explicit.
Fictional collection example
A fictional young cohort has observed M0 and M1 but no observed M3. Return M3 as unavailable, not zero. A workbook formula without a cached value also requires review. Cohort profit that crosses acquisition cost once can fall below it after returns and does not establish bank cash recovery.
Invented teaching scenario, not a customer result or a reproduced vendor defect.
Capture the setup with the evidence
- Company, legal entity or account, report name, period, basis, currency and timezone.
- Selected filters, status, page count, original record identifiers and control totals.
- Collection time, source route and authorized role. Record browser and automation versions when using a browser.
- Original files and exceptions. Keep credentials, customer identifiers and financial artifacts private.
A browser version helps reproduce an interface issue. It does not validate the financial conclusion.
Pitfalls and stop conditions
Uncached formulas, repeated hierarchy codes and missing history require review. Export inspection is separate from ledger import. B2B customer reports do not establish DTC cohort economics. Cohort profit recovery is separate from cash recovery. Verify included acquisition spend, estimates and returns in the current methodology. Keep download settings stable while a file is being delivered.
How a plausible answer can go wrong
A report can pass arithmetic checks and still have incomplete ledger or source-family coverage. A profitable cohort also does not prove cash has returned to the bank.
Stop if account identity, permission, cutoff or population is uncertain. Return the missing evidence for review. Do not fill the gap with an invented record, a balancing entry or an assumed zero.
Read-only AI collection prompt
Replace the bracketed scope before use. This prompt collects evidence; it does not permit edits, approvals or accounting execution. Requesting an emailed report is a separate account action and requires explicit authorization.
Collect read-only evidence for Finaloop to answer [financial question]. Confirm [company], [account/entity], [period], [basis], [currency] and [allowed reports]. Select the correct company, report, period and basis; retain native XLSX and every sheet. For an emailed GL, wait for the actual file. Preserve original and derivative hashes; inspect formulas and cutoff. For cohort analysis, verify the current native lifetime-value report and its definitions. Compare the same store, platform, period and predictive setting, retaining the complete grid. Retain original files, complete record IDs, counts, filters, collection timestamp and exceptions. Uncached formulas, repeated hierarchy codes and missing history require review. Export inspection is separate from ledger import. B2B customer reports do not establish DTC cohort economics. Cohort profit recovery is separate from cash recovery. Verify included acquisition spend, estimates and returns in the current methodology. Keep download settings stable while a file is being delivered. Stop if the source or scope is uncertain. Do not post, match, reconnect, delete or change settings. Return the evidence for financial review; do not claim the books are correct. Request an emailed export only when the collection authorization explicitly allows it; otherwise leave it pending for the account owner to obtain. Do not approve, submit payroll, pay, transfer, refund, send messages, invite users or accept terms. Stop at any login, MFA or credential prompt and hand back to the account owner. Store files only in [approved private location]. Do not paste customer artifacts into public tools. Use only preauthorized collection actions. Request an emailed report only when its delivery is explicitly authorized; otherwise ask the account owner to supply the file.
Next decision
What does the evidence support?
State exactly which report population supports the decision and what has been verified: extraction, arithmetic, ledger completeness or financial accuracy. Do not promote one passed check into all four.
Compare the same population, identities and cutoff. Keep unsupported costs or settlements visible before using the result for pricing, cash or close.
Open the financial acceptance guide →Sources and scope
Base product-reference scopes were reviewed . No end-to-end dated native UI walkthrough is published for this software. Individual source rechecks are dated with their citations. Operator decision guidance was reviewed 2026-10-07. The references below support their stated product scope, not every observed interface detail. It is not a vendor capability certification, a measured customer result or an independently reconciled account. Verify current features and entitlement in the account you use.
- Finaloop official documentation
Cohort lifetime-value methodology.
- Finaloop: Reading your Profit & Loss (including exports and Export history)
Report center, financial reports and export history.