Days, not weeks

The typical close after switching off spreadsheets. Connect, configure, done.

100% of transactions

Pulled, matched, and tied out. No sampling, no gaps, no mystery variances.

Every entry traceable

Each journal entry links to the transactions behind it. Audit season stops being a season.

Sound familiar

The close shouldn't be stupid.

You're a revenue accountant, not a human ETL pipeline. So why does every period feel like one?

"I run nine reports from six systems, paste them into Excel, stack formulas on top, and pray it ties out."

It's not the time, it's the activity. Tally pulls every source together and applies your rules in one place. No spreadsheet to babysit.

"My numbers changed since last month. Again."

Returns, chargebacks, transactions that never cleared. Tally ties every change back to the transaction behind it. Explainable, not alarming.

"I have no holistic view of what I'm selling."

Stop stitching exports together to answer one question. Tally is the command center: every marketplace, consolidated, in real time.

Walkthrough

How it works.

Five steps from raw processor data to a signed-off close. You run the close. Tally does the grunt work.

Step 1

Connect your data sources

Connect your payment processors and app-store marketplaces (Apple, Google Play, Stripe, Shopify, PayPal, Braintree, and more) via direct API, or upload transaction files manually. Tally shows connection status and last-sync timestamps so you know exactly what's in before you start the close.

app.tallyrevenue.com

Connect data sources

Step 1 of 5 · 6 of 8 connected

Syncing

Apple App Store

Last sync 2 min ago

Connected

Google Play

Last sync 4 min ago

Connected

Stripe

Last sync 1 min ago

Connected

PayPal

Awaiting authorization

Action needed

Connect data sources: each processor with live connection status and last-sync time

Step 2

Configure your ASC 606 recognition rules

Assign a contract term and recognition method to each SKU: daily deferred, monthly, point-in-time, or others. Tally applies the correct recognition schedule to every matching transaction automatically, so your deferred and recognized splits are always in line with the standard, without manual journal adjustments each period.

app.tallyrevenue.com

Recognition rules

Step 2 of 5 · ASC 606

12 SKUs mapped

SKU

Contract term

Method

pro_annual

Yearly

Daily deferred

pro_monthly

Monthly

credits_pack

One-time

Point-in-time

team_annual

Yearly

Daily deferred

Recognition rules: each SKU mapped to a contract term and an ASC 606 method

Step 3

Check data completeness

Confirm that every data source has imported completely before you proceed. Tally surfaces transaction counts and gross revenue per marketplace so you can catch missing data or partial syncs before they cause reconciling items later in the close.

app.tallyrevenue.com

Data completeness

Step 3 of 5 · June 2026

All imported

Apple App Store

128,440 transactions

$22,118

Complete

Google Play

96,210 transactions

$14,907

Complete

Stripe

103,361 transactions

$12,296

Complete

Data completeness: transaction counts and gross revenue per marketplace

Step 4

Consult variances

Review recognized and deferred revenue trends over time, then reconcile account balances against the prior period. Expected drift is flagged automatically so you spend your time on real variances, not chasing noise.

app.tallyrevenue.com

Analyze & validate

Step 4 of 5 · vs May 2026

In range

Recognized

$49,321

↑ 23%

Deferred

$14,213

↑ 6%

Variance

0.4%

within tol.

Recognized vs deferred

RecognizedDeferred

Consult variances: recognized vs deferred revenue with account-level variance, on the Analyze & Validate screen

Step 5

Close the period

Map recognized revenue, deferred balances, fees, and refunds to the appropriate GL accounts, then work through the required close checklist. Every close produces real, auditable journal entries, with no dummy data and no manual adjustments needed to satisfy your auditor.

app.tallyrevenue.com

Close period

Step 5 of 5 · June 2026

Ready to close

Journal entry preview

Dr — Deferred revenue$49,321

Cr — Recognized revenue$49,321

All transactions importedRequired

Variances reconciledRequired

GL mapping approvedRequired

Close period: journal-entry preview and the required close checklist

Built for finance