The product, in detail
See what happens inside each stage of the payment run.
The workflow stays connected from the first authorised bill through to Xero writeback, supplier remittances and payment-run history. Each stage below shows the controls and outcomes Batchly supports.
01 · Prepare and control
Decide what belongs in the payment run before anything reaches the bank.
Batchly starts with authorised Xero bills and gives finance teams the controls needed to shape the run without changing the underlying accounting records just to manage payment timing.
What this includes
- Sync authorised bills from Xero and work across suppliers in one run
- Search and filter bills and suppliers before making the final selection
- Use planned payment dates to help control when bills are paid
- Hold bills or exclude suppliers from the run without changing their Xero status
- Surface missing supplier bank or remittance details before export
02 · Credits and payable amount
Keep supplier credits inside the run instead of working around them.
Core supports cash-only payment runs. Plus and Scale add credit-aware workflows so eligible supplier credits can change the final cash requirement before the payment is prepared.
What this includes
- Allocate eligible supplier credit notes within the payment run
- Control credit application by supplier
- Support partial bill payments when the full bill is not being paid
- Handle credit-only and partial-cash outcomes
- Support selected FX bill payment workflows
- Confirm the final payable amount before the bank file is generated
03 · Bank file and authorisation
Prepare the banking output without replacing your approval process.
Batchly prepares the supported payment file and final cash amounts. Your team still uploads, reviews and authorises the payment through the bank process it already controls.
What this includes
- Generate a supported bank file from the final selected payment run
- Keep payment authorisation and release inside your existing bank
- Review final cash amounts before export
- Use bank-file format review and custom workflow setup on Scale when needed
Supported bank files
Australia
ABA files
New Zealand
ASB MT9 · BNZ Direct Credit AFI
United Kingdom
NatWest Bankline
US workflows are available where bank-file export is not required. Other bank formats can be reviewed separately.
04 · Complete the run
Keep Xero, suppliers and the completed payment run aligned.
Once the bank step is complete, Batchly keeps the administration around the payment connected instead of leaving the finance team to rebuild the outcome across Xero, email and spreadsheets.
What this includes
- Write cash-payment records back to Xero
- Write credit allocations back to Xero on credit-aware plans
- Send business-branded remittances automatically or later
- Send remittances from your own email domain with Custom Domain
- Track sent, opened and bounced remittance delivery
- Retain payment-run history for later review
- Export a payment-run report when a separate record is needed
Run at the right scale
Start with the run size you need. Keep the same workflow as volume grows.
Core and Plus cover standard and credit-aware payment runs, eligible Volume Boosts extend self-serve runs, and Scale supports payment runs up to 5,000 bills with a more supported rollout.
500
Core bills per run
1,000
Plus bills per run
2,000
with eligible boosts
5,000
Scale bills per run
Go deeper
Some payment-run problems deserve their own explanation.
High-volume payment runs and supplier credit notes are two of the biggest reasons finance teams find Batchly. These detailed guides keep that problem-specific depth separate from the core product story.
High-volume payment runs
Xero batch payments
See how Batchly helps finance teams keep larger Xero supplier payment runs together rather than splitting the work into small batches.
Explore batch paymentsSupplier credits
Credit note automation
See how eligible supplier credits are handled inside the payment run before the final cash amount is prepared for the bank.
Explore credit notesBuilt for payment runs that have become too manual, too fragmented or too large.
If Xero already handles your payment cycles comfortably, you may not need Batchly. If the work around the payment is becoming the problem, that is where Batchly is designed to fit.