Founding offer: 40% off the first payment on selected apps with code FOUNDING40, until 30 November 2026.40% off selected apps’ first payment: FOUNDING40 until 30 Nov. See founding prices

Atesen Software Find your appAll apps
Menu

Reporting Tag Re-tagger documentation

Documentation for Reporting Tag Re-tagger, an extension that works with Zoho Books. It describes the extension as it exists today and will be extended as the extension changes.

Requirements

  • A Zoho Books organisation outside the China data centre, with reporting tags or locations already set up.
  • A Zoho Books user who may edit the expenses and manual journals to be changed.

Installation

Install Reporting Tag Re-tagger from Zoho Marketplace into your Zoho Books organisation and authorise its Zoho Books connection when Zoho asks. The connection asks to read and update invoices, expenses and manual journals, and to read settings (reporting tags, locations and transaction locking).

Open Reporting Tag Re-tagger from its web tab in Zoho Books.

Re-tagging, step by step

  • Find: choose the transaction type, the date range and, if you like, an account and a customer or vendor. Then choose the reporting tag and its current option, or the current location, and the new option or location.
  • Preview: every header and line change is listed, for example Region: North → South. Transactions in a locked period, void transactions and others that cannot be edited are listed as skipped, with the reason. Nothing has been written yet.
  • Apply: type RETAG and the number of transactions, for example RETAG 25, and apply. Each transaction is read fresh, changed, written and read back. Keep the tab open until the job ends.
  • Log: download the CSV log of the job. It lists transaction, line, old value, new value and result. Keep it if you may want to undo the job.
  • Undo: open Undo from a log, choose the log file of the job and type UNDO and the number shown. The old values are put back.

Checks on every write

  • Only the reporting tag option or location changes. Everything else in the transaction is sent back as it was read, and every line keeps its line ID.
  • After writing, the transaction is read back. Its total, tax, line count and line IDs must match, and for a manual journal debits must still equal credits. If anything differs, the job stops at once and no further transactions are touched.

Daily API limits

Zoho Books limits API calls per day by plan: 1,000 on Free, 2,000 on Standard, 5,000 on Professional, and 10,000 on Premium and above. The extension shows your daily budget, keeps 100 calls in reserve and uses about three calls per transaction. A large job pauses when the budget for the day is used up and resumes from its checkpoint the next day.

Not included in this version

  • Creating reporting tags or options.
  • Changing anything other than a reporting tag option or a location.
  • Invoice changes (switched off until verified on live data), bills and credit notes (a later version).
  • Undoing a change that set an option on a tag that was empty.
  • Organisations in the China data centre.

Troubleshooting

  • A transaction was skipped: the preview and the log give the reason, such as a locked period, a void transaction or a state that cannot be edited. Clear the cause in Zoho Books, then preview again.
  • The job stopped after a read-back difference: do not run it again. Email the log and the transaction number to support.
  • The job paused at the daily limit: open the extension the next day and resume it.
  • A permission error means that your Zoho Books user may not edit those transactions, or that the extension's Zoho Books connection has not been authorised.

Licence and terms

Reporting Tag Re-tagger is installed and billed through Zoho Marketplace, which will show its price when it is listed. Installing it is subject to Zoho Marketplace's terms and your agreement with Zoho, and to the Atesen Software terms of use.

Atesen Software terms of use