SAP Business One integration

Connect from Bookkeeping → Integrations → SAP Business One. Invoice import starts enabled. Payment recording and MakePay notifications start disabled.

Connect your SAP company

Use your current SAP Business One 10.0 Service Layer address (FP2502 or later is recommended), exact company database name, service username and password. The connection supports direct-credential login. Your SAP administrator must provide a reachable public HTTPS address with a trusted certificate, on port443 or50000. Private networks, self-signed certificates and installations requiring an OAuth-only login need a different connection arrangement.

Self-hosted and hosted SAP installations use the same Service Layer API. Enter the service origin or its /b1s/v2 address. Company database names are case-sensitive. See SAP's authentication documentation.

Select Check SAP company, inspect the detected company name, database and accounting currency, and confirm the intended business. Each connection targets that company database. Credentials are encrypted with your MakePay company and connection context. Replacing credentials for the same service address/database retains its history. Disconnect before changing company databases. An alternative server alias is a separate endpoint binding; use one canonical address for the company.

The service user needs permission to read company settings, currencies, invoices, monetary G/L accounts, cash flow items and incoming payments. Incoming-payment write permission is needed only when you enable recording. Use the SAP permissions appropriate for this connection.

Configure invoice payments

To enable Accept and record MakePay invoice payments:

• Choose an active, postable monetary receiving or clearing account in the company's local currency, or an account supporting all currencies. If absent from the list, enter its native SAP account code; MakePay verifies the account before use.
• Select Manual bank transfer and confirm the receiving account for MakePay settlements. This records an already-received payment in SAP.
• If your SAP company requires cash flow assignment, select an active cash flow item. Enter its native item ID if it is absent from the list.

MakePay rereads the invoice, account and cash flow item before checkout and first dispatch. Eligible invoices are open, uncancelled, in the company's local currency, and have a positive balance that fits MakePay's exact two-decimal checkout value. The full remaining balance is allocated across the original unpaid native installments, using the invoice's branch. Ordered installments, deferred-tax invoices and invoices with withholding-tax allocations require review instead of checkout. Values are never rounded to make them eligible.

Foreign-currency invoices are imported using their native foreign total and paid amount; checkout recording currently supports local-currency invoices. Multi-installment checkout requires the native per-installment paid amounts exposed in SAP10.0 FP2502 or later. Earlier versions can support a single installment when the invoice's parent balance verifies its remaining amount. Missing or inconsistent installment evidence prevents checkout.

After a confirmed checkout, MakePay creates an Incoming Payment against the original invoice and installments, preserving the selected account, cash flow item, branch and UTC settlement date. The receipt uses a stable MakePay reference and no payment-level VAT, bank charge, discount or other document allocation. This operation records the settlement in SAP; it does not send funds from a bank account. Independently configured SAP workflows still apply.

Sync, recovery and notifications

Full invoice scans run in batches of20 about every five minutes. A scan advances after each saved invoice and repeats to refresh balances and cancellations. Large accounts take several runs. Sync requests another batch. The panel shows the latest100 imported invoices. Changed invoice allocations or receipt settings pause unpaid links; confirmed checkouts retain their original context.

Before dispatch, MakePay saves the exact financial request. The native receipt must match its MakePay reference, customer, currency, receiving account, amount, dates, branch, cash flow item and every native invoice/installment allocation. A changed invoice balance alone is insufficient proof.

SAP's native receipt ID is saved before verification. After a timeout or uncertain response, recovery looks up the original receipt by ID or exact reference and never automatically sends a replacement. A missing, cancelled, duplicate or inconsistent receipt remains in review. Use the displayed operation reference and SAP's incoming-payment records to investigate it.

Payment-recorded and sync-problem notifications are optional, in-app and deduplicated. Disconnecting retains local history. Invoice creation, invoice-note edits, wallet exports and receipt uploads are unavailable through this connector. Local contract tests do not substitute for a live SAP company test with merchant credentials.