Our core specialism
SAP Business One, end to end
SAP Business One runs finance, sales, purchasing, inventory, production and reporting on one set of data. Getting it live is a configuration exercise. Keeping it useful as your processes change, your volumes grow and other systems come and go is the actual work — and that is the part we are built for.
- Microsoft SQL Server and SAP HANA
- Functional and technical, one team
- UK-based, working nationwide
Why people call us
Most SAP Business One problems are not software problems
The product is capable. Almost every difficult situation we are called into comes from how it was set up, what was left unfinished, or what happened after the implementer moved on.
The chart of accounts was designed for the software
Not for the reporting the board actually wants. Every management pack then needs a spreadsheet to translate it, and the translation is where the errors live.
Half the modules were never switched on
You are licensed for production, or service, or the approval procedures, and the business is still running that part on email and a shared folder.
Reporting happens outside the system
The data is in SAP Business One but not in a shape anyone can use, so the real numbers are assembled in Excel — and quietly diverge from the ledger.
The implementer has gone
Whoever configured it is no longer available, nothing was documented, and nobody currently in the business knows why it was set up this way.
Standard functionality genuinely does not fit
Your process is a real exception, not an unwillingness to change, and you have been told the only options are change the business or live with the workaround.
Support means explaining yourself from scratch
You raise a ticket and describe your configuration again to somebody who has never seen it, then wait for a fix that treats the symptom.
Integration was left as a manual step
Orders arrive in one system, stock lives in SAP Business One, and someone re-keys between them every morning before anything else can happen.
Nobody owns the month-end
Reconciliations take days. The stock valuation and the ledger disagree, and no single person can explain the difference without opening three screens.
How we work
We start with the close, not the configuration
The test of an ERP system is not whether it goes live. It is whether the month-end close gets easier afterwards. That is the outcome we design backwards from.
Most SAP Business One work is quoted as a configuration project with a training day at the end. We approach it differently, because the people doing the configuration here also understand what the finance team has to produce at the end of every month. Chart of accounts design, control accounts, cost centres and distribution rules, stock valuation method, the point at which revenue is recognised — these are finance decisions with system consequences. They are cheap to get right at the start and expensive to unpick later.
That also changes how we handle the parts of a system that do not fit. Where standard functionality genuinely runs out, we build: user-defined fields and tables, screen extensions, approval workflows, alerts, or a proper add-on against the SDK and Service Layer. Where it does not, we say so, because every line of bespoke code is something you will carry through every future upgrade.
We work on both database platforms, Microsoft SQL Server and SAP HANA, and we are equally comfortable taking over a system somebody else implemented. A good deal of our work starts as a short review of an installation that is not delivering what was promised.
What that means in practice
- Finance in the room from the first workshop
- A written solution design you approve before anything is built
- Bespoke development only where standard genuinely runs out
- Documentation you keep, whoever supports you next
Services
Six ways we work on SAP Business One
Engagements usually start with one of these and grow. You are not required to take the whole programme.
Implementation
Scoping, chart of accounts design, configuration, data load, testing and go-live — run with the finance team involved from the first workshop rather than the last.
Read more
Support
Named consultants who already know how your system is configured, so you are not re-explaining it to a queue every time something breaks.
Read more
Development & Add-ons
SDK and Service Layer work, user-defined fields and tables, screen extensions, approval workflows and alerts — where standard functionality genuinely runs out.
Read more
Integration
Connecting SAP Business One to e-commerce, warehouse, CRM, payment and third-party systems so data is entered once and moves on its own.
Read more
Reporting & Analytics
Crystal Reports layouts, query-based reports and dashboards built natively against your database, whether that is SQL Server or SAP HANA.
Read more
Data Migration
Master data, open items and trading history moved across with a reconciliation your finance team can actually sign off.
Read more
Engagement
Six stages, and you can stop after any of them
We do not require a full programme to begin. A two-day review of an existing system is a perfectly normal way to start.
Discover
We look at how the business actually runs rather than how the process document says it runs. Usually a day or two on site with the people doing the work.
- Process walkthroughs
- System health check
- Data quality assessment
Design
A written solution design: what the system will do, what it will not, which processes need to change and what will be built. You approve it before anything starts.
- Chart of accounts design
- Gap analysis
- Development specifications
Implement
Configuration, development and data migration delivered in stages you can see and test, rather than one long silence ending in a go-live weekend.
- Staged configuration
- Iterative demonstrations
- Trial data loads
Integrate
Connecting SAP Business One to the other systems that matter, so data is entered once and reconciles automatically rather than by hand.
- Interface design
- Error handling and retries
- Reconciliation reporting
Optimise
User acceptance testing, training and the first month-end close. This is where the value of an ERP project is either realised or quietly lost.
- UAT scripts
- Role-based training
- First close supported
Support
Ongoing support from the people who built it, with the option of us running the bookkeeping and management reporting on top of it.
- Named consultants
- Agreed response times
- Change requests
Depth
The parts of SAP Business One we actually work in
This is not a feature list from a brochure. It is the ground we cover on a normal engagement, functionally and technically.
Financials and banking
- Chart of accounts design and control accounts
- Journal entries, posting templates and recurring postings
- Accounts receivable and accounts payable
- Bank reconciliation and payment runs
- VAT handling and Making Tax Digital submissions
- Multi-currency and exchange rate differences
- Cost centres and distribution rules
- Fixed assets and depreciation
Sales, purchasing and CRM
- Quotations, orders, deliveries and returns
- A/R and A/P invoicing and credit notes
- Blanket agreements and special prices
- Business partner master data and credit limits
- Opportunities, activities and pipeline tracking
- Gross profit checks and approval thresholds
Inventory and warehouse
- Item master data and item groups
- Multiple warehouses and bin locations
- Batch and serial number management
- Goods receipts, issues and stock transfers
- Cycle counting and stock postings
- Landed costs and valuation methods
Production and planning
- Bills of material and production orders
- Backflush and manual issue methods
- MRP runs, forecasts and recommendation reports
- Subcontracting and outsourced operations
- Resources, capacity and routing
- Work in progress and variance reporting
Platform and database
- Microsoft SQL Server and SAP HANA deployments
- Windows client and Web Client
- System landscape, companies and authorisations
- Upgrade planning and regression testing
- Performance investigation and query tuning
- Backup, recovery and environment refreshes
Extension and integration
- DI API and UI API development
- Service Layer (OData) services
- Integration framework (B1if) scenarios
- User-defined fields, tables and objects
- Formatted searches and validations
- Approval procedures and alerts
- Crystal Reports layouts and reports
What changes
What a properly looked-after system gives you
These are the outcomes we work towards. What any individual business achieves depends on where it starts, and we would rather say that than publish an average.
A close that shortens instead of slipping
Reconciliations designed into the configuration rather than bolted on afterwards, so month-end stops being an exercise in finding differences.
Reporting that comes out of the system
Management figures produced from the ledger itself, not rebuilt in a spreadsheet each month by the one person who knows how.
Data entered once
Integrations that move orders, stock and payments between systems automatically, removing the morning re-keying and the errors that come with it.
Capacity you already paid for
Modules you are licensed for actually in use — production, service, approvals — rather than sitting switched off behind a workaround.
Fewer people-shaped dependencies
Configuration and customisation documented, so the business is not exposed when one person is on leave or leaves altogether.
An upgrade path you can take
Bespoke work built against supported interfaces, so a version upgrade is a planned exercise rather than a reason to stay where you are.
What to expect
The shape of a typical engagement
Every business is different and we will not quote before we understand yours. These are the ranges we see most often, so you can judge whether the conversation is worth having.
System review
Two to five days. A health check of an existing installation, ending in a written findings and recommendations document that you own.
New implementation
Typically three to six months from first workshop to go-live for a single-company, single-site business. Multi-company, multi-currency, manufacturing or heavy integration extends this.
Development work
From a half-day formatted search or alert, to a multi-week add-on with its own specification, test plan and support arrangement.
Integration
Usually two to eight weeks per interface, depending on how well the other system is documented and whether it has a usable API.
Data migration
Runs alongside implementation. Master data is straightforward; open items and trading history are where the time goes.
Support
Ongoing, with agreed response times and a named consultant who knows your configuration. Monthly, with no long tie-in.
We do not publish day rates or fixed prices, because a number without a scope behind it is meaningless and usually wrong. You will have a written scope and a fixed quotation before any work begins.
Fit
Whether this is the right conversation
A good fit if
- You are running SAP Business One and are not getting what you expected from it
- You are choosing an ERP system and want an assessment rather than a demonstration
- Your implementer has moved on and you need someone who will learn your configuration
- You need development work that will survive an upgrade
- You want the finance function and the system looked after by the same team
- You are a growing UK business that has outgrown its accounting software
Probably not us if
- You need SAP S/4HANA — a different product, for a much larger business
- You are looking for the cheapest possible licence resale and no advice
- You want a development team that will build whatever is asked without questioning it
- You need someone on site full time for an extended period
Common questions
Questions we are asked before a project starts
Is Oskar Systems an SAP partner?
No. Oskar Systems is an independent consultancy and is not affiliated with, endorsed by, or a reseller for SAP. We provide consultancy, development and support services around SAP Business One. Licences are bought from SAP or through an SAP partner, and we work alongside whoever holds that relationship. Being explicit about this matters more to us than the badge would.
Can you support a system that somebody else implemented?
Yes, and it is a large part of what we do. We start with a review of the existing configuration and data so we understand what we are taking on, then agree what needs correcting before ongoing support begins. We will tell you plainly if we think the right answer is a reimplementation rather than a rescue.
Do you work with SQL Server or SAP HANA?
Both. SAP Business One runs on Microsoft SQL Server or on SAP HANA, and the choice affects reporting, licensing and infrastructure more than it affects day-to-day use. We work across both, including reporting and development written natively for each, and we can advise on which suits your circumstances.
How is SAP Business One different from SAP S/4HANA?
They are separate products for different sizes of business. SAP Business One is SAP’s ERP for small and mid-sized companies, usually running as a single integrated system across finance, sales, purchasing, inventory and production. S/4HANA is SAP’s enterprise platform, aimed at much larger organisations, with a correspondingly larger cost and implementation footprint. If a consultancy is proposing S/4HANA to a fifty-person business, ask why.
Should we choose SAP Business One or Microsoft Business Central?
It depends on how you manufacture, how you report, and what your team already uses day to day. We work with both, so we have no reason to steer you either way. We have published an honest comparison rather than a sales case, and we will give you a straight recommendation once we have looked at your processes.
Can you help if we have not decided on an ERP system yet?
Yes. A selection exercise is a reasonable engagement on its own: we look at how you operate, what your reporting has to produce and where the manual work sits, then set out the realistic options with the trade-offs stated. That work stands on its own whether or not you go on to implement with us.
What happens to our customisations when we upgrade?
That depends entirely on how they were built. Work done through supported interfaces — user-defined fields and tables, formatted searches, the SDK and the Service Layer — carries forward predictably and is tested as part of the upgrade. Direct database modification does not, and it is the usual reason a business finds itself stranded on an old version. We only build the former.
Related
Where to go next
Microsoft Business Central
The Microsoft alternative, and an honest comparison from a team that works with both platforms.
Read more
ERP + Accounting
Why running the system and the finance function together removes most of the manual work in between.
Read more
Industries
How this work differs in manufacturing, distribution, wholesale and professional services.
Read more
Tell us what your system is not doing.
A first conversation costs nothing and commits you to nothing. Describe what is not working and we will tell you honestly whether it is a configuration problem, a process problem, or a reason to look at something else entirely.
Or call +44 7493 619245 — Monday to Friday, 09:00–17:30.