System guide · Cash & Tally

Proper Cash or Proper Accounting: start with the system you want to keep

A decision guide for improving AP, AR, payments and payroll while deciding whether to retain or change the accounting system.

View Markdown

Proper Cash Management groups AP, AR, Payments and Payroll. Proper Accounting adds General Ledger and accounting under the Tally identity. Start by deciding whether your current ledger should remain the accounting system of record, then prove the operational and integration requirements for that choice.

Describe the operating problem before choosing the system

A finance team may be satisfied with its ledger but lose time collecting invoices, resolving customer disputes or coordinating payment approvals. Another team may also struggle to explain balances, control the close or keep its chart of accounts consistent. Those situations lead to different evaluation scopes.

Write down the working moments that cause delay and rework. Identify which are operational tasks and which depend on the accounting system itself. The distinction helps prevent a project aimed at better collections from becoming an unplanned ledger replacement, while ensuring that a necessary accounting change is considered deliberately.

Evaluate Cash when retaining the ledger is the intended path

Cash represents four connected operating areas. Billie’s AP story concerns supported supplier obligations. Arlo’s AR story concerns customer balances and collection blockers. Penny’s Payments story concerns authorized movement of money. Payton’s Payroll story concerns supported pay inputs, calculations and results.

For a retain-ledger evaluation, ask how each relevant area exchanges records with the existing accounting system. Specify which application owns supplier and customer identifiers, account codes, balances and corrections. Confirm direction, frequency and supported fields for each integration. “Connected” is only useful when the necessary records and acknowledgements actually travel across the connection.

Retaining a ledger does not remove implementation work. The team still needs mapped fields, permission boundaries, an exception process and a way to reconcile the operational record with the books. Confirm the available Proper connector and product scope for the chosen region and plan; the system identity alone is not evidence of compatibility.

Evaluate Accounting when the books belong in the same change

Tally represents the five-part accounting system, adding Glen’s General Ledger and accounting role to the four Cash areas. The intended operating model links transactions, balanced entries, reconciliations and financial reporting to a coherent set of books.

An accounting evaluation should include the chart of accounts, dimensions, opening balances, journal controls, period access, reporting and the records retained from the previous system. Confirm any required multi-entity, consolidation, currency or tax capabilities separately. They should not be assumed from a general statement that a product includes accounting.

Changing the ledger can create an opportunity to simplify processes, but it also creates a broader transition. Agree the authoritative records, conversion scope, reconciliation evidence and ownership before promising a cutover date. A successful demonstration of invoice capture does not establish readiness for the entire accounting transition.

Compare both choices using the same business events

Use the same cases in each evaluation: a supplier bill corrected by a credit, a customer receipt that pays only part of an invoice, a payment with an uncertain bank response, and an approved payroll correction. Follow each event through its operational owner and accounting result.

Then introduce a failure. A connector rejects a code; a receipt arrives short; a source document changes after approval. The useful question is how the team sees the problem, retains the original record and safely reaches the intended state. A demonstration that shows only the successful path leaves the operating burden unclear.

  • Which system owns this record and its stable identifier?
  • What action is authorized, and by whom?
  • What confirms that the destination accepted the intended result?
  • Who owns an unresolved handoff, and how is it reconciled?

Choose the implementation sequence around dependencies

Begin with a defined scope and a measurable working outcome. For example, the first phase might demonstrate supplier invoice handling through acknowledged posting for a limited group. Broader rollout depends on that proof plus the remaining operational requirements.

For either system choice, plan data quality, access, configuration, testing and training. Maintain a record of unresolved requirements instead of hiding them inside a general readiness label. The team should know what is confirmed, what needs configuration and what remains unavailable or under review.

The choice is therefore about the system boundary you want and can validate. Cash can frame the evaluation around finance operations while retaining the existing ledger; Accounting frames a broader evaluation that includes the books. Confirm the exact deployment and integration path with Proper before committing either approach.

Questions & answers

Does choosing Cash automatically mean my ledger is supported?

No. Confirm the specific connector, supported records, permissions, refresh behavior and reconciliation path for the ledger you intend to retain.

Does Tally imply every accounting feature is included?

No. The identity describes the five-part system. Requirements such as consolidation, multiple currencies, tax and reporting depth need explicit scope confirmation.

Can we make this decision from the videos alone?

The films explain the intended workflows and control boundaries. Use them to shape a demonstration, then verify the actual product configuration and implementation requirements.

Start with your workflow.

Bring your records, exceptions and the decisions that matter to your team.

Let’s talk Proper