What Tipalti's AP Agent means if your finance runs on Business Central in Southeast Asia

As of 5 November 2026. Product pages change. The vendor pages linked below are the authority, not this post.

On 22 October 2026, Tipalti announced AP Agent, an AI agent for accounts payable that runs inside its payables and payments platform. If your finance team is on Business Central in Singapore or Malaysia, somebody will forward you that announcement with one line on top: "Should we be doing this?"

This is our answer. The design is right. The scope is narrower than the headline. And the questions that matter in this region are ones the announcement does not address.

The shape is right

Going by the press release, the agent connects invoice capture, coding, approvals, payments and reconciliation into one flow, and it decides from vendor history, general ledger data, accounting practice and company policy instead of fixed rules alone. The feature list matters less than four things the release says about control:

• Your team chooses which activities the agent handles alone and which need a person's approval.
• Each value the agent fills in comes with field-level reasoning, and its actions are kept in an audit trail.
• Exceptions go to a person.
• Corrections are applied to later processing, and the range of work the agent does alone can be widened over time.

That is the pattern we build to as well: the agent works the case and shows why, a person decides the uncertain ones, and automation is extended one decision type at a time. A large vendor shipping it is good news for buyers. It makes "explains itself, hands the exceptions to a person, keeps a record" the minimum to ask of anyone selling AI into finance operations. That includes us.

What it means on Business Central

The vendor has an AppSource-certified connector for Business Central, and its own page is clear about the division of labour. Capture, validation, routing and payment execution happen in its platform. Results sync back in both directions. Business Central stays the system of record.

So the agent is not a setting you turn on in your ERP. Adopting it means moving the payables operation, and the payments, onto another platform. That can be a perfectly good decision. It is a bigger one than "add AI to AP", and it deserves to be evaluated as a platform change: migration, bank connections, supplier onboarding, who administers it.

Two things to check while you are there. Business Central has a Payables Agent of its own, and Microsoft's FAQ is candid about it: PDF invoices only, it does not post purchase invoices, it is supported in specific languages only, and you review each draft. And if your group runs more than one accounting system, read the vendor's integrations list. Today it names Business Central and SAP Business One. It does not name AutoCount or SQL Account.

Four questions the announcement leaves open here

None of this is criticism. A press release is not a specification. These are the questions we would put in writing before the demo.

Is it available to you? The release gives no availability date and names no country in Asia. The vendor's AI product page says availability depends on your region. Ask for the date in yours.

Does it fit local e-invoicing? In Singapore, the GST InvoiceNow Requirement reaches existing GST-registered businesses in steps between 1 April 2028 and 1 April 2031, and the IRAS FAQ (version dated 23 September 2026) puts purchase invoice data in scope wherever you claim input tax, not only sales. In Malaysia, e-invoicing has been phased in since 1 August 2024. The vendor's Business Central page mentions links to European e-invoicing networks and invoice capture in more than 145 languages. It does not mention InvoiceNow or MyInvois. That is not proof of a gap. It is a reason to ask which networks are live, and to have your own supplier documents read in front of you: Bahasa Malaysia, Chinese, Thai, whatever your suppliers actually send.

What about everything that isn't a supplier bill? By its own description the platform covers payables, mass payments, procurement, expenses, cards and treasury. The customer side is not on that list: billing readiness, matching receipts, claims, refunds, complaints, applications. Those queues have the same structure as AP. A document arrives, someone looks things up, checks them, and decides from a short list. An AP product does not cover them, by definition.

How would you know it works on your cases? No product page can answer this one, ours included. A demo runs on the vendor's invoices. What you need is the result on yours: take 200 to 500 past cases where you already know the right outcome, and measure what share the agent would have handled, where it would have been wrong, and what a case costs before and after. Then run it in parallel with your team, on live work, before anything is switched on. We wrote about why that order matters in why pilots fail.

Where that leaves you

If your payables already run on a suite that has an agent, use it. Turn it on for one activity, read its explanations for a month, and widen it when the errors have become boring. If you are choosing a payables platform anyway, put those four controls on the shortlist criteria.

The gap is somewhere else: the decisions those suites do not cover, on the systems you already have. Business Central, NAV, SAP Business One or AutoCount, with spreadsheets and a workflow tool around them. That is where we work. We do not sell a payables platform. Our assessment takes one process and three weeks, and measures it on your past cases. If the numbers hold up, we build Casesure for that process and start with a parallel run.

Whichever route you take, keep the order. Measure on your own past cases. Run in parallel. Automate one decision type at a time. A vendor who wants to skip a step, us included, is telling you something.