If you're processing more than 15 international payments per month and doing them one by one, you're creating work that doesn't need to exist. We've seen finance teams at mid-market companies spend 4 to 6 hours every payment run manually initiating individual wire transfers, downloading confirmations, emailing suppliers, and updating spreadsheets. Then doing it again two weeks later. Batch payment processing eliminates most of that. Here's exactly how it works and when it makes sense.
What Batch Payment Processing Is
Batch processing means initiating multiple cross-border payments as a single operation rather than individually. The input is a structured data file, typically a CSV, containing recipient details and payment amounts for each transaction. The platform validates all rows, applies FX rates, runs beneficiary verification, gets a single approval from the authorized approver, and executes all payments together.
The output is a single batch confirmation with a reference ID, individual transaction references for each payment, total amount sent, and a reconciliation file suitable for ERP import. Instead of 20 separate payment confirmations to match against 20 invoices, you have one batch reconciliation file that maps payment amounts to invoice references.
Simple concept. The operational impact is significant when the numbers are right.
When Batch Processing Saves Meaningful Time
The break-even point for batch processing typically sits around 8 to 10 payments per run. Below that threshold, the CSV preparation and validation time approaches the time saved versus individual payments, and the economics are marginal. Above 15 payments per run, the time saving is substantial and the error rate reduction is significant.
Here's a realistic time comparison for a finance team running 30 international supplier payments monthly, all in the same payment run:
| Task | Individual wires | Batch processing |
|---|---|---|
| Payment initiation | 3.5 hours (7 min per payment) | 45 minutes (CSV prep + review) |
| Approval workflow | 30-90 min (30 separate approvals) | 10 minutes (single batch approval) |
| Confirmation tracking | 1 hour (30 confirmations) | 10 minutes (one batch status) |
| ERP reconciliation | 2 hours (30 manual entries) | 15 minutes (single import) |
| Total per run | 7-9 hours | 1.5-2 hours |
5 to 7 hours saved per payment run. At twice monthly, that's 10 to 14 hours of finance team time recovered per month. Every month. That's not a minor efficiency gain.
The FX Rate Window: How Batch Pricing Works
One concern finance teams have about batch processing is FX rate consistency: if I'm submitting 30 payments at once, are they all processed at the same rate? The short answer is yes, with a time window.
JuniGo locks FX rates for a batch within a 30-minute window. When you submit a batch, all payments in the batch are priced at the rates active at submission time. If the batch executes within 30 minutes (which is standard for batches under 200 payments), all transactions settle at the submitted rates. If processing extends beyond 30 minutes (rare, typically for very large batches or compliance review holds), rates are re-locked at current rates for the remaining transactions with a notification to the approver.
This means your batch confirmation shows a single consistent FX rate per currency pair, not 30 different rates for 30 different execution times. Clean for reconciliation, clean for your management accounts.
Building Your Batch Payment CSV
The standard JuniGo batch CSV format requires the following columns per row:
- recipient_id: JuniGo-verified beneficiary ID (from your beneficiary list). Alternatively, include full account details in the row.
- source_currency: The currency you're paying from (SGD, USD).
- destination_currency: The currency the recipient receives (INR, MXN, PHP, etc.).
- amount: Amount in destination currency. Or source currency with a "source_amount" flag if you prefer to specify what you send rather than what they receive.
- invoice_reference: Your invoice number or internal reference. Appears in the reconciliation file and ERP posting.
- purpose_code: The regulatory purpose of payment code for the destination country (required for some corridors including India and certain Southeast Asian markets).
If your ERP generates payment export files, it's worth building a template that outputs directly to this format. Most NetSuite, QuickBooks, and Xero AP modules can be configured to export vendor payment runs in a custom CSV format. One-time setup. Ongoing automation.
Approval Workflow for Batch Payments
The dual-approval model matters more for batch payments than for individual transfers, because a single batch can represent substantial total value. JuniGo's batch payment workflow supports configurable approval thresholds: single approver for batches under USD 20,000, dual approval for batches USD 20,000 to USD 200,000, CFO-level approval for batches exceeding USD 200,000.
Set these thresholds at account setup and document them in your payment control policy. Batch processing increases efficiency but also increases the potential impact of a single control failure. The approval workflow is the primary control. Make sure it's configured deliberately, not left at default settings.
