Possible to use csv import payment reference to "key" in Purchase Invoices?

The current cloud version using invoice number as reference

Any idea if we can use the unique key instead of invoice number as reference?

Date Reference PaidFrom Cleared BankClearDate ExchangeRate ExchangeRateIsInverse Payee Customer Supplier Contact Description Lines.1.Item Lines.1.Account Lines.1.InterAccountTransferAccount Lines.1.AccountsReceivableCustomer Lines.1.AccountsReceivableSalesInvoice Lines.1.BillableExpenseCustomer Lines.1.BillableExpenseSalesInvoice Lines.1.AccountsPayableSupplier Lines.1.PurchaseInvoice Lines.1.WithholdingTaxPayableSupplier Lines.1.Employee Lines.1.CapitalAccount Lines.1.SubAccount Lines.1.SpecialAccount Lines.1.FixedAsset Lines.1.IntangibleAsset Lines.1.ExpenseClaimsPayer Lines.1.Investment Lines.1.LineDescription Lines.1.Qty Lines.1.PurchaseUnitPrice Lines.1.Amount Lines.1.CurrencyAmount Lines.1.DiscountPercentage Lines.1.DiscountAmount Lines.1.TaxCode Lines.1.Project Lines.1.Division InventoryLocation HasLineNumber HasLineDescription QuantityColumn UnitPriceColumn Discount DiscountType AmountsAreTaxExclusive FixedTotal FixedTotalAmount CustomTheme PaymentCustomTheme AutomaticReference HasPaymentCustomTitle PaymentCustomTitle ShowTaxAmountColumn HasPaymentFooters FdxTransactionId Obsolete_BankClearDate Obsolete_Status Obsolete_AmountsIncludeTax
22-Jan-26 193bf915-8417-484b-b8de-f6ecc0801e47 OnTheSameDate FALSE Supplier d109898c-d167-4ca5-8633-72a396451290 dac7ba37-0ccd-45e5-906e-548e6c50df37 d109898c-d167-4ca5-8633-72a396451290 0028 204.83 1082.4 FALSE TRUE FALSE FALSE FALSE Percentage TRUE FALSE FALSE FALSE FALSE FALSE FALSE Pending FALSE
15-Dec-25 193bf915-8417-484b-b8de-f6ecc0801e47 OnTheSameDate FALSE Supplier d109898c-d167-4ca5-8633-72a396451290 dac7ba37-0ccd-45e5-906e-548e6c50df37 d109898c-d167-4ca5-8633-72a396451290 0103 156.07 806 FALSE TRUE FALSE FALSE FALSE Percentage TRUE FALSE FALSE FALSE FALSE FALSE FALSE Pending FALSE
IssueDate DueDate DueDateDays DueDateDate Reference OrderNumber Supplier PurchaseQuote PurchaseOrder ExchangeRate ExchangeRateIsInverse Description Lines.1.Item Lines.1.Account Lines.1.BillableExpenseCustomer Lines.1.BillableExpenseSalesInvoice Lines.1.CapitalAccount Lines.1.SubAccount Lines.1.Employee Lines.1.SpecialAccount Lines.1.FixedAsset Lines.1.IntangibleAsset Lines.1.LineDescription Lines.1.Qty Lines.1.PurchaseUnitPrice Lines.1.CurrencyAmount Lines.1.DiscountPercentage Lines.1.DiscountAmount Lines.1.TaxCode Lines.1.Project Lines.1.Division HasLineNumber HasLineDescription Discount DiscountType FreightIn LandedCostLines.1.LandedCostDescription LandedCostLines.1.LandedCostAmount LandedCostLines.1.LandedCostTaxCode AmountsIncludeTax WithholdingTax WithholdingTaxType WithholdingTaxPercentage WithholdingTaxAmount HasPurchaseInvoiceCustomTheme PurchaseInvoiceCustomTheme HideBalanceDue ShowTaxAmountColumn AlsoActsAsGoodsReceipt PurchaseInventoryLocation HasPurchaseInvoiceFooters ClosedInvoice AutomaticReference Obsolete_DueDate Obsolete_Notes Obsolete_Lines.1.Item Obsolete_Lines.1.Account Obsolete_Lines.1.MemberAccount Obsolete_Lines.1.BillableExpenseCustomer Obsolete_Lines.1.BillableExpenseSalesInvoice Obsolete_Lines.1.Invoice Obsolete_Lines.1.Description Obsolete_Lines.1.Qty Obsolete_Lines.1.Amount Obsolete_Lines.1.Discount Obsolete_Lines.1.DiscountAmount Obsolete_Lines.1.Debit Obsolete_Lines.1.Credit Obsolete_Lines.1.TaxCode Obsolete_Lines.1.TrackingCode Obsolete_Lines.1.ProposedAccountAmount Obsolete_Lines.1.WithholdingTaxPayableSupplier Obsolete_Lines.1.Project Obsolete_Lines.1.Obsolete_Disbursement Obsolete_Lines.1.Obsolete_Account Obsolete_Lines.1.Obsolete_SalesInvoice Obsolete_Lines.1.Obsolete_PurchaseInvoice Obsolete_Lines.1.Obsolete_Employee Obsolete_Lines.1.Obsolete_ExpenseClaimPayer Obsolete_Lines.1.Obsolete_IntangibleAsset Obsolete_Lines.1.Obsolete_InventoryItem Obsolete_Lines.1.Obsolete_Customer Obsolete_Lines.1.Obsolete_Supplier Obsolete_Lines.1.Obsolete_FixedAsset Obsolete_Lines.1.Obsolete_Member Obsolete_Lines.1.Obsolete_Item Obsolete_Lines.1.Obsolete_PurchaseInvoiceItem Obsolete_Lines.1.Obsolete_Discount Obsolete_Lines.1.Obsolete_EquityReason Obsolete_Lines.1.Obsolete_CurrencyAmount Obsolete_Lines.1.Obsolete_DisbursementStatus Obsolete_Lines.1.Obsolete_DisbursementSalesInvoice Obsolete_Lines.1.Obsolete_DisbursementWriteOffDate Obsolete_Lines.1.Obsolete_Cheque Obsolete_Lines.1.Obsolete_BankDeposit Obsolete_Lines.1.Obsolete_BankAccount Obsolete_Lines.1.Obsolete_CashAccount Obsolete_Lines.1.Obsolete_Amount Obsolete_Lines.1.Obsolete_Invoice Obsolete_Lines.1.Obsolete_BillableExpense Obsolete_Lines.1.Obsolete_CustomerOrSupplier Obsolete_PartialPayment Obsolete_ConversionBalance Key
22-Jan-26 Net 0028 d109898c-d167-4ca5-8633-72a396451290 5.2845 TRUE 5122aaea-2522-4a6b-8cf4-b6278c501b08 1082.4 GST Not Registered FALSE FALSE FALSE Percentage FALSE TRUE FALSE Rate FALSE FALSE FALSE FALSE FALSE FALSE FALSE By Uninvoiced FALSE d36b971d-03b7-413c-b09a-a0cd26f6313b
15-Dec-25 Net 0103 d109898c-d167-4ca5-8633-72a396451290 5.1644 TRUE 5122aaea-2522-4a6b-8cf4-b6278c501b08 806 GST Not Registered FALSE FALSE FALSE Percentage FALSE TRUE FALSE Rate FALSE FALSE FALSE FALSE FALSE FALSE FALSE By Uninvoiced FALSE ce057b2b-5dc6-42b7-af32-52e0b327c990

Also any help will be appreciated, anyone can see why the system just don’t import these 2 payments?

Try using Reference numbers without the leading zeros.

Hello @stevenluk,

There’s nothing wrong with the two tables you shared. And yes, you should be able to use both Reference as well as Key in your Lines.1.PurchaseInvoice column, provided they are unique as you just pointed out.

In case your References are not unique, your import could fail.

However, you seem to have used your References inside the wrong column here:

Lines.1.Item Lines.1.BillableExpenseSalesInvoice Lines.1.AccountsPayableSupplier
dac7ba37-0ccd-45e5-906e-548e6c50df37 d109898c-d167-4ca5-8633-72a396451290 0028
dac7ba37-0ccd-45e5-906e-548e6c50df37 d109898c-d167-4ca5-8633-72a396451290 0103

Here :backhand_index_pointing_up: you used Lines.1.AccountsPayableSupplier when you should have used Lines.1.PurchaseInvoice instead.

Also, I see populated columns that make no sense, for example, you have Lines.1.Item, Lines.1.BillableExpenseSalesInvoice and Lines.1.AccountsPayableSupplier all populated for a single row, which makes no sense as far as Manager goes.

This makes me question whether your data and column names are aligned properly :thinking: