Confirm your exact Empire installation, the company and books to include, authorised users and how recently the connected records were updated. Then compare a small set of supported answers with the same Empire reports. Treat this as an assisted setup, not a universal self-service connection.
Start with the installation you actually use
Software names alone are not enough to establish compatibility. Share the product and version details with the setup team, along with the reports you want to access. Do not assume another product called Empire uses the same connector.
The current Empire connector overview describes Dhandha GPT’s starting point. The first version reads supported business records. It should not be understood as permission to post bills, change orders or send customer messages. Guided future-workflow examples are a separate experience.
Prepare a short company-and-books list
Ask the owner and accounts person to agree which books represent the business you want to query. List test or unused books separately. Decide what a phrase such as “our business total” should include; do not leave that decision to a name match.
| Prepare | Example of the decision |
|---|---|
| Business and book names | Which records belong to this trial? |
| Default scope | One company or an agreed set of books? |
| Excluded books | Which test records must never enter the answer? |
| Owner confirmation | Who signs off the included records? |
| Change contact | Who reports a newly added or renamed book? |
For example, a fictional business may have one trading company, another separately owned company and a test book. The intended answer might include only the first. Adding both companies would be a different scope, and adding them would not by itself eliminate intercompany transactions.
Agree access before sharing records
Identify who may see customer balances, sales and supplier information. Ask the setup team which access restrictions are available in your trial. If a requested restriction is not supported, resolve that before granting the user access; do not assume ordinary chat membership provides it.
Keep credentials out of chat messages and public forms. Use the agreed secure setup method. Have your technical contact confirm the read-only connection and what data is made available. Do not change the source software or expose it publicly merely to follow a generic online guide.
Check freshness with one known entry
Ask how records reach the connected view and what its latest update time means. Choose a recent, authorised example entry and confirm whether it appears in both places. If the latest entry is absent, establish the reason and expected update before using the answer for a time-sensitive decision.
No universal refresh interval is promised here. A live query, a copied database and a fixed demo dataset have different freshness properties. The public demo is fictional and uses its displayed period.
Run a small acceptance sheet
Use a supported sales question, a returns question and a customer-balance question. For each, save the company, period, report definition, expected amount and actual answer. Include a case with a return or an unallocated receipt so the trial checks more than a simple total.
Agree how failures will be reported and retested. If a number differs, use the reconciliation guide rather than adjusting records to make it agree. Once these checks pass, extend to the supported questions that matter to your team.
Keep the setup sheet when the trial ends. A new financial year, book or access requirement is a reason to review the configuration, not to assume the original choices remain correct.
Questions you might ask
Is Empire connection a self-service setup?
This guide describes preparation for an assisted trial. Compatibility, scope, permissions and supported questions must be confirmed for the installation.
Can the first connector enter bills or change orders?
The first version is read-only. Future-workflow demonstrations do not establish live posting, dispatch or messaging capabilities.