TallyUp

Sources and financial relationships

See what supports the answer.

Browse the documented scope of each source, financial concept, and output. Availability, evidence, and limitations are shown with each entry.

What can contribute

Source records.

See the records a demonstrated connector contract can carry, how access is authorized, what coverage can be missing, and which financial concepts those records can support.

BankingCurrent · demonstrated

Plaid

Connect bank and credit accounts through a consented provider flow.

Records in scope
Account identity, balances, bank transactions, and statements.
Authorization boundary
Hosted consent flow; the customer authorizes the provider relationship.
Coverage behavior
Request the earliest provider history and expose uncovered periods as missing evidence.
Financial contribution
Bank activity can contribute to cash, revenue settlement, operating expenses, and reconciliation.
Limitation

Coverage, account types, and history depend on the connected institution and consented provider response.

Provenance behavior

Account and transaction identities remain attached to observed source records; acquisition does not imply classification.

Contributing relationships

Related outputs

Inspect plaid
PayrollCurrent · demonstrated

Gusto

Connect payroll operations and their historical evidence.

Records in scope
Payroll runs, employees and contractors, payroll taxes, benefits, and historical payroll.
Authorization boundary
OAuth authorization; access follows the provider and company permission boundary.
Coverage behavior
Preserve provider status and request history where coverage is absent.
Financial contribution
Payroll evidence can contribute to payroll expense, liabilities, employee cost, cash planning, and close readiness.
Limitation

Provider history and object coverage may leave gaps; TallyUp keeps those gaps visible instead of inferring completeness.

Provenance behavior

Payroll run, worker, tax, benefit, payment, and observed-time identities remain addressable through derived views.

Contributing relationships

  • Contributes forwardCashexplains
  • Contributes forwardPayrollcontributes to

Related outputs

Inspect gusto
Revenue operationsCurrent · demonstrated

Stripe

Connect payments, payouts, refunds and subscriptions as revenue evidence.

Records in scope
Payments, charges, payouts, refunds, disputes, and subscriptions.
Authorization boundary
OAuth authorization; connected-account scope remains explicit.
Coverage behavior
Retain provider event identity and settlement timing so revenue and cash remain separately explainable.
Financial contribution
Commerce evidence can contribute to revenue, cash settlement, receivables, fees, unit economics, and reconciliation.
Limitation

A payment event is evidence, not an accepted revenue treatment; contracts, periods, refunds, and review may still be required.

Provenance behavior

Charge, balance-transaction, payout, refund, and subscription identities stay connected through accepted treatments.

Contributing relationships

  • Contributes forwardCashsettles
  • Contributes forwardRevenuecontributes to

Related outputs

Inspect stripe
Spend managementCurrent · demonstrated

Ramp

Connect cards, bills, reimbursements and receipt evidence.

Records in scope
Card transactions, bills, reimbursements, payments, approvals, and receipts.
Authorization boundary
OAuth authorization; company and provider scopes control accessible activity.
Coverage behavior
Retain transaction, merchant, cardholder, approval, and receipt lineage while exposing unsupported spend.
Financial contribution
Spend evidence can contribute to operating expenses, payables, cash planning, team analysis, and close readiness.
Limitation

A receipt or approval does not determine the accepted account, period, entity, or business purpose.

Provenance behavior

Spend records remain related to their merchant, cardholder, approval, receipt, classification, and review decisions.

Contributing relationships

Related outputs

Inspect ramp
Source documentsCurrent · demonstrated

Upload source documents

Add statements, invoices, exports and other source evidence from any system.

Records in scope
Statements, invoices, exports, PDFs, CSVs, spreadsheets, and image evidence.
Authorization boundary
Direct upload into a protected tenant boundary; this public site accepts no financial documents.
Coverage behavior
Retain original bytes, observed source, time range, and derived relationships.
Financial contribution
Documents can contribute evidence to cash, revenue, payroll, expenses, obligations, reconciliation, and outputs.
Limitation

Document presence does not prove authenticity, completeness, classification, or accepted treatment.

Provenance behavior

Original bytes and observed coordinates remain separate from extracted structure and accepted meaning.

Contributing relationships

Related outputs

Inspect upload source documents

What the numbers mean

Financial meaning.

See how TallyUp forms a financial answer from contributing records, accepted treatment, time, review, and the limitations that remain visible.

PositionCurrent · demonstrated

Cash

Available, restricted, and in-transit balances understood with the movements and obligations that explain them.

How it is formed
Resolve accounts and balances, distinguish restrictions and transfers, then reconcile movements and accepted adjustments.
What contributes
Banking, commerce settlement, spend, payroll, ledger, and source documents can contribute.
What changes the answer
Institution coverage, timing, restrictions, transfers, and unresolved reconciliation affect the position.
Where it is useful
Inspect the balance, explain movement, plan obligations, compare periods, and open every supporting record.
Limitation

A precise bank balance is not by itself a complete or accepted company cash position.

Provenance behavior

Every accepted amount can retain its account, transaction, adjustment, evidence, reviewer, and time coordinates.

Contributing relationships

Related outputs

Inspect cash
PerformanceCurrent · demonstrated

