How MakePay works with Bukku
Bukku’s company access token lets MakePay import invoices without a separate OAuth app registration. You confirm the business and home accounting currency, then choose a bank or cash account and payment method for optional receipt recording.
The connection targets ready credit invoices in the confirmed home currency with an exchange rate of one and a whole-unit outstanding balance. Other imported invoices stay available for review rather than being rounded or treated as a different document type.
Before you connect
- Enable API Access in the intended Bukku company’s Control Panel → Integrations and copy the access token.
- The company’s hosted bukku.my HTTPS address and home accounting currency verified directly in Bukku.
- An active, unlocked bank/cash leaf receiving account in the invoice currency and an existing non-archived payment method.
Set up Bukku with MakePay
- 01
Connect the company token
Enter the Bukku company address and token in Bookkeeping → Integrations → Bukku. The address identifies the company, while API requests use Bukku’s fixed production API host.
- 02
Confirm the accounting scope
Select Check API key and confirm your business name and home currency from Bukku. The public merchant API used here does not supply a verified company-profile or home-currency endpoint.
- 03
Enable eligible invoice checkout
Choose the receiving account and payment method, enable payment recording, then sync. Share MakePay links for ready credit invoices with supported whole-unit balances in the confirmed home currency.
- 04
Review the Bukku sales payment
A confirmed checkout creates a ready receipt with one invoice allocation, one receiving-account deposit and zero accounting fee. Bukku assigns its normal receipt number. Check the payment and exact allocation against the original invoice.
What happens when a customer pays
Import detail before offering checkout
Bukku’s invoice collection omits balances, so MakePay reads individual invoice details. Scans include active and void records and repeat to pick up edits. Large companies import across bounded batches.
Receipts use a clearing-account workflow
The receipt’s accounting fee is explicitly zero. If your later bank payout includes fees, use a clearing account and reconcile those differences in Bukku. The connector does not submit tax documents or request receipt emails.
Check these connection limits
- Fractional balances, foreign currency, cash invoices, drafts, pending approvals and void documents cannot use this checkout.
- Custom domains, private servers and staging addresses are unsupported by this hosted production connector.
- Receipt attachments, automatic invoice creation, document edits and wallet expense exports are unavailable.
Setup resources
Follow the detailed connection guide and your software’s own account requirements. Configure merchant settlement before sharing a customer invoice.
