Batch Creat Problem

1

Screenshot 2026-06-12 133613
Screenshot 2026-06-12 1336131915Ă—992 177 KB

2

I am not able to upload Paid by, Accounts, Amounts. Please help me to solve the problem. Thanks

3

Based on your screenshot, I can see you are trying to Batch Create receipts and some fields like “Paid by”, “Accounts” and “Amounts” are not behaving as you expect. Let me suggest a safer way to approach this.

Batch tools in Manager are powerful — but, just like accounting itself, they are not forgiving when the fundamentals are missing.

When you use Batch Create for payments or receipts, you are not only entering dates and amounts. You are also telling Manager exactly how to link many parts of the system together:

  • Bank and cash accounts (PaidBy, ReceivedIn)
  • Customers and suppliers, and their invoices/credit notes
  • Line accounts, tax codes, projects, locations
  • Internal keys and GUIDs (Key, Customer, Lines.1.Account, etc.) that tie everything together in the database

A small mistake in any of these columns can create many incorrect transactions at once.

:test_tube: Safer learning path

Instead of starting with Batch Create, I strongly recommend this path:

  • Manually create 1–2 correct transactions of the type you need (payment/receipt).
  • Use Batch Update to export those same transactions to a spreadsheet.
  • Study the exported columns carefully — especially: PaidBy, Customer, Supplier, Lines.1.Account, Lines.1.Amount, TaxCode, and the Key.
  • Make a tiny change to just 1–2 rows (for example, description or amount), then paste them back using Batch Update.
  • When this round-trip is 100% clear and safe, only then think about scaling up.

From my professional experience helping businesses implement Manager, I never recommend batch-creating payments or receipts from scratch. That is where mistakes are most expensive.

:brick: Where Batch Create is safer

Use Batch Create mainly for “static” or master data:

  • Customers and suppliers
  • Inventory items
  • Fixed assets and other non-transaction records

For real money movements (bank, cash, payments, receipts), it is usually better to:

  • Enter them manually, or
  • Use bank statement import where available, or
  • Use Batch Update based on existing, correct entries.

Think of Batch Create/Update as working directly at the database layer of Manager.
Manager combines two precise disciplines: accounting logic + relational database design. The power is there for advanced users — but it assumes you already understand the structure you are touching.

If you share an anonymized Batch Update export of 1–2 transactions, the community can help point out exactly which columns and keys need to match for your specific case.

4

I’d recommend doing a Batch Update and taking one transaction that looks like the ones you want to import and copying that into an Excel file to see what it looks like. Batch actions are rather rudimentary, so don’t take too much credence on the label, if you do a Batch Update and import a null Key it won’t update the existing transactions you chose on export, it will add new ones, if you include a valid Key then it will update that matching transaction.

A word of caution, batches are hard to work with (like Abu_Hasan’s message) so starting with a good base is the best way. The Line columns (like Line.1.Account, Line.1.Project, Line.1.Division) rely on the UUID of the destination item so you need to match to those, whereas the cash account is the Account Code from the control account.