Tally / Zoho cutover and accounting coexistence
Adopt connected manufacturing with reconciled source data while the selected external product remains the accounting book of record.
Purpose
Adopt connected manufacturing with reconciled source data while the selected external product remains the accounting book of record.
Company administrator, Finance Accountant, independent Finance Controller and customer warehouse/accounting reviewers
Two controlled training companies: one TallyPrime file-exchange case and one Zoho Books case. Customer pilot acceptance remains a separate observed decision.
Before you begin
- Assign all legal-entity sites and appropriate clearance. Configure the native legal entity, active accounts and independently approved material/site value profiles before adopting stock.
- Agree the source product/version, exact company/organization ID, prior closing-date cutoff, base currency and every external account mapping with the accountant. Use a quiet cutover window.
- Prepare UTF-8 CSV extracts with a single unambiguous header, plain decimal amounts and ISO dates. Tally Excel reports can be saved as CSV. Scope is reviewed flat exports; arbitrary Tally XML/JSON backups and automatic OAuth synchronization are not imported.
- Retain CLEAN evidence for cutover, external postings and observed customer tests. Never upload passwords, tokens or TOTP material.
Field guide
One immutable source-company and ledger mapping version. Correct it by creating a replacement before cutover approval. One approved baseline is permitted per native entity.
All four opening exports must use the cutoff. Later trial balances support reconciliation.
Reusable immutable mapping for this company and export kind. Reinspect after changing a column.
The actual published external journal/document identifier, independently confirmed against the exact approved payload and company.
Retained observations from the real customer environment; fixture tests do not automatically accept a warehouse device or an external close.
Procedure
- 1
Open Finance → Onboarding. Enter the rationale, set up the source company and map each active native account to a unique external code and ledger name. The external book retains statutory accounting ownership.
- 2
Inspect item and supplier CSV extracts. Store each exact export in Documents, wait for CLEAN status and select its matching version. Resolve row errors, save the mapping and download a normalized workbook. Continue through Programme operations → Migration for workbook preview, database dry run and commit. Material revisions and supplier qualifications still need their normal approvals.
- 3
Bring native opening custody and approved carrying values into agreement through the existing migration/adoption workflows. The cutover review itself never adds stock, balances, invoices or fictitious historical transactions.
- 4
Inspect the cutoff trial balance, stock, open-item and open-order files. Header-only stock/open-item/open-order files declare an empty register. Use signed outstanding balances for customer credits/supplier debits; currency must match the entity base currency.
- 5
Link each remaining open order to an independently approved, unused native line for its exact remaining item/quantity. Do not import old receipt/delivery history or authorize it by a CSV row. Resolve unsupported tracked/project opening custody separately before cutover.
- 6
Check the opening reconciliation. Trial balance must balance, every mapped account must appear once including zeros, AR/AP details must agree to their control accounts and source stock must agree with native quantity/value and inventory GL. Request cutover; a different controller rechecks the unchanged proof and CLEAN evidence.
- 7
Select complete posted base-currency journals after the cutoff. Request a handoff; a different controller approves. Each journal can belong to only one approved handoff. Downloads retain the same checksum.
- 8
Use the Tally journal XML or Zoho draft-journal CSV only for eligible general-ledger movements. Party, cash and tax-control journals produce a review-only manifest: create or match the corresponding external native document instead of importing duplicate journals. Neither file lane files GST returns, settles external invoices or updates external stock quantities.
- 9
Review and publish externally where required. A different Finance authority records every exact external reference and CLEAN receipt evidence. Rejections remain visible; correct the external setup and retry the same approved file. An accepted receipt cannot be reused for another journal.
- 10
Inspect a later complete external trial balance and reconcile. Expected balances equal opening plus all native journal movements. Unacknowledged journals and unexplained external movements remain blockers; retain and investigate differences rather than waiving them.
- 11
Request actual device/printed-label, operating-cycle and accountant-close acceptance only after observing the customer environment. Accountant acceptance pins an exact balanced reconciliation and becomes stale if new native accounting activity appears before approval.
Expected result
- One approved source baseline, exact identities and independent decisions, with original custody and journals preserved.
- Approved files and external acknowledgements are distinct facts. An external posting is a human-attested receipt, not an automatic connector response.
- The initial lane is base-currency file exchange and untracked unrestricted OWN opening stock. Historical document replay, FX opening migration, tracked/project opening value adoption, automatic tax filing and universal Tally/Zoho compatibility are not attested.