A CFO's guide to touchless AP in SAP B1

What “touchless” actually means

A supplier invoice arrives — by email, a watched folder, or an upload. The system reads it, checks the maths, resolves the supplier, matches it to the purchase order and goods receipt, and posts the A/P invoice through the SAP Business One Service Layer. When everything lines up, no one has to key anything. When something doesn't, it stops and asks. Touchless isn't “no humans” — it's “humans only where they add value.”

Where automation is safe

Automation is at its best on the invoices that are boring precisely because they're predictable:

• Recurring invoices from established suppliers you've posted dozens of times.
• PO-backed invoices where a 2- or 3-way match reconciles against the order and the receipt.
• Documents where the figures reconcile deterministically — lines sum to the subtotal, tax checks out, the grand total agrees.
• Amounts under a threshold your finance team is comfortable with.

For these, a person re-keying the data adds cost, not control. The machine is faster and, frankly, more consistent.

Where a human still belongs

Some decisions should never be automatic, no matter how confident the system is:

• A brand-new supplier the system has never seen — someone should confirm who they are.
• A change to a supplier's bank details — the single most common vector for invoice fraud.
• Any invoice over your mandatory-approval threshold, regardless of how routine it looks.
• Price or quantity variances outside tolerance, suspected duplicates, or a missing exchange rate.

These aren't failures of automation; they're the exceptions automation exists to surface.

Earned autonomy, not blind trust

The distinction that matters isn't “automated vs. manual” — it's whether autonomy was earned. A good AP system gates on the minimum confidence across every field and every line-to-account mapping, not an average, so one shaky value holds the whole invoice back. It learns each supplier's posting pattern from your team's own decisions, and a rule only earns the right to post on its own after a run of clean confirmations. The moment a person corrects it, that rule loses its autonomy and goes back to being watched.

The controls a CFO should insist on

Ask any AP automation vendor how they enforce these — in the data, not just the interface:

• A mandatory approval threshold no rule can bypass, changeable only under dual control.
• Segregation of duties: whoever — or whatever — creates a posting can never approve it.
• Two-person control plus out-of-band verification on any bank-detail change.
• An append-only, tamper-evident audit trail of what was extracted, what a person changed, and exactly what was posted.

Get those right and touchless AP stops being a leap of faith. It becomes what it should be: your team spending its time on the invoices that actually need judgement, and nothing else.