Revenue

Accepted economic activity separated from collections, processor settlement, refunds, and unresolved treatment.

How it is formed
Relate economic activity to contracts, delivery, refunds, accepted treatment, period, and settlement without collapsing revenue into cash.
What contributes
Commerce, billing, banking, CRM context, ledger activity, contracts, and source documents can contribute.
What changes the answer
Recognition definition, delivery evidence, refunds, collectability, period, and human review affect the result.
Where it is useful
Explain reported revenue, compare channels and cohorts, trace settlement, and support statements or planning.
Limitation

Payments, invoices, pipeline, and cash receipts are evidence with distinct meanings; none alone determines accepted revenue.

Provenance behavior

Source occurrence, contract, accepted definition, treatment, period, and settlement path remain connected.

Contributing relationships

Related outputs

Inspect revenue
People costCurrent · demonstrated

Payroll

Gross pay, employer taxes, benefits, liabilities, payments, and allocation understood as one inspectable employment-cost path.

How it is formed
Relate payroll runs, workers, taxes, benefits, payments, allocations, liabilities, and accepted journal treatment.
What contributes
Payroll providers, banking, ledger activity, employment documents, and organizational context can contribute.
What changes the answer
Coverage period, off-cycle activity, allocation policy, employer tax, benefits, and payment timing affect the result.
Where it is useful
Explain payroll expense, liabilities, team cost, cash impact, variance, close readiness, and forecasts.
Limitation

A completed payroll run can still leave missing history, allocation, payment, or period evidence.

Provenance behavior

Payroll run, worker, component, allocation, journal, payment, reviewer, and source remain addressable.

Contributing relationships

Related outputs

Inspect payroll
PerformanceCurrent · demonstrated

Operating expenses

Spend and obligations classified by accepted period, entity, account, team, and evidence state.

How it is formed
Relate spend and obligations to accepted account, period, entity, team, business purpose, and evidence.
What contributes
Cards, bills, banking, payroll, ledger activity, contracts, receipts, and source documents can contribute.
What changes the answer
Accrual timing, prepayments, entity allocation, capital treatment, reimbursement, and missing evidence affect the result.
Where it is useful
Review spend, explain variance, prepare close, understand team cost, plan cash, and produce statements.
Limitation

Merchant, receipt, card category, or ledger account alone does not determine the accepted financial treatment.

Provenance behavior

Transaction, merchant, obligation, receipt, classification, allocation, period, and decision remain connected.

Contributing relationships

Related outputs

Inspect operating expenses
ControlCurrent · demonstrated

Close readiness

Whether a period can advance based on coverage, reconciliation, unresolved treatments, and accountable review—not checklist completion.

How it is formed
Evaluate source and period coverage, reconciliation, open treatments, evidence gaps, accountable review, and the conditions required to advance.
What contributes
Every financially material source, document, treatment, reviewer, and accepted fact for the period can contribute.
What changes the answer
Materiality, required coverage, reconciliation policy, review authority, evidence gaps, and accepted exceptions affect readiness.
Where it is useful
See what is complete, what is missing, what needs judgment, why advance is blocked, and what to do next.
Limitation

Task completion and elapsed calendar time do not prove the financial period is supportable.

Provenance behavior

Each readiness state retains the exact evidence, gap, treatment, policy, reviewer, and condition behind it.

Contributing relationships

Related outputs

Inspect close readiness

What the work can produce

Reporting and decisions.

Explore the modeled requirements for financial statements and operating views, the contributing concepts, and the review each output requires.

ReportingCurrent · demonstrated

Financial statements

Period truth is complete enough to produce statements with visible qualifications.

What it contains
Income statement, balance sheet, cash flow, comparative periods, and visible qualifications.
What it requires
Requires resolved identity, source and time coverage, classification, reconciliation, and explainability.
Who remains responsible
Finance reviews definitions, open qualifications, treatments, and the period advance state.
How it is used
Share a statement while keeping each line and number connected to its support.
Limitation

Output readiness depends on admitted company evidence; this page does not promise unattended or universally available statements.

Provenance behavior

Statement lines retain accepted concept, period, source evidence, treatment, reviewer, and revision history.

Contributing relationships

Related outputs

Inspect financial statements
OperationsCurrent · demonstrated

Operational insights

Operational activity and financial outcomes share resolved identities and meaning.

What it contains
Operating drivers related to accepted financial effect, definitions, evidence coverage, and the work a team can change.
What it requires
Requires resolved identity, accepted classification, and explainability between operating and financial activity.
Who remains responsible
Finance owns financial definitions; operators own the activity and proposed operational response.
How it is used
See the driver behind margin, cost, inventory, service, or plan variance without inheriting an accounting queue.
Limitation

Correlation or source proximity does not by itself prove the financial cause of a variance.

Provenance behavior

Each stated driver retains the operating records, accepted financial relationship, uncertainty, owner, and review.

Contributing relationships

Related outputs

Inspect operational insights

Follow a number to its support

Open the fictional company and inspect the chain in context.

No signup, provider connection, customer claim, or financial-record submission is required.

Explore the example company