# Tally and the connected ledger: follow a financial number back to its evidence

> How to evaluate the transaction, journal, reconciliation and review links behind a coherent accounting system.

- **Source:** https://www.runproper.com/resources/systems/tally-connected-ledger
- **Publisher:** Proper Technologies Inc.
- **Format:** System guide · Cash & Tally
- **Reading time:** 4 min

A connected ledger should let a finance team trace a reported number to the transactions, evidence, postings and reviews that support it. Tally represents Proper’s five-part accounting system; evaluate that connection through actual records and confirmed results rather than the appearance of a single dashboard.

## Define what connected means for your books

Putting AP, AR, Payments, Payroll and General Ledger in one interface does not by itself establish a coherent accounting record. The important connections are between the business event, its operational record, the accounting treatment, the posting and the resulting balance.

Glen’s accounting role in Proper’s source material provides the fifth part of the Tally identity. The intended system connects the four operating areas to shared accounting controls and reports. This guide translates that model into practical evaluation questions; it does not establish that every described control is available in every configuration.

## Follow one transaction through its complete history

Start with a supplier invoice. Find the source, its approval, the relevant account and dimension coding, and the posting acknowledged by the ledger. If the supplier later issues a credit, locate the linked correction and confirm its actual effect. The original invoice history should remain understandable.

Next inspect the payment independently. Approval of the supplier obligation, release of money, bank processing and reconciliation are different events. The ledger view should not imply that cash left the account simply because an invoice was approved or a payment instruction was prepared.

Repeat the exercise for a customer receipt and a payroll run. Ask which supporting detail remains accessible and who is allowed to see it. Payroll evidence requires appropriately restricted access even when the resulting accounting totals appear in the shared books.

## Prove period decisions using the underlying evidence

The Accounting AI Now story illustrates an invoice crossing two months. Its synthetic $6,000 service total covers three separately priced phases. Acceptance evidence and an approved accounting policy support the proposed period treatment. The relevant work is reconstructing that evidence and explaining the proposed entries, not guessing from the invoice date.

The accountant retains the judgment and approves the entries within authorized periods. Follow the accrual, reversal and later invoice as one linked sequence, then confirm that the expense was recorded once in total. This example does not prescribe a universal recognition policy; the organization’s applicable policy and facts govern its decision.

A useful demonstration includes missing acceptance evidence and a locked period. The system should expose the issue and route it to an authorized person. A balanced entry alone cannot prove that the timing, classification or underlying business interpretation is correct.

## Connect reconciliation to an owner and a reviewed version

A reconciliation explains why a balance agrees with its supporting record or why a difference remains. Ask to see the bank or subledger detail, ledger balance, matching rules, unresolved items and accountable owner. A completion badge should have a clear basis.

When a correction changes the books, determine which reports and reviews relied on the affected version. A saved reporting pack and a refreshed live balance may no longer describe the same state. The team needs a way to recognize that difference and complete the appropriate review.

Proper’s AI Wow accounting story explores sustained tracking of changing evidence and dependent close work. It remains a future concept for product evaluation. A film’s creative approval does not prove continuous dependency coverage or establish that a fresh sign-off can be created automatically.

## Use a proof checklist that includes failure

Evaluate the routine accounting controls before the more ambitious AI story. Request supported recurring entries, allocations, reversals, approval history, period controls and traceable reports for the chosen scope. Confirm special requirements separately, including consolidation, currencies and additional books.

Deliberately introduce an import rejection, a duplicate event and a late correction. Observe how the record remains visible, who resolves the issue and what confirms the final posting. The demonstration should show the team how to recover and reconcile, not merely how to produce the initial entry.

-   Trace a statement line to its underlying transactions.
-   Inspect source evidence, posting acknowledgement and approval.
-   Reconcile the supporting balance and explain open differences.
-   Identify the version and period used by the report.
-   Show the authority required to change or close the period.

## Make the outcome an explained set of books

The practical goal is an accounting record the team can explain: what happened, how it was treated, which records support it and what remains unresolved. AI can assist with preparation and investigation where available; accounting policy, consequential judgments and close authority remain explicitly assigned.

Use the Tally system story as a starting structure, then document the exact controls and results demonstrated in your configuration. That evidence supports a better implementation decision than a broad promise of automated accuracy.

## Questions & answers

### Are balanced books necessarily correct?

No. Entries can balance while using the wrong period, account or underlying assumption. Evidence, policy, reconciliation and authorized review address different parts of accounting quality.

### Does a refreshed report mean the close is approved again?

No. A report update and an authorized review are different events. Material changes may require the affected owner to reconsider the earlier conclusion.

### What is the first connected-ledger test?

Select one statement balance and follow it back through postings, operational transactions and source records. Include a correction and verify the resulting balance and review history.
