Bukku integration

Connect your Bukku company from Bookkeeping → Integrations → Bukku. Import existing invoices and optionally record confirmed MakePay payments with your company access token. MakePay does not need to register an OAuth app.

Connect your company

1. In your intended Bukku company, open Control Panel → Integrations, enable API Access and save to retrieve the access token. See Bukku's official API guide.
2. Select Connect, enter your company's base HTTPS address, such as https://your-company.bukku.my, and the token. The connection uses Bukku's hosted production API; custom domains, private servers and staging addresses are not accepted here.
3. Select Check API key. Confirm the business name and home accounting currency as shown in your Bukku company. The public merchant API does not provide a verified company-profile or home-currency endpoint, so MakePay requires your confirmation rather than inferring these from a name or a favourite-currency list.
4. Optionally choose an active bank/cash receiving or clearing account and an existing payment method. The account must be an unlocked leaf account in the invoice currency. Parent/group accounts, archived accounts and archived methods cannot be used.
5. Enable only the workflows you want and save. Invoice import starts enabled; payment recording and notifications start disabled.

The company address determines Bukku's Company-Subdomain tenant selector. The token and address are encrypted together. They are not sent to the company website; server requests go to Bukku's fixed API host. A different business address requires a separate connection. Public connection summaries return the business address, never the token.

Invoice payments

Enable Accept and record MakePay invoice payments to share payment links from imported open invoices. Links appear in the connection panel and main Invoices list. Checkout rereads the invoice and validates its customer, balance, currency, receiving account and payment method before issuing a payment link.

Checkout supports ready credit invoices in the confirmed home currency with an exchange rate of 1 and a positive whole-unit balance, following the published integer amount accepted by Bukku's payment-creation endpoint. Fractional-balance, foreign-currency, cash, draft, pending-approval and void invoices remain available for review without an enabled checkout. Fully paid invoices cannot accept another payment. Values use the API's stated currency without an implicit multiplier.

A verified MakePay settlement creates a ready sales-payment receipt with one invoice allocation and one receiving-account deposit. The accounting fee is explicitly zero; choose a clearing account if your eventual bank payout contains fees. Bukku assigns its normal receipt number. MakePay does not change your invoice or numbering configuration, send a receipt email, submit tax documents, or attach files through this connection.

Each checkout retains its original account and method. Changing those settings pauses older unpaid links. Disabling payment recording prevents new checkouts while completed settlements remain eligible for reconciliation with their original mapping. Sandbox/demo sessions, adjusted values, mismatched customers/currencies and multiple completed checkouts require review.

Sync and notifications

Invoice collection responses omit balances, so MakePay fetches invoice detail in bounded batches. It scans active records and then void records because Bukku's default list excludes voids. Full scans repeat to pick up edits. Sync runs in batches about every five minutes; larger companies need multiple runs. The panel shows the most recent 100 imported invoices. Use Sync to request another batch.

Recorded-payment and sync-problem notifications are optional, in-app and deduplicated. Receipt emails and other vendor notifications are not requested by MakePay. Rules you independently configure in Bukku remain subject to Bukku's own behaviour.

Recovery and token rotation

Every payment has a durable MakePay reference before a request is sent. The reference is included in the receipt description and payment reference. MakePay searches both normal and void receipts and verifies the created record, receiving deposit and the exact amount linked from the original invoice.

If a response is lost, a matching receipt can be recovered. An uncertain request without a matching receipt stays in review; MakePay does not automatically post a replacement. Duplicate references, incomplete search results, void receipts, unexpected accounting fees or missing allocation proof also require review. Check the displayed reference in Bukku before taking manual action.

Use Replace API key to rotate the token for the same business address and confirmed home currency. Reconnecting that company preserves invoice links and history. Disconnect before choosing a different company; completed checkouts must be reviewed before disconnecting.

Wallet expense exports, supporting-file uploads, automatic invoice creation and existing-document edits are not enabled through this connection. Local contract and recovery tests use fixtures. A live Bukku account round trip needs merchant credentials and is not implied by fixture results.