Skip to main content

BECS and BPAY Disbursement Processing

Disbursements were previously built separately from the pay run, and employee balances relied on overnight jobs to catch up. This left room for mismatches between what was deducted, what was paid out and what employees could see.

What's new

  • A new Pay Runs / Disbursements screen builds and posts claims for a selected pay run or disbursement date.

  • Scheduled claim jobs can be limited to a specific disbursement date or pay run.

  • BECS disbursement batches are created through the same validated process, whether from the screen or the API.

  • Before a BECS batch is created, its totals are checked against the payments the operator reviewed. If they no longer match, the batch is rejected.

  • APCA numbers are validated consistently wherever they are entered, and 000000 is accepted as valid.

  • Creating or deleting a BPAY or BECS disbursement updates employee records straight away.

  • Employee transactions and pay run records update as soon as disbursements, receipts and claims are posted or un-posted, with no wait for overnight jobs.

Benefits

  • Disbursements are checked against what was reviewed before money moves.

  • Fewer mismatches between deductions, invoices and payments.

  • Employees and administrators see up-to-date balances without delay.

Who Benefits?
Business Impact
Priority
High
Status: Completed

Log in to comment and vote

No comments yet

Be the first to share your thoughts.