Guide · SAP Business One
SAP Business One automation — documents that write into your ERP
You already run SAP. The problem isn't SAP — it's that someone still keys every sale and every supplier invoice into it, one document at a time.
Sfarim doesn't replace SAP Business One. It connects through the Service Layer and builds the documents your team keys in by hand today — tax invoices, supplier invoices, purchase orders — and writes them straight into your SAP company. You approve; nothing is replaced.
A two-way connection to your store
An order arrives from your store, and Sfarim builds the tax invoice: the customer maps to a business partner in SAP, the SKU to an item, and the order number goes in as the reference that prevents duplicates. The invoice lands in SAP as a draft. Drop-ship orders fan out automatically to one purchase order per supplier, shipping to the end customer.
The connection runs both ways: every order is read from the store in real time and the documents are written into SAP, and the status is updated back onto the order in the store — so the store and SAP never drift apart. It all sits in one lane: what's ready to invoice, what's already invoiced, and what needs a look.
Supplier invoices capture themselves — and post into SAP
Supplier invoices capture themselves: from email, a phone photo, a folder, or a manual upload. Sfarim reads the document, builds an A/P invoice from it in SAP, and matches it automatically to the open purchase-order line it draws from — by supplier, item, open quantity, price, and the PO number printed on the invoice — so the PO line closes. An ambiguous match is held for a person, never guessed.
Item mapping that gets better over time
A store SKU and a supplier code aren't always the same as the item code in SAP. Sfarim learns the matches from your confirmations: map a SKU to a SAP item once and it remembers — and the supplier and its VAT identity are learned the same way. Anything still unmapped is held for review instead of posted to a catch-all account, so the books stay clean as coverage grows.
Draft first. You sign.
Every document lands in SAP as a draft by default. A real post is a separate, deliberate switch. An unmapped item or an ambiguous match is held for review and never posted to a catch-all account. And every document carries a durable key, so a retry or a repeated order never creates a second invoice.
Sfarim writes the document. You approve the posting.
The journal entry stays SAP's. Margin and VAT become visible.
SAP still creates the journal entry from the document, by your account determination — Sfarim never posts a second one. Instead it reads SAP's entry back and keeps a shadow ledger beside it, reconciled document by document, so margin and VAT are visible and any drift surfaces before the period closes.
Built for Israel
Allocation numbers (מספר הקצאה) stay owned by SAP's Israeli localization and the Tax Authority flow: an A/R invoice posts into your digital series and the number is read back, and a supplier invoice carries the supplier's own allocation number. VAT-inclusive web prices reconcile on gross, tax, and document total.
Do we have to replace SAP Business One?
No. Sfarim writes into your existing SAP company through the Service Layer. SAP stays the system of record and still creates every journal entry; we build the documents and feed them in.
Does anything post without our approval?
No. Every document lands as a draft by default, and a real post is a separate, deliberate choice. Anything unmapped or ambiguous is held for review, not guessed.
Could it create duplicate invoices?
No. Every document carries a durable key, so a retry or an order that repeats from the store never creates a second document.
How are supplier invoices captured?
From email, a phone photo, a folder, or a manual upload. Sfarim reads the document and builds an A/P invoice from it in SAP, matched to the open purchase order — no typing.
Do we have to map every item up front?
No. Sfarim learns from your confirmations — map a SKU to a SAP item once and it remembers, and the same for suppliers. Anything still unmapped is held for review, not posted to a catch-all account.
What do we need to install?
A Service-Layer integration user, and a small field on the SAP documents that makes duplicates impossible — added by your SAP partner, not by editing the database directly.