Contact Code Improvements
Batch imports just got easier.
Following our recent Introducing Contact Code release in Release Notes v2.51.0, we heard your feedback about Contact Code making imports harder — whether you're importing contacts or transactions, having to look up or manage a code for every row added unnecessary friction. Good news: both flows are now much smoother.
Transaction Import Updates
Contact Code is now optional
When batch importing transactions, the system can now identify the customer, supplier, or employee using either:
Contact Code — if filled in and it matches an existing code, the system will use it directly.
Legal Name — if Contact Code is left blank, or doesn't match anything, the system will match using the Legal Name instead.
This applies across all transaction imports, including Sales, Purchases, and Bank modules.
Clearer matching on the review page
Matched rows show both Contact Code and Legal Name together.
If the same Legal Name matches more than one contact in the system, the row is flagged so you can pick the right one — instead of the system guessing.
If a row doesn't match any contact, you can create a new contact on the fly, or manually select one right from the review page — nothing gets stuck or skipped.
See it in action
Here's a quick walkthrough — from the contact list, to the import file, to the matched result in the batch table:
Contact list — existing contact records, each with its own Contact Code and Legal Name
Import template — Contact Code and/or Legal Name filled in for each transaction row
Batch table — how each row gets matched after upload, including:
Rows where the Legal Name matches more than one contact — flagged so you can pick the right one
Rows with no match — you can create a new contact on the fly, right from the table
Contact Import Updates
Matched by Contact Code, not by Legal Name
You can now import contacts that share the same name — Legal Name no longer needs to be unique.
Each row is matched to an existing contact using its Contact Code. If the code exists, that contact is updated; if not, a new contact is created.
Importing a new contact? Enter
[AUTO]in the Contact Code column and the system will generate one for you.To change an existing contact's code, use the separate Update Contact Code column.
What You Need to Know
You don't need to fill in Contact Code for every row of a transaction import anymore — typing the contact's Legal Name works fine.
If you fill in both Contact Code and Legal Name on a transaction import, Contact Code takes priority.
If a legal name matches more than one contact, the system will flag it for you to confirm — rather than picking one automatically.
When importing your contact list, matching is done by Contact Code, not name — so duplicate names are no longer a problem.
Frequently Asked Questions (FAQ)
Do I need to fill in Contact Code for every row when importing transactions?
No. Just typing the contact's Legal Name works fine — Contact Code is optional, and if left blank, system will match the row using the Legal Name instead.
What if the name I enter matches more than one contact on a transaction import?
If the same Legal Name exists on more than one contact record, the system will flag the row and show a message like "
Name- Multiple contacts with this name — click to pick between them." Just click the row to select the correct one.
If a transaction import has a new customer or supplier that doesn't exist yet, can I create it on the fly?
Yes — if a row doesn't match any existing contact, you can create the new contact directly from the batch table before saving, without leaving the import flow.
What if I fill in both Contact Code and Legal Name on a transaction import?
No worries — Contact Code takes priority. Once the system finds a match using Contact Code, it will use that contact directly — the Legal Name column is simply ignored for that row.
I'm importing a new contact — do I need to make up a Contact Code myself?
No, just type[AUTO]in the Contact Code column and system will generate one for you.
This update was shaped by your feedback — thank you for helping us make Bukku better. If you run into any issues, don't hesitate to reach out to our support team. 😊