Your Invoices Are Not Training Data: Why FlowGo Went and Got ISO/IEC 27001:2022 Certified

On 13 August 2026, FlowGo was certified to ISO/IEC 27001:2022, the international standard for information security management, following an independent audit by InterCert. We're publishing this post not to wave a badge around, but because of a question we get in almost every serious procurement conversation: "If your AI reads our invoices, where does that information actually go?" It's the right question. Most vendors give a vague answer. Here's ours, in detail.

The Shortcut Most "AI Automation" Tools Take

Building a demo that reads an invoice is now trivially easy. A developer can wire a document to a public chatbot API in an afternoon, get a plausible-looking result, and put "AI-powered" on the pricing page. That is genuinely where a large share of the AI automation tools now being sold to SMEs came from.

The problem isn't the AI. It's everything that isn't there around it:

• Free and consumer AI tiers can use what you submit. On most consumer chatbot plans, the content you paste in may be used to improve the provider's models and can be surfaced to human reviewers. That is a documented, deliberate feature of those tiers — not a breach.
• Nobody signed anything. No data processing agreement, no defined retention period, no breach notification obligation, no named sub-processors. If your data ends up somewhere it shouldn't, there is no contract to point at.
• There's no audit trail. Ask a typical AI tool who accessed a specific document, when, and why. Most cannot answer at all.
• Shadow AI does the rest. Even where the vendor is careful, an overloaded admin staffer pasting a supplier price list into a free chatbot to "just summarise it quickly" achieves the same exposure without anyone noticing.

None of this shows up in a demo. It shows up two years later, in a due diligence questionnaire, a customer audit, or a PDPA enquiry you can't answer.

What's Actually Inside the Documents You're Automating

It's easy to think of accounts payable and sales order processing as low-stakes admin. Look at what a single month of those documents contains:

• Your customer list — who you sell to, how often, and how much. The single most valuable thing a competitor could obtain.
• Your pricing structure per customer — including the discounts you give your largest accounts and don't give anyone else.
• Your costing and margins — supplier invoices reveal what you pay, and purchase orders reveal what you charge. Together they expose your entire margin position.
• Your supplier terms — credit periods, rebates, exclusivity arrangements.
• Payment and banking details — the exact information targeted in invoice fraud and business email compromise.
• Personal data — contact names, phone numbers, and signatures, which brings Malaysia's PDPA, Singapore's PDPA, and Australia's Privacy Act into scope whether you planned for it or not.

Put plainly: a year of your AP and sales order documents is a fairly complete blueprint of your business. It deserves better handling than a copy-paste into a chat window.

"The AI Won't Remember It" Is Not a Security Control

The most common reassurance in this space is that the model doesn't retain anything. Even where that's true for a given tier, it answers only one narrow question and leaves the rest untouched:

• Where is the document stored before, during, and after processing?
• Which employees at the vendor can open it, and is that access logged?
• How long is it kept, and what happens when you cancel?
• Which sub-processors touch it, and were any of them assessed?
• What happens on the day something goes wrong — who gets told, how fast?

Those questions are about an organisation, not a model. Which is exactly what ISO/IEC 27001 examines.

How FlowGo Handles Your Data Differently

Here is what we actually do, stated concretely enough that you can hold us to it:

1. Your documents are not training data

FlowGo processes documents through paid enterprise AI APIs governed by commercial terms that prohibit the provider from using customer prompts, files, or outputs to train its models. We do not use free consumer chatbot tiers, and your documents are never pasted into one by a FlowGo employee. Nothing you send us is used to improve a public model.

2. Each company's data sits in isolated storage

Every company gets its own dedicated document storage, not a shared pool with logical filters bolted on top. One customer's invoices, price lists, and costing are not co-mingled with another's.

3. Your accounting system stays the system of record

FlowGo extracts data and posts entries into your AutoCount, SQL Account, QuickBooks, Xero, SAP Business One, or Biztory. We are the automation layer, not the place your financial history moves to. If you ever stop using FlowGo, your books are already where they belong.

4. Access is restricted, authenticated, and logged

Platform access uses role-based permissions and multi-factor authentication, and actions are audit-logged. Our staff do not review customer data except where required for support, security, or legal compliance — and we do not use customer financial data for advertising or profiling.

5. Encryption in transit and at rest

Documents are encrypted while moving between your channels and our platform, and while stored.

6. Vendors are assessed, not assumed

Vendor management sits inside our certified ISMS scope. Every sub-processor that touches customer data is assessed under the same system that was audited — including the AI providers.

7. Your customers keep using WhatsApp, and it's still controlled

The channels that make FlowGo convenient — WhatsApp, Telegram, email — are the same channels where documents usually leak, because they end up on personal phones and in personal inboxes. Routing them through FlowGo replaces an uncontrolled process with a governed one: a defined destination, defined access, and a record of what happened.

What ISO/IEC 27001:2022 Certification Actually Means

ISO/IEC 27001 is the international standard for an information security management system — the policies, controls, risk assessments, and review processes an organisation runs to protect information. Certification means an accredited independent body audited that system and found it conformant. It is not a self-declaration, a logo you can buy, or a one-off checklist.

Our certified scope covers the secure design, development, deployment, operation, and maintenance of FlowGo's AI, workflow automation, and business process optimisation solutions — including the automation platform itself, workflow orchestration, system integrations, data processing, and the supporting cloud infrastructure. It is supported by the functions of IT Infrastructure, Engineering, Product Development, Information Security, Human Resources, Legal & Compliance, Finance, Customer Success, Sales & Operations, and Vendor Management.

Note the last one. Vendor management is inside the scope, which is precisely the control that governs how customer data reaches an AI provider. That is the part most AI vendors have no answer for.

Certification is also not a one-time event: it carries annual surveillance audits, with full recertification due 12 August 2029. If we stop doing the things we were audited on, we lose it.

What certification does not mean is that risk is zero. No system is completely secure, and any vendor who tells you otherwise is selling something. What it means is that the risks are identified, controlled, independently checked, and reviewed on a schedule — instead of being hoped about.

Five Questions to Ask Any AI Vendor Before You Send Them a Single Invoice

Use these on us too. If a vendor can't answer them in writing, that answer is the answer:

1. Is our data used to train any AI model, yours or a third party's? Get it in writing, and get it specific to the tier you're on.
2. Who are your sub-processors, and how were they assessed? "We use AI" is not a sub-processor list.
3. Do you hold an independent security certification, and can I see the certificate? Ask for the registration number and verify it with the issuing body.
4. What is your data retention and deletion policy, and what happens when we leave? Especially where the vendor, not your accounting system, holds the records.
5. What is your breach notification commitment? If there's no defined timeline, there's no commitment.

The Point of All This

AI automation is worth doing. A team that stops keying invoices by hand gets days back every month. But the version of that trade where you quietly hand your customer list, pricing, and margins to a public model is a bad trade — you just don't get the bill for it until later.

We built FlowGo for distributors, wholesalers, F&B suppliers, contractors, and the accounting firms that serve them: businesses where pricing is competitive intelligence and a customer list is the company. The certification is our way of proving that we treat it that way, verified by someone who doesn't work for us.