Skip to content
PALBON-SuitesComplete ERP Solution
PALBONIbankingCore operations · Banking & payments

Pay suppliers from the books and watch the payment settle

PALBONIbanking links PALBONSphere to Indian bank accounts. Approved payables go into a payment order, the order is sent to the bank through a connector, and the status comes back to the voucher. Bank statements can be pulled in for reconciliation.

Capabilities

What is inside PALBONIbanking

Payment orders

Gather what is due into one payment order, summarised by party or by voucher, and send it for payment.

  • Orders created from payment requests, payment entries or bank journal entries
  • Summary by party or by voucher, with cost centre and project carried through
  • Suppliers, customers and employees as payees
  • Pending payments can be cancelled from the order

Bank connector

Each company bank account is tied to a connector that carries the payment to the bank and brings the reply back.

  • Connector per company bank account, in API or host-to-host mode
  • Bulk transaction support for banks that offer it
  • OTP step for banks that require one
  • Payments can be processed in the background

Mode of transfer

Say which payment rail may carry which payment, and let the order pick one for each row.

  • NEFT, RTGS, IMPS and internal account-to-account modes
  • Minimum and maximum amount for each mode
  • Start and end time and a priority for each mode
  • A mode can be tied to one bank or one bank account

Status and reconciliation

The bank's reply updates each payment row, so the order shows what has gone, what is pending and what failed.

  • Payment status: Pending, Initiated, Processed, Failed, Rejected or On Hold
  • Automatic status check every 20 minutes, every hour or at midnight
  • Payment entries created from an order built on payment requests
  • Posting date can follow the date the bank paid

Balance and statements

Check the balance before you pay, and bring bank transactions in so they can be matched to the books.

  • Bank balance fetched from a bank account's form
  • Optional check that the balance covers the order
  • Statements fetched for a date range
  • New transactions added as pending bank transactions, without duplicates

Controls and notices

Guard the account details payments depend on, and tell the payee when the money has gone.

  • IFSC code checked when a bank account is saved
  • Optional approval workflow on bank accounts
  • Payment advice emailed to the party, with a print format
  • Request log of every call to the bank connector

Outcomes

What changes for your team

From payable to paid in one place

The request, the order, the bank's response and the payment entry all sit on one trail in the books.

Payments sent in bulk

Select several purchase invoices, raise their payment requests together and pay them in one order.

Fewer surprises at the bank

Limits, bank account checks and the balance test are applied before an order goes out.

FAQ

Questions about PALBONIbanking

Which banks does it support?

That depends on the bank connector you set up. Banks are reached over API, in bulk or host-to-host, depending on the bank. Your implementation partner can confirm yours.

Does it need a separate connector service?

Yes. Payments, balances and statements are requested from a connector service that you set up and point each bank connector to, with its own key and secret.

Can we turn off automatic status checks?

Yes. Automatic updating is a setting, with a choice of 20 minutes, hourly or daily, and the status can also be fetched by hand from the order.

See PALBONIbanking on your own data

Tell us how you work today. We will walk you through the products that fit, on your data and your terms.