Voucher verification and recovery
Resolve uncertain Sales Voucher and Credit Note writes using the Activity controls.
A write can reach TallyPrime even when its response never reaches the Agent. Reconcile in Tally means the connector cannot safely replay that attempt. Resolve the actual voucher state before authorizing another export.
Identify the original attempt
Open Activity, locate the failed Sales Voucher or Credit Note, and record its command ID, Shopify resource, timestamp, and error. Confirm the company in which the attempt was made. Do not switch companies to clear the failure.
Tally Connect owns the voucher's Reference field and stores an identity in
the form TC:<uuid>. The original Shopify reference is retained in narration.
A voucher number alone is insufficient to prove that the correct Shopify
resource was posted.
Check the voucher in TallyPrime
Verify the exact connector reference, voucher type, date, amount, items, quantities, and accounting allocations. Record the Tally Master ID and voucher number; include the Tally GUID if available. Check the original company and relevant date range before concluding that a voucher is absent.
An Import Exceptions entry is a failed import record, not a verified posted voucher. If you cannot establish the outcome, preserve the failed command and ask support to inspect it.
When the voucher exists
For an eligible unresolved Sales Voucher or Credit Note, Activity shows Record what you found in TallyPrime:
- Enter Tally Master ID.
- Enter Voucher number.
- Enter Tally GUID (optional) if known.
- Select Link existing voucher.
- Inspect the returned result and confirm the linked record in Orders.
The service checks the evidence and original relationship. If the company or voucher mappings changed, linking can be refused. Resolve the mismatch in the original company; do not substitute a similarly named voucher.
When the voucher is confirmed absent
Only after checking the original company and exact identity, select Confirm absent and allow fresh export in Activity. This records the absence decision; it does not itself create a replacement voucher.
Return to the relevant order or refund workflow, complete its current readiness checks, and use the offered export control. Eligible refund rows show Create fresh export after confirmed absence. Follow the new attempt until it is verified and linked.
Where these controls apply
| Failed operation | Recovery route |
|---|---|
| Eligible Sales Voucher or Credit Note | Activity voucher reconciliation |
| Disposable ₹1 test voucher | Correct the test setup and follow the test workflow; the general voucher-link form excludes tests |
| Stock Item creation or alteration | Inspect the Tally master, then use Products review |
| Physical Stock or inventory adjustment | Inspect actual quantities and use Inventory recovery |
| Read-only command | Fix the cause and use Retry read when offered |
Historical or resolved failures can remain visible. Judge recovery by the current linked voucher and latest workflow result, not the total historical failure count.
Details to send support
Provide the command ID, operation type, failure time and timezone, Agent version, error message, and redacted diagnostics. State whether the voucher was found and whether mappings or company binding changed. Do not send credentials, pairing codes, raw customer payloads, or an unredacted company export.