An AP team processing forty thousand invoices a year isn't making forty thousand tax decisions. On most PO-backed invoices the tax code arrived with the order, and AP's job is to check that the invoice agrees with it.

The decisions concentrate somewhere much narrower: non-PO spend, cross-border services, and anything involving a supplier whose status you can't confirm. That's where the liability hides, and it's worth knowing which of your invoices belong to that group before you automate anything.

Where the tax decision actually sits

The checks a clerk runs by hand divide cleanly into two kinds, and only one of them needs judgment.

Validity has an answer. An EU VAT number is checked in VIES, a UK one through the HMRC service that returns the registered name and address, and other countries maintain their own registers. A US employer identification number has no public validator, and IRS matching is open only to payers filing information returns, so for a US supplier the check is the number on file against the number on the invoice.

Treatment splits again. Where the jurisdiction and the supplier type determine the code, it is a rule and it can be applied automatically. Where the answer turns on facts about the transaction, a person decides: does reverse charge or an exemption apply, is the place of supply what the invoice claims, does the product category change the rate. The EU VAT Directive sets that framework, and the second group does not reduce to a lookup.

The invoice from Lisbon

Take a consultant in Portugal invoicing your German entity for services. There's no purchase order, so nothing upstream decided the tax treatment. The place of supply rules decide whether Portuguese VAT applies or whether your entity self-accounts under reverse charge.

Get it wrong in one direction and you've paid VAT you can't recover. Get it wrong in the other and your entity carries an underdeclaration.

Now change one detail. Instead of consulting days, the Portuguese supplier licenses you a piece of software and charges a royalty. A different regime applies here. Germany makes the debtor of the remuneration liable for withholding and paying the tax under Section 50a of the Income Tax Act, and that section is a closed list: performances by artists, sportspeople and entertainers in Germany, the domestic exploitation of those performances, remuneration for the use of rights such as copyright, know-how and industrial property, and supervisory board fees.

Straight consulting is not on that list, which is exactly why it catches people. The invoice that triggers withholding rarely looks special: a licence line, a speaker at your sales conference, a board fee to a non-resident director. The payer carries the liability in every one of those cases, and your AP process is where the obligation is caught or missed.

The four questions that decide who touches an invoice

Route on these, and you'll find that the vast majority never reaches your tax team at all:

• Did the order already settle the treatment? If the tax code came from the PO, AP checks agreement and stops there.
• Is the supplier's status confirmable today? Validity check with a date on it, not a memory from onboarding.
• Is this cross-border services? If yes, place of supply is a decision, not a check.
• Does a withholding obligation attach to the payer? If yes, it goes to a named tax owner before payment, always.

Write those four into your routing and the tax team's queue becomes short enough that they can look at every item in it properly.

What finance governs, and what stays automated

The line that holds under audit is the one where the automated part prepares and the person decides. Agents assemble the tax context before anyone opens the invoice: supplier master data with VAT identifiers, the ERP record, the external registers, the compliance history. They run every check that has a definite answer and present the ones that don't with reasoning logged.

Where the rule is determinate, letting agents assign the code and move on is the right choice. What an agentic workforce should not do autonomously is settle the judgment cases, the reverse charge calls and the place-of-supply questions, because your tax lead has to be able to say why in front of an authority eighteen months later, and that answer has to have an owner.

How Hypatos prepares and routes the tax check

At Hypatos, tax compliance validation is a skill of the invoice processing workforce. It builds the context first, checks validity against the registers, and applies the treatment rules your tax lead has written as instructions, then routes.

Invoices requiring a judgment call go to the named tax owner with the supplier record, the registry result and the relevant rule already attached, so the decision takes minutes rather than an afternoon of gathering.

The workforce proposes, a named person decides, and the record shows what was checked. For a tax question that sentence is the whole compliance position, because it means every treatment applied during the year has an owner and an evidence trail.

Hypatos fits when your tax exposure is concentrated in non-PO and cross-border spend, and when the people who answer for it need the context assembled rather than the decision made.

Count the population first

Before changing anything, count how many of last quarter's invoices fell into each of the four routing questions. In most AP volumes the percentage that needs a real judgment call turns out to be a small fraction, but yours is the only number that matters and nobody else can produce it for you.

That count is the whole business case. It tells you how much of your tax team's time currently goes on checks that had a definite answer all along.

‍