BigBooks Docs
Buying & Paying

Pay Suppliers & Recurring Payables

As an operator, you will be able to pay a supplier and set up a recurring payable that drafts itself each cycle, so that regular costs like rent and subscriptions are never missed and each posting is reviewed before it hits the GL.

What you'll accomplish

As an Operator, you will be able to pay a supplier and set up a recurring payable that drafts itself each cycle, so that regular costs like rent and subscriptions are never missed and each posting is reviewed before it hits the GL.

Before you start

Payments at /[lang]/payments settle outstanding supplier balances, while /[lang]/expenses/recurring defines payables that repeat on a schedule. Both are classic list screens (a stats strip over a filterable table, with an illustrated empty state on first run). A recurring rule drafts both a draft expense and a draft journal voucher each cycle rather than posting automatically, so the operator stays in control.

Compliance Note

Amounts are integer satang in LAK; nothing hits the GL until the operator approves the cycle's draft, keeping the audit trail clean for MoF 2020.

Steps

Pay a supplier
Open the /[lang]/payments page, select the bill(s) with an open supplier balance, choose the bank/cash account, and confirm the payment. The supplier's outstanding balance reduces by the paid amount to the satang.

Payment screen with bills selected and bank account chosen.
Payment screen with bills selected and bank account chosen.

Set up a recurring payable
Go to /[lang]/expenses/recurring and define the supplier, expense account, amount, VAT treatment, and schedule. A recurring rule is created and the system queues drafts for upcoming cycles.

Recurring payable setup with schedule and amount.
Recurring payable setup with schedule and amount.

Review drafts
Review the generated draft expense and draft journal voucher for each cycle on the review screen.

Review screen showing drafts pending approval.
Review screen showing drafts pending approval.

What happens behind the scenes

A confirmed payment settles the payable: it debits the supplier's Accounts Payable and credits the chosen Cash/Bank account, reducing the outstanding balance.

AccountDebitCredit
Accounts PayablePayment Amount-
Cash / Bank-Payment Amount

For a recurring payable, nothing posts until the operator approves the cycle's draft. On approval the draft expense's journal posts:

AccountDebitCredit
Expense AccountNet Amount-
Input VATVAT Amount-
Accounts Payable-Gross Amount

Common problems

  • Overpayment: Paying more than the outstanding balance is blocked or flagged as overpayment.
  • Payment failure: Insufficient or unselected bank/cash account blocks the payment.
  • Draft confusion: A pending draft awaiting approval is clearly distinguished from posted entries.
  • Recurring history: Editing a recurring rule does not retroactively change already-posted cycles.
  • Closed Period: A draft generated into a closed period cannot be approved until reopened.
  • Permissions: Operator lacking payment or approval permission sees a restricted state.

On this page