The short answer
CeramicPortal’s Tally export produces an XML voucher file for a person to download and import into the receiving accounting system. It is a file handover, not a live connector or automatic synchronisation. Agree the scope with your accountant and reconcile a controlled sample before wider use.
Keep these in mind
- Treat the XML as a manual file handover.
- Reconcile document references as well as totals.
- Agree how corrected or overlapping exports will be handled.
Agree the destination before downloading a file
Start with the person who will import the file. Confirm the receiving company, accounting-system version, intended document types and period. A file can be structurally valid while still being unsuitable for that company’s ledger setup.
The current Tally export choices cover sales invoices, sales returns, payments received, purchase bills, payments made, customer ledger balances, supplier ledger balances and expenses. Estimates, challans and purchase orders are not Tally export choices. Transaction exports use a date range; customer and supplier ledger exports are current balance snapshots.
The existence of a Tally format does not mean every receiving version or company configuration has been tested. Confirm the exact record type and receiving workflow with the person responsible for the accounts.
Define one handover clearly
| Record in your handover note | Reason |
|---|---|
| Source business and receiving company | Prevents a file being imported into the wrong company. |
| Transaction dates or current ledger snapshot | Distinguishes a selected transaction period from the current customer or supplier balances. |
| Document type and references | Explains what should be included. |
| Record count and relevant totals | Provides a basis for reconciliation. |
| Who exports and who imports | Makes exceptions traceable. |
| File version and import result | Distinguishes a correction from an earlier handover. |
This note is a suggested operating practice, not an export-history feature claim. Keep it using the process agreed with your accountant.
Rehearse with a controlled sample
- Choose a small reviewed set of documents and confirm their source details.
- Select the record type and format. Review the date range for transaction records, or confirm that a ledger export is a current balance snapshot.
- Download the XML and retain the reviewed file version.
- Have the responsible accountant test the receiving import in an appropriate test company or protected workflow.
- Compare references, values and the reported import result before accepting the handover.
Resolve an exception at its source
Review the source record, selected dates and receiving import message. A period boundary, incorrect source field or destination mapping may need attention. Correct the identified problem and agree a new file version, instead of repeatedly importing the same output and hoping the result changes.
Do not assume repeated exports are deduplicated
Transaction exports use selected dates; customer and supplier ledger exports capture current balances. A new file can overlap a previous handover. Confirm whether it is a replacement snapshot or another transaction batch before importing it. Automatic duplicate prevention in the receiving system has not been established for this workflow.
Before importing a corrected or overlapping transaction file, ask the accountant how already imported records will be handled. Keep the earlier result available for comparison. Apply the same deliberate review when replacing a balance snapshot; do not treat the snapshot as another period of transactions.
Know the boundary of the feature
Tally XML export does not imply automatic pushing, scheduled runs, two-way updates or an official partnership. Changes made after an export do not become proof that the receiving accounts have been updated.
For a demo, bring the intended document type and receiving setup. Ask to inspect the source scope and the generated output, then plan a separate reconciliation with the person responsible for the accounts.
Common questions
Does CeramicPortal automatically synchronise with Tally?
No. The described workflow is a downloaded XML file that a person imports.
Is it safe to re-import the same period?
Do not assume automatic deduplication. Review the receiving system’s behaviour with the responsible accountant before a repeat import.
Explore the relevant workflow
Put the explanation in context.
Product education from CeramicPortal. Examples are illustrative unless identified as recorded product evidence. The available actions depend on your account and assigned access.