Sales Order
From a customer's purchase order: PDF, Word, e-mail or a phone photo.
B1Nexus DocuFlow AI reads purchase orders, supplier invoices, e-mails, receipts and fault reports, matches them to your SAP Business One master data, and posts the right transaction after a quick review.
Illustrative example.
DocuFlow AI recognises what arrived and builds the matching SAP Business One document. Each type is a licensed module, so you switch on only what you use.
From a customer's purchase order: PDF, Word, e-mail or a phone photo.
From a supplier invoice: item lines, service lines on G/L accounts, or matched to goods receipts with a three-way check.
From an inquiry e-mail, with a new lead when you confirm one, and the first activity.
From a follow-up e-mail or meeting notes, with suggested opportunity changes and a follow-up task.
From a fault report or a typed description, with serial numbers and a scheduled technician visit.
From a receipt, bill or phone photo, with G/L accounts allocated from your own rules.
Auto-post rules let routine documents go straight to SAP. A document is posted without a person only when every condition holds. Otherwise it waits for review, and the job says why.
Watch Microsoft 365 and Gmail mailboxes, route jobs to the right person, and send an automatic acknowledgement.
In the app, by e-mail, or in Microsoft Teams and Slack: jobs to review, postings, failures.
Sales, AP, Service and Expense users, approvers and viewers. Users see their own jobs; shared queues when you want them.
Usage reports, data-retention rules, and an audit trail of who reviewed and posted what.
One installation per company, on your own Linux server next to SAP. No access from the internet needed; users connect over your network or VPN.
Documents go to Anthropic only to be read, with your organisation's own API key, stored encrypted. Card numbers are cut to the last 4 digits.
Every posting goes through the SAP Business One Service Layer, so SAP's own validation and authorisations apply.
Authenticator-app sign-in or Microsoft sign-in, role-based permissions per transaction type, and virus scanning of incoming files.
PDF, Word, e-mails (EML and MSG), images including phone photos, and plain text. Typed descriptions work too, for example a fault report entered by hand.
Only if you set up an auto-post rule, and only when every one of its conditions holds: no open checks, confidence above your minimum, exact or remembered SAP matches, a trusted partner and an amount within your limit. Everything else waits for review.
They are stored on your own server. They are sent to Anthropic only so Claude can read them, using your organisation's API key. Card numbers on receipts are reduced to the last 4 digits before anything is stored, and data-retention rules can remove old documents.
Every field shows a confidence score and every SAP match shows how it was found. The reviewer corrects the field or picks the right SAP record, and DocuFlow remembers that choice for the next document from the same partner.
No. Posting is idempotent: before it creates anything, DocuFlow checks what already exists in SAP, so a retry or a double click never creates a second document.
Yes. One installation serves one or more SAP Business One company databases, and every job belongs to a company. Users get access per company.
See DocuFlow AI read your purchase orders and supplier invoices and post them to SAP Business One.
The B1Nexus MCP Server lets Claude look up and act on live Business One data, with each user's own SAP permissions.