A build-to-order SAP Business One add-on that links regional Gulf and Levant payment acquirers to Incoming Payments and Journal Entries, with settlement-file reconciliation. Built for your acquirers after a scoped quotation. Built to order by ECOSIRE for SAP Business One (build-to-order) — indicative price from $799.00 USD; request a quote for a scoped proposal.
A build-to-order SAP Business One add-on that links regional Gulf and Levant payment acquirers to Incoming Payments and Journal Entries, with settlement-file reconciliation. Built for your acquirers after a scoped quotation.
Built to order
Businesses across the Gulf and the Levant rarely collect through a single global card processor. A distributor in Riyadh takes domestic debit cards, a retailer in Kuwait routes through the national switch, a services firm in Amman or Beirut collects through a local acquirer with its own settlement calendar, and almost everyone is now accepting an installment or wallet product alongside cards. Each of those channels produces its own authorisation record, its own merchant statement, and its own fee structure.
SAP Business One does not know any of it. The typical result is an accountant exporting a portal report once a week, matching amounts by eye against a list of open A/R Invoices, keying Incoming Payments one at a time, and then posting a manual Journal Entry for the acquirer's commission and any FX difference. Refunds and chargebacks arrive days later and get handled as ad-hoc credit notes with no link back to the original transaction. Cash in the bank never quite equals cash in the ledger, and the month-end close absorbs the gap.
ECOSIRE builds a per-tenant SAP Business One add-on that treats each regional acquirer as a configured payment channel and writes every money movement back into the ledger where it belongs.
Each acquirer you use is defined as a channel record stored in User-Defined Tables, exposed through a User-Defined Object form inside the SAP Business One client. A channel holds its endpoint and credentials, the currency it settles in, the merchant identifier, the fee model (percentage, fixed, or tiered), the settlement cycle, and the House Bank Account and G/L accounts to be used for clearing, fees and FX differences. Credentials are stored encrypted and never written to the transaction rows.
When a payment authorisation is confirmed, the add-on creates an Incoming Payment against the correct Business Partner and applies it to the open A/R Invoice or Sales Order down payment, using the Service Layer so that SAP Business One's own posting logic, exchange rates and internal reconciliation all apply. Where a channel settles net of commission, the add-on books the gross receipt to a clearing account and posts the acquirer fee to its configured expense account, so the amount landing on the House Bank Account matches the bank statement line rather than the invoice total.
Most regional acquirers publish a settlement or batch report rather than a real-time ledger. The add-on ingests those files on a schedule, matches each line to the transaction it created using the stored acquirer reference in a User-Defined Field, and produces a reconciliation run showing matched, unmatched and disputed lines. Matched batches post the corresponding Journal Entries for fees and rounding. Unmatched lines are held in a review queue with the reason recorded, so nothing is silently written off.
A refund raised against a captured transaction creates an Outgoing Payment or applies to an A/R Credit Memo, keeping the link to the original document through the stored reference. Chargebacks are recorded as a distinct state with their own G/L treatment and can be routed through a SAP Business One approval procedure before anything posts.
Channels settling in a currency other than the local currency post through the configured FX difference account using the exchange rate on the settlement date, not the invoice date, which is where most manual reconciliations drift. Where you run several company databases, each database receives its own channel configuration and its own accounts.
The add-on ships with a transaction browser inside SAP Business One filtered by channel, status, date and Business Partner, plus Crystal Reports layouts for a settlement summary and an unreconciled-transaction listing that finance can run without leaving the client.
Wholesale and retail businesses in Saudi Arabia, the UAE, Kuwait, Qatar, Bahrain, Oman, Jordan, Egypt and Lebanon that collect through domestic switches or regional acquirers; e-commerce operations feeding orders into SAP Business One that need the money side to follow; and finance teams whose close is being delayed by manual payment matching.
The add-on is built against the SAP Business One Service Layer (OData/REST) for document creation and reading, with the DI API used where a specific object or posting behaviour is only exposed there. Extensibility is handled through User-Defined Fields on Business Partners, Incoming Payments, A/R Invoices and Journal Entries, User-Defined Tables for channel and settlement data, and User-Defined Objects for the configuration and reconciliation forms. It runs on SAP Business One 10.0 on either Microsoft SQL Server or SAP HANA, on-premise or on your hosted infrastructure. Outbound calls to acquirers go over TLS from a service component you control; no payment card data is stored in your company database.
Nothing here is a shelf product. The sequence is:
1. Scoping call. We confirm which acquirers you use, their integration documentation and settlement formats, your currencies, your chart of accounts mapping, your SAP Business One version and database platform, and who owns the merchant credentials. 2. Fixed quote. You receive a written scope and a fixed price and timeline before any code is written. The listed price is the starting point for a single-acquirer scope; additional acquirers or unusual settlement formats are quoted explicitly. 3. Build. Typical lead time is two to four weeks depending on how many acquirers are in scope and how quickly their sandbox credentials are available. 4. Install in test. We install into your test company database first, configure the channels, and run transactions end to end against acquirer sandbox or low-value live credentials with your finance team watching the postings. 5. Production install. Once you sign off on the test postings, we install into the production company database, migrate the configuration, and stand by for the first live settlement cycle. 6. Support. A defined support window follows go-live for defect fixes and configuration adjustments, with the source code handed to you so you are never locked to us.
A short call to confirm the workflow, your platform version and where the integration boundaries sit.
You receive a written scope and a fixed price. Nothing is built until you approve it.
We develop against a copy of your configuration and test it there. Typically two to four weeks.
We install on your instance, hand over the source, and support it for twelve months.
Spends the first week of every month reconciling acquirer portal reports against open invoices and posting commission entries by hand. Gets automated Incoming Payments, fee postings and a settlement reconciliation run that shows exactly which lines still need a human.
Cannot close confidently because the bank balance and the clearing account never agree once commission and FX are involved. Gets gross-versus-net posting on the settlement-date rate, so the House Bank Account matches the statement and differences land in a named account rather than a suspense adjustment.
Is asked to connect several regional acquirers to SAP Business One but has no appetite for a fragile database-level integration. Gets a Service Layer and DI API add-on with source code, credentials held outside the transaction tables, and an install path through the test company database first.
| Criterion | ECOSIRE | Custom Build | Competitor |
|---|---|---|---|
| Regional Gulf and Levant acquirers rather than only global card processors | Included | Partial support | Partial support |
| Automatic Incoming Payment creation applied to open A/R Invoices | Included |
From $799.00
Starting point — quoted to your scope
| Included |
| Settlement-file ingestion with matched, unmatched and disputed classification | Included | Partial support | Partial support |
|---|
| Acquirer commission posted automatically as a Journal Entry to a mapped G/L account | Included | Partial support | Partial support |
|---|
| Settlement-date FX difference handling for cross-currency channels | Included | Not included | Partial support |
|---|
| Chargeback tracking routed through a SAP Business One approval procedure | Included | Partial support | Not included |
|---|
| Source code delivered to the customer with no runtime dependency on the vendor | Included | Included | Not included |
|---|
| Install path through the test company database before production | Included | Partial support | Partial support |
|---|
OCR capture and two- and three-way matched A/P invoice posting for SAP Business One. Built to order for your suppliers, tolerances and approval rules after a scoping call and fixed quote.
A guided month-end close and reconciliation assistant for SAP Business One, built to order for your chart of accounts, period calendar and approval rules. Nothing is pre-packaged.
A build-to-order SAP Business One add-on that scores invoice, inventory and price-list activity for anomalies — negative margin, dead stock, shrink and price drift — and routes them for review. ECOSIRE builds it for your company after a fixed quotation.
A conversational analytics layer for SAP Business One that answers plain-language questions on sales, margin and stock. Built to order for your company database, quoted after a scoping call and installed per tenant.