Mandate management, collection runs and bank-ready SEPA, ACH and local payment files inside SAP Business One, with return handling. Built to order against your bank's published specification. Built to order by ECOSIRE for SAP Business One (build-to-order) — indicative price from $599.00 USD; request a quote for a scoped proposal.
Mandate management, collection runs and bank-ready SEPA, ACH and local payment files inside SAP Business One, with return handling. Built to order against your bank's published specification.
Built to order
Recurring collections and bulk payments are where a well-run SAP Business One installation quietly falls back on spreadsheets. The invoices are correct, the sub-ledger is clean, and then someone exports a list, retypes it into a bank portal, saves a file the bank rejects for a header field, and spends the afternoon reconciling what actually went out. When a collection fails, the return notice arrives days later as a PDF, and the reversal, the bank charge and the customer follow-up are all manual.
Mandates make it worse. A direct debit mandate is a legal instrument with a reference, a signature date, a scheme, a sequence position and an amendment history — and in most installations it exists as a scanned document in a folder, with no link to the Business Partner and nothing preventing a collection being taken against a mandate that was cancelled last quarter.
Direct Debit and ACH Payment Files is a SAP Business One add-on that ECOSIRE builds to order. It holds mandates as first-class records, builds collection and payment runs from your open sub-ledger, produces bank files in the exact format your bank publishes, and imports the resulting status and return files so the ledger reflects what the bank actually did.
Mandates are implemented as a User-Defined Object over User-Defined Tables: unique mandate reference, signature date, scheme, status, first-use date, cancellation date and a full amendment history, each linked to the Business Partner and to a specific Business Partner bank account. User-Defined Fields on the Business Partner surface the active mandate on the master record. Sequence type is tracked and advanced automatically as collections succeed, so a first collection is presented as first and subsequent ones as recurring, with a final presentation flagged when a mandate is being closed.
Collections cannot be raised against a mandate that is cancelled, expired under your rules, or missing a validated bank account. That check happens server-side, not in a warning dialog someone can dismiss.
A run selects open A/R Invoices by due date, Business Partner group, payment terms and payment method, and presents the proposal for review before anything is posted or exported. You can exclude a line, split a collection, apply a pre-notification lead time, or hold a customer pending a query. On submission the add-on posts the Incoming Payments against the selected invoices, so the sub-ledger reflects the run without a second data-entry pass, and the run is locked against regeneration once the file is marked as submitted to the bank.
The add-on generates ISO 20022 pain.008 direct debit instructions and pain.001 credit transfers at the message version and profile your bank specifies, and NACHA-format ACH files with correct company and batch header records, entry detail records, batch and file control records and hash totals. Local formats your bank publishes are built to the same standard where they are named in your scope.
This matters more than it sounds: two banks on the same standard will differ on optional fields, character sets, file naming and batching rules. We build against the specification document your bank issues and we run a test file through their acceptance process as part of delivery, rather than shipping a generic template and leaving you to argue with a rejection notice.
The same engine runs the payables side: select open A/P Invoices by due date, vendor group or currency, review the proposal, post the Outgoing Payments and produce the credit transfer file. Remittance advice is generated per vendor from a Crystal Reports layout and emailed from the run, so suppliers can apply the payment without calling your accounts payable team.
Status reports and return files are imported and matched back to the originating payment: pain.002 status reports, camt.054 debit and credit notifications, and ACH return files with their return reason codes. A rejected collection triggers the workflow you define — reverse or flag the Incoming Payment, post the bank charge to the account you nominate, change the mandate status or block it after a number of consecutive failures, and raise an Activity for the collections owner with the reason code attached.
Payment runs route through SAP Business One approval procedures, with dual authorisation where you require it. Every generated file is recorded with its hash, its creation user, its submission timestamp and its contents, and a submitted run cannot be regenerated without an explicit, logged override. The audit table is queryable and included in the reporting pack.
The add-on targets SAP Business One 10.0 on Microsoft SQL Server and on SAP HANA, on-premise or cloud-hosted. Payments are posted through the Service Layer (REST), with the DI API used where the payment object requires it. Mandates, run headers and the file audit trail are User-Defined Tables and User-Defined Objects; master data extensions are User-Defined Fields on Business Partners and their bank accounts. Multi-currency and multiple company databases are supported where they are in scope. Crystal Reports layouts cover the mandate register, the collection run summary, failed-collection ageing and remittance advice.
Subscription, service and rental businesses collecting from a recurring customer base; wholesalers collecting on account; and any SAP Business One site paying suppliers in bulk where the current process is a manual portal upload. It is worth most where collection volume makes manual reconciliation of returns impractical.
Nothing here is pre-built or downloadable. Each deployment is built for one customer's bank relationships and company database.
1. Scoping call. We collect your bank's format specification documents, your schemes, your currencies, your posting accounts for charges and reversals, and your existing mandate records. 2. Fixed quote. A written scope naming each file format in and out of scope, with a fixed price, issued before any code is written. 3. Build. Typical lead time is two to four weeks from acceptance of the quote, depending on how many formats and banks are in scope. 4. Install in test. Installation into your test company database, migration of existing mandates, and a test file cycle submitted to your bank for acceptance before go-live. 5. Install in production. After your sign-off and the bank's acceptance of a test file, we install into production and run the first live collection alongside your team. 6. Support window. A defect-fix and support period runs from the production install date, with the duration stated in your quote.
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.
Runs collections from a spreadsheet and finds out about failures days later, by which time the customer has been invoiced again. A mandate-validated run with automatic import of return files means failures reverse themselves, post the bank charge and land on a follow-up list the same day.
Pays suppliers by typing batches into a bank portal and then emailing remittances by hand. Selecting open A/P Invoices, posting the Outgoing Payments and producing both the bank file and the per-vendor remittance from one run removes the retyping and the reconciliation that follows it.
Carries the risk of a payment file being altered, duplicated or regenerated after submission, and cannot evidence who authorised what. Dual authorisation through approval procedures, a submission lock and a hash-logged file audit trail make the control demonstrable to an auditor.
| Criterion | ECOSIRE | Custom Build | Competitor |
|---|---|---|---|
| Mandate register with unique reference, scheme, status and amendment history linked to the Business Partner | Included | Included | Partial support |
| Automatic first, recurring and final sequence handling per mandate | Included |
From $599.00
Starting point — quoted to your scope
| Partial support |
| Bank file built against your bank's own specification and accepted in a test cycle before go-live | Included | Partial support | Not included |
|---|
| Import and matching of pain.002, camt.054 and ACH return files to the originating payment | Included | Partial support | Partial support |
|---|
| Failed-collection workflow: reversal, bank charge posting, mandate block and follow-up Activity | Included | Partial support | Not included |
|---|
| Dual authorisation through approval procedures with a submission lock and hash-logged file audit | Included | Partial support | Not included |
|---|
| Bulk vendor payment run with Outgoing Payments and per-vendor remittance advice | Included | Included | Partial support |
|---|
| Configured to your company databases, currencies and posting accounts rather than a fixed schema | Included | Included | Not included |
|---|
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.