What Are Accounting Batches?
Batches are periodic transfers of approved expenses to accounting systems. They work with NetSuite, Severa, Workday, Procountor, Fortnox, and spreadsheet integrations (SFTP/email exports).
Batches are sent automatically according to your configured schedule, or an accountant can manually trigger one by clicking "Send to accounting" from the main menu.
Automatic vs Manual Batching
Automatic batching runs on a set schedule (daily, weekly or last day of the month), collecting all approved expenses at the scheduled time.
Manual batching lets accountants trigger batches outside the normal schedule by clicking "Send to accounting" for more control or urgent expenses.
Batch Schedule (Helsinki timezone)
Integration | Start Time | Approx End | Notes |
NetSuite | 00:10 | 00:40 | Some companies 10+ min |
Airplus | 02:00 | 02:50 | Includes file fetching |
Severa | 02:30 | 02:50 | Most finish in ~10min |
Danske MasterCard | 05:00 | 05:05 | Usually <5min |
Workday | 05:00 | 05:05 | Usually <5min |
Procountor | 06:00 | 06:05 | Usually <5min |
Netvisor | 06:20 | 06:25 | Usually <5min |
Mepco | 06:40 | 06:47 |
|
Projects from D365 | 06:50 | 06:55 | Usually <5min |
Cost Centers from D365 | 07:00 | 07:05 | Usually <5min |
Cost Centers via SFTP | 07:30 | 07:35 | Runs Mon-Sun |
Nordea FirstCard | 08:00 | 08:05 | Usually <5min |
Fortnox | 10:00 | 10:05 | Usually <5min |
Expense Selection for Batching
Expenses must be fully approved, not previously sent, and valid (has required fields: account, VAT code, cost center if mandatory).
Excluded from batches: expenses missing required IBAN, expenses with validation errors, already-paid reimbursable expenses.
Transaction Limits
Netvisor and Procountor have a 30-transaction limit per batch for both personal and company expenses. If accounting queue is bigger than that, the queue is split into smaller batches (i.e. max 30 transaction/batch) that are sent directly after each other.
Understanding Batch Failures
When a batch fails, Bezala emails your company's support contact with error details and resolution instructions. Failed expenses remain in the queue marked as "failed," allowing you to edit and retry them.
Common Errors and Solutions:
Authentication/Connection Issues - The Bezala-accounting integration connection has expired. Solution: Re-establish the connection in “Company settings” ==> “Basic settings”-tab ==> “Reimbursement & Accounting”-tab ==> Check/Change credentials in the accounting authentication box.
Missing IBAN - Personal expenses require the employee's IBAN for reimbursement. Non-Finnish IBANs also need a BIC code. Solution: Employee adds IBAN (and BIC if needed) in their profile settings.
Invalid Account Number - An expense account in the batch doesn't exist in the accounting software. Solution: Update the account in Bezala or ensure it matches the chart of accounts.
Deactivated Account - An account deactivated in the accounting software was used. Solution: Select a different active account and deactivate the old one in Bezala.
VAT Code Mismatch - The VAT percentage doesn't match allowed values for the selected VAT code. Solution: Verify the VAT percentage matches what the account allows.
Cost Center Mismatch - Cost centers in Bezala don't match exactly with the accounting software. Solution: Ensure cost center names match precisely between systems.
Unprocessed Attachments - Receipt images haven't finished processing. Solution: Wait for processing to complete or re-upload the receipt.
How to Retry a Failed Batch
After fixing the issue: Go to "Scheduled to be sent to your bookkeeper", edit the failed expense to correct the problem, then wait for the next scheduled batch or click "Send to accounting."
Duplicate Prevention
Bezala automatically prevents duplicates. Once successfully sent, an expense is marked "Accounted" and won't send again. The system checks receipt IDs to prevent duplicate processing.
Payment Generation
Creates payments: Netvisor, SEPA, Wise
Creates purchase invoices: Procountor, Fortnox, EmCe
Still Having Issues?
Contact [email protected] with the error message if you cannot resolve it.