A build-to-order SAP Business One add-on that emails a secure per-invoice payment link, escalates reminders on an aging-based schedule, and posts settlements back as Incoming Payments. Scoped and quoted before we build. Built to order by ECOSIRE for SAP Business One (build-to-order) — indicative price from $499.00 USD; request a quote for a scoped proposal.
A build-to-order SAP Business One add-on that emails a secure per-invoice payment link, escalates reminders on an aging-based schedule, and posts settlements back as Incoming Payments. Scoped and quoted before we build.
Built to order
Most SAP Business One sites chase overdue receivables with a monthly statement run and a person with a phone. The statement lists balances but gives the customer no way to act on it. The customer has to find their own accounts payable process, raise a bank transfer, quote a reference that may or may not survive the transfer, and then somebody in your finance team matches an unreferenced bank line against an open A/R Invoice several days later.
Every friction point in that chain adds days to your DSO. The customer who genuinely intended to pay is blocked by effort. The customer who is stalling has no prompt beyond a statement they can ignore. And your team burns hours on manual matching and on remembering who was chased, when, and what they said.
The pattern that works is well established outside ERP: send the payer a link tied to one invoice, for the exact open amount, that takes a payment in a few clicks; then escalate automatically if it is not paid. What is missing is that pattern driven from the SAP Business One aging data itself, with settlements posting straight back to the invoice.
This is a build-to-order SAP Business One add-on. Nothing is pre-built and nothing is downloaded — after a scoping call and a fixed quotation we develop it for your gateway, your document set and your company database, then install it.
For any open A/R Invoice the add-on generates a signed, expiring link tied to that document key, the Business Partner, the open amount and the currency. The link resolves to a hosted payment page served by your gateway, so card data never touches SAP or our code. The link can be emailed automatically when the invoice is posted, sent on demand from the invoice screen, or included in the reminder emails described below. Partial payment can be allowed or blocked per your policy, and the link closes itself once the invoice reaches zero open balance.
Reminder levels are driven off the invoice due date and the current open balance read from SAP, not from a static list. You define the schedule — for example a courtesy notice before due date, then reminders at 7, 14 and 30 days past due, then a final notice — and the content of each level. Each reminder carries the payment link, the invoice PDF, and the current open amount at the moment of sending, so a customer who has part-paid never receives a demand for the original gross figure.
Escalation respects reality. A Business Partner on payment hold, in dispute, on a payment plan, or flagged for manual handling is excluded through a User-Defined Field on the Business Partner master or the invoice. Once an invoice is settled, the remaining schedule for that document stops immediately.
When the gateway confirms a payment, the add-on creates the Incoming Payment through the Service Layer and applies it to the specific A/R Invoice the link was issued for, posting the corresponding Journal Entry. This is the step that removes the manual matching work: the payment arrives already reconciled to a document rather than as an unidentified bank line. Gateway fees can be posted to a nominated G/L account so the deposit amount ties out.
A collections view built on your aging data shows, per Business Partner and per invoice, which reminder level has been reached, when each message was sent, whether the link was opened, and whether a payment attempt failed. Notes and promised-to-pay dates are captured against the document. Approval procedures can gate anything sensitive — a final-notice send, a write-off, or a suspension of chasing on a key account.
The add-on reads aging and document data through the SAP Business One Service Layer (REST/OData), with the DI API used where an operation is better handled there. Reminder state, link tokens, send history and promised-to-pay notes are stored in User-Defined Tables wrapped in User-Defined Objects; per-Business-Partner and per-invoice exclusions use User-Defined Fields. The scheduler runs as a service alongside SAP rather than as a client-side job, so reminders send whether or not a user is logged in. Reminder templates and statement layouts can be delivered as Crystal Reports where you need the existing document look preserved.
Supported: SAP Business One 10.0 on Microsoft SQL Server or SAP HANA, on-premise or cloud-hosted. Delivered per tenant.
Any SAP Business One site with more open A/R Invoices than the finance team can personally chase — distributors, service companies, subscription and maintenance billers, and organisations with a long tail of small-value invoices where the cost of a phone call exceeds the value of the debt.
1. Scoping call. We confirm your gateway, your reminder levels and wording, which Business Partner groups are in scope, your exclusion rules, your G/L mapping and your email or messaging sender setup. 2. Fixed quotation. A written scope and fixed price before development begins. Typical lead time is 2 to 4 weeks from acceptance. 3. Build. Developed against a copy of your configuration and tested against your gateway sandbox with real aging data from a test company. 4. Install in test. Installed into your test company database first. We run a full reminder cycle with sending redirected to your team so you see every message before a customer would. 5. Install in production. After sign-off we install into production, switch to live gateway credentials, and start with a limited Business Partner group before opening it up. 6. Support window. A support period for defect fixes and configuration changes, on the terms stated in your quotation.
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.
They work a spreadsheet of overdue invoices, phoning and emailing the same accounts repeatedly with no shared record of what was said. Automated escalation handles the routine chasing and the promised-to-pay log keeps the history on the document, so their time goes to the accounts that genuinely need a conversation.
They watch DSO climb because customers who intend to pay are slowed down by bank-transfer friction and unreferenced remittances. A per-invoice link removes the friction at the payer's end and the settlement posts back as an applied Incoming Payment, cutting both the delay and the manual matching.
Most of their week is matching bank lines to open A/R Invoices where the reference is missing or wrong. Because each link is bound to one invoice, the payment arrives already applied to the right document and the reconciliation queue shrinks to genuine exceptions.
| Criterion | ECOSIRE | Custom Build | Competitor |
|---|---|---|---|
| Per-invoice payment link bound to a single A/R Invoice | Included | Partial support | Included |
| Escalating reminder schedule driven off live aging data | Included |
From $499.00
Starting point — quoted to your scope
| Partial support |
| Reminder amount recalculated at send time for part-paid invoices | Included | Not included | Partial support |
|---|
| Settlement posted back as an applied Incoming Payment | Included | Partial support | Partial support |
|---|
| Dispute, hold and payment-plan exclusions via Business Partner UDFs | Included | Partial support | Partial support |
|---|
| Runs as a service so reminders send with no user logged in | Included | Partial support | Partial support |
|---|
| Promised-to-pay and collection notes stored against the document | Included | Partial support | Partial support |
|---|
| Dry-run cycle in a test company before any customer is contacted | 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.