Skip to content
Swostik Nepal, home

Enterprise

Sarbo360

An ERP portal on top of SAP Business One, with connectIPS bill payments, used daily by about 200 staff.

Role
Developed and deployed
Organisation
Saurabh Group · Sarbottam Steels & Sarbottam Spinning
Timeline
2026 – present
Status
In production
Private codebase · walkthrough on request
  • TypeScript
  • React
  • Node.js
  • SAP Business One
  • SAP HANA
  • Service Layer
  • connectIPS
  • Mobile app
staff using it daily
~200staff using it daily
group companies
2group companies
SAP documents posted in one step
4SAP documents posted in one step

Context

Saurabh Group runs its companies, including Sarbottam Steels and Sarbottam Spinning, on SAP Business One. Purchasing, stores and finance staff needed one place to raise, approve, track and report on their daily work, on the web and on their phones, with every document still landing correctly in SAP.

Sarbo360 is a private, in-house system. Screens on this page are redrawn with sample data; no company records are shown.

Requirements

A selection of what the system had to do, written the way it was agreed with users:

Requirements
IDTypeRequirement
FR-01FunctionalTrace every purchase requisition through purchase order and goods receipt, and export the trail to Excel with the requester's remarks.
FR-02FunctionalPost a vendor transaction to four linked SAP documents in one step, with a vendor reference carried onto each.
FR-03FunctionalManage loans with per-row exchange rates; lock the loan header once its journal entry is posted.
FR-04FunctionalIssue stock from the bins that actually hold it, not from a default bin.
FR-05FunctionalPay bills through connectIPS from inside Sarbo360.
FR-06FunctionalReport raw-material lead time from PO date to production date.
NFR-01Non-functionalOne gateway to SAP: every read and write goes through a single, configured integration layer.
NFR-02Non-functionalIdempotent posting: a retried request never creates a duplicate SAP document, scoped per company.
NFR-03Non-functionalAudit: record who signed in and when.
NFR-04Non-functionalReports total on SAP's own basis (cancelled documents excluded, whole periods, not just the first page).

Process model

Purchase-to-pay in Sarbo360
  1. 01Purchase requestRaised by a department; stays editable
  2. 02Purchase orderApproved, sent to vendor
  3. 03Goods receiptReceived into the right bins
  4. 04A/P invoiceMatched to receipt
  5. 05PaymentSettled via connectIPS

Each step posts the matching SAP Business One document through the Service Layer.

Integration design

How Sarbo360 connects
  1. People
    • Purchasing
    • Stores
    • Finance
    • Management
  2. Sarbo360
    • Web portal
    • Mobile app
    • API & posting engine
    • Audit log
  3. SAP Business One
    • Service Layer (REST)
    • SAP HANA database
Payments
  • connectIPS
  • Bank

Simplified. One integration layer talks to SAP; payments go out through connectIPS.

What I built

  • Posting Wizard: one form that creates four linked SAP documents, with credit-memo reasons and vendor references.
  • Requisition-to-receipt tracing: a report that follows each request to its goods receipt, opened by default for buyers.
  • Loan management: per-row exchange rates, bank names instead of codes, and a header that locks once posted.
  • Inventory: stock issued from the bins that hold it; material requisitions close automatically when fulfilled.
  • connectIPS bill payments inside the portal.
  • Multi-company tenancy so the portal can serve more of the group's companies, with SAP posting keys scoped per company.
  • Audit log, recurring tasks with reminders, print layouts with whole amounts and the currency once in the column head.

Validation and deployment

Changes were checked against the agreed behaviour on SAP itself, not just in the portal: a report total had to match SAP's own figure, and a posted document had to appear in SAP with the right links. A pre-deployment checklist gated each release, and fixes came straight from users. One example: editing a purchase order once matched rows by their position instead of SAP's LineNum, which could update the wrong line, so I changed it to match on LineNum.

Outcome

staff in daily use
~200staff in daily use
companies: Sarbottam Steels and Sarbottam Spinning
2companies: Sarbottam Steels and Sarbottam Spinning
integration layer to SAP
1integration layer to SAP

Artefacts I produced

  • Requirements and screen inventory
  • Process flows (purchase-to-pay, payments)
  • User-permission matrix
  • Integration design (SAP Service Layer, connectIPS)
  • Pre-deployment checklist
  • User guides
Next case studyRotaract District 3292 Platform