How MakePay works with SAP Business One
SAP Business One separates a company database, branch, G/L account and invoice installments. MakePay’s Service Layer connector preserves that accounting context and records a confirmed settlement as an Incoming Payment against the original invoice allocations.
Self-hosted and hosted installations use the same direct-credential Service Layer path. Your administrator supplies a trusted, publicly reachable HTTPS address, exact company database name and service-user credentials. OAuth-only installations need a different connection arrangement.
Before you connect
- SAP Business One 10.0 Service Layer on a trusted public HTTPS endpoint, port 443 or 50000; FP2502 or later is recommended.
- The case-sensitive company database name and a service user with the reads and incoming-payment writes your enabled workflow needs.
- An active postable monetary receiving account in local/all currencies and, when required by the company, a cash flow item.
Set up SAP Business One with MakePay
- 01
Prepare Service Layer access
Ask the SAP administrator for the service origin or /b1s/v2 address, company database and dedicated credentials. Private network endpoints and self-signed certificates are unsupported.
- 02
Confirm the SAP company
In Bookkeeping → Integrations → SAP Business One, select Check SAP company. Confirm the detected company name, database and accounting currency. Use a single canonical service address for that company.
- 03
Choose the receiving mapping
Select the active receiving or clearing G/L account and confirm Manual bank transfer as the accounting classification. Choose the required cash flow item if your company uses one. Native IDs/codes can be entered when absent from the list.
- 04
Collect and inspect allocations
Enable payment recording and share an eligible open invoice’s MakePay link. A confirmed payment becomes a native Incoming Payment with the original branch, settlement date and unpaid installment allocations.
What happens when a customer pays
Installments stay attached to the invoice
The full remaining balance is allocated to the original native unpaid installments. Multi-installment checkout needs native per-installment paid amounts exposed by FP2502 or later. Earlier versions can support a single installment when the parent balance proves the amount.
Incoming payment records the settlement
The entry does not send funds from a bank account. MakePay verifies the receipt reference, customer, receiving account, currency, dates, branch, cash flow item and every invoice/installment allocation before accepting it as recorded.
Check these connection limits
- Checkout recording currently supports local-currency invoices. Foreign-currency invoices can be imported for review.
- Ordered installments, deferred tax, withholding-tax allocations and unsupported amount precision require review.
- Invoice creation, note edits, wallet exports and receipt attachments are unavailable through this connector.
Setup resources
Follow the detailed connection guide and your software’s own account requirements. Configure merchant settlement before sharing a customer invoice.
