SAP integration consulting

Connect SAP to the rest of your business.

SAP runs your finance, purchasing, inventory and production. We build the connections and tools around it, outside the core, so upgrades stay simple and your team stops retyping what SAP already knows.

Keep it, then extend it

What SAP does well, and where teams outgrow it.

Where SAP shines
  • One system for the operationFinance, purchasing, inventory, production and sales share one set of records.
  • Approvals inside S/4HANAFlexible workflow lets a configuration expert set approval steps for documents like purchase orders, and approvers act from My Inbox.
  • Stable, published connection pointsSAP lists its released interfaces in the SAP Business Accelerator Hub and keeps them stable from release to release.
Where teams hit the limits
  • Data still arrives from outsideCustomer orders by email, supplier invoices as PDFs and forecasts in spreadsheets still get keyed in.
  • Changing the core is costlyCustom code inside SAP makes upgrades harder, which is why SAP's own clean core guidance pushes new work outside it.
  • Teams work around itDepartments keep side spreadsheets and email threads for work SAP screens don't fit.
What we build around it

Connecting SAP to the rest of your work.

01

Customer orders from email into SAP

Incoming orders are read and drafted as sales orders for a person to confirm.

02

Supplier invoices matched to POs

Invoices are read and matched to purchase orders and goods receipts, with differences flagged.

03

Approvals people actually see

Requests reach approvers by email or chat, with the decision recorded in SAP.

04

Business One and your other tools in sync

Customers, items and orders stay matched between Business One and your online store or CRM.

05

Department tools outside the core

Small applications for work SAP doesn't fit, reading and writing through SAP's released interfaces.

06

Reports across systems

SAP numbers combined with data from your other tools in one scheduled report.

Before we start

How access works.

How we connect depends on your edition. In S/4HANA Cloud, your SAP administrator sets up a communication arrangement: a named outside system, a technical user and a predefined set of SAP services it may use, nothing more. In S/4HANA we follow SAP's clean core approach and build outside the core on its released interfaces, so your upgrades stay simple (see SAP on released interfaces). SAP Business One is sold and supported only through SAP partners, and connections use its Service Layer, so we work alongside your Business One partner. Either way, we build and test in a non-production system first.

FAQ

Common questions.

Do we have to replace SAP?

No. SAP stays your system of record. We build around it and connect what it doesn't reach.

Will this break when SAP upgrades?

We build on SAP's released interfaces, which SAP keeps stable across releases, test in a non-production system and add checks that alert us if something stops matching.

Do you replace our SAP partner?

No. Your partner keeps looking after SAP itself. We build the tools and connections around it and coordinate with them on access and testing.

Are you a certified SAP partner?

No. We're an independent integration consultant and development team. We build with SAP's official developer tools and approved access, using the access your team grants, and we work alongside your SAP admin or implementation partner rather than replacing them.

Partner with Inkwell

Tell us how you use SAP today.

A few sentences is plenty. We'll tell you what we'd connect first, and whether a ready-made app already does the job.