Automate the Business One jobs that only get done when somebody remembers.
B1Flow is workflow automation software for SAP Business One. It runs on your own server beside Business One and takes over the jobs your team does by hand today, like turning deliveries into invoices, chasing overdue accounts, reordering stock and closing orders that will never ship. You describe a job the way you'd explain it to a colleague, it asks the questions a consultant would ask, and it builds the workflow in dry run so you can see what it would do before it does anything.
See it in action
From one sentence to the invoice in the customer's inbox
This is the first job on the list further down, built and run for real. One sentence goes in, B1Flow asks whether the invoice should be posted or left as a draft, and it builds a twelve-step workflow that's saved switched off. Once it's switched on, a delivery added in Business One is invoiced on its own, and the PDF is in the customer's inbox about a minute later. Every screen is from that one build and that one run. It's a minute and a half long and silent, with the captions in the picture.
+–Read what's on screen
- The truck has left. Has the invoice left SAP Business One?
- Describe it the way you'd say it. One sentence goes into the builder: “When a delivery is added, create the invoice from it and e-mail the customer the PDF.”
- It plans, and asks first. Before it builds anything it writes a plan and asks its questions. The first one is whether to post the invoice, since a customer can only be sent the PDF of a posted one. Its recommended answer was a draft for somebody to review, and the answer chosen was to post it straight away and mail the PDF.
- It writes down what you chose, before anything is saved. On the review screen, under Assumed and noted, it says it creates posted A/R invoices rather than drafts, because that's what it was asked to do.
- 12 steps, from one sentence. The workflow checks first that the delivery hasn't been invoiced already, so no delivery is ever invoiced twice.
- It copies the delivery the way B1 does. The invoice it sends to Business One points each line at the delivery (base type 15, delivery 386), so Business One copies the items, quantities and prices itself.
- Created switched off, writing nothing. Until you switch it on. It's saved with Enabled unticked and Dry run ticked, and then switched on.
- A delivery is added in SAP Business One. Delivery 386 for Parameter Technology, AUD 1,856.25.
- B1Flow picks it up on its own. The run starts from the event at 12:21:12. Every step on the delivery's path succeeds, and the two logging steps it didn't need are skipped.
- The invoice is created from it, and the delivery is closed. A/R invoice 561, with the remark “Created by B1Flow from delivery 386”. The delivery now shows as Closed, and Business One's Relationship Map links the two.
- In the customer's inbox at 12:22. An e-mail with the subject Invoice 561, and Invoice 561.pdf attached.
- In B1's own invoice layout. The PDF is Business One's own invoice layout, with a total of AUD 1,856.25.
Sound familiar?
Twelve jobs that belong to a person today
Most Business One sites have a list like this one, and every item on it gets done late, or on a good week, or not at all. Some of the fixes below ship as ready-made templates you install and switch on, and the rest are a single sentence typed into the workflow builder.
Getting paid
The work between the goods leaving and the money arriving, which tends to be somebody's job on a Friday afternoon.
Delivered on Monday, invoiced on Friday, and now and then never invoiced at all.
When a delivery is added, B1Flow creates the A/R invoice from it, gets Business One's own PDF of it and emails it to the customer. The invoice is copied from the delivery the way you'd copy a document by hand, so the items, quantities and prices come from the delivery itself rather than being typed in again.
Built from one sentenceNobody chases overdue invoices until the last week of the month.
Every Tuesday morning, each customer with invoices more than 30 days overdue gets an email with those invoices attached as Business One PDFs, and you get the list of who was sent what. On the first of the month, every customer can get last month's invoices combined into one PDF, and that one ships ready-made.
Built from one sentenceThe credit check passed, and the customer was months behind.
Every new sales order goes to an AI agent that looks up the customer's overdue invoices and credit, compares the lines with what they normally buy, rates the risk and writes a note. Anything that isn't low risk lands in the sales manager's inbox, because a credit limit is one number and whether an order should go out has never been one number.
Ships as a templateCustomers quietly stop reordering, and nobody notices until the year-end numbers.
B1Flow reads each customer's buying history, works out who is due to reorder what, and creates draft sales orders for the rep with the reason attached. Claude reviews every proposal first and can drop one-off purchases or round to pack sizes, and a review step can put the list in front of the rep to change or drop lines before anything reaches Business One.
Ships as a templateStock and margin
Where money leaks slowly enough that nobody sees it until the quarterly review.
Your supplier put the price up in March, and you found out in September.
When a goods receipt is added, B1Flow compares each line's price with the purchase order it came from and emails the buyer anything more than 2% higher, while there's still time to have the conversation with the supplier.
Built from one sentenceOut of stock on the things that sell, and years deep in the things that don't.
The stock reordering automation looks at each item's own history before it forecasts it, so a part that sells four times a year doesn't get the same maths as one that sells every day. Lead times are learned from your own receipts against your own orders rather than the number somebody typed into the item master years ago, and the result is a draft purchase order per vendor for purchasing to approve.
Ships as a templateYou bought the last system and still can't say whether it helped.
Before you switch anything on, the back-test runs the forecasts as of dates in the past on your own history and sets them against what was actually ordered. Once it's running, the outcome report shows which drafts became real orders, which were changed first and which were deleted.
Built inThe everyday admin
Small jobs, done by hand every day by someone who could be doing something more useful.
Customers email their orders as PDFs, and somebody types every line into Business One.
When an order lands in the orders mailbox, Claude reads the PDF, scan or photo, finds the customer in Business One and matches each line to your items, starting with the customer's own item codes if you keep them as BP catalogue numbers. Anything it isn't sure of, like a line matched only by its description, a price well away from that customer's price list or a delivery date that's already gone, is written down for whoever approves it. They can correct the customer, the items, the quantities and the prices, and then it becomes a draft sales order for sales to check.
Ships as a templateCustomers ring to ask whether you got their order.
When a sales order is added, the customer gets the order confirmation as a PDF in their inbox a minute or so later, so nobody has to ring anybody.
Built from one sentenceThe Monday report is somebody's whole Monday morning.
The open orders report groups your orders by customer with subtotals and a grand total, and produces a web page, a PDF and an Excel workbook. It's emailed every Monday and can be run any time with a date range, and people who only need to read reports can open them without being able to change anything.
Ships as a templateThe warehouse waits for somebody to print the pick list.
When an order is added it waits for someone to release it, from the Reviews page or a button in Teams or Slack, and then the pick list is created in Business One and printed on the warehouse printer.
Ships as a templateSales orders from years ago, still open and still in your commitments.
Every night, orders older than the age you choose are closed with a note in the remarks saying why, unless somebody has marked them to keep. In dry run it hands you the list and touches nothing, so you can read it for a week before it closes a single order.
Ships as a templateThe real reason
Why none of this got automated before
Each of those jobs is half a day of consultant time, and nobody signs a quote for half a day to save somebody twenty minutes a week. So the list never gets shorter, and the jobs stay with whoever has always done them. B1Flow makes each one small enough to simply get done, and it doesn't leave you with something only one person understands.
Say it the way you'd say it to a person
Type what should happen and B1Flow asks what a Business One consultant would ask before building anything: a draft or a posting, which documents count as history, who gets the proposals. Then it builds the workflow, checks that every step is complete and connected, and saves it switched off and in dry run.
A change is a sentence, not a support ticket
Tell it to also skip customers who are on hold and you get back exactly what would change, step by step, with the workflow switched off while you look. Keep the half you like, and nothing is saved until you press Save.
Somebody finally writes down what it does
Explain turns any workflow, including one you didn't build, into a hand-over document: the trigger in plain words, each step and what to watch out for, what it writes into Business One, and what to check before switching it on.
When Business One says no, you see what it was asked
Every failed step keeps the request exactly as it was sent next to the error Business One gave back, and Fix this proposes a correction you can check before applying, or tells you the problem is somewhere else.
Before it touches the live company
Nobody wants to be the person who let software loose on the live company.
That's a fair worry, and it's the one B1Flow was designed around rather than covered with a disclaimer.
Dry run first
Every template that writes into Business One, and every workflow the builder creates, starts out writing nothing. It runs against your live company and logs what it would have created, changed or sent, so you can read that for a week before you trust it.
Drafts, not postings
The sales and purchase orders the forecasts propose arrive as drafts in Business One for a person to confirm, and when you ask the builder for a document, its recommended answer is a draft. Posting straight away is a choice you make.
A person where it matters
A workflow can stop and wait for someone to tick, correct and approve, from a link in an email, a Business One message, or a button in Teams or Slack, with reminders and a deadline you decide in advance.
Every run on the record
Each step's input, output and log is kept, so what happened at two in the morning last Tuesday is a page you can open. With the failed-run alert switched on, a failure reaches a person straight away, and Retry picks up from the step that broke.
The approved lines become a draft purchase order in Business One, and the decision is recorded under the approver's name.
For whoever looks after your server
It isn't an add-on, so it won't be the reason an upgrade gets put off.
B1Flow runs as a Windows service on your own server and talks to Business One through SAP's Service Layer, on SQL Server or HANA. Your workflows, your run history and your stored connections stay on that server, and the connection passwords are encrypted there.
At a glance
The short version
- What it is
- Workflow automation software for SAP Business One, with a visual editor and an AI builder
- Runs on
- Your own Windows machine or server, as a Windows service beside Business One. Your workflows, run history and connections stay there.
- Connects through
- SAP's Service Layer, on SQL Server or HANA, with Business One 10.0 or later. Business One's own document PDFs come through SAP's API Gateway.
- Starts from
- New or changed Business One records, a schedule, an e-mail arriving in a mailbox, a file landing in a folder, a webhook, a button, another workflow, or a run that failed
- Works with
- E-mail, Microsoft Teams, Slack, printers, PDF, Excel and CSV, and any system with an HTTP API. It reads orders and other documents from PDFs, scans and photos, and from CSV, Excel, JSON and text files.
- Building blocks
- 55 triggers and steps, and 18 ready-made templates
- AI
- The builders use Claude, on your own Anthropic API key, to build, explain and fix workflows, and they can be switched off. The AI steps inside a workflow run on Claude, or on Mistral's EU endpoint, a German or French cloud, OpenAI or Azure OpenAI on your own key with that provider, or on a model on your own server.
- Data protection
- New AI steps hide personal fields like phone numbers, e-mail addresses, street addresses and bank details from the model, and can send names and contact details as placeholders that B1Flow swaps back in the answer. An administrator sets one AI policy for the installation, deciding which providers, models and files the AI steps may use, and a workflow that breaks it doesn't run.
- Before it writes
- Dry run, drafts instead of postings, approval steps from e-mail, Teams or Slack, and a record of every run
- Founding price
- US$2,990 a year per company database, with unlimited users, fixed for three years. This is the founding price, for the ten founding places only. The founding offer has the details.
- Made by
- B1 Developers in Brisbane, Australia, building for SAP Business One since 2011
How it compares
Where B1Flow fits among the other automation tools
There are good tools for automating around Business One, and they're built for different jobs. This is how each one reaches Business One, and when it's the better choice.
| TOOL | HOW IT REACHES BUSINESS ONE | THE BETTER CHOICE WHEN |
|---|---|---|
| B1Flow | Built for Business One only. It runs on your own server, reads and writes through the Service Layer, reacts to new and changed records, and gets Business One's own document PDFs. | The job lives inside Business One, in finance, sales, purchasing or the warehouse, and you want it built from a sentence and proven in dry run before it writes anything. |
| appse ai | An AI automation platform for several ERPs, Business One among them, with its own Business One connector. It builds a workflow from a plain-English description, has over 100 Business One templates, and runs in the cloud, on-premise or hybrid. | Business One is one of several ERPs in the group, or most of the work is keeping it in step with a web shop, a CRM and other apps, with AI agents watching orders, receivables and stock across them. |
| n8n, Make, Zapier and Power Automate | General tools for connecting cloud apps. None of them makes a connector for Business One itself, so it's reached through the Service Layer with HTTP steps, or through a third-party or community connector. | Most of the work happens between cloud apps, Business One is one stop among many, and someone on the team is happy wiring up APIs. |
| Magic xpi, Alumio and BPA Platform | Integration platforms, each with its own Business One connector. | You're moving data between Business One and other systems, like a web shop, a CRM or EDI. |
| Boyum B1UP | An add-on inside the Business One client. | You want to change how the Business One screens behave for the people using them, with validations, macros and extra buttons. It works alongside B1Flow rather than instead of it. |
| SAP Build Process Automation | SAP's own automation platform, running in SAP's cloud (SAP BTP). | You're already on SAP BTP, or automating across several SAP products rather than Business One alone. |
Checked against each vendor's own pages in September 2026. If something here has changed, tell us and we'll fix it. Every option side by side, with pricing and where each one runs, is in our guide to workflow automation for SAP Business One.
Before you ask
The questions we get most
We already use Business One alerts. What's different?+–
An alert tells somebody that a job needs doing, and then it's still their job. B1Flow does the job: it creates the invoice, sends the PDF, drafts the purchase order or closes the order, and it only stops to ask a person at the points where you've told it to.
How is B1Flow different from n8n, Zapier or Power Automate?+–
Those are general tools for connecting cloud apps, and none of them makes a connector for Business One itself, so reaching it means working with the Service Layer through HTTP steps or a third-party connector. B1Flow is built for Business One only: it reacts to new and changed records, knows the documents, gets Business One's own PDFs, and its builder asks the questions a Business One consultant would ask. It runs on your own server beside Business One, and everything it builds starts in dry run, writing nothing until you switch it on. If most of your automation happens between cloud apps and Business One is only one stop along the way, one of those tools may suit you better.
Is B1Flow an add-on? Does it work alongside B1UP?+–
It isn't an add-on. Nothing is installed in the Business One client or on anybody's PC, and B1Flow talks to Business One through SAP's Service Layer from its own Windows service, so it runs alongside B1UP and other add-ons rather than instead of them. They change how the Business One screens behave for the people using them, and B1Flow does the jobs nobody needs to sit at a screen for. One thing to know: checks that live in the client, like B1UP's validations, run on what people enter in the screens, so they don't see what B1Flow writes, while Business One's own business logic and your SP_TransactionNotification do.
Is it safe to let AI build things that write into our company?+–
The AI proposes and you decide. The builders show you a plan and a list of exactly what would change, nothing is saved until you press Save, and a new workflow is saved switched off and in dry run. Inside a workflow, the AI agent can only read from Business One, so every write happens in a step you can see and switch off.
What leaves our network?+–
Two things. The first is the AI calls, on your own key. When you use the builders, Claude sees the names of your fields and settings but not the values in your company, apart from anything quoted in an error you ask it to fix, unless you choose to let it see a couple of sample rows, and you can switch the builders off altogether. A workflow step that uses AI sends what that step is given to the provider it's set up with, which can be Claude, an EU provider or a model on your own server, where nothing leaves at all. New AI steps hide personal fields like phone numbers and bank details from the model, and the forecasting automations still work with their AI review switched off. The second is the licence check: when B1Flow starts and once a day after that, it tells b1developers.com its licence key, an install id, the SAP installation number, the names of the company databases it works with, the Service Layer's address, the server's name and the B1Flow version, and never any Business One data, workflows or counts.
Can the AI run in the EU, or without leaving the building?+–
Yes, for the AI steps inside a workflow. Besides Claude, they can run on Mistral's EU endpoint, on German and French clouds such as STACKIT, IONOS, OVHcloud and Scaleway, on OpenAI with European data residency or Azure OpenAI, or on a model on your own server, where nothing leaves the building. Mistral's EU endpoint is the one we've run with real documents so far. An administrator can set one AI policy for the whole installation: processing in the EU only, no US company, your own server only, or providers ticked one by one, along with which models are allowed and whether files may be sent. A workflow that breaks the policy is refused before it sends anything, dry runs included. Claude runs through Anthropic's own API, which processes in the US or globally, so under an EU policy the Claude steps are refused and the builders only ever see the names of your fields. Your data protection officer has the final word on what's acceptable, and we're happy to walk them through it.
Do we need a developer or a consultant to use it?+–
Not to run it, review what it proposes or build the everyday automations, which somebody who knows your Business One processes can describe in a sentence. For the bigger ones, we can build them with you.
Can we see what it would do with our own data?+–
That's what dry run and the back-test are for. Dry run runs against your live company and shows you everything it would have done without writing anything, and the back-test sets what the forecasts would have proposed last year against what your customers actually ordered.
What does it need to run?+–
A 64-bit Windows machine or server (Windows 10 or 11, or Windows Server 2016 or later) that can reach your Service Layer, SAP Business One 10.0 or later on SQL Server or HANA, and a B1Flow licence key. It brings its own .NET, so there's nothing else to install. The AI builders and the Claude steps need an Anthropic API key, and the other AI steps need a key for the provider they use, or a model on your own server. Business One document PDFs also need SAP's API Gateway, and printing needs a printer that server can see.
Does B1Flow work with SAP Business One on HANA, and in the cloud?+–
On HANA, yes: it works through the Service Layer on SQL Server or HANA, with Business One 10.0 or later. If your Business One is hosted, B1Flow needs a Windows machine that can reach the hosted Service Layer, and the API Gateway for Business One's own document PDFs, so it runs either on a Windows server at your host or on your own network with access to theirs. Whether that's possible is a question for your hosting partner, and it's worth asking before anything else.
How much does B1Flow cost?+–
The founding price, for the ten founding places only, is US$2,990 a year per company database, with unlimited users and everything included, and it's fixed for three years. Australian companies pay A$3,990 a year plus GST. The first year also has a one-off launch package, currently US$900, in which we install B1Flow on your server and set up three jobs with your team. The founding offer page has the full price table.
Tell us the job nobody has time for, and we'll show you it running.
A 30-minute demo, run on a job that looks like one of yours.
Or take one of the ten founding places →Requires SAP Business One 10.0 or later with Service Layer access (SQL Server or HANA), a 64-bit Windows machine or server to run on, and a B1Flow licence. The AI builders need an Anthropic API key, and the AI steps a key for the provider they use, unless the model runs on your own server. B1Flow is an independent product by B1 Developers and is not endorsed by or affiliated with SAP SE. SAP and SAP Business One are trademarks of SAP SE.
Last updated 5 October 2026