IntelekIQ
Secure Accounting · Private AI for Accounting Practice
Solution Paper  |  Public AI vs on-premises private AI

The Assistant You Already Trust

Public AI can be an excellent assistant for general work. Secure Accounting addresses a different need: research, document review and drafting with confidential client files on premises, under the firm's control.

For: principals, partners and practice managers · Malaysia & Singapore  ·  Reading time ~13 min

AI tools are already useful in accounting practice. They can explain concepts, help with formulas and prepare drafts. The question is not whether accountants should use AI. It is which AI should be used for each task, what information it may process and who remains responsible for the result.

1Public AI is useful for general work

Public AI can support general research, learning, non-client drafting, formulas and formatting. These tools are capable and convenient. Firms can use them within clear policies and with suitable attention to provider terms, retention settings and access controls.

That usefulness does not make public AI the right destination for confidential client files. A separate, firm-approved path is needed when work involves a client's trial balance, tax file, working papers or other confidential information.

2Confidential client work changes the decision

When an accountant submits confidential client information to a public AI service, the information leaves the firm's immediate control and enters the provider's processing environment. That is a firm-level data-handling decision, even when it begins as an individual request.

The firm should decide which tools staff may use, what information each tool may process and what review is required. A policy based only on individual judgement is difficult to apply consistently.

Public AI can remain useful. Confidential client work needs a firm-approved way to use AI.

3Accounting work requires particular care

Confidentiality has no general privilege backstop. Accountants have binding professional and contractual duties of confidentiality. In most jurisdictions, they do not have a general accountant-client privilege that can defeat lawful compulsion.

Some information is especially sensitive. Tax files, payroll information, identity documents and some AML-related material require careful handling. Firms should classify this information and keep material that is not approved for AI use out of AI workflows.

AI can return convincing errors. A wrong rate, total or accounting treatment may look plausible. Accountants must verify figures and sources, apply professional judgement and remain responsible for anything provided to a client or filed with an authority.

4The two models create different boundaries

A public or third-party AI service processes information within the provider's environment, subject to its technical controls, contracts and legal obligations. Secure Accounting uses private AI on premises. Confidential client files can be used for research, document review and drafting without being sent to a public or third-party AI model.

Both processing models can be legitimate. They suit different work. Storing files in a cloud platform is also a separate decision from sending their contents to an external AI model.

Public AI and on-premises private AI Both can be useful. The difference is where confidential client information is processed. PUBLIC AI: EXTERNAL PROCESSING Accountant submits information sent for processing jurisdiction border Provider's cloud processed in the provider's environment terms, retention and settings apply provider jurisdiction may apply SECURE ACCOUNTING: ON PREMISES Accountant works with authorised files PRIVATE AI: INSIDE THE FIRM Private model reads the numbers here never decrypted elsewhere · nothing sent for processing AI processing remains under the firm's control no border crossed Both models can be legitimate. The firm should choose the processing boundary that fits the work.
Figure 1. Both models can be useful. Secure Accounting processes confidential client files on premises, while public AI processes information within a provider's environment.

5Assess external AI on its actual controls

Check the provider's terms and settings. Training, retention, monitoring and access arrangements vary by service and tier. Firms should verify the current position rather than assume every account has the same protections.

Understand where processing occurs. Encryption protects information in storage and transit. AI processing also requires the model to work with the relevant text inside a protected runtime. The firm should know who operates that environment and which controls apply.

Consider provider jurisdiction. Lawful demands may be directed to a provider that holds or processes information. The US CLOUD Act is one documented example of a law that can reach data controlled by a US-based provider regardless of storage location. Safeguards apply, and the existence of the power is not evidence of routine access.

Govern the full processing chain. The software vendor, cloud platform and model provider may be different organisations. The firm should understand each role and keep responsibility for classification, access and review.

6Secure Accounting provides the private path

Secure Accounting is powered by SAIA (Secure Accounting Internet Appliance), IntelekIQ's private AI infrastructure for accounting practice. It runs on premises and works with authorised client files, previous work and approved accounting sources.

Accountants can use it for research, document review and drafting while confidential client information remains under the firm's control. Secure Accounting can still produce inaccurate or incomplete work. Accountants must check the sources, verify the figures and remain accountable for the result.

The goal is not to remove a useful assistant. It is to give staff a firm-approved assistant for confidential client work.

7Choose the assistant for the information

Public AI can remain part of daily work where no confidential client information is involved. Secure Accounting is intended for work that uses confidential client files or client numbers. The firm should define that line clearly and train staff to apply it.

Choose the right AI environment for the work Public AI suits general work; confidential client work needs a firm-approved private path Public AI can be right for · Explaining a standard or a tax concept · General research & getting unstuck · Non-client drafting & internal notes · Formulas, formatting, learning · Anything with no client-confidential data Genuinely excellent; keep it in daily use for all of this. Secure Accounting is right for · Client ledgers, trial balances, accounts · Tax files & computations · Audit working papers · KYC / AML material & suspicions · Anything confidential to a client Confidential client work stays under firm control. The firm should classify the work and use Secure Accounting for confidential client files and client numbers.
Figure 2. The choice is not all or nothing. The firm can use public AI for general work and Secure Accounting for confidential client work.

Malaysia's amended Personal Data Protection Act and Singapore's PDPA both make governance of personal information and cross-border transfers relevant to accounting firms. Neither regime makes every cloud service unsuitable, nor does either remove the need for a firm-specific assessment.

On-premises private AI gives the firm a clear processing boundary for confidential client work. The wider environment still requires access control, retention policies, security maintenance and professional oversight.

The bottom line

Ask where confidential client information is processed, who operates the model, what terms and controls apply, and who remains accountable. Secure Accounting's answer is that private AI processing takes place on premises. Accountants remain responsible for the work.

See how it fits your practice

Start a conversation about which work can use public AI and which requires on-premises private AI.

Book a discovery conversation →

Sources & further reading

  1. AI already legitimate in audit/accounting: DataSnipper reporting over US$1.4bn in productivity savings to audit and finance teams in 2025 (PRNewswire, Jan 2026: prnewswire.com); MindBridge and comparable tools for ledger-wide anomaly detection. Cited to show the question is "which AI," not "whether."
  2. No accountant–client privilege; confidentiality under the MIA By-Laws (On Professional Ethics, Conduct and Practice) and the international ethics code (ethicsboard.org/iesba-code), a professional/contractual duty, not a shield against lawful compulsion. Confirm with qualified counsel.
  3. Accountants as reporting institutions under Malaysia's AMLA (Anti-Money Laundering, Anti-Terrorism Financing and Proceeds of Unlawful Activities Act 2001) when they carry out certain gazetted activities, not for audit or tax-compliance work alone: customer due diligence and suspicious-transaction reporting duties, and the tipping-off offence. See MIA, Accountants Today (obligations of reporting institutions; raising STRs) and Obligations by Reporting Institutions Under AMLA.
  4. Consumer vs business AI tiers: on free/consumer tiers, submitted content may by default be retained and used to improve models; training-off and retention controls are opt-in and tier-dependent. Confirm each provider's current terms.
  5. US CLOUD Act (2018) and its extraterritorial reach: Cross-Border Data Forum, CLOUD Act FAQs. Microsoft France testimony before the French Senate (June 2025): executive stating, under oath, that transfer to the US government under the CLOUD Act could not be guaranteed against; reported by The Register (25 Jul 2025) and Forbes (22 Jul 2025).
  6. Cloud shared-responsibility model (customer remains responsible for data classification and configuration). Snowflake customer-environment breach (2024): ~165 organisations reached via stolen customer credentials; cloud-concentration illustration.
  7. Malaysia PDPA (Amendment) 2024 and Cross-Border Personal Data Transfer Guidelines (2025); Singapore PDPA transfer-limitation obligation. LHDN MyInvois e-invoicing as the source of the firm's new structured-data estate.
  8. Companion papers: Secure Accounting: The Layer Above the Ledger; Solution Paper: Proof of Custody; the sector-parallel Secure Law paper Secure Cloud, or Sealed?; and scenario paper Sealed Desktop, or Sealed Inference?

Vendor positions, provider terms and regulatory specifics change and are partly self-reported. Reconfirm against current official sources, and have qualified counsel review, before external circulation. This paper is information only and is not legal, tax or accounting advice.

IntelekIQ · Secure Accounting · Solution Paper: The Assistant You Already Trust. Companion to the Secure Accounting series. Conceptual overview; product detail is shared in discovery conversations